From opsawg-bounces@ietf.org Fri Jun 15 06:04:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz8fD-00084C-Lj; Fri, 15 Jun 2007 06:04:19 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyMgb-0004k4-Fh; Wed, 13 Jun 2007 02:50:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyMga-00017P-5K; Wed, 13 Jun 2007 02:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 16C5D175C6; Wed, 13 Jun 2007 06:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HyMg5-0005eb-Rf; Wed, 13 Jun 2007 02:50:01 -0400 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: ietf-announce@ietf.org From: IESG Secretary Message-Id: Date: Wed, 13 Jun 2007 02:50:01 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b X-Mailman-Approved-At: Fri, 15 Jun 2007 06:04:18 -0400 Cc: opsawg@ietf.org Subject: [OPSAWG] WG Action: Operations and Management Area Working Group (opsawg) X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org A new IETF working group has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. +++ Operations and Management Area Working Group (opsawg) ====================================================== Current Status: Active Working Group Chair(s): Scott Bradner Operations and Management Area Directors: Dan Romascanu Ronald Bonica General Discussion: opsawg@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/opsawg Archive: http://www1.ietf.org/mail-archive/web/opsawg/current/index.html Description: The Operations and Management Area receives occasional proposals for the development and publication of RFCs dealing with operational and management topics that are not in scope of an existing working group and do not justify the formation of a new working group. The OPSAWG will serve as the forum for developing such work items in the IETF. The OPSAWG mailing list is an open discussion forum for such work items, when they arise. The working group meets if there are active proposals that require discussion. The working group milestones are updated as needed to reflect the current work items and their associated milestones. All new work items and rechartering proposals will be brought for approval with the IESG. The focus of the work will be on topics that govern the behavior or WGs in the O&M area (e.g., manageability requirements) and on small, highly focused projects that don't merit a WG of their own or belong to WGs that have already concluded (e.g. advancement of documents on the standards track, application statements, extensions of MIB modules). The OPSAWG will undertake only work items that are proved to have at least a reasonable level of interest from the operators and users community and have a committed number of editors and reviewers. It is not within the scope of the OPSAWG to pick up failed WG work or parts of a WG charter items that could not come to convergence on what they were chartered to do. The currently active OPSAWG work items mostly fall under the following topics: (A) Development of a BCP document that will provide guidelines for authors and a reference for reviewers of IETF documents that specify new protocols or protocol extensions about the information about operational and manageability requirements that needs to be covered in these documents (B) Templates and tools for Operations and Management Area Documents (C) Maintenance and small scale extensions of documents that were developed in working groups that have concluded (e.g. MIB modules). Goals and Milestones: June 2007 - Initial submission for the "Guidelines for Considering Operations and Management of New Protocols" Internet-Draft June 2007 - Initial submission for the "SNMP Engine ID Discovery" Internet-Draft October 2007 - Initial submission for the "Template for Generic Management Data Models" Internet-Draft October 2007 - Initial submission for the "Structured Data Elements (SDEs) for syslog" Internet-Draft October 2007 - WGLC for the "SNMP Engine ID Discovery" Internet-Draft December 2007 - WGLC for the "Guidelines for Considering Operations and Management of New Protocols" Internet-Draft December 2007 - Submit the "SNMP Engine ID Discovery" Internet-Draft to the IESG for consideration as Proposed Standard February 2008 - Submit the "Guidelines for Considering Operations and Management of New Protocols" Internet-Draft to the IESG for consideration as BCP April 2008 - WGLC for the "Template for Generic Management Data Models" April 2008 - WGLC for the "Structured Data Elements (SDEs) for syslog" June 2008 - Submit the "Template for Generic Management Data Models" to the IESG for consideration as BCP June 2008 - Submit the "Structured Data Elements (SDEs) for syslog" to the IESG for consideration as Proposed Standard _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Mon Jun 18 14:46:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0MFE-0005Ip-44; Mon, 18 Jun 2007 14:46:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0MFC-0005GX-54; Mon, 18 Jun 2007 14:46:30 -0400 Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0MFA-00064J-UZ; Mon, 18 Jun 2007 14:46:30 -0400 Received: from 16.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-outbound.avaya.com with ESMTP; 18 Jun 2007 14:46:27 -0400 X-IronPort-AV: i="4.16,435,1175486400"; d="scan'208"; a="28702339:sNHT7851684" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Jun 2007 20:46:26 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Submission cut-off dates before Chicago Thread-Index: Acex2PmEtxbDklB8TrC3YaXjv/x7Yw== From: "Romascanu, Dan (Dan)" To: , , "Netconf (E-mail)" , , , , , X-Spam-Score: 0.1 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: Subject: [OPSAWG] Submission cut-off dates before Chicago X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org Working Group and BOF Chairs and Contributors, Please note the submission dates for Internet-Drafts before Chicago.=20 July 2, Monday - Internet Draft Cut-off for initial document (-00) submission by 09:00 ET (13:00 UTC/GMT) July 9, Monday - Internet Draft final submission cut-off by 09:00 ET (13:00 UTC/GMT) Dan =20 _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Tue Jun 19 15:44:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jcc-0004kq-9K; Tue, 19 Jun 2007 15:44:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jca-0004kU-4b; Tue, 19 Jun 2007 15:44:12 -0400 Received: from borg.juniper.net ([207.17.137.119] helo=smtpb.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0jcY-0005ds-Tf; Tue, 19 Jun 2007 15:44:12 -0400 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by smtpb.juniper.net with ESMTP; 19 Jun 2007 12:44:10 -0700 Received: from [172.23.1.54] ([172.23.1.54] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 15:44:09 -0400 Message-ID: <46783204.5020806@juniper.net> Date: Tue, 19 Jun 2007 15:44:04 -0400 From: Ron Bonica User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: opsawg@ietf.org, ops-area@ietf.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Jun 2007 19:44:09.0450 (UTC) FILETIME=[344574A0:01C7B2AA] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Cc: Subject: [OPSAWG] WG chairs X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org Folks, Dan and I are happy to announces that Scott Bradner and Ted Seely will be serving as chairs of the OPS AREA WG. Best wishes to both of them. Ron _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Thu Jun 21 17:15:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1U0U-0003h5-TZ; Thu, 21 Jun 2007 17:15:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1U0T-0003h0-Vc for opsawg@ietf.org; Thu, 21 Jun 2007 17:15:57 -0400 Received: from kremlin.juniper.net ([207.17.137.120] helo=smtpa.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1U0S-00084k-Nb for opsawg@ietf.org; Thu, 21 Jun 2007 17:15:57 -0400 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by smtpa.juniper.net with ESMTP; 21 Jun 2007 14:15:56 -0700 X-IronPort-AV: i="4.16,448,1175497200"; d="scan'208"; a="22965150:sNHT33646476" Received: from [172.23.1.54] ([172.23.1.54] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 17:15:54 -0400 Message-ID: <467AEA86.5050100@juniper.net> Date: Thu, 21 Jun 2007 17:15:50 -0400 From: Ron Bonica User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: opsawg@ietf.org, dharrington@huawei.com X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Jun 2007 21:15:55.0072 (UTC) FILETIME=[5AB43400:01C7B449] X-Spam-Score: 1.1 (+) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: Subject: [OPSAWG] draft-harrington-operations-and-management X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org Folks, The following are a few comments on draft-harrington-operations-and-management. As this is a version-00 draft, the comments are somewhat general. - This document seems to be just as concerned with the protocol designer's "mind-set" and the protocol development process as it is with the protocol as a finished product. While we all agree that it would be a good thing to imprint operational sensitivities into the consciousness of the protocol developer, I do not think that this is a practical goal. The best that we can do is to set forth a list of objective criteria by which a protocol designer can evaluate whether the protocol that he/she has developed is manageable. - Objective criteria might take the form of a checklist. Questions would be of the following nature: . are configuration parameters clearly identified? . are configuration parameters normalized? . does each configuration parameter have a reasonable default value? . is protocol state information exposed to the user? How? . is protocol performance information exposed to the user? How? . are significant state transitions logged? . etc etc etc - Finally, the document may attempt to cover too much ground. Maybe it will develop into a framework document, supported by documents of the following sort: . what makes a MIB usable? . how much protocol state information needs to be exposed and how? . how much performance information needs to be exposed and how? Ron /speaking as individual contributor _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Sun Jun 24 12:04:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2UZX-0007H3-D2; Sun, 24 Jun 2007 12:04:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2UZW-0007Gy-Ea for opsawg@ietf.org; Sun, 24 Jun 2007 12:04:18 -0400 Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2UZT-0008CA-Vp for opsawg@ietf.org; Sun, 24 Jun 2007 12:04:18 -0400 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by de307622-de-outbound.net.avaya.com with ESMTP; 24 Jun 2007 12:04:15 -0400 X-IronPort-AV: i="4.16,456,1175486400"; d="scan'208"; a="30408549:sNHT8459880" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [OPSAWG] draft-harrington-operations-and-management Date: Sun, 24 Jun 2007 18:03:34 +0200 Message-ID: In-Reply-To: <467AEA86.5050100@juniper.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPSAWG] draft-harrington-operations-and-management Thread-Index: Ace0SXmZUf1byarDSY+OI5Q348wPWgCLwItQ References: <467AEA86.5050100@juniper.net> From: "Romascanu, Dan (Dan)" To: "Ron Bonica" , , X-Spam-Score: 1.2 (+) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org See in-line.=20 Dan (speaking as a contributor) =20 =20 > -----Original Message----- > From: Ron Bonica [mailto:rbonica@juniper.net]=20 > Sent: Friday, June 22, 2007 12:16 AM > To: opsawg@ietf.org; dharrington@huawei.com > Subject: [OPSAWG] draft-harrington-operations-and-management >=20 > Folks, >=20 > The following are a few comments on > draft-harrington-operations-and-management. As this is a=20 > version-00 draft, the comments are somewhat general. >=20 > - This document seems to be just as concerned with the=20 > protocol designer's "mind-set" and the protocol development=20 > process as it is with the protocol as a finished product.=20 > While we all agree that it would be a good thing to imprint=20 > operational sensitivities into the consciousness of the=20 > protocol developer, I do not think that this is a practical goal. > The best that we can do is to set forth a list of objective=20 > criteria by which a protocol designer can evaluate whether=20 > the protocol that he/she has developed is manageable. Agreed, but this is also about documenting the minimal information about manageability that a protocol document published by the IETF should contain.=20 >=20 > - Objective criteria might take the form of a checklist.=20 Yes. This checklist would have two categories of users. Writers of protocol documents and reviewers of protocol documents. Both categories of contributors will have a common set of criteria for the information to be included and looked in a protocol document.=20 > Questions would be of the following nature: >=20 > . are configuration parameters clearly identified? > . are configuration parameters normalized? What do you mean by normalized? > . does each configuration parameter have a reasonable default value? > . is protocol state information exposed to the user? How? > . is protocol performance information exposed to the user? How? > . are significant state transitions logged? > . etc etc etc >=20 > - Finally, the document may attempt to cover too much ground.=20 Do you have specific proposals about sections or items that should be taken out?=20 > Maybe it will develop into a framework document, supported by=20 > documents of the following sort: >=20 > . what makes a MIB usable? > . how much protocol state information needs to be exposed and how? > . how much performance information needs to be exposed and how? >=20 > Ron > /speaking as individual contributor >=20 _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Mon Jun 25 10:24:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2pU6-0008Aa-Tg; Mon, 25 Jun 2007 10:24:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2pU5-00087e-HP for opsawg@ietf.org; Mon, 25 Jun 2007 10:24:05 -0400 Received: from borg.juniper.net ([207.17.137.119] helo=smtpb.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2pTt-0000Rs-O4 for opsawg@ietf.org; Mon, 25 Jun 2007 10:24:04 -0400 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by smtpb.juniper.net with ESMTP; 25 Jun 2007 07:23:52 -0700 Received: from [172.25.51.54] ([172.25.51.54] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jun 2007 10:23:51 -0400 Message-ID: <467FCFF4.2000408@juniper.net> Date: Mon, 25 Jun 2007 10:23:48 -0400 From: Ron Bonica User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" Subject: Re: [OPSAWG] draft-harrington-operations-and-management References: <467AEA86.5050100@juniper.net> In-Reply-To: X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Jun 2007 14:23:51.0300 (UTC) FILETIME=[73D6FC40:01C7B734] X-Spam-Score: 1.1 (+) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 Cc: opsawg@ietf.org, dharrington@huawei.com X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org Romascanu, Dan (Dan) wrote: > See in-line. > > Dan > (speaking as a contributor) > > > > > > >>-----Original Message----- >>From: Ron Bonica [mailto:rbonica@juniper.net] >>Sent: Friday, June 22, 2007 12:16 AM >>To: opsawg@ietf.org; dharrington@huawei.com >>Subject: [OPSAWG] draft-harrington-operations-and-management >> >>Folks, >> >>The following are a few comments on >>draft-harrington-operations-and-management. As this is a >>version-00 draft, the comments are somewhat general. >> >>- This document seems to be just as concerned with the >>protocol designer's "mind-set" and the protocol development >>process as it is with the protocol as a finished product. >>While we all agree that it would be a good thing to imprint >>operational sensitivities into the consciousness of the >>protocol developer, I do not think that this is a practical goal. >>The best that we can do is to set forth a list of objective >>criteria by which a protocol designer can evaluate whether >>the protocol that he/she has developed is manageable. > > > Agreed, but this is also about documenting the minimal information about > manageability that a protocol document published by the IETF should > contain. > > >>- Objective criteria might take the form of a checklist. > > > Yes. This checklist would have two categories of users. Writers of > protocol documents and reviewers of protocol documents. Both categories > of contributors will have a common set of criteria for the information > to be included and looked in a protocol document. > > >>Questions would be of the following nature: >> >>. are configuration parameters clearly identified? >>. are configuration parameters normalized? > > > What do you mean by normalized? I borrowed the term from database technology. For details see http://en.wikipedia.org/wiki/Database_normalization . > > >>. does each configuration parameter have a reasonable default value? >>. is protocol state information exposed to the user? How? >>. is protocol performance information exposed to the user? How? >>. are significant state transitions logged? >>. etc etc etc >> >>- Finally, the document may attempt to cover too much ground. > > > Do you have specific proposals about sections or items that should be > taken out? Not so much taken out as split into separate documents. For example, we might be able to write a document on syslog requirements for a new protocol. That document might talk about logging levels, what should be logged, what should not, and how to deal with log chattiness. The base document might provide a pretty good framework for all of those more specific documents. Ron > > >>Maybe it will develop into a framework document, supported by >>documents of the following sort: >> >>. what makes a MIB usable? >>. how much protocol state information needs to be exposed and how? >>. how much performance information needs to be exposed and how? >> >> Ron >> /speaking as individual contributor >> > > _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg From opsawg-bounces@ietf.org Tue Jun 26 15:25:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Gep-0008FK-9E; Tue, 26 Jun 2007 15:24:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Geo-0008En-27 for opsawg@ietf.org; Tue, 26 Jun 2007 15:24:58 -0400 Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3GeA-0002Vc-K0 for opsawg@ietf.org; Tue, 26 Jun 2007 15:24:58 -0400 Received: by newdev.harvard.edu (Postfix, from userid 501) id 30D6B3EA042; Tue, 26 Jun 2007 15:24:17 -0400 (EDT) To: opsawg@ietf.org Message-Id: <20070626192417.30D6B3EA042@newdev.harvard.edu> Date: Tue, 26 Jun 2007 15:24:17 -0400 (EDT) From: sob@harvard.edu (Scott O. Bradner) X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [OPSAWG] meeting in Chicago X-BeenThere: opsawg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: OPSA Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: opsawg-bounces@ietf.org the opsawg is scheduled to meet Tuesday afternoon at 15:20 - we have a 2 hour slot we are working on the agenda - if you have topics you would like to discuss please let us know - Scott & Ted _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www1.ietf.org/mailman/listinfo/opsawg