From hubmib-admin@ietf.org Wed Oct 10 14:08:13 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17216 for ; Wed, 10 Oct 2001 14:08:08 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA26193; Wed, 10 Oct 2001 14:06:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA26165 for ; Wed, 10 Oct 2001 14:06:22 -0400 (EDT) Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17144 for ; Wed, 10 Oct 2001 14:06:20 -0400 (EDT) Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26080 for ; Wed, 10 Oct 2001 14:05:08 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26058 for ; Wed, 10 Oct 2001 14:05:07 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C151B5.FB64E4DE" Date: Wed, 10 Oct 2001 20:04:19 +0200 Message-ID: Thread-Topic: Ethernet MIBs (hubmib and atommib) meetings in Salt Lake City Thread-Index: AcFRtintr6uE+ZhETU64VrGk6ckWSA== From: "Romascanu, Dan (Dan)" To: , Subject: [Hubmib] Ethernet MIBs (hubmib and atommib) meetings in Salt Lake City Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C151B5.FB64E4DE Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I suggest that for the December IETF we plan for a similar meeting structure as we did in London: * one two hours slot for hubmib for all issues excepting WIS MIB * one joint one hour session of hubmib and atommib for WIS MIB Please let me know if there are any objections, and also let me know what are the conflicts to be avoided. I personally would like to avoid meeting on Friday morning. Regards, Dan ------_=_NextPart_001_01C151B5.FB64E4DE Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Ethernet MIBs (hubmib and atommib) meetings in Salt Lake = City

I suggest that for the = December IETF we plan for a similar meeting structure as we did in = London:

  • one two hours slot for = hubmib for all issues excepting WIS MIB
  • one joint one hour = session of hubmib and atommib for WIS MIB

Please let me know if there = are any objections, and also let me know what are the conflicts to be = avoided. I personally would like to avoid meeting on Friday = morning.

Regards,

Dan

------_=_NextPart_001_01C151B5.FB64E4DE-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sat Oct 13 05:03:46 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02148 for ; Sat, 13 Oct 2001 05:03:46 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02928; Sat, 13 Oct 2001 05:03:19 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02898 for ; Sat, 13 Oct 2001 05:03:17 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02145 for ; Sat, 13 Oct 2001 05:03:13 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9D92JO21987 for ; Sat, 13 Oct 2001 05:02:19 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9D92Ie21975 for ; Sat, 13 Oct 2001 05:02:18 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 13 Oct 2001 11:03:09 +0200 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Thread-Topic: WIS design team deadline extension Thread-Index: AcFTXtNv+7DPy3cWRiWPJkTWsXkyywAZdlPg From: "Romascanu, Dan (Dan)" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA02900 Subject: [Hubmib] FW: WIS design team deadline extension Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit For the intention of the WG members - The WIS MIB Design team was awarded an extension of the deadline for submission of the conclusions of their work. The Internet-Draft that includes the results of their work will be made available on 10/19, end of business day for the hubmib and atommib WG members to review and comments (this is instead of the original 10/15 submission date). The decision was taken together with the chairs of atommib, and the reason is that we want to allow all design team members to review and agree to the latest version of their draft before it is made available for the WGs. Regards, Dan -----Original Message----- From: C. M. Heard [mailto:heard@pobox.com] Sent: Friday, October 12, 2001 10:45 PM To: Romascanu, Dan (Dan); Nathan Kohn; Faye Ly Subject: WIS design team deadline extension On Fri, 12 Oct 2001, Romascanu, Dan (Dan) wrote: > I would agree with Mike H. It would be nice that all members of the > Design Team have the opportunity to comment. I have no problem to have > the deadline extended to 10/19, so that Mike A., and maybe other Design > Team members have time to provide their input, and changes be made if > needed. > > By 10/19, you may want to make the text of the I-D available at some Web > location, so that the hubmib and atommib WG members can start looking at > it, in parallel with the official submission to the Internet-Drafts > repositories (which always takes a few days). Dan, May I suggest that you and/or other WG chairs forward this to information the hubmib and atommib mailing lists so that WG members will be aware of the delay? Thanks and regards, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Oct 15 18:03:00 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13839 for ; Mon, 15 Oct 2001 18:03:00 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA08723; Mon, 15 Oct 2001 18:01:52 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA06385 for ; Sun, 14 Oct 2001 03:54:26 -0400 (EDT) Received: from web20109.mail.yahoo.com (web20109.mail.yahoo.com [216.136.226.46]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27541 for ; Sun, 14 Oct 2001 03:54:22 -0400 (EDT) Message-ID: <20011014075425.96885.qmail@web20109.mail.yahoo.com> Received: from [194.90.150.45] by web20109.mail.yahoo.com via HTTP; Sun, 14 Oct 2001 00:54:25 PDT Date: Sun, 14 Oct 2001 00:54:25 -0700 (PDT) From: James Colin Subject: Re: [Hubmib] FW: WIS design team deadline extension To: hubmib@ietf.org In-Reply-To: <1D3B17415E5DD411A07A00304810480550EAAF@MYSTIMAIL> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Hi, I'm new to this forum so please forgive my ignorance. My question is: Does the WIS MIB require hardware support? What sort of HW? What is its location in the system (MAC/LLC/PHY)? Thank you and regards, Jim > -----Original Message----- > From: Romascanu, Dan (Dan) > [mailto:dromasca@avaya.com] > Sent: Saturday, October 13, 2001 11:03 AM > To: hubmib@ietf.org > Subject: [Hubmib] FW: WIS design team deadline > extension > > > For the intention of the WG members - The WIS MIB > Design team was > awarded an extension of the deadline for submission > of the conclusions > of their work. The Internet-Draft that includes the > results of their > work will be made available on 10/19, end of > business day for the hubmib > and atommib WG members to review and comments (this > is instead of the > original 10/15 submission date). > > The decision was taken together with the chairs of > atommib, and the > reason is that we want to allow all design team > members to review and > agree to the latest version of their draft before it > is made available > for the WGs. > > Regards, > > Dan > > > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, October 12, 2001 10:45 PM > To: Romascanu, Dan (Dan); Nathan Kohn; Faye Ly > Subject: WIS design team deadline extension > > > On Fri, 12 Oct 2001, Romascanu, Dan (Dan) wrote: > > > I would agree with Mike H. It would be nice that > all members of the > > Design Team have the opportunity to comment. I > have no problem to have > > the deadline extended to 10/19, so that Mike A., > and maybe other > Design > > Team members have time to provide their input, and > changes be made if > > needed. > > > > By 10/19, you may want to make the text of the I-D > available at some > Web > > location, so that the hubmib and atommib WG > members can start looking > at > > it, in parallel with the official submission to > the Internet-Drafts > > repositories (which always takes a few days). > > Dan, > > May I suggest that you and/or other WG chairs > forward this to > information the hubmib and atommib mailing lists so > that WG > members will be aware of the delay? > > Thanks and regards, > > Mike > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > http://www1.ietf.org/mailman/listinfo/hubmib __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 16 01:40:09 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23615 for ; Tue, 16 Oct 2001 01:40:05 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24626; Tue, 16 Oct 2001 01:39:19 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24597 for ; Tue, 16 Oct 2001 01:39:15 -0400 (EDT) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23592 for ; Tue, 16 Oct 2001 01:39:13 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id WAA09481; Mon, 15 Oct 2001 22:39:13 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 15 Oct 2001 22:39:12 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: HUBMIB Mailing List In-Reply-To: <20011014075425.96885.qmail@web20109.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] Re: FW: WIS design team deadline extension Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Sun, 14 Oct 2001, James Colin wrote: > I'm new to this forum so please forgive my ignorance. > My question is: Does the WIS MIB require hardware > support? What sort of HW? What is its location in the > system (MAC/LLC/PHY)? Short answers: the WIS (WAN Interface Sublayer) resides within a 10Gb/s PHY between the Reconciliation Sublayer (RS) and the PMA/PMD sublayers. It implements a SONET STS-192c frame structure into whose payload 64B/66B encoded data from the RS is mapped. Hardware support is required, both for the WIS itself and for the managed objects. More details will appear in the forthcoming WIS MIB draft when the design team completes its work this Friday. Mike P.S. If you wish to participate in the Hubmib WG's review of the design team's work I would encourage you to apply to the Chair for a username and password to access to the latest IEEE P802.3ae draft standard, which contains the 10 Gb/s Ethernet extensions. The WIS MIB draws heavily from that document, as do the recent updates to the MAU-MIB and the EthernetLike-MIB. _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 16 15:43:43 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17613 for ; Tue, 16 Oct 2001 15:43:43 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA20551; Tue, 16 Oct 2001 15:42:00 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA20519 for ; Tue, 16 Oct 2001 15:41:59 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17505 for ; Tue, 16 Oct 2001 15:41:58 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9GJf7I05975 for ; Tue, 16 Oct 2001 15:41:07 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9GJf6Q05954 for ; Tue, 16 Oct 2001 15:41:06 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 16 Oct 2001 21:41:59 +0200 Message-ID: Thread-Topic: Internet-Draft Cutoff Dates for Salt Lake City, Utah Thread-Index: AcFWVVhyFnYdf6WiRd2iXob3/BHhIwAD5UIw From: "Romascanu, Dan (Dan)" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA20520 Subject: [Hubmib] FW: Internet-Draft Cutoff Dates for Salt Lake City, Utah Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit -----Original Message----- From: Internet-Drafts Administrator [mailto:internet-drafts@ietf.org] Sent: Tuesday, October 16, 2001 1:10 PM To: IETF-Announce; @loki.ietf.org@rhe.post.avaya.com Subject: Internet-Draft Cutoff Dates for Salt Lake City, Utah NOTE: There are two (2) Internet-Draft Cutoff dates November 14th: Cutoff for Initial Submissions (new documents) All initial submissions(-00) must be submitted by Friday, November 14th, 17:00 US-EST. Initial submissions received after this time will NOT be made available in the Internet-Drafts directory, and will have to be resubmitted. As before, all initial submissions (-00.txt) with a filename beginning with a draft-ietf MUST be approved by the appropriate WG Chair prior to processing and announcing. WG Chair approval must be received by Monday, November 19th. Please do NOT wait until the last minute to submit. Be advised: NO placeholders. Updates to initial submissions received the week of November 14th will NOT be accepted. November 21st: FINAL Internet-Draft Cutoff All revised Internet-Draft submissions must be submitted by Friday, November 21st, 2001 at 17:00 US-EST. Internet-Drafts received after this time will NOT be announced NOR made available in the Internet-Drafts Directories. 2 We will begin accepting Internet-Draft submissions the week of the meeting, though announcements will NOT be sent until the IETF meeting is over. Thank you for your understanding and cooperation. Please do not hesitate to contact us if you have any questions or concenrs. FYI: These and other significant dates can be found at http://www.ietf.org/meetings/cutoff_dates_52.html _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 00:58:02 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26397 for ; Fri, 19 Oct 2001 00:58:02 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04577; Fri, 19 Oct 2001 00:44:30 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04555 for ; Fri, 19 Oct 2001 00:44:29 -0400 (EDT) Received: from c001.snv.cp.net (c001-h001.c001.snv.cp.net [209.228.32.115]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA26235 for ; Fri, 19 Oct 2001 00:44:27 -0400 (EDT) Received: (cpmta 22080 invoked from network); 18 Oct 2001 21:43:58 -0700 Received: from cpe-24-221-253-53.ut.sprintbbd.net (HELO slc252750) (24.221.253.53) by smtp.register-admin.com (209.228.32.115) with SMTP; 18 Oct 2001 21:43:58 -0700 X-Sent: 19 Oct 2001 04:43:58 GMT Message-ID: <003f01c15858$33cfb060$3a0f880a@slc252750> Reply-To: "K.C. Norseth" From: "K.C. Norseth" To: , Date: Thu, 18 Oct 2001 22:40:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 7bit Subject: [Hubmib] Wis MIB submission - draft-wis-design-team-wis-mib-00.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 7bit The wis mib design team has submitted the ID for the Wis mib to the IETF. While waiting for it to come out officially by the IETF, you can review the draft at: http://norseth.org/ietf/hubmib/draft-wis-design-team-wis-mib-00.txt This document was created by a design team with people by both the HUBMIB and ATOMMIB WG's. The problem we were tasked to do was to create a mib that followed the 802.ae wis spec, clause 30 from the IEEE. This mib has a mix of both the ETHERNET and SONET worlds. From a combined meeting in London of the two groups, this design team was formed from both groups. We tried to put in the document any issues discussed in the overlap of both worlds. We were hoping to anticipate any problems or questions arising from both groups. The design team consisted of: Mike Ayers John Flick C. M. Heard Kam Lam Kerry McDonald K. C. Norseth Kaj Tesink If you have any questions or comments, post to either WG. Good work team. K.C. _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 02:37:12 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09246 for ; Fri, 19 Oct 2001 02:37:12 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA13631; Fri, 19 Oct 2001 02:27:12 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA13606 for ; Fri, 19 Oct 2001 02:27:06 -0400 (EDT) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08633 for ; Fri, 19 Oct 2001 02:27:00 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id XAA32540; Thu, 18 Oct 2001 23:27:01 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 18 Oct 2001 23:27:01 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] Re: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Thu, 18 Oct 2001, K.C. Norseth wrote: > The wis mib design team has submitted the ID for the Wis mib to the IETF. > While waiting for it to come out officially by the IETF, you can review the > draft at: > http://norseth.org/ietf/hubmib/draft-wis-design-team-wis-mib-00.txt [ ... ] > If you have any questions or comments, post to either WG. I'd like to bring a couple of open issues to the attention of the WGs. 1.) The WIS MIB draft extensively references RFC 2558 (the SONET-MIB). However, it requires that the value of sonetPathCurrentWidth be set to sts192cSTM64(6), which is not supported by RFC 2558. This will be resolved when a new version of the SONET-MIB is published with the changes that Kaj Tesink posted to the AToMMIB mailing list on 7 June 2001. 2.) The draft proposes the following ifTable layering model: ------------------- | ethernetCsmacd | +-------------------+ | sonetPath | +-------------------+ | sonet | ------------------- One of the members of the design team (Mike Ayers) has suggested that a better model would be ------------------- | ethernetCsmacd | +-------------------+ | ethernet64-66bWIS | +-------------------+ | sonetPath | +-------------------+ | sonet | ------------------- on the grounds that there is more than one Ethernet-over-SONET payload mapping. A conter-argument to this proposal is that this distinction can be represented more economically by having different ifMauType values for different EoS mappings. Comments are invited. Regards, Mike -- C. M. Heard heard@pobox.com _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 14:05:50 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26295 for ; Fri, 19 Oct 2001 14:05:50 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03064; Fri, 19 Oct 2001 13:54:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA03035 for ; Fri, 19 Oct 2001 13:54:18 -0400 (EDT) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25955 for ; Fri, 19 Oct 2001 13:53:56 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA31533; Fri, 19 Oct 2001 10:53:57 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 19 Oct 2001 10:53:56 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] WIS MIB draft name changed to Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org FYI - The design team's draft will appear in the I-D repository on Monday under the name Regards, //cmh ---------- Forwarded message ---------- Date: Fri, 19 Oct 2001 13:12:46 -0400 (Eastern Daylight Time) From: Natalia Syracuse To: C. M. Heard Subject: Re: Submission of Your draft will be announced on Monday (Oct. 22nd) with a filename draft-ayers-wis-mib-00.txt (according to our mnaming rule). Natalia Syracuse _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 14:25:35 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27032 for ; Fri, 19 Oct 2001 14:25:35 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA03833; Fri, 19 Oct 2001 14:14:36 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA03816 for ; Fri, 19 Oct 2001 14:14:35 -0400 (EDT) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.cabletron.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26594 for ; Fri, 19 Oct 2001 14:14:32 -0400 (EDT) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id OAA26089; Fri, 19 Oct 2001 14:22:41 -0400 (EDT) Received: from unknown(134.141.77.96) by ctron-dnm.ctron.com via smap (4.1) id xma026075; Fri, 19 Oct 01 14:21:49 -0400 Received: by cnc-exc1.enterasys.com with Internet Mail Service (5.5.2653.19) id <42HJPY35>; Fri, 19 Oct 2001 14:13:21 -0400 Message-ID: <0BF8B32B723ED5119E0B0002A551748B946EAF@corp-exc3.ctron.com> From: "Harrington, David" To: "'C. M. Heard'" , Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] WIS MIB draft name changed to Date: Fri, 19 Oct 2001 14:13:19 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C158C9.BB2E2980" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C158C9.BB2E2980 Content-Type: text/plain Hi, Why is this being published as an individual submission instead of a WG item? Isn't this the result of the design team, and an official WG document? dbh > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, October 19, 2001 1:54 PM > To: Hubmib Mailing List; AToMMIB Mailing List > Subject: [Hubmib] WIS MIB draft name changed to > > > > FYI - > > The design team's draft will appear in the I-D repository on Monday > under the name > > Regards, > > //cmh > > ---------- Forwarded message ---------- > Date: Fri, 19 Oct 2001 13:12:46 -0400 (Eastern Daylight Time) > From: Natalia Syracuse > To: C. M. Heard > Subject: Re: Submission of > > Your draft will be announced on Monday (Oct. 22nd) with a filename > draft-ayers-wis-mib-00.txt (according to our mnaming rule). > > Natalia Syracuse > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > http://www1.ietf.org/mailman/listinfo/hubmib > ------_=_NextPart_001_01C158C9.BB2E2980 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Hubmib] WIS MIB draft name changed to = <draft-ayers-wis-mib-00.txt>

Hi,

Why is this being published as an individual = submission instead of a WG item? Isn't this the result of the design = team, and an official WG document?

dbh

> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]
> Sent: Friday, October 19, 2001 1:54 PM
> To: Hubmib Mailing List; AToMMIB Mailing = List
> Subject: [Hubmib] WIS MIB draft name changed = to
> <draft-ayers-wis-mib-00.txt>
>
>
> FYI -
>
> The design team's draft will appear in the I-D = repository on Monday
> under the name = <draft-ayers-wis-mib-00.txt>
>
> Regards,
>
> //cmh
>
> ---------- Forwarded message ----------
> Date: Fri, 19 Oct 2001 13:12:46 -0400 (Eastern = Daylight Time)
> From: Natalia Syracuse = <nsyracus@ietf.org>
> To: C. M. Heard <heard@pobox.com>
> Subject: Re: Submission of = <draft-wis-design-team-wis-mib-00.txt>
>
> Your draft will be announced on Monday (Oct. = 22nd) with a filename
> draft-ayers-wis-mib-00.txt (according to our = mnaming rule).
>
> Natalia Syracuse
>
>
> = _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> http://www1.ietf.org/mailman/listinfo/hubmib
>

------_=_NextPart_001_01C158C9.BB2E2980-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 15:58:17 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29736 for ; Fri, 19 Oct 2001 15:58:17 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA06577; Fri, 19 Oct 2001 15:47:32 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA06556 for ; Fri, 19 Oct 2001 15:47:31 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29467 for ; Fri, 19 Oct 2001 15:47:29 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9JJkck19194 for ; Fri, 19 Oct 2001 15:46:38 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9JJkbw19183 for ; Fri, 19 Oct 2001 15:46:37 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Subject: RE: [Hubmib] Re: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 19 Oct 2001 21:47:26 +0200 Message-ID: Thread-Topic: [Hubmib] Re: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt Thread-Index: AcFYZyH2LByHPT8WTGC2WchbXmIDAwAVVfPQ From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hubmib Mailing List" , "AToMMIB Mailing List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA06557 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit The preferable editorial path would have been to list these in an Open Issues session of the design team draft. In the absence of such a section, I would suggest that the design team moderator opens a list of such issues - which can be augmented until the Utah meeting and which we would work to resolve by that time. Regards, Dan > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, October 19, 2001 8:27 AM > To: Hubmib Mailing List; AToMMIB Mailing List > Subject: [Hubmib] Re: Wis MIB submission - > draft-wis-design-team-wis-mib-00.txt > > > On Thu, 18 Oct 2001, K.C. Norseth wrote: > > > The wis mib design team has submitted the ID for the Wis > mib to the IETF. > > While waiting for it to come out officially by the IETF, > you can review the > > draft at: > > http://norseth.org/ietf/hubmib/draft-wis-design-team-wis-mib-00.txt > [ ... ] > > If you have any questions or comments, post to either WG. > > I'd like to bring a couple of open issues to the attention of the WGs. > > 1.) The WIS MIB draft extensively references RFC 2558 (the SONET-MIB). > However, it requires that the value of sonetPathCurrentWidth be > set to sts192cSTM64(6), which is not supported by RFC 2558. This > will be resolved when a new version of the SONET-MIB is published > with the changes that Kaj Tesink posted to the AToMMIB > mailing list > on 7 June 2001. > > 2.) The draft proposes the following ifTable layering model: > > ------------------- > | ethernetCsmacd | > +-------------------+ > | sonetPath | > +-------------------+ > | sonet | > ------------------- > > One of the members of the design team (Mike Ayers) has > suggested that a better model would be > > ------------------- > | ethernetCsmacd | > +-------------------+ > | ethernet64-66bWIS | > +-------------------+ > | sonetPath | > +-------------------+ > | sonet | > ------------------- > > on the grounds that there is more than one Ethernet-over-SONET > payload mapping. A conter-argument to this proposal is that > this distinction can be represented more economically by > having different ifMauType values for different EoS mappings. > Comments are invited. > > Regards, > > Mike > -- > C. M. Heard > heard@pobox.com > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > http://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 16:00:14 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29787 for ; Fri, 19 Oct 2001 16:00:14 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA06619; Fri, 19 Oct 2001 15:47:37 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA06598 for ; Fri, 19 Oct 2001 15:47:36 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29470 for ; Fri, 19 Oct 2001 15:47:30 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9JJkdk19224 for ; Fri, 19 Oct 2001 15:46:39 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9JJkcw19206 for ; Fri, 19 Oct 2001 15:46:38 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Subject: RE: [Hubmib] Submission of Implementation Reports MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-8" Date: Fri, 19 Oct 2001 21:47:28 +0200 Message-ID: Thread-Topic: [Hubmib] Submission of Implementation Reports Thread-Index: AcEg+jcsHl2jdozfEdWDigCQJ5z34A3wuCvw From: "Romascanu, Dan (Dan)" To: "kerry mcdonald" , Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA06599 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit Do we have news concerning the implementation reports? FYI, all vendors - providing the reports is both of technical interest, and also required if you want to see the current RFCs advance on the standards track. This is important for the industry as a whole - pardon me the rhetoric! - and is certainly worth the effort of documenting the current implementations. As we previously said dr. Yasha and Kerry are independent from the vendors community, and their services were required in order to ensure the confidentiality of the information that vendors would like to keep. Regards, Dan > -----Original Message----- > From: kerry mcdonald [mailto:kerry_mcd@hotmail.com] > Sent: Thursday, August 09, 2001 5:22 PM > To: hubmib@ietf.org > Cc: ykarant@csci.csusb.edu > Subject: [Hubmib] Submission of Implementation Reports > > > As per the hubmib WG meeting at the 51st IETF in London all > vendors with > current implementation reports are requested to submit these > reports to: > > Dr. Yasha Karant > Director, Institute for Applied Supercomputing > Department of Computer Science > California State University, San Bernardino > ykarant@csci.csusb.edu > > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > http://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 17:25:08 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02126 for ; Fri, 19 Oct 2001 17:25:08 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09176; Fri, 19 Oct 2001 17:11:39 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09157 for ; Fri, 19 Oct 2001 17:11:38 -0400 (EDT) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01744 for ; Fri, 19 Oct 2001 17:11:35 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA12796; Fri, 19 Oct 2001 14:11:37 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 19 Oct 2001 14:11:36 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] Re: WIS MIB draft name changed to Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Fri, 19 Oct 2001, Harrington, David wrote: > Why is this being published as an individual submission instead of a WG > item? Isn't this the result of the design team, and an official WG document? We were asked (by the Hubmib chair) to make the initial submission a design team draft in order to leave some time for the other WG participants to provide feedback to the mailing list. My understanding is that if the two WGs endorse the design team's approach then will be issued to replace the current WG draft. However, I don't know if that is expected to happen before or after the Utah meeting. Note that we originally asked to have this draft named to make it clear that it is a design team draft, but that name was not acceptable to the folks that run the I-D repository. On Fri, 19 Oct 2001, Romascanu, Dan (Dan) wrote: > The preferable editorial path would have been to list these in an Open > Issues session of the design team draft. In the absence of such a > section, I would suggest that the design team moderator opens a list of > such issues - which can be augmented until the Utah meeting and which we > would work to resolve by that time. That omission was my fault. It can be fixed when/if the draft is respun as a WG draft. //cmh _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 20:31:40 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07796 for ; Fri, 19 Oct 2001 20:31:40 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13182; Fri, 19 Oct 2001 20:21:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13153 for ; Fri, 19 Oct 2001 20:21:21 -0400 (EDT) Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07334 for ; Fri, 19 Oct 2001 20:21:18 -0400 (EDT) Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA22526 for ; Fri, 19 Oct 2001 20:20:08 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id UAA22511 for ; Fri, 19 Oct 2001 20:20:07 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Subject: RE: [Hubmib] WIS MIB draft name changed to MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C158FD.1FFA5EE5" Date: Sat, 20 Oct 2001 02:21:12 +0200 Message-ID: Thread-Topic: [Hubmib] WIS MIB draft name changed to Thread-Index: AcFYyf4nFr1BOC8cRwecZbwu0Dr8XQAGSmVw From: "Romascanu, Dan (Dan)" To: "Harrington, David" , "C. M. Heard" , "Hubmib Mailing List" , "AToMMIB Mailing List" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C158FD.1FFA5EE5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am not sure if there are firm procedural rules in this case. The work was indeed mandated by the two WGs, but there will not be a standard document directly resulted from this I-D. What we actualy want to do is to generate discussions on the lists, and then update draft-ietf- hubmib-wis-mib-00.txt which is targeted to become eventually the standard tracks document.=20 =20 Regards, =20 Dan =20 -----Original Message----- From: Harrington, David [mailto:dbh@enterasys.com] Sent: Friday, October 19, 2001 8:13 PM To: 'C. M. Heard'; Hubmib Mailing List; AToMMIB Mailing List Subject: RE: [Hubmib] WIS MIB draft name changed to Hi,=20 Why is this being published as an individual submission instead of a WG item? Isn't this the result of the design team, and an official WG document? dbh=20 > -----Original Message-----=20 > From: C. M. Heard [ mailto:heard@pobox.com]=20 > Sent: Friday, October 19, 2001 1:54 PM=20 > To: Hubmib Mailing List; AToMMIB Mailing List=20 > Subject: [Hubmib] WIS MIB draft name changed to=20 > =20 >=20 >=20 > FYI -=20 >=20 > The design team's draft will appear in the I-D repository on Monday=20 > under the name =20 >=20 > Regards,=20 >=20 > //cmh=20 >=20 > ---------- Forwarded message ----------=20 > Date: Fri, 19 Oct 2001 13:12:46 -0400 (Eastern Daylight Time)=20 > From: Natalia Syracuse =20 > To: C. M. Heard =20 > Subject: Re: Submission of =20 >=20 > Your draft will be announced on Monday (Oct. 22nd) with a filename=20 > draft-ayers-wis-mib-00.txt (according to our mnaming rule).=20 >=20 > Natalia Syracuse=20 >=20 >=20 > _______________________________________________=20 > Hubmib mailing list=20 > Hubmib@ietf.org=20 > http://www1.ietf.org/mailman/listinfo/hubmib=20 >=20 ------_=_NextPart_001_01C158FD.1FFA5EE5 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Hubmib] WIS MIB draft name changed to = <draft-ayers-wis-mib-00.txt>
I am=20 not sure if there are firm procedural rules in this case. The work was = indeed=20 mandated by the two WGs, but there will not be a standard = document=20 directly resulted from this I-D. What we actualy want to do is to = generate=20 discussions on the lists, and then update draft-ietf- = hubmib-wis-mib-00.txt=20 which is targeted to become eventually the standard tracks document.=20
 
Regards,
 
Dan
 
-----Original Message-----
From: Harrington, David=20 [mailto:dbh@enterasys.com]
Sent: Friday, October 19, 2001 = 8:13=20 PM
To: 'C. M. Heard'; Hubmib Mailing List; AToMMIB Mailing=20 List
Subject: RE: [Hubmib] WIS MIB draft name changed to=20 <draft-ayers-wis-mib-00.txt>

Hi,

Why is this being published as an individual = submission=20 instead of a WG item? Isn't this the result of the design team, and an = official WG document?

dbh

> -----Original Message-----
>=20 From: C. M. Heard [mailto:heard@pobox.com] =
> Sent: Friday, October 19, 2001 1:54 PM
> To: Hubmib Mailing List; AToMMIB Mailing List =
> Subject: [Hubmib] WIS MIB draft name changed to =
> <draft-ayers-wis-mib-00.txt>
>=20
>
> FYI = -=20
>
> The design = team's draft=20 will appear in the I-D repository on Monday
> under=20 the name <draft-ayers-wis-mib-00.txt>
>=20
> Regards,
> =
> //cmh
>=20
> ---------- Forwarded message = ----------=20
> Date: Fri, 19 Oct 2001 13:12:46 -0400 (Eastern = Daylight=20 Time)
> From: Natalia Syracuse=20 <nsyracus@ietf.org>
> To: C. M. = Heard=20 <heard@pobox.com>
> Subject: Re: = Submission=20 of <draft-wis-design-team-wis-mib-00.txt>
>=20
> Your draft will be announced on Monday = (Oct.=20 22nd) with a filename
> = draft-ayers-wis-mib-00.txt=20 (according to our mnaming rule).
> =
> Natalia Syracuse
> =
>
>=20 _______________________________________________
>=20 Hubmib mailing list
> = Hubmib@ietf.org=20
> http://www1.ietf.or= g/mailman/listinfo/hubmib=20
>

------_=_NextPart_001_01C158FD.1FFA5EE5-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 20:31:52 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07811 for ; Fri, 19 Oct 2001 20:31:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13215; Fri, 19 Oct 2001 20:21:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13188 for ; Fri, 19 Oct 2001 20:21:23 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07337 for ; Fri, 19 Oct 2001 20:21:20 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9K0KS106266 for ; Fri, 19 Oct 2001 20:20:28 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9K0KR706261 for ; Fri, 19 Oct 2001 20:20:27 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 20 Oct 2001 02:21:16 +0200 Message-ID: Thread-Topic: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt Thread-Index: AcFYWQARO+JGAr03SrGzJNBKmRNtFwAjsfhQ From: "Romascanu, Dan (Dan)" To: "K.C. Norseth" , , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id UAA13189 Subject: [Hubmib] RE: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit Please allow me to congratulate and thank the design team for a work well done. I would now kindly request all the WG members to go ahead and read the draft. We intent to collect feedback in the next two weeks, and then issue a revised version of draft-ietf-hubmib-wis-mib-00. txt, taking into account the results of the design team work, and the discussions on the list. Regards, Dan > -----Original Message----- > From: K.C. Norseth [mailto:kcn@norseth.com] > Sent: Friday, October 19, 2001 6:41 AM > To: atommib@research.telcordia.com; hubmib@ietf.org > Subject: Wis MIB submission - draft-wis-design-team-wis-mib-00.txt > > > The wis mib design team has submitted the ID for the Wis mib > to the IETF. > While waiting for it to come out officially by the IETF, you > can review the > draft at: > http://norseth.org/ietf/hubmib/draft-wis-design-team-wis-mib-00.txt > > This document was created by a design team with people by > both the HUBMIB > and ATOMMIB WG's. The problem we were tasked to do was to > create a mib that > followed the 802.ae wis spec, clause 30 from the IEEE. This > mib has a mix > of both the ETHERNET and SONET worlds. From a combined > meeting in London of > the two groups, this design team was formed from both groups. > We tried to > put in the document any issues discussed in the overlap of > both worlds. We > were hoping to anticipate any problems or questions arising from both > groups. > > The design team consisted of: > Mike Ayers > John Flick > C. M. Heard > Kam Lam > Kerry McDonald > K. C. Norseth > Kaj Tesink > > If you have any questions or comments, post to either WG. > > Good work team. > > K.C. > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri Oct 19 21:16:50 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09520 for ; Fri, 19 Oct 2001 21:16:50 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14302; Fri, 19 Oct 2001 21:06:58 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14273 for ; Fri, 19 Oct 2001 21:06:57 -0400 (EDT) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09180 for ; Fri, 19 Oct 2001 21:06:54 -0400 (EDT) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9K162115709 for ; Fri, 19 Oct 2001 21:06:02 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9K161715684 for ; Fri, 19 Oct 2001 21:06:01 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message Subject: RE: [Hubmib] Re: WIS MIB draft name changed to MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 20 Oct 2001 03:06:50 +0200 Message-ID: Thread-Topic: [Hubmib] Re: WIS MIB draft name changed to Thread-Index: AcFY4rX+yAckZ12FT+uMHTgMEUCK1gAHPdIQ From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hubmib Mailing List" , "AToMMIB Mailing List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id VAA14274 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit > We were asked (by the Hubmib chair) to make the initial > submission a design > team draft in order to leave some time for the other WG > participants to > provide feedback to the mailing list. My understanding is > that if the two > WGs endorse the design team's approach then > > will be issued to replace the current WG draft. However, I > don't know if > that is expected to happen before or after the Utah meeting. > From the WG Charter: Oct 01 Issue revised WG Drafts for MIBs for P802.3ae/P802.3af As the design team Internet-Draft was made available only today for the bulk of the WG members to comment, I would recommend that we allow two weeks for comments and discussions. After this period, I would like draft-hubmib-wis-mib-01.txt to be issued, before the deadline for the Salt Lake City submissions. The Charter says that after the Utah meeting we need to proceed to the WG Last Call. It looks like we have chances to meet it. Regards, Dan _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Oct 22 11:35:07 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20114 for ; Mon, 22 Oct 2001 11:35:07 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24550; Mon, 22 Oct 2001 11:22:51 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24529 for ; Mon, 22 Oct 2001 11:22:50 -0400 (EDT) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19767 for ; Mon, 22 Oct 2001 11:22:46 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id IAA09570; Mon, 22 Oct 2001 08:22:49 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 22 Oct 2001 08:22:49 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] I-D ACTION:draft-ayers-wis-mib-00.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Fri, 19 Oct 2001, C. M. Heard wrote: > The design team's draft will appear in the I-D repository on Monday > under the name It's now there. The announcement may be viewed at the following URL: http://www.ietf.org/mail-archive/ietf-announce/Current/msg14893.html Thanks, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon Oct 22 14:42:47 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26813 for ; Mon, 22 Oct 2001 14:42:46 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA01673; Mon, 22 Oct 2001 14:30:53 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA01646 for ; Mon, 22 Oct 2001 14:30:52 -0400 (EDT) Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26412 for ; Mon, 22 Oct 2001 14:30:47 -0400 (EDT) Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA25261 for ; Mon, 22 Oct 2001 14:29:38 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA25240 for ; Mon, 22 Oct 2001 14:29:37 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 22 Oct 2001 20:30:44 +0200 Message-ID: Thread-Topic: To avoid confusion it's Internet-Draft Cutoff Dates for Salt Lake City,Utah announcement again Thread-Index: AcFbJzRep9LBwRkYQ+GlHlVQ/b6fRAAAFEXg From: "Romascanu, Dan (Dan)" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA01647 Subject: [Hubmib] FW: To avoid confusion it's Internet-Draft Cutoff Dates for Salt Lake City,Utah announcement again Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit -----Original Message----- From: Internet-Drafts Administrator [mailto:internet-drafts@ietf.org] Sent: Monday, October 22, 2001 7:23 PM To: IETF-Announce; @loki.ietf.org@rhe.post.avaya.com Subject: To avoid confusion it's Internet-Draft Cutoff Dates for Salt Lake City,Utah announcement again NOTE: There are two (2) Internet-Draft Cutoff dates November 14th: Cutoff for Initial Submissions (new documents) All initial submissions(-00) must be submitted by Wednesday, November 14th, 17:00 US-EST. Initial submissions received after this time will NOT be made available in the Internet-Drafts directory, and will have to be resubmitted. As before, all initial submissions (-00.txt) with a filename beginning with a draft-ietf MUST be approved by the appropriate WG Chair prior to processing and announcing. WG Chair approval must be received by Monday, November 19th. Please do NOT wait until the last minute to submit. Be advised: NO placeholders. Updates to initial submissions received the week of November 14th will NOT be accepted. November 21st: FINAL Internet-Draft Cutoff All revised Internet-Draft submissions must be submitted by Wednesday, November 21st, 2001 at 17:00 US-EST. Internet-Drafts received after this time will NOT be announced NOR made available in the Internet-Drafts Directories. We will begin accepting Internet-Draft submissions the week of the meeting, though announcements will NOT be sent until the IETF meeting is over. Thank you for your understanding and cooperation. Please do not hesitate to contact us if you have any questions or concenrs. FYI: These and other significant dates can be found at http://www.ietf.org/meetings/cutoff_dates_52.html _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From mailman-owner@ietf.org Wed Oct 24 14:40:10 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10987 for ; Wed, 24 Oct 2001 14:40:10 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA01727 for ; Wed, 24 Oct 2001 14:40:11 -0400 (EDT) Date: Wed, 24 Oct 2001 14:40:11 -0400 (EDT) Message-Id: <200110241840.OAA01727@optimus.ietf.org> From: mailman-owner@ietf.org Subject: ietf.org mailing list memberships reminder To: hubmib-archive@ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Session Initiation Protocol This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, hubmib-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for hubmib-archive@lists.ietf.org: List Password // URL ---- -------- hubmib@ietf.org XUKx http://www1.ietf.org/mailman/options/hubmib/hubmib-archive@lists.ietf.org From hubmib-admin@ietf.org Tue Oct 30 12:22:43 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07905 for ; Tue, 30 Oct 2001 12:22:43 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09483; Tue, 30 Oct 2001 11:37:59 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09460 for ; Tue, 30 Oct 2001 11:37:50 -0500 (EST) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.cabletron.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06399 for ; Tue, 30 Oct 2001 11:37:45 -0500 (EST) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id LAA14971; Tue, 30 Oct 2001 11:45:53 -0500 (EST) Received: from unknown(134.141.77.103) by ctron-dnm.ctron.com via smap (4.1) id xma014950; Tue, 30 Oct 01 11:45:22 -0500 Received: by cnc-exc2.enterasys.com with Internet Mail Service (5.5.2653.19) id ; Tue, 30 Oct 2001 11:36:45 -0500 Message-ID: <59358A738F45D51186A30008C74CE25062A5CF@slc-exc1.ctron.com> From: "Norseth, KC" To: "'hubmib@ietf.org'" , "'atommib@research.telcordia.com'" Date: Tue, 30 Oct 2001 11:36:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C16161.101B9690" Subject: [Hubmib] Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C16161.101B9690 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C16161.101B9690" ------_=_NextPart_001_01C16161.101B9690 Content-Type: text/plain The team formed from people of the atommib and the hubmib group submitted an ID for Definitions of Managed Objects for the Ethernet WAN Interface Sublayer http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt . We have not heard of any objections to the ID, so I would like to move it to replace the "official" ID that is identified in the hubmib WG (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00.txt ) Anyone comments on this? K.C. Norseth Firmware Engineering - Routing Enterasys Networks Phone: 801.887.9823 FAX: 801.972.5789 Email: knorseth@enterasys.com www: http://www.enterasys.com <> ------_=_NextPart_001_01C16161.101B9690 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Comments for wis mib

The team formed from people of the = atommib and the hubmib group submitted an ID for Definitions of Managed = Objects
for the Ethernet WAN Interface = Sublayer = http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-0= 0.txt.  We have not = heard of any objections to the ID, so I would like to move it to = replace the "official" ID that is identified in the hubmib WG = (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis= -mib-00.txt)

Anyone comments on this?

K.C. = Norseth
Firmware = Engineering -  Routing
Enterasys = Networks
   Phone: 801.887.9823
   = FAX:    801.972.5789
   = Email:   knorseth@enterasys.com
   = www:    http://www.enterasys.com=
<<Norseth, = KC.vcf>>

------_=_NextPart_001_01C16161.101B9690-- ------_=_NextPart_000_01C16161.101B9690 Content-Type: application/octet-stream; name="Norseth, KC.vcf" Content-Disposition: attachment; filename="Norseth, KC.vcf" BEGIN:VCARD VERSION:2.1 N:Norseth;KC FN:Norseth, KC ORG:Cabletron Systems, Inc.;5167 TEL;WORK;VOICE:53823 ADR;WORK:;Salt Lake City;2835 South Decker Lake Drive;Salt Lake City;UT;84119;US LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Salt Lake City=0D=0A2835 South Decker Lake Drive=0D=0ASalt Lake City, UT 841= 19=0D=0AUS EMAIL;PREF;INTERNET:knorseth@cabletron.com REV:19991213T143559Z END:VCARD ------_=_NextPart_000_01C16161.101B9690-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Tue Oct 30 12:22:44 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07915 for ; Tue, 30 Oct 2001 12:22:44 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA11290 for hubmib-archive@odin.ietf.org; Tue, 30 Oct 2001 12:22:48 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09483; Tue, 30 Oct 2001 11:37:59 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09460 for ; Tue, 30 Oct 2001 11:37:50 -0500 (EST) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.cabletron.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06399 for ; Tue, 30 Oct 2001 11:37:45 -0500 (EST) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id LAA14971; Tue, 30 Oct 2001 11:45:53 -0500 (EST) Received: from unknown(134.141.77.103) by ctron-dnm.ctron.com via smap (4.1) id xma014950; Tue, 30 Oct 01 11:45:22 -0500 Received: by cnc-exc2.enterasys.com with Internet Mail Service (5.5.2653.19) id ; Tue, 30 Oct 2001 11:36:45 -0500 Message-ID: <59358A738F45D51186A30008C74CE25062A5CF@slc-exc1.ctron.com> From: "Norseth, KC" To: "'hubmib@ietf.org'" , "'atommib@research.telcordia.com'" Date: Tue, 30 Oct 2001 11:36:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C16161.101B9690" Subject: [Hubmib] Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C16161.101B9690 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C16161.101B9690" ------_=_NextPart_001_01C16161.101B9690 Content-Type: text/plain The team formed from people of the atommib and the hubmib group submitted an ID for Definitions of Managed Objects for the Ethernet WAN Interface Sublayer http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt . We have not heard of any objections to the ID, so I would like to move it to replace the "official" ID that is identified in the hubmib WG (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00.txt ) Anyone comments on this? K.C. Norseth Firmware Engineering - Routing Enterasys Networks Phone: 801.887.9823 FAX: 801.972.5789 Email: knorseth@enterasys.com www: http://www.enterasys.com <> ------_=_NextPart_001_01C16161.101B9690 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Comments for wis mib

The team formed from people of the = atommib and the hubmib group submitted an ID for Definitions of Managed = Objects
for the Ethernet WAN Interface = Sublayer = http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-0= 0.txt.  We have not = heard of any objections to the ID, so I would like to move it to = replace the "official" ID that is identified in the hubmib WG = (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis= -mib-00.txt)

Anyone comments on this?

K.C. = Norseth
Firmware = Engineering -  Routing
Enterasys = Networks
   Phone: 801.887.9823
   = FAX:    801.972.5789
   = Email:   knorseth@enterasys.com
   = www:    http://www.enterasys.com=
<<Norseth, = KC.vcf>>

------_=_NextPart_001_01C16161.101B9690-- ------_=_NextPart_000_01C16161.101B9690 Content-Type: application/octet-stream; name="Norseth, KC.vcf" Content-Disposition: attachment; filename="Norseth, KC.vcf" BEGIN:VCARD VERSION:2.1 N:Norseth;KC FN:Norseth, KC ORG:Cabletron Systems, Inc.;5167 TEL;WORK;VOICE:53823 ADR;WORK:;Salt Lake City;2835 South Decker Lake Drive;Salt Lake City;UT;84119;US LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Salt Lake City=0D=0A2835 South Decker Lake Drive=0D=0ASalt Lake City, UT 841= 19=0D=0AUS EMAIL;PREF;INTERNET:knorseth@cabletron.com REV:19991213T143559Z END:VCARD ------_=_NextPart_000_01C16161.101B9690-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 30 13:44:33 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10947 for ; Tue, 30 Oct 2001 13:44:32 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13141; Tue, 30 Oct 2001 13:01:58 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13117 for ; Tue, 30 Oct 2001 13:01:57 -0500 (EST) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09358 for ; Tue, 30 Oct 2001 13:01:54 -0500 (EST) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9UI0xJ09802 for ; Tue, 30 Oct 2001 13:00:59 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9UI0wO09791 for ; Tue, 30 Oct 2001 13:00:58 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1616C.F2533AA3" Date: Tue, 30 Oct 2001 20:01:49 +0200 Message-ID: Thread-Topic: Comments for wis mib Thread-Index: AcFhYYT+zYgDYMo1Tq2IdMc9Qi3xPAAAxxuA From: "Romascanu, Dan (Dan)" To: "Norseth, KC" , , Subject: [Hubmib] RE: Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C1616C.F2533AA3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I did not hear any significant objections or discussions either. As Ethernet WG chair I would propose that if no objections are raised until the end of the week we consider the design team recommendations as adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt based on them. =20 I would like to hear the blessing from the atommib WG chairs as well. =20 Mike Heard draw my attention to a change between version D3.2 and D3.3 of the IEEE draft - concerning the elimination of the acResetWIS object. I would recommend that this change be reflected in the new version of the MIB, as well as other nits that we might discover. =20 Regards, =20 Dan =20 -----Original Message----- From: Norseth, KC [mailto:knorseth@enterasys.com] Sent: Tuesday, October 30, 2001 6:37 PM To: 'hubmib@ietf.org'; 'atommib@research.telcordia.com' Subject: Comments for wis mib The team formed from people of the atommib and the hubmib group submitted an ID for Definitions of Managed Objects=20 for the Ethernet WAN Interface Sublayer http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt. We have not heard of any objections to the ID, so I would like to move it to replace the "official" ID that is identified in the hubmib WG ( http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00.txt) Anyone comments on this?=20 K.C. Norseth=20 Firmware Engineering - Routing=20 Enterasys Networks=20 Phone: 801.887.9823=20 FAX: 801.972.5789=20 Email: knorseth@enterasys.com=20 www: http://www.enterasys.com=20 <>=20 ------_=_NextPart_001_01C1616C.F2533AA3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comments for wis mib
I did=20 not hear any significant objections or discussions either. As Ethernet = WG chair=20 I would propose that if no objections are raised until the end of the = week we=20 consider the design team recommendations as adopted and we proceed to = issue=20 draft-ietf-hubmib-wis-mib-01.txt based on them.
 
I=20 would like to hear the blessing from the atommib WG chairs as=20 well.
 
Mike=20 Heard draw my attention to a change between version D3.2 and D3.3 of the = IEEE=20 draft - concerning the elimination of the acResetWIS=20 object. I would = recommend=20 that this change be reflected in the new version of the MIB, as well as = other=20 nits that we might discover.
 
Regards,
 
Dan
 

 -----Original = Message-----
From:=20 Norseth, KC [mailto:knorseth@enterasys.com]
Sent: Tuesday, = October 30,=20 2001 6:37 PM
To: 'hubmib@ietf.org';=20 'atommib@research.telcordia.com'
Subject: Comments for wis=20 mib

The team formed from people of the = atommib and the=20 hubmib group submitted an ID for Definitions of Managed Objects =
for the Ethernet WAN Interface = Sublayer <= U>http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt.  We have not heard of any objections to = the ID, so I=20 would like to move it to replace the "official" ID that is identified = in the=20 hubmib WG (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00= .txt)

Anyone comments on this?

K.C. = Norseth=20
Firmware = Engineering - =20 Routing
Enterasys=20 Networks
   = Phone:=20 801.887.9823 =
   FAX:    = 801.972.5789 =
   Email:   knorseth@enterasys.com
   www:    http://www.enterasys.com= =20
<<Norseth, = KC.vcf>>=20

------_=_NextPart_001_01C1616C.F2533AA3-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Tue Oct 30 13:44:33 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10956 for ; Tue, 30 Oct 2001 13:44:33 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA14296 for hubmib-archive@odin.ietf.org; Tue, 30 Oct 2001 13:44:36 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13141; Tue, 30 Oct 2001 13:01:58 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13117 for ; Tue, 30 Oct 2001 13:01:57 -0500 (EST) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09358 for ; Tue, 30 Oct 2001 13:01:54 -0500 (EST) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9UI0xJ09802 for ; Tue, 30 Oct 2001 13:00:59 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9UI0wO09791 for ; Tue, 30 Oct 2001 13:00:58 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1616C.F2533AA3" Date: Tue, 30 Oct 2001 20:01:49 +0200 Message-ID: Thread-Topic: Comments for wis mib Thread-Index: AcFhYYT+zYgDYMo1Tq2IdMc9Qi3xPAAAxxuA From: "Romascanu, Dan (Dan)" To: "Norseth, KC" , , Subject: [Hubmib] RE: Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C1616C.F2533AA3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I did not hear any significant objections or discussions either. As Ethernet WG chair I would propose that if no objections are raised until the end of the week we consider the design team recommendations as adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt based on them. =20 I would like to hear the blessing from the atommib WG chairs as well. =20 Mike Heard draw my attention to a change between version D3.2 and D3.3 of the IEEE draft - concerning the elimination of the acResetWIS object. I would recommend that this change be reflected in the new version of the MIB, as well as other nits that we might discover. =20 Regards, =20 Dan =20 -----Original Message----- From: Norseth, KC [mailto:knorseth@enterasys.com] Sent: Tuesday, October 30, 2001 6:37 PM To: 'hubmib@ietf.org'; 'atommib@research.telcordia.com' Subject: Comments for wis mib The team formed from people of the atommib and the hubmib group submitted an ID for Definitions of Managed Objects=20 for the Ethernet WAN Interface Sublayer http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt. We have not heard of any objections to the ID, so I would like to move it to replace the "official" ID that is identified in the hubmib WG ( http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00.txt) Anyone comments on this?=20 K.C. Norseth=20 Firmware Engineering - Routing=20 Enterasys Networks=20 Phone: 801.887.9823=20 FAX: 801.972.5789=20 Email: knorseth@enterasys.com=20 www: http://www.enterasys.com=20 <>=20 ------_=_NextPart_001_01C1616C.F2533AA3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comments for wis mib
I did=20 not hear any significant objections or discussions either. As Ethernet = WG chair=20 I would propose that if no objections are raised until the end of the = week we=20 consider the design team recommendations as adopted and we proceed to = issue=20 draft-ietf-hubmib-wis-mib-01.txt based on them.
 
I=20 would like to hear the blessing from the atommib WG chairs as=20 well.
 
Mike=20 Heard draw my attention to a change between version D3.2 and D3.3 of the = IEEE=20 draft - concerning the elimination of the acResetWIS=20 object. I would = recommend=20 that this change be reflected in the new version of the MIB, as well as = other=20 nits that we might discover.
 
Regards,
 
Dan
 

 -----Original = Message-----
From:=20 Norseth, KC [mailto:knorseth@enterasys.com]
Sent: Tuesday, = October 30,=20 2001 6:37 PM
To: 'hubmib@ietf.org';=20 'atommib@research.telcordia.com'
Subject: Comments for wis=20 mib

The team formed from people of the = atommib and the=20 hubmib group submitted an ID for Definitions of Managed Objects =
for the Ethernet WAN Interface = Sublayer <= U>http://www.ietf.org/internet-drafts/draft-ayers-wis-mib-00.txt.  We have not heard of any objections to = the ID, so I=20 would like to move it to replace the "official" ID that is identified = in the=20 hubmib WG (http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-00= .txt)

Anyone comments on this?

K.C. = Norseth=20
Firmware = Engineering - =20 Routing
Enterasys=20 Networks
   = Phone:=20 801.887.9823 =
   FAX:    = 801.972.5789 =
   Email:   knorseth@enterasys.com
   www:    http://www.enterasys.com= =20
<<Norseth, = KC.vcf>>=20

------_=_NextPart_001_01C1616C.F2533AA3-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 30 13:58:39 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11314 for ; Tue, 30 Oct 2001 13:58:34 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14116; Tue, 30 Oct 2001 13:34:57 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14092 for ; Tue, 30 Oct 2001 13:34:56 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10586 for ; Tue, 30 Oct 2001 13:34:53 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA01768; Tue, 30 Oct 2001 10:34:51 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 30 Oct 2001 10:34:50 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] Re: Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Tue, 30 Oct 2001, Romascanu, Dan (Dan) wrote: > I did not hear any significant objections or discussions either. As > Ethernet WG chair I would propose that if no objections are raised until > the end of the week we consider the design team recommendations as > adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt based > on them. > > I would like to hear the blessing from the atommib WG chairs as well. > > Mike Heard draw my attention to a change between version D3.2 and D3.3 > of the IEEE draft - concerning the elimination of the acResetWIS object. > I would recommend that this change be reflected in the new version of > the MIB, as well as other nits that we might discover. Here is my list of changes: - update the reference from P802.3ae/D3.2 to P802.3ae/D3.3 and make the necessary fixes for alignment (currently all I have found is the need to remove mention of acResetWIS in the Section 3.6 and also in Section 3.3). - update the CONTACT-INFO clause ... guidance as to what is appropriate is requested from the WG chairs and the design team moderator. - if there will be a new SONET-MIB I-D before the Salt Lake City IETF meeting, then the references should point to it instead of RFC 2558 (since we depend on one of the changes to appear in the next version of that MIB). Regards, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Tue Oct 30 13:58:44 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11324 for ; Tue, 30 Oct 2001 13:58:39 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA14598 for hubmib-archive@odin.ietf.org; Tue, 30 Oct 2001 13:58:42 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14116; Tue, 30 Oct 2001 13:34:57 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14092 for ; Tue, 30 Oct 2001 13:34:56 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10586 for ; Tue, 30 Oct 2001 13:34:53 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA01768; Tue, 30 Oct 2001 10:34:51 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 30 Oct 2001 10:34:50 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] Re: Comments for wis mib Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Tue, 30 Oct 2001, Romascanu, Dan (Dan) wrote: > I did not hear any significant objections or discussions either. As > Ethernet WG chair I would propose that if no objections are raised until > the end of the week we consider the design team recommendations as > adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt based > on them. > > I would like to hear the blessing from the atommib WG chairs as well. > > Mike Heard draw my attention to a change between version D3.2 and D3.3 > of the IEEE draft - concerning the elimination of the acResetWIS object. > I would recommend that this change be reflected in the new version of > the MIB, as well as other nits that we might discover. Here is my list of changes: - update the reference from P802.3ae/D3.2 to P802.3ae/D3.3 and make the necessary fixes for alignment (currently all I have found is the need to remove mention of acResetWIS in the Section 3.6 and also in Section 3.3). - update the CONTACT-INFO clause ... guidance as to what is appropriate is requested from the WG chairs and the design team moderator. - if there will be a new SONET-MIB I-D before the Salt Lake City IETF meeting, then the references should point to it instead of RFC 2558 (since we depend on one of the changes to appear in the next version of that MIB). Regards, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 30 16:57:19 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15673 for ; Tue, 30 Oct 2001 16:57:18 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19825; Tue, 30 Oct 2001 16:25:47 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19796 for ; Tue, 30 Oct 2001 16:25:45 -0500 (EST) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.cabletron.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14853 for ; Tue, 30 Oct 2001 16:25:40 -0500 (EST) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id QAA04068; Tue, 30 Oct 2001 16:33:37 -0500 (EST) Received: from unknown(134.141.77.96) by ctron-dnm.ctron.com via smap (4.1) id xma004042; Tue, 30 Oct 01 16:33:10 -0500 Received: by cnc-exc1.enterasys.com with Internet Mail Service (5.5.2653.19) id ; Tue, 30 Oct 2001 16:24:32 -0500 Message-ID: <59358A738F45D51186A30008C74CE25062A5D6@slc-exc1.ctron.com> From: "Norseth, KC" To: "'C. M. Heard'" , Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib Date: Tue, 30 Oct 2001 16:24:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C16189.44038620" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C16189.44038620 Content-Type: text/plain |-----Original Message----- |From: C. M. Heard [mailto:heard@pobox.com] |Sent: Tuesday, October 30, 2001 11:35 AM |To: Hubmib Mailing List; AToMMIB Mailing List |Subject: [Hubmib] Re: Comments for wis mib | | |On Tue, 30 Oct 2001, Romascanu, Dan (Dan) wrote: | |> I did not hear any significant objections or discussions either. As |> Ethernet WG chair I would propose that if no objections are raised |> until the end of the week we consider the design team |recommendations |> as adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt |> based on them. |> |> I would like to hear the blessing from the atommib WG chairs as well. |> |> Mike Heard draw my attention to a change between version |D3.2 and D3.3 |> of the IEEE draft - concerning the elimination of the acResetWIS |> object. I would recommend that this change be reflected in the new |> version of the MIB, as well as other nits that we might discover. | |Here is my list of changes: | |- update the reference from P802.3ae/D3.2 to P802.3ae/D3.3 and |make the necessary fixes for alignment (currently all I have |found is the need to remove mention of acResetWIS in the |Section 3.6 and also in Section 3.3). Agreed. |- update the CONTACT-INFO clause ... guidance as to what is |appropriate is requested from the WG chairs and the design |team moderator. As for the CONTACT-INFO, rfc1442 "The CONTACT-INFO clause, which must be present, contains the name, postal address, telephone number, and electronic mail address of the person to whom technical queries concerning this information module should be sent." This should probably be you where you are the main editor, although I have seen where they just give the Working group list group email address. If we put the email address of the WG, put in both hubmib and atommib groups. |- if there will be a new SONET-MIB I-D before the Salt Lake |City IETF meeting, then the references should point to it |instead of RFC 2558 (since we depend on one of the changes to |appear in the next version of that MIB). We have till 11/21 to submit. Unless there is a last-call for a new SONET-MIB RFC, we should use the current rfc. ID's change, at least rfc 2558 is currently an accepted RFC. |Regards, | |Mike | K.C. ------_=_NextPart_001_01C16189.44038620 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Hubmib] Re: Comments for wis mib

|-----Original Message-----
|From: C. M. Heard [mailto:heard@pobox.com]
|Sent: Tuesday, October 30, 2001 11:35 AM
|To: Hubmib Mailing List; AToMMIB Mailing = List
|Subject: [Hubmib] Re: Comments for wis mib
|
|
|On Tue, 30 Oct 2001, Romascanu, Dan (Dan) = wrote:
|
|> I did not hear any significant objections or = discussions either. As
|> Ethernet WG chair I would propose that if no = objections are raised
|> until the end of the week we consider the = design team
|recommendations
|> as adopted and we proceed to issue = draft-ietf-hubmib-wis-mib-01.txt
|> based on them.
|> 
|> I would like to hear the blessing from the = atommib WG chairs as well.
|> 
|> Mike Heard draw my attention to a change = between version
|D3.2 and D3.3
|> of the IEEE draft - concerning the elimination = of the acResetWIS
|> object. I would recommend that this change be = reflected in the new
|> version of the MIB, as well as other nits that = we might discover.
|
|Here is my list of changes:
|
|- update the reference from P802.3ae/D3.2 to = P802.3ae/D3.3 and
|make the necessary fixes for alignment (currently = all I have
|found is the need to remove mention of acResetWIS = in the
|Section 3.6 and also in Section 3.3).

Agreed.

|- update the CONTACT-INFO clause ... guidance as to = what is
|appropriate is requested from the WG chairs and the = design
|team moderator.

As for the CONTACT-INFO,  rfc1442
"The CONTACT-INFO clause, which must be = present, contains the
name, postal address, telephone number, and = electronic mail
address of the person to whom technical queries = concerning
this information module should be sent."

This should probably be you where you are the main = editor, although I have seen where they just give the Working group = list group email address.  If we put the email address of the WG, = put in both hubmib and atommib groups.

|- if there will be a new SONET-MIB I-D before the = Salt Lake
|City IETF meeting, then the references should point = to it
|instead of RFC 2558 (since we depend on one of the = changes to
|appear in the next version of that MIB).

We have till 11/21 to submit.  Unless there is a = last-call for a new SONET-MIB RFC, we should use the current rfc. ID's = change, at least rfc 2558 is currently an accepted RFC.

|Regards,
|
|Mike
|

K.C.

------_=_NextPart_001_01C16189.44038620-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Tue Oct 30 16:57:19 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15681 for ; Tue, 30 Oct 2001 16:57:19 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA20634 for hubmib-archive@odin.ietf.org; Tue, 30 Oct 2001 16:57:24 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19825; Tue, 30 Oct 2001 16:25:47 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA19796 for ; Tue, 30 Oct 2001 16:25:45 -0500 (EST) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.cabletron.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14853 for ; Tue, 30 Oct 2001 16:25:40 -0500 (EST) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id QAA04068; Tue, 30 Oct 2001 16:33:37 -0500 (EST) Received: from unknown(134.141.77.96) by ctron-dnm.ctron.com via smap (4.1) id xma004042; Tue, 30 Oct 01 16:33:10 -0500 Received: by cnc-exc1.enterasys.com with Internet Mail Service (5.5.2653.19) id ; Tue, 30 Oct 2001 16:24:32 -0500 Message-ID: <59358A738F45D51186A30008C74CE25062A5D6@slc-exc1.ctron.com> From: "Norseth, KC" To: "'C. M. Heard'" , Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib Date: Tue, 30 Oct 2001 16:24:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C16189.44038620" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C16189.44038620 Content-Type: text/plain |-----Original Message----- |From: C. M. Heard [mailto:heard@pobox.com] |Sent: Tuesday, October 30, 2001 11:35 AM |To: Hubmib Mailing List; AToMMIB Mailing List |Subject: [Hubmib] Re: Comments for wis mib | | |On Tue, 30 Oct 2001, Romascanu, Dan (Dan) wrote: | |> I did not hear any significant objections or discussions either. As |> Ethernet WG chair I would propose that if no objections are raised |> until the end of the week we consider the design team |recommendations |> as adopted and we proceed to issue draft-ietf-hubmib-wis-mib-01.txt |> based on them. |> |> I would like to hear the blessing from the atommib WG chairs as well. |> |> Mike Heard draw my attention to a change between version |D3.2 and D3.3 |> of the IEEE draft - concerning the elimination of the acResetWIS |> object. I would recommend that this change be reflected in the new |> version of the MIB, as well as other nits that we might discover. | |Here is my list of changes: | |- update the reference from P802.3ae/D3.2 to P802.3ae/D3.3 and |make the necessary fixes for alignment (currently all I have |found is the need to remove mention of acResetWIS in the |Section 3.6 and also in Section 3.3). Agreed. |- update the CONTACT-INFO clause ... guidance as to what is |appropriate is requested from the WG chairs and the design |team moderator. As for the CONTACT-INFO, rfc1442 "The CONTACT-INFO clause, which must be present, contains the name, postal address, telephone number, and electronic mail address of the person to whom technical queries concerning this information module should be sent." This should probably be you where you are the main editor, although I have seen where they just give the Working group list group email address. If we put the email address of the WG, put in both hubmib and atommib groups. |- if there will be a new SONET-MIB I-D before the Salt Lake |City IETF meeting, then the references should point to it |instead of RFC 2558 (since we depend on one of the changes to |appear in the next version of that MIB). We have till 11/21 to submit. Unless there is a last-call for a new SONET-MIB RFC, we should use the current rfc. ID's change, at least rfc 2558 is currently an accepted RFC. |Regards, | |Mike | K.C. ------_=_NextPart_001_01C16189.44038620 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Hubmib] Re: Comments for wis mib

|-----Original Message-----
|From: C. M. Heard [mailto:heard@pobox.com]
|Sent: Tuesday, October 30, 2001 11:35 AM
|To: Hubmib Mailing List; AToMMIB Mailing = List
|Subject: [Hubmib] Re: Comments for wis mib
|
|
|On Tue, 30 Oct 2001, Romascanu, Dan (Dan) = wrote:
|
|> I did not hear any significant objections or = discussions either. As
|> Ethernet WG chair I would propose that if no = objections are raised
|> until the end of the week we consider the = design team
|recommendations
|> as adopted and we proceed to issue = draft-ietf-hubmib-wis-mib-01.txt
|> based on them.
|> 
|> I would like to hear the blessing from the = atommib WG chairs as well.
|> 
|> Mike Heard draw my attention to a change = between version
|D3.2 and D3.3
|> of the IEEE draft - concerning the elimination = of the acResetWIS
|> object. I would recommend that this change be = reflected in the new
|> version of the MIB, as well as other nits that = we might discover.
|
|Here is my list of changes:
|
|- update the reference from P802.3ae/D3.2 to = P802.3ae/D3.3 and
|make the necessary fixes for alignment (currently = all I have
|found is the need to remove mention of acResetWIS = in the
|Section 3.6 and also in Section 3.3).

Agreed.

|- update the CONTACT-INFO clause ... guidance as to = what is
|appropriate is requested from the WG chairs and the = design
|team moderator.

As for the CONTACT-INFO,  rfc1442
"The CONTACT-INFO clause, which must be = present, contains the
name, postal address, telephone number, and = electronic mail
address of the person to whom technical queries = concerning
this information module should be sent."

This should probably be you where you are the main = editor, although I have seen where they just give the Working group = list group email address.  If we put the email address of the WG, = put in both hubmib and atommib groups.

|- if there will be a new SONET-MIB I-D before the = Salt Lake
|City IETF meeting, then the references should point = to it
|instead of RFC 2558 (since we depend on one of the = changes to
|appear in the next version of that MIB).

We have till 11/21 to submit.  Unless there is a = last-call for a new SONET-MIB RFC, we should use the current rfc. ID's = change, at least rfc 2558 is currently an accepted RFC.

|Regards,
|
|Mike
|

K.C.

------_=_NextPart_001_01C16189.44038620-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue Oct 30 17:51:17 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16578 for ; Tue, 30 Oct 2001 17:51:17 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21457; Tue, 30 Oct 2001 17:27:29 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21434 for ; Tue, 30 Oct 2001 17:27:26 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16168 for ; Tue, 30 Oct 2001 17:27:21 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA19269; Tue, 30 Oct 2001 14:27:24 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 30 Oct 2001 14:27:23 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib In-Reply-To: <59358A738F45D51186A30008C74CE25062A5D6@slc-exc1.ctron.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Tue, 30 Oct 2001, Norseth, KC wrote: > We have till 11/21 to submit. Unless there is a last-call for a new > SONET-MIB RFC, we should use the current rfc. ID's change, at least > rfc 2558 is currently an accepted RFC. I'm afraid I must disagree. The ETHER-WIS conformance statements will not even compile properly until the new enum sts192cSTM64(6) is added to the definition of sonetPathCurrentWidth. That enum is not currently in RFC 2558 but is on the editor's change list. For that reason we should reference the work in progress as soon as a draft is available, whether or not it has made last call. Of course, we can't publish the ETHER-WIS MIB until that change is also published, which will require a last call. That reminds me of something else ... On Sat, 20 Oct 2001, Romascanu, Dan (Dan) wrote: > The Charter says that after the Utah meeting we need to proceed to the > WG Last Call. It looks like we have chances to meet it. We might indeed be able to do that, but we can't publish until P802.3ae gets through its sponsor ballot, can we? Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Tue Oct 30 17:51:21 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16588 for ; Tue, 30 Oct 2001 17:51:18 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA22012 for hubmib-archive@odin.ietf.org; Tue, 30 Oct 2001 17:51:23 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21457; Tue, 30 Oct 2001 17:27:29 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21434 for ; Tue, 30 Oct 2001 17:27:26 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16168 for ; Tue, 30 Oct 2001 17:27:21 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA19269; Tue, 30 Oct 2001 14:27:24 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 30 Oct 2001 14:27:23 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib In-Reply-To: <59358A738F45D51186A30008C74CE25062A5D6@slc-exc1.ctron.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Tue, 30 Oct 2001, Norseth, KC wrote: > We have till 11/21 to submit. Unless there is a last-call for a new > SONET-MIB RFC, we should use the current rfc. ID's change, at least > rfc 2558 is currently an accepted RFC. I'm afraid I must disagree. The ETHER-WIS conformance statements will not even compile properly until the new enum sts192cSTM64(6) is added to the definition of sonetPathCurrentWidth. That enum is not currently in RFC 2558 but is on the editor's change list. For that reason we should reference the work in progress as soon as a draft is available, whether or not it has made last call. Of course, we can't publish the ETHER-WIS MIB until that change is also published, which will require a last call. That reminds me of something else ... On Sat, 20 Oct 2001, Romascanu, Dan (Dan) wrote: > The Charter says that after the Utah meeting we need to proceed to the > WG Last Call. It looks like we have chances to meet it. We might indeed be able to do that, but we can't publish until P802.3ae gets through its sponsor ballot, can we? Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Oct 31 01:18:15 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24616 for ; Wed, 31 Oct 2001 01:18:15 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA29343; Wed, 31 Oct 2001 00:55:03 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA29324 for ; Wed, 31 Oct 2001 00:55:02 -0500 (EST) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22851 for ; Wed, 31 Oct 2001 00:54:58 -0500 (EST) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9V5s2B14769 for ; Wed, 31 Oct 2001 00:54:02 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9V5s1014757 for ; Wed, 31 Oct 2001 00:54:01 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Hubmib] Re: Comments for wis mib Date: Wed, 31 Oct 2001 07:54:52 +0200 Message-ID: Thread-Topic: [Hubmib] Re: Comments for wis mib Thread-Index: AcFhkj73GRKrBw2zR0OBEfX4cPskDAAPJXgQ From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hubmib Mailing List" , "AToMMIB Mailing List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id AAA29325 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit > > On Tue, 30 Oct 2001, Norseth, KC wrote: > > We have till 11/21 to submit. Unless there is a last-call for a new > > SONET-MIB RFC, we should use the current rfc. ID's change, at least > > rfc 2558 is currently an accepted RFC. > > I'm afraid I must disagree. The ETHER-WIS conformance statements will > not even compile properly until the new enum sts192cSTM64(6) is added > to the definition of sonetPathCurrentWidth. That enum is not > currently > in RFC 2558 but is on the editor's change list. For that > reason we should > reference the work in progress as soon as a draft is > available, whether > or not it has made last call. Of course, we can't publish > the ETHER-WIS > MIB until that change is also published, which will require a > last call. > Mike is right. Technically we created a linkage between the WIS MIB and son-of-RFC 2558. Frankly speaking, this concerns me a little, and I would like to discuss the issue in SLC with the atommib WG chairs and Bert. At this point in time the reference should be to the new SONET MIB Internet-Draft. > That reminds me of something else ... > > On Sat, 20 Oct 2001, Romascanu, Dan (Dan) wrote: > > The Charter says that after the Utah meeting we need to > proceed to the > > WG Last Call. It looks like we have chances to meet it. > > We might indeed be able to do that, but we can't publish > until P802.3ae > gets through its sponsor ballot, can we? > I am not sure that the formal requirement is that strict relative to a non-IETF standard, but for obvious reasons we do not aim publish the WIS MIB as a Proposed Standard before the IEEE approved 802.3ae. Their schedule says this will happen by March 2002. I estimate that we will need this time also to go through our WG Last Call process and through the IESG quality review. It looks that by the time the IESG will do its last call we will have the approved 802.3ae reference at hand. > Mike Regards, Dan _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Wed Oct 31 01:18:15 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24625 for ; Wed, 31 Oct 2001 01:18:15 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA07118 for hubmib-archive@odin.ietf.org; Wed, 31 Oct 2001 01:18:18 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA29343; Wed, 31 Oct 2001 00:55:03 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA29324 for ; Wed, 31 Oct 2001 00:55:02 -0500 (EST) Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22851 for ; Wed, 31 Oct 2001 00:54:58 -0500 (EST) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9V5s2B14769 for ; Wed, 31 Oct 2001 00:54:02 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h149-49-38-91.avaya.com [149.49.38.91]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id f9V5s1014757 for ; Wed, 31 Oct 2001 00:54:01 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Hubmib] Re: Comments for wis mib Date: Wed, 31 Oct 2001 07:54:52 +0200 Message-ID: Thread-Topic: [Hubmib] Re: Comments for wis mib Thread-Index: AcFhkj73GRKrBw2zR0OBEfX4cPskDAAPJXgQ From: "Romascanu, Dan (Dan)" To: "C. M. Heard" , "Hubmib Mailing List" , "AToMMIB Mailing List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id AAA29325 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org Content-Transfer-Encoding: 8bit > > On Tue, 30 Oct 2001, Norseth, KC wrote: > > We have till 11/21 to submit. Unless there is a last-call for a new > > SONET-MIB RFC, we should use the current rfc. ID's change, at least > > rfc 2558 is currently an accepted RFC. > > I'm afraid I must disagree. The ETHER-WIS conformance statements will > not even compile properly until the new enum sts192cSTM64(6) is added > to the definition of sonetPathCurrentWidth. That enum is not > currently > in RFC 2558 but is on the editor's change list. For that > reason we should > reference the work in progress as soon as a draft is > available, whether > or not it has made last call. Of course, we can't publish > the ETHER-WIS > MIB until that change is also published, which will require a > last call. > Mike is right. Technically we created a linkage between the WIS MIB and son-of-RFC 2558. Frankly speaking, this concerns me a little, and I would like to discuss the issue in SLC with the atommib WG chairs and Bert. At this point in time the reference should be to the new SONET MIB Internet-Draft. > That reminds me of something else ... > > On Sat, 20 Oct 2001, Romascanu, Dan (Dan) wrote: > > The Charter says that after the Utah meeting we need to > proceed to the > > WG Last Call. It looks like we have chances to meet it. > > We might indeed be able to do that, but we can't publish > until P802.3ae > gets through its sponsor ballot, can we? > I am not sure that the formal requirement is that strict relative to a non-IETF standard, but for obvious reasons we do not aim publish the WIS MIB as a Proposed Standard before the IEEE approved 802.3ae. Their schedule says this will happen by March 2002. I estimate that we will need this time also to go through our WG Last Call process and through the IESG quality review. It looks that by the time the IESG will do its last call we will have the approved 802.3ae reference at hand. > Mike Regards, Dan _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Wed Oct 31 14:05:41 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28103 for ; Wed, 31 Oct 2001 14:05:41 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01653; Wed, 31 Oct 2001 13:40:35 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01626 for ; Wed, 31 Oct 2001 13:40:34 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27478 for ; Wed, 31 Oct 2001 13:40:27 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA26782; Wed, 31 Oct 2001 10:40:27 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Wed, 31 Oct 2001 10:40:26 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Wed, 31 Oct 2001, Romascanu, Dan (Dan) wrote: > Mike is right. Technically we created a linkage between the WIS MIB and > son-of-RFC 2558. Frankly speaking, this concerns me a little, and I > would like to discuss the issue in SLC with the atommib WG chairs and > Bert. I agree that there is reason for concern. On the other hand, I don't see any road around that _if_ we re-use the SONET-MIB for the WIS application as the design team's draft proposes. The current SONET-MIB simply does not support STS-192c or STS-768c path widths. Even if the ETHER-WIS MIB did not specifically mention the new enum sts192cSTM64(6) for sonetPathCurrentWidth, that enum would still need to be present in the SONET-MIB before it could be used to manage the WIS path. Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib From daemon@optimus.ietf.org Wed Oct 31 14:05:41 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28112 for ; Wed, 31 Oct 2001 14:05:41 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA03065 for hubmib-archive@odin.ietf.org; Wed, 31 Oct 2001 14:05:42 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01653; Wed, 31 Oct 2001 13:40:35 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01626 for ; Wed, 31 Oct 2001 13:40:34 -0500 (EST) Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27478 for ; Wed, 31 Oct 2001 13:40:27 -0500 (EST) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA26782; Wed, 31 Oct 2001 10:40:27 -0800 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Wed, 31 Oct 2001 10:40:26 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hubmib Mailing List , AToMMIB Mailing List Subject: RE: [Hubmib] Re: Comments for wis mib In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: hubmib@ietf.org On Wed, 31 Oct 2001, Romascanu, Dan (Dan) wrote: > Mike is right. Technically we created a linkage between the WIS MIB and > son-of-RFC 2558. Frankly speaking, this concerns me a little, and I > would like to discuss the issue in SLC with the atommib WG chairs and > Bert. I agree that there is reason for concern. On the other hand, I don't see any road around that _if_ we re-use the SONET-MIB for the WIS application as the design team's draft proposes. The current SONET-MIB simply does not support STS-192c or STS-768c path widths. Even if the ETHER-WIS MIB did not specifically mention the new enum sts192cSTM64(6) for sonetPathCurrentWidth, that enum would still need to be present in the SONET-MIB before it could be used to manage the WIS path. Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org http://www1.ietf.org/mailman/listinfo/hubmib