From mailman-owner@ietf.org  Tue Jan  1 06:04:52 2002
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 GAA10891
	for <hubmib-archive@odin.ietf.org>; Tue, 1 Jan 2002 06:04:52 -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 GAA26759
	for <hubmib-archive@lists.ietf.org>; Tue, 1 Jan 2002 06:04:55 -0500 (EST)
Date: Tue, 1 Jan 2002 06:04:55 -0500 (EST)
Message-Id: <200201011104.GAA26759@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 <sip.ietf.org>

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  Wed Jan  2 12:26:04 2002
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 MAA07501
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 12:26:04 -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 MAA13894;
	Wed, 2 Jan 2002 12:22:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13867
	for <hubmib@optimus.ietf.org>; Wed, 2 Jan 2002 12:22:20 -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 MAA07448
	for <hubmib@ietf.org>; Wed, 2 Jan 2002 12:22:17 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id JAA11413;
	Wed, 2 Jan 2002 09:22:10 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 2 Jan 2002 09:22:09 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Roy Bynum <rabynum@mindspring.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
Message-ID: <Pine.LNX.4.10.10201010840350.4754-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and recommendations
 for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Mon, 31 Dec 2001, Roy Bynum wrote:
> Because there is becoming a likely hood that the WIS overhead definition
> will be adopted as a separate functional optical link protocol for optical
> switched networks, I would like to see more of a divorce between the WIS
> MIB and SONET.  By making references to the SONET MIB, there is still the
> perception that the WIS is part of SONET.  It is not.  Neither is it part
> of SDH.   I would like to see a totally separate set of definitions for the
> WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I
> think that it should be on a separate AIN branch from SONET or SDH.

Although the WIS is not a subset of SONET or SDH, it does use the same
frame structure as SONET, as is explicitly stated in the following
excerpt from 802.3ae subclause 50.1.1:

  "The WIS maps the encoded Ethernet data received (transmitted) from (to)
   the PCS into a frame structure that has the same format as that defined
   by T1.416-1999, implementing a minimal number of the standard SONET
   overhead fields and functions.  The WIS does not adhere to the electrical
   and optical aspects of SONET specified by T1.416-1999, as it is intended
   to be used with PHYs that conform to the corresponding parameters defined
   by the 10GBASE-W standard."

A consequence of this fact is that the objects in the SONET-MIB's
sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2,
sonetFarEndLineStuff2, sonetPathStuff2, and sonetFarEndPathStuff2
object groups are valid for the WIS, although only a subset of the
possible values apply for some of the objects.  Furthermore, these
objects are already used in systems where 10 Gb/s Ethernet interfaces
likely to be deployed, and this argues strongly for re-use of these
objects.  Two specific examples of such systems are:

(a) Routers.  It's common now for PoS (PPP over SONET) and ATM over
SONET to be used on a router's WAN interfaces, and the standard means
for managing the SONET sublayers is the SONET-MIB.  Both management
applications and agents exist that know how to deal with it.  Using
the SONET-MIB to manage the WIS would be a way to leverage on that
technology.

(b) SONET transport NEs.  It's common for such NEs to have non-SONET
interfaces, i.e., line cards that map non-SONET signals (such as DS3)
into SONET payloads and that perform SONET multiplexing.  A 10GBASE-W
Ethernet interface would technically be a non-SONET interface (since
the optical specs and jitter specs are not SONET-compliant), but thanks
to the use of the WIS there is no format conversion in the payload
mapping.  If such an NE offers an SNMP management interface, then the
SONET-MIB is once again the standard way to manage the SONET interfaces.
Using the SONET-MIB to manage 10GBASE-W tributary interfaces would be
a win in this case, too.

> Because of developments that are taking place in T1X1 and ITU regarding the
> development of a "path relay" type of "Lite LTE" or as it is known to
> 802.3ae an "ELTE" as a standard, it will be better that these two MIBs not
> have references to each other.  The proposed "path relay" may well have two
> separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also
> likely be part of actively managed wavelength transponders, which may be a
> lot less expensive than current LTEs or the proposed Digital Wrapper
> systems.  Over a period of time, this would make the WIS MIB a part of a
> much larger market than it has been previously believed.

The path relay function is in no way unique to ELTE but exists in any
any network element that contains LTE -- in other words, it exists in
any network element that strips off section and line overhead and
extracts the Synchronous Payload Envelope (SPE) at one interface and
inserts that SPE into a different SONET frame (with newly generated
section and line overhead) at another interface.  A typical realization
of ELTE in a SONET ADM would be a 10GBASE-W tributary interface, which
would differ from an OC-192c tributary interface in using different
optics and complying with different jitter specs, but would be essentially
the same in its processing of the section and line overhead.  Thus, the
SONET-MIB's sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, and
sonetFarEndLineStuff2 object groups can be used to manage a 10GBASE-W
tributary interface just as well as they can be used to manage an OC-192c
tributary interface.  [Note, however, that the proposed WIS MIB does not
address the management of ELTE, which only contains a subset of the WIS.
This was considered out-of-scope for the present standardization effort.]

> Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if
> there are objects in the WIS MIB that may have the same function, and
> possibly the same "text", as objects in the SONET or SDH MIBs, they should
> be separate and inclusive within themselves.

To many of us it is anathema to duplicate the definitions of managed
objects in different MIB modules for exactly the same reason that people
frown on cloning text from one standard to another.  802.3ae incorporates
by reference the appropriate definitions from T1.416-1999 rather than
cloning the text.  Similarly, the proposed WIS MIB incorporates by
reference applicable objects from the SONET-MIB.  The same reasons for
doing so apply in both cases.

Thanks,

Mike


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan  2 12:26:06 2002
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 MAA07514
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 12:26:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA14025
	for hubmib-archive@odin.ietf.org; Wed, 2 Jan 2002 12:26:08 -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 MAA13894;
	Wed, 2 Jan 2002 12:22:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13867
	for <hubmib@optimus.ietf.org>; Wed, 2 Jan 2002 12:22:20 -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 MAA07448
	for <hubmib@ietf.org>; Wed, 2 Jan 2002 12:22:17 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id JAA11413;
	Wed, 2 Jan 2002 09:22:10 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 2 Jan 2002 09:22:09 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Roy Bynum <rabynum@mindspring.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
Message-ID: <Pine.LNX.4.10.10201010840350.4754-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and recommendations
 for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Mon, 31 Dec 2001, Roy Bynum wrote:
> Because there is becoming a likely hood that the WIS overhead definition
> will be adopted as a separate functional optical link protocol for optical
> switched networks, I would like to see more of a divorce between the WIS
> MIB and SONET.  By making references to the SONET MIB, there is still the
> perception that the WIS is part of SONET.  It is not.  Neither is it part
> of SDH.   I would like to see a totally separate set of definitions for the
> WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I
> think that it should be on a separate AIN branch from SONET or SDH.

Although the WIS is not a subset of SONET or SDH, it does use the same
frame structure as SONET, as is explicitly stated in the following
excerpt from 802.3ae subclause 50.1.1:

  "The WIS maps the encoded Ethernet data received (transmitted) from (to)
   the PCS into a frame structure that has the same format as that defined
   by T1.416-1999, implementing a minimal number of the standard SONET
   overhead fields and functions.  The WIS does not adhere to the electrical
   and optical aspects of SONET specified by T1.416-1999, as it is intended
   to be used with PHYs that conform to the corresponding parameters defined
   by the 10GBASE-W standard."

A consequence of this fact is that the objects in the SONET-MIB's
sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2,
sonetFarEndLineStuff2, sonetPathStuff2, and sonetFarEndPathStuff2
object groups are valid for the WIS, although only a subset of the
possible values apply for some of the objects.  Furthermore, these
objects are already used in systems where 10 Gb/s Ethernet interfaces
likely to be deployed, and this argues strongly for re-use of these
objects.  Two specific examples of such systems are:

(a) Routers.  It's common now for PoS (PPP over SONET) and ATM over
SONET to be used on a router's WAN interfaces, and the standard means
for managing the SONET sublayers is the SONET-MIB.  Both management
applications and agents exist that know how to deal with it.  Using
the SONET-MIB to manage the WIS would be a way to leverage on that
technology.

(b) SONET transport NEs.  It's common for such NEs to have non-SONET
interfaces, i.e., line cards that map non-SONET signals (such as DS3)
into SONET payloads and that perform SONET multiplexing.  A 10GBASE-W
Ethernet interface would technically be a non-SONET interface (since
the optical specs and jitter specs are not SONET-compliant), but thanks
to the use of the WIS there is no format conversion in the payload
mapping.  If such an NE offers an SNMP management interface, then the
SONET-MIB is once again the standard way to manage the SONET interfaces.
Using the SONET-MIB to manage 10GBASE-W tributary interfaces would be
a win in this case, too.

> Because of developments that are taking place in T1X1 and ITU regarding the
> development of a "path relay" type of "Lite LTE" or as it is known to
> 802.3ae an "ELTE" as a standard, it will be better that these two MIBs not
> have references to each other.  The proposed "path relay" may well have two
> separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also
> likely be part of actively managed wavelength transponders, which may be a
> lot less expensive than current LTEs or the proposed Digital Wrapper
> systems.  Over a period of time, this would make the WIS MIB a part of a
> much larger market than it has been previously believed.

The path relay function is in no way unique to ELTE but exists in any
any network element that contains LTE -- in other words, it exists in
any network element that strips off section and line overhead and
extracts the Synchronous Payload Envelope (SPE) at one interface and
inserts that SPE into a different SONET frame (with newly generated
section and line overhead) at another interface.  A typical realization
of ELTE in a SONET ADM would be a 10GBASE-W tributary interface, which
would differ from an OC-192c tributary interface in using different
optics and complying with different jitter specs, but would be essentially
the same in its processing of the section and line overhead.  Thus, the
SONET-MIB's sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, and
sonetFarEndLineStuff2 object groups can be used to manage a 10GBASE-W
tributary interface just as well as they can be used to manage an OC-192c
tributary interface.  [Note, however, that the proposed WIS MIB does not
address the management of ELTE, which only contains a subset of the WIS.
This was considered out-of-scope for the present standardization effort.]

> Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if
> there are objects in the WIS MIB that may have the same function, and
> possibly the same "text", as objects in the SONET or SDH MIBs, they should
> be separate and inclusive within themselves.

To many of us it is anathema to duplicate the definitions of managed
objects in different MIB modules for exactly the same reason that people
frown on cloning text from one standard to another.  802.3ae incorporates
by reference the appropriate definitions from T1.416-1999 rather than
cloning the text.  Similarly, the proposed WIS MIB incorporates by
reference applicable objects from the SONET-MIB.  The same reasons for
doing so apply in both cases.

Thanks,

Mike


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan  2 14:56:47 2002
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 OAA09629
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:56:47 -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 OAA18885;
	Wed, 2 Jan 2002 14:50:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19597
	for <hubmib@optimus.ietf.org>; Thu, 27 Dec 2001 13:54:19 -0500 (EST)
Received: from father.pmc-sierra.bc.ca (father.pmc-sierra.bc.ca [216.241.224.13])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19694
	for <hubmib@ietf.org>; Thu, 27 Dec 2001 13:54:16 -0500 (EST)
Received: (qmail 15723 invoked by uid 104); 27 Dec 2001 18:53:42 -0000
Received: from Tom_Alexander@pmc-sierra.com by father with qmail-scanner-1.00 (uvscan: v4.1.40/v4178. . Clean. Processed in 0.53953 secs); 27 Dec 2001 18:53:42 -0000
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 27 Dec 2001 18:53:41 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (jason/8.11.6) with ESMTP id fBRIrfc29667;
	Thu, 27 Dec 2001 10:53:41 -0800 (PST)
Received: by bby1exi01 with Internet Mail Service (5.5.2653.19)
	id <XNRNZ6L7>; Thu, 27 Dec 2001 10:53:41 -0800
Message-ID: <B513C2E3B290D41185CA00306E0070FE451BD2@pld1exm01.pmc-sierra.bc.ca>
From: Tom Alexander <Tom_Alexander@pmc-sierra.com>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>,
        "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>
Cc: "C. M. Heard" <heard@pobox.com>, hubmib@ietf.org,
        "'Roy Bynum'"
	 <rabynum@mindspring.com>
Date: Thu, 27 Dec 2001 10:53:40 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C18F07.CC7C3640"
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and recommendations
 for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
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_01C18F07.CC7C3640
Content-Type: text/plain;
	charset="iso-8859-1"

Dan,
 
Thanks for the clarification. I believe I understand the issue now.
 
Roy, it looks like Dan's explanation is in general agreement with the point you made
in your e-mail as well. The WIS and SONET/SDH MIBs are being kept separate for
the reasons you mentioned.
 
Best regards,
 
- Tom

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Wednesday, December 26, 2001 10:46 PM
To: Tom Alexander; HSSG Reflector (E-mail)
Cc: C. M. Heard; hubmib@ietf.org
Subject: RE: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution


Tom,
 
The problem is that some of the objects that the authors of the SONET MIB decided that may remain optional for their management model are mandatory for a full definition and understanding of the WIS interface behavior. This is the reason for defining a separate compliance statement that is stricter than the compliance statement for a 'regular' SONET MIB implementation.
 
The minutes of the Salt Lake City meeting will be soon out. There was not much controversy on this issue, the resolution being that the editors will document their decision so that the later implementers of the standard can understand the rationale of the path that was taken.
 
Regards,
 
Dan
 

-----Original Message-----
From: Tom Alexander [mailto:Tom_Alexander@pmc-sierra.com]
Sent: Thursday, December 27, 2001 4:26 AM
To: Romascanu, Dan (Dan); HSSG Reflector (E-mail)
Cc: C. M. Heard
Subject: RE: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution


Dan,
 
The recommendations to the issues you mentioned look reasonable to me;
however, I did have a question on the third issue you raised (compliance statements
and optional/mandatory groups). The general intent of the WIS was to implement
a perfect subset of SONET/SDH. Therefore, should not the MIB object groups
likewise represent a perfect subset of the SONET MIB object groups? That is,
optional SONET MIB objects should either be omitted entirely, or remain optional
in the WIS MIB?
 
I have not read the minutes of the IETF Plenary, so apologies in advance if I have
inadvertently re-hashed something that should have been obvious.
 
Thanks, and best regards,
 
- Tom Alexander
WIS Scribe
 

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Wednesday, December 26, 2001 7:36 AM
To: HSSG Reflector (E-mail)
Cc: C. M. Heard
Subject: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution



The IETF Ethernet Interfaces and Hub MIB WG met during the IETF Plenary meeting in Salt Lake City in the week of 12/10. One of the items in the WG Charter that was discussed during the meeting was the latest WIS MIB http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt <http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt> .

The WG identified a list of four open issues, and recommended solutions for their resolution. It was established during the meeting that it would be appropriate if these issues would also be published on the IEEE 802.3ae reflector, so that interested IEEE participants can provide feedback on the issues and the suggested solutions.

Please note that the open issues are related to the IETF WIS MIB proposal, and do not affect the text of the 802.3ae standard.

Comments are welcome on the 802.3ae reflector and/or on the IETF WG list hubmib@ietf.org. 

I intent to ask the Chair of IEEE 802.3ae to allocate a slot at the Raleigh Interim meeting for the presentation and discussions of the status of the WIS MIB work.

Regards, 

Dan 

Dan Romascanu, 
Chair, IETF Ethernet Interfaces and Hub MIB WG 
  


------_=_NextPart_001_01C18F07.CC7C3640
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>FW: WIS MIB list of open issues and recommendations for resolution</TITLE>

<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001>Dan,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Thanks 
for the clarification. I believe I understand the issue now.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Roy, 
it looks like Dan's explanation is in general agreement with the point you 
made</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>in 
your e-mail as well. The WIS and SONET/SDH MIBs are being kept separate 
for</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>the 
reasons you mentioned.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Best 
regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>- 
Tom</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Romascanu, Dan (Dan) 
  [mailto:dromasca@avaya.com]<BR><B>Sent:</B> Wednesday, December 26, 2001 10:46 
  PM<BR><B>To:</B> Tom Alexander; HSSG Reflector (E-mail)<BR><B>Cc:</B> C. M. 
  Heard; hubmib@ietf.org<BR><B>Subject:</B> RE: [802.3ae] FW: WIS MIB list of 
  open issues and recommendations for resolution<BR><BR></DIV></FONT>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Tom,</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial size=2>The 
  problem is that some of the objects that the authors of the SONET MIB decided 
  that may remain optional for their management model are mandatory for a full 
  definition and understanding of the WIS interface behavior. This is the reason 
  for defining a separate compliance statement that is stricter than the 
  compliance statement for a 'regular' SONET MIB 
  implementation.</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial size=2>The 
  minutes of the Salt Lake City meeting will be soon out. There was not much 
  controversy on this issue, the resolution being that the editors will document 
  their decision so that the later implementers of the standard can understand 
  the rationale of the path that was taken.</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Dan</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Tom Alexander 
    [mailto:Tom_Alexander@pmc-sierra.com]<BR><B>Sent:</B> Thursday, December 27, 
    2001 4:26 AM<BR><B>To:</B> Romascanu, Dan (Dan); HSSG Reflector 
    (E-mail)<BR><B>Cc:</B> C. M. Heard<BR><B>Subject:</B> RE: [802.3ae] FW: WIS 
    MIB list of open issues and recommendations for 
    resolution<BR><BR></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>Dan,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>The recommendations to the issues you mentioned 
    look reasonable to me;</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>however, I did have a question on the third issue 
    you raised (compliance statements</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>and optional/mandatory groups). The general intent 
    of the WIS was to implement</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>a 
    perfect subset of SONET/SDH. Therefore, should not the MIB object 
    groups</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>likewise</SPAN></FONT><FONT color=#0000ff 
    face=Arial size=2><SPAN class=414561802-27122001> represent a perfect subset 
    of the SONET MIB object groups? That is,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>optional</SPAN></FONT><FONT color=#0000ff 
    face=Arial size=2><SPAN class=414561802-27122001> SONET MIB objects should 
    either be omitted entirely, or remain optional</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>in 
    the</SPAN></FONT><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001> WIS MIB?</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>I 
    have not read the minutes of the IETF Plenary, so apologies in advance if I 
    have</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>inadvertently re-hashed something that should have 
    been obvious.</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>Thanks, and best regards,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>- 
    Tom Alexander</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>WIS Scribe</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <BLOCKQUOTE style="MARGIN-RIGHT: 0px">
      <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Romascanu, Dan (Dan) 
      [mailto:dromasca@avaya.com]<BR><B>Sent:</B> Wednesday, December 26, 2001 
      7:36 AM<BR><B>To:</B> HSSG Reflector (E-mail)<BR><B>Cc:</B> C. M. 
      Heard<BR><B>Subject:</B> [802.3ae] FW: WIS MIB list of open issues and 
      recommendations for resolution<BR><BR></DIV></FONT><!-- Converted from text/plain format -->
      <P><FONT size=2>The IETF Ethernet Interfaces and Hub MIB WG met during the 
      IETF Plenary meeting in Salt Lake City in the week of 12/10. One of the 
      items in the WG Charter that was discussed during the meeting was the 
      latest WIS MIB <A 
      href="http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt</A>.</FONT></P>
      <P><FONT size=2>The WG identified a list of four open issues, and 
      recommended solutions for their resolution. It was established during the 
      meeting that it would be appropriate if these issues would also be 
      published on the IEEE 802.3ae reflector, so that interested IEEE 
      participants can provide feedback on the issues and the suggested 
      solutions.</FONT></P>
      <P><FONT size=2>Please note that the open issues are related to the IETF 
      WIS MIB proposal, and do not affect the text of the 802.3ae 
      standard.</FONT></P>
      <P><FONT size=2>Comments are welcome on the 802.3ae reflector and/or on 
      the IETF WG list hubmib@ietf.org.</FONT> </P>
      <P><FONT size=2>I intent to ask the Chair of IEEE 802.3ae to allocate a 
      slot at the Raleigh Interim meeting for the presentation and discussions 
      of the status of the WIS MIB work.</FONT></P>
      <P><FONT size=2>Regards,</FONT> </P>
      <P><FONT size=2>Dan</FONT> </P>
      <P><FONT size=2>Dan Romascanu,</FONT> <BR><FONT size=2>Chair, IETF 
      Ethernet Interfaces and Hub MIB WG</FONT> <BR><FONT size=2>&nbsp;</FONT> 
      </P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C18F07.CC7C3640--


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From hubmib-admin@ietf.org  Wed Jan  2 14:58:06 2002
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 OAA09659
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:58:06 -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 OAA18894;
	Wed, 2 Jan 2002 14:50:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA29458
	for <hubmib@optimus.ietf.org>; Mon, 31 Dec 2001 13:09:30 -0500 (EST)
Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05775
	for <hubmib@ietf.org>; Mon, 31 Dec 2001 13:09:28 -0500 (EST)
Received: from 1cust79.tnt5.plano.tx.da.uu.net ([67.202.70.79] helo=RABHPNOTEBK.mindspring.com)
	by hall.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16L6sB-0002Ep-00; Mon, 31 Dec 2001 13:09:20 -0500
Message-Id: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 31 Dec 2001 12:08:34 -0600
To: "C. M. Heard" <heard@pobox.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <Pine.LNX.4.10.10112310819350.25400-100000@shell4.bayarea.n
 et>
References: <B513C2E3B290D41185CA00306E0070FE451BD2@pld1exm01.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and
 recommendations for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

Because there is becoming a likely hood that the WIS overhead definition 
will be adopted as a separate functional optical link protocol for optical 
switched networks, I would like to see more of a divorce between the WIS 
MIB and SONET.  By making references to the SONET MIB, there is still the 
perception that the WIS is part of SONET.  It is not.  Neither is it part 
of SDH.   I would like to see a totally separate set of definitions for the 
WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I 
think that it should be on a separate AIN branch from SONET or SDH.

Because of developments that are taking place in T1X1 and ITU regarding the 
development of a "path relay" type of "Lite LTE" or as it is known to 
802.3ae an "ELTE" as a standard, it will be better that these two MIBs not 
have references to each other.  The proposed "path relay" may well have two 
separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also 
likely be part of actively managed wavelength transponders, which may be a 
lot less expensive than current LTEs or the proposed Digital Wrapper 
systems.  Over a period of time, this would make the WIS MIB a part of a 
much larger market than it has been previously believed.

Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if 
there are objects in the WIS MIB that may have the same function, and 
possibly the same "text", as objects in the SONET or SDH MIBs, they should 
be separate and inclusive within themselves.

Thank you,
Roy Bynum
Orbital View LLC

At 09:37 AM 12/31/2001 -0800, C. M. Heard wrote:
>On Thu, 27 Dec 2001, Tom Alexander wrote:
> > Roy, it looks like Dan's explanation is in general agreement with
> > the point you made in your e-mail as well. The WIS and SONET/SDH
> > MIBs are being kept separate for the reasons you mentioned.
>
>On Thu, 27 Dec 2001, Roy Bynum wrote:
> > I would take a different tack on the issue of "optional" WIS MIB
> > items.  I would prefer the stance that the MIB for the WIS is
> > restricted to the items that are included in the current draft,
> > and not include any additional "SONET" or "SDH" MIB items.  SONET
> > and SDH are specific and different protocol standards from 802.3ae.
> > The IETF should not confuse these standards, as they originate from
> > very different standards organizations[,] by trying to get creative
> > with the MIB definition for 802.3ae.
>
>On Thu, 27 Dec 2001, Dan Romascanu wrote:
> > The problem is that some of the objects that the authors of the
> > SONET MIB decided that may remain optional for their management
> > model are mandatory for a full definition and understanding of
> > the WIS interface behavior.  This is the reason for defining a
> > separate compliance statement that is stricter than the
> > compliance statement for a 'regular' SONET MIB implementation.
>
>Further elaboration may be helpful.  The draft SNMP WIS MIB in
>http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt
>defines some new WIS-specific objects but also incorporates by
>reference a specific subset of the objects in the SONET/SDH MIB.
>That subset of course exludes objects that are not relevent to the
>WIS (e.g. objects for managing SONET VTs), but it also includes as
>mandatory objects some that are considered conditionally mandatory
>or optional in the SONET/SDH MIB compliance statement (e.g. near-
>and far-end line and path layer objects).  All items listed in the
>draft SNMP WIS MIB compliance statement are mandatory, including both
>those that map to objects in the 802.3ae pWISBasic package and those
>that map to objects in the pWISOptional package (see Section 3.6 of
>the draft for details).  It was the consensus of the design team (and
>of the meeting participants at Salt Lake City) that all these objects
>need to be present to ensure effective management of the WIS.
>
>Regards (and best wishes for 2002),
>
>Mike Heard



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Wed Jan  2 14:58:06 2002
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 OAA09670
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:58:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19280
	for hubmib-archive@odin.ietf.org; Wed, 2 Jan 2002 14:58:08 -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 OAA18894;
	Wed, 2 Jan 2002 14:50:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA29458
	for <hubmib@optimus.ietf.org>; Mon, 31 Dec 2001 13:09:30 -0500 (EST)
Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05775
	for <hubmib@ietf.org>; Mon, 31 Dec 2001 13:09:28 -0500 (EST)
Received: from 1cust79.tnt5.plano.tx.da.uu.net ([67.202.70.79] helo=RABHPNOTEBK.mindspring.com)
	by hall.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16L6sB-0002Ep-00; Mon, 31 Dec 2001 13:09:20 -0500
Message-Id: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 31 Dec 2001 12:08:34 -0600
To: "C. M. Heard" <heard@pobox.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <Pine.LNX.4.10.10112310819350.25400-100000@shell4.bayarea.n
 et>
References: <B513C2E3B290D41185CA00306E0070FE451BD2@pld1exm01.pmc-sierra.bc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and
 recommendations for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

Because there is becoming a likely hood that the WIS overhead definition 
will be adopted as a separate functional optical link protocol for optical 
switched networks, I would like to see more of a divorce between the WIS 
MIB and SONET.  By making references to the SONET MIB, there is still the 
perception that the WIS is part of SONET.  It is not.  Neither is it part 
of SDH.   I would like to see a totally separate set of definitions for the 
WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I 
think that it should be on a separate AIN branch from SONET or SDH.

Because of developments that are taking place in T1X1 and ITU regarding the 
development of a "path relay" type of "Lite LTE" or as it is known to 
802.3ae an "ELTE" as a standard, it will be better that these two MIBs not 
have references to each other.  The proposed "path relay" may well have two 
separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also 
likely be part of actively managed wavelength transponders, which may be a 
lot less expensive than current LTEs or the proposed Digital Wrapper 
systems.  Over a period of time, this would make the WIS MIB a part of a 
much larger market than it has been previously believed.

Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if 
there are objects in the WIS MIB that may have the same function, and 
possibly the same "text", as objects in the SONET or SDH MIBs, they should 
be separate and inclusive within themselves.

Thank you,
Roy Bynum
Orbital View LLC

At 09:37 AM 12/31/2001 -0800, C. M. Heard wrote:
>On Thu, 27 Dec 2001, Tom Alexander wrote:
> > Roy, it looks like Dan's explanation is in general agreement with
> > the point you made in your e-mail as well. The WIS and SONET/SDH
> > MIBs are being kept separate for the reasons you mentioned.
>
>On Thu, 27 Dec 2001, Roy Bynum wrote:
> > I would take a different tack on the issue of "optional" WIS MIB
> > items.  I would prefer the stance that the MIB for the WIS is
> > restricted to the items that are included in the current draft,
> > and not include any additional "SONET" or "SDH" MIB items.  SONET
> > and SDH are specific and different protocol standards from 802.3ae.
> > The IETF should not confuse these standards, as they originate from
> > very different standards organizations[,] by trying to get creative
> > with the MIB definition for 802.3ae.
>
>On Thu, 27 Dec 2001, Dan Romascanu wrote:
> > The problem is that some of the objects that the authors of the
> > SONET MIB decided that may remain optional for their management
> > model are mandatory for a full definition and understanding of
> > the WIS interface behavior.  This is the reason for defining a
> > separate compliance statement that is stricter than the
> > compliance statement for a 'regular' SONET MIB implementation.
>
>Further elaboration may be helpful.  The draft SNMP WIS MIB in
>http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt
>defines some new WIS-specific objects but also incorporates by
>reference a specific subset of the objects in the SONET/SDH MIB.
>That subset of course exludes objects that are not relevent to the
>WIS (e.g. objects for managing SONET VTs), but it also includes as
>mandatory objects some that are considered conditionally mandatory
>or optional in the SONET/SDH MIB compliance statement (e.g. near-
>and far-end line and path layer objects).  All items listed in the
>draft SNMP WIS MIB compliance statement are mandatory, including both
>those that map to objects in the 802.3ae pWISBasic package and those
>that map to objects in the pWISOptional package (see Section 3.6 of
>the draft for details).  It was the consensus of the design team (and
>of the meeting participants at Salt Lake City) that all these objects
>need to be present to ensure effective management of the WIS.
>
>Regards (and best wishes for 2002),
>
>Mike Heard



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From daemon@ns.ietf.org  Wed Jan  2 15:54:31 2002
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 OAA09638
	for <hubmib-archive@odin.ietf.org>; Wed, 2 Jan 2002 14:56:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19242
	for hubmib-archive@odin.ietf.org; Wed, 2 Jan 2002 14:56:49 -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 OAA18885;
	Wed, 2 Jan 2002 14:50:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19597
	for <hubmib@optimus.ietf.org>; Thu, 27 Dec 2001 13:54:19 -0500 (EST)
Received: from father.pmc-sierra.bc.ca (father.pmc-sierra.bc.ca [216.241.224.13])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19694
	for <hubmib@ietf.org>; Thu, 27 Dec 2001 13:54:16 -0500 (EST)
Received: (qmail 15723 invoked by uid 104); 27 Dec 2001 18:53:42 -0000
Received: from Tom_Alexander@pmc-sierra.com by father with qmail-scanner-1.00 (uvscan: v4.1.40/v4178. . Clean. Processed in 0.53953 secs); 27 Dec 2001 18:53:42 -0000
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 27 Dec 2001 18:53:41 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (jason/8.11.6) with ESMTP id fBRIrfc29667;
	Thu, 27 Dec 2001 10:53:41 -0800 (PST)
Received: by bby1exi01 with Internet Mail Service (5.5.2653.19)
	id <XNRNZ6L7>; Thu, 27 Dec 2001 10:53:41 -0800
Message-ID: <B513C2E3B290D41185CA00306E0070FE451BD2@pld1exm01.pmc-sierra.bc.ca>
From: Tom Alexander <Tom_Alexander@pmc-sierra.com>
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>,
        "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>
Cc: "C. M. Heard" <heard@pobox.com>, hubmib@ietf.org,
        "'Roy Bynum'"
	 <rabynum@mindspring.com>
Date: Thu, 27 Dec 2001 10:53:40 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C18F07.CC7C3640"
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and recommendations
 for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
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_01C18F07.CC7C3640
Content-Type: text/plain;
	charset="iso-8859-1"

Dan,
 
Thanks for the clarification. I believe I understand the issue now.
 
Roy, it looks like Dan's explanation is in general agreement with the point you made
in your e-mail as well. The WIS and SONET/SDH MIBs are being kept separate for
the reasons you mentioned.
 
Best regards,
 
- Tom

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Wednesday, December 26, 2001 10:46 PM
To: Tom Alexander; HSSG Reflector (E-mail)
Cc: C. M. Heard; hubmib@ietf.org
Subject: RE: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution


Tom,
 
The problem is that some of the objects that the authors of the SONET MIB decided that may remain optional for their management model are mandatory for a full definition and understanding of the WIS interface behavior. This is the reason for defining a separate compliance statement that is stricter than the compliance statement for a 'regular' SONET MIB implementation.
 
The minutes of the Salt Lake City meeting will be soon out. There was not much controversy on this issue, the resolution being that the editors will document their decision so that the later implementers of the standard can understand the rationale of the path that was taken.
 
Regards,
 
Dan
 

-----Original Message-----
From: Tom Alexander [mailto:Tom_Alexander@pmc-sierra.com]
Sent: Thursday, December 27, 2001 4:26 AM
To: Romascanu, Dan (Dan); HSSG Reflector (E-mail)
Cc: C. M. Heard
Subject: RE: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution


Dan,
 
The recommendations to the issues you mentioned look reasonable to me;
however, I did have a question on the third issue you raised (compliance statements
and optional/mandatory groups). The general intent of the WIS was to implement
a perfect subset of SONET/SDH. Therefore, should not the MIB object groups
likewise represent a perfect subset of the SONET MIB object groups? That is,
optional SONET MIB objects should either be omitted entirely, or remain optional
in the WIS MIB?
 
I have not read the minutes of the IETF Plenary, so apologies in advance if I have
inadvertently re-hashed something that should have been obvious.
 
Thanks, and best regards,
 
- Tom Alexander
WIS Scribe
 

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Wednesday, December 26, 2001 7:36 AM
To: HSSG Reflector (E-mail)
Cc: C. M. Heard
Subject: [802.3ae] FW: WIS MIB list of open issues and recommendations for resolution



The IETF Ethernet Interfaces and Hub MIB WG met during the IETF Plenary meeting in Salt Lake City in the week of 12/10. One of the items in the WG Charter that was discussed during the meeting was the latest WIS MIB http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt <http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt> .

The WG identified a list of four open issues, and recommended solutions for their resolution. It was established during the meeting that it would be appropriate if these issues would also be published on the IEEE 802.3ae reflector, so that interested IEEE participants can provide feedback on the issues and the suggested solutions.

Please note that the open issues are related to the IETF WIS MIB proposal, and do not affect the text of the 802.3ae standard.

Comments are welcome on the 802.3ae reflector and/or on the IETF WG list hubmib@ietf.org. 

I intent to ask the Chair of IEEE 802.3ae to allocate a slot at the Raleigh Interim meeting for the presentation and discussions of the status of the WIS MIB work.

Regards, 

Dan 

Dan Romascanu, 
Chair, IETF Ethernet Interfaces and Hub MIB WG 
  


------_=_NextPart_001_01C18F07.CC7C3640
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>FW: WIS MIB list of open issues and recommendations for resolution</TITLE>

<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001>Dan,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Thanks 
for the clarification. I believe I understand the issue now.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Roy, 
it looks like Dan's explanation is in general agreement with the point you 
made</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>in 
your e-mail as well. The WIS and SONET/SDH MIBs are being kept separate 
for</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>the 
reasons you mentioned.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>Best 
regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=578585118-27122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=578585118-27122001>- 
Tom</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Romascanu, Dan (Dan) 
  [mailto:dromasca@avaya.com]<BR><B>Sent:</B> Wednesday, December 26, 2001 10:46 
  PM<BR><B>To:</B> Tom Alexander; HSSG Reflector (E-mail)<BR><B>Cc:</B> C. M. 
  Heard; hubmib@ietf.org<BR><B>Subject:</B> RE: [802.3ae] FW: WIS MIB list of 
  open issues and recommendations for resolution<BR><BR></DIV></FONT>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Tom,</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial size=2>The 
  problem is that some of the objects that the authors of the SONET MIB decided 
  that may remain optional for their management model are mandatory for a full 
  definition and understanding of the WIS interface behavior. This is the reason 
  for defining a separate compliance statement that is stricter than the 
  compliance statement for a 'regular' SONET MIB 
  implementation.</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial size=2>The 
  minutes of the Salt Lake City meeting will be soon out. There was not much 
  controversy on this issue, the resolution being that the editors will document 
  their decision so that the later implementers of the standard can understand 
  the rationale of the path that was taken.</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2>Dan</FONT></SPAN></DIV>
  <DIV><SPAN class=289283806-27122001><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Tom Alexander 
    [mailto:Tom_Alexander@pmc-sierra.com]<BR><B>Sent:</B> Thursday, December 27, 
    2001 4:26 AM<BR><B>To:</B> Romascanu, Dan (Dan); HSSG Reflector 
    (E-mail)<BR><B>Cc:</B> C. M. Heard<BR><B>Subject:</B> RE: [802.3ae] FW: WIS 
    MIB list of open issues and recommendations for 
    resolution<BR><BR></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>Dan,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>The recommendations to the issues you mentioned 
    look reasonable to me;</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>however, I did have a question on the third issue 
    you raised (compliance statements</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>and optional/mandatory groups). The general intent 
    of the WIS was to implement</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>a 
    perfect subset of SONET/SDH. Therefore, should not the MIB object 
    groups</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>likewise</SPAN></FONT><FONT color=#0000ff 
    face=Arial size=2><SPAN class=414561802-27122001> represent a perfect subset 
    of the SONET MIB object groups? That is,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>optional</SPAN></FONT><FONT color=#0000ff 
    face=Arial size=2><SPAN class=414561802-27122001> SONET MIB objects should 
    either be omitted entirely, or remain optional</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>in 
    the</SPAN></FONT><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001> WIS MIB?</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>I 
    have not read the minutes of the IETF Plenary, so apologies in advance if I 
    have</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>inadvertently re-hashed something that should have 
    been obvious.</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>Thanks, and best regards,</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN class=414561802-27122001>- 
    Tom Alexander</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001>WIS Scribe</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=414561802-27122001></SPAN></FONT>&nbsp;</DIV>
    <BLOCKQUOTE style="MARGIN-RIGHT: 0px">
      <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
      size=2>-----Original Message-----<BR><B>From:</B> Romascanu, Dan (Dan) 
      [mailto:dromasca@avaya.com]<BR><B>Sent:</B> Wednesday, December 26, 2001 
      7:36 AM<BR><B>To:</B> HSSG Reflector (E-mail)<BR><B>Cc:</B> C. M. 
      Heard<BR><B>Subject:</B> [802.3ae] FW: WIS MIB list of open issues and 
      recommendations for resolution<BR><BR></DIV></FONT><!-- Converted from text/plain format -->
      <P><FONT size=2>The IETF Ethernet Interfaces and Hub MIB WG met during the 
      IETF Plenary meeting in Salt Lake City in the week of 12/10. One of the 
      items in the WG Charter that was discussed during the meeting was the 
      latest WIS MIB <A 
      href="http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt</A>.</FONT></P>
      <P><FONT size=2>The WG identified a list of four open issues, and 
      recommended solutions for their resolution. It was established during the 
      meeting that it would be appropriate if these issues would also be 
      published on the IEEE 802.3ae reflector, so that interested IEEE 
      participants can provide feedback on the issues and the suggested 
      solutions.</FONT></P>
      <P><FONT size=2>Please note that the open issues are related to the IETF 
      WIS MIB proposal, and do not affect the text of the 802.3ae 
      standard.</FONT></P>
      <P><FONT size=2>Comments are welcome on the 802.3ae reflector and/or on 
      the IETF WG list hubmib@ietf.org.</FONT> </P>
      <P><FONT size=2>I intent to ask the Chair of IEEE 802.3ae to allocate a 
      slot at the Raleigh Interim meeting for the presentation and discussions 
      of the status of the WIS MIB work.</FONT></P>
      <P><FONT size=2>Regards,</FONT> </P>
      <P><FONT size=2>Dan</FONT> </P>
      <P><FONT size=2>Dan Romascanu,</FONT> <BR><FONT size=2>Chair, IETF 
      Ethernet Interfaces and Hub MIB WG</FONT> <BR><FONT size=2>&nbsp;</FONT> 
      </P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C18F07.CC7C3640--


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Thu Jan  3 21:57:16 2002
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 VAA16584
	for <hubmib-archive@odin.ietf.org>; Thu, 3 Jan 2002 21:57:16 -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 VAA28234;
	Thu, 3 Jan 2002 21:56:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA27045
	for <hubmib@optimus.ietf.org>; Thu, 3 Jan 2002 20:42:17 -0500 (EST)
Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14892
	for <hubmib@ietf.org>; Thu, 3 Jan 2002 20:42:13 -0500 (EST)
Received: from crtntx1-ar4-4-34-248-233.elnk.dsl.gtei.net ([4.34.248.233] helo=RABHPNOTEBK.mindspring.com)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16MJMt-0000xI-00; Thu, 03 Jan 2002 20:41:59 -0500
Message-Id: <5.1.0.14.2.20020103190259.00b618e8@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 03 Jan 2002 19:41:44 -0600
To: "C. M. Heard" <heard@pobox.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <Pine.LNX.4.10.10201010840350.4754-100000@shell4.bayarea.ne
 t>
References: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and
 recommendations for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Dan,

The POS and other SONET MIB standards were defined before T1.416-1999 was 
published.  Prior to T1.416-1999 there was not a specific and different 
"client" interface for "SONET like" transmission interfaces.  Even within 
this context T1.416.1999 was referenced only to provide an operational 
context for the overhead bytes that were defined and to give a 
justification for not defining a SONET interface within the WIS.  Also, the 
WIS is unique in the use of the existing format for a data originating 
interface in a way that has never been recognized until now.   It might be 
noted that unlike T1.416-1999, the WIS is not a "client" interface, it is a 
"peer" service interface.

Thank you,
Roy Bynum


At 09:22 AM 1/2/2002 -0800, C. M. Heard wrote:
>On Mon, 31 Dec 2001, Roy Bynum wrote:
> > Because there is becoming a likely hood that the WIS overhead definition
> > will be adopted as a separate functional optical link protocol for optical
> > switched networks, I would like to see more of a divorce between the WIS
> > MIB and SONET.  By making references to the SONET MIB, there is still the
> > perception that the WIS is part of SONET.  It is not.  Neither is it part
> > of SDH.   I would like to see a totally separate set of definitions for the
> > WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I
> > think that it should be on a separate AIN branch from SONET or SDH.
>
>Although the WIS is not a subset of SONET or SDH, it does use the same
>frame structure as SONET, as is explicitly stated in the following
>excerpt from 802.3ae subclause 50.1.1:
>
>   "The WIS maps the encoded Ethernet data received (transmitted) from (to)
>    the PCS into a frame structure that has the same format as that defined
>    by T1.416-1999, implementing a minimal number of the standard SONET
>    overhead fields and functions.  The WIS does not adhere to the electrical
>    and optical aspects of SONET specified by T1.416-1999, as it is intended
>    to be used with PHYs that conform to the corresponding parameters defined
>    by the 10GBASE-W standard."
>
>A consequence of this fact is that the objects in the SONET-MIB's
>sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2,
>sonetFarEndLineStuff2, sonetPathStuff2, and sonetFarEndPathStuff2
>object groups are valid for the WIS, although only a subset of the
>possible values apply for some of the objects.  Furthermore, these
>objects are already used in systems where 10 Gb/s Ethernet interfaces
>likely to be deployed, and this argues strongly for re-use of these
>objects.  Two specific examples of such systems are:
>
>(a) Routers.  It's common now for PoS (PPP over SONET) and ATM over
>SONET to be used on a router's WAN interfaces, and the standard means
>for managing the SONET sublayers is the SONET-MIB.  Both management
>applications and agents exist that know how to deal with it.  Using
>the SONET-MIB to manage the WIS would be a way to leverage on that
>technology.
>
>(b) SONET transport NEs.  It's common for such NEs to have non-SONET
>interfaces, i.e., line cards that map non-SONET signals (such as DS3)
>into SONET payloads and that perform SONET multiplexing.  A 10GBASE-W
>Ethernet interface would technically be a non-SONET interface (since
>the optical specs and jitter specs are not SONET-compliant), but thanks
>to the use of the WIS there is no format conversion in the payload
>mapping.  If such an NE offers an SNMP management interface, then the
>SONET-MIB is once again the standard way to manage the SONET interfaces.
>Using the SONET-MIB to manage 10GBASE-W tributary interfaces would be
>a win in this case, too.
>
> > Because of developments that are taking place in T1X1 and ITU regarding the
> > development of a "path relay" type of "Lite LTE" or as it is known to
> > 802.3ae an "ELTE" as a standard, it will be better that these two MIBs not
> > have references to each other.  The proposed "path relay" may well have two
> > separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also
> > likely be part of actively managed wavelength transponders, which may be a
> > lot less expensive than current LTEs or the proposed Digital Wrapper
> > systems.  Over a period of time, this would make the WIS MIB a part of a
> > much larger market than it has been previously believed.
>
>The path relay function is in no way unique to ELTE but exists in any
>any network element that contains LTE -- in other words, it exists in
>any network element that strips off section and line overhead and
>extracts the Synchronous Payload Envelope (SPE) at one interface and
>inserts that SPE into a different SONET frame (with newly generated
>section and line overhead) at another interface.  A typical realization
>of ELTE in a SONET ADM would be a 10GBASE-W tributary interface, which
>would differ from an OC-192c tributary interface in using different
>optics and complying with different jitter specs, but would be essentially
>the same in its processing of the section and line overhead.  Thus, the
>SONET-MIB's sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, and
>sonetFarEndLineStuff2 object groups can be used to manage a 10GBASE-W
>tributary interface just as well as they can be used to manage an OC-192c
>tributary interface.  [Note, however, that the proposed WIS MIB does not
>address the management of ELTE, which only contains a subset of the WIS.
>This was considered out-of-scope for the present standardization effort.]
>
> > Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if
> > there are objects in the WIS MIB that may have the same function, and
> > possibly the same "text", as objects in the SONET or SDH MIBs, they should
> > be separate and inclusive within themselves.
>
>To many of us it is anathema to duplicate the definitions of managed
>objects in different MIB modules for exactly the same reason that people
>frown on cloning text from one standard to another.  802.3ae incorporates
>by reference the appropriate definitions from T1.416-1999 rather than
>cloning the text.  Similarly, the proposed WIS MIB incorporates by
>reference applicable objects from the SONET-MIB.  The same reasons for
>doing so apply in both cases.
>
>Thanks,
>
>Mike



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Thu Jan  3 21:57:17 2002
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 VAA16596
	for <hubmib-archive@odin.ietf.org>; Thu, 3 Jan 2002 21:57:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA28271
	for hubmib-archive@odin.ietf.org; Thu, 3 Jan 2002 21:57:20 -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 VAA28234;
	Thu, 3 Jan 2002 21:56:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA27045
	for <hubmib@optimus.ietf.org>; Thu, 3 Jan 2002 20:42:17 -0500 (EST)
Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14892
	for <hubmib@ietf.org>; Thu, 3 Jan 2002 20:42:13 -0500 (EST)
Received: from crtntx1-ar4-4-34-248-233.elnk.dsl.gtei.net ([4.34.248.233] helo=RABHPNOTEBK.mindspring.com)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16MJMt-0000xI-00; Thu, 03 Jan 2002 20:41:59 -0500
Message-Id: <5.1.0.14.2.20020103190259.00b618e8@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 03 Jan 2002 19:41:44 -0600
To: "C. M. Heard" <heard@pobox.com>,
        Tom Alexander <Tom_Alexander@pmc-sierra.com>,
        Dan Romascanu <dromasca@avaya.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: "HSSG Reflector (E-mail)" <stds-802-3-hssg@ieee.org>, hubmib@ietf.org
In-Reply-To: <Pine.LNX.4.10.10201010840350.4754-100000@shell4.bayarea.ne
 t>
References: <5.1.0.14.2.20011231115227.00b611d0@pop.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] RE: [802.3ae] FW: WIS MIB list of open issues and
 recommendations for resolution
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Dan,

The POS and other SONET MIB standards were defined before T1.416-1999 was 
published.  Prior to T1.416-1999 there was not a specific and different 
"client" interface for "SONET like" transmission interfaces.  Even within 
this context T1.416.1999 was referenced only to provide an operational 
context for the overhead bytes that were defined and to give a 
justification for not defining a SONET interface within the WIS.  Also, the 
WIS is unique in the use of the existing format for a data originating 
interface in a way that has never been recognized until now.   It might be 
noted that unlike T1.416-1999, the WIS is not a "client" interface, it is a 
"peer" service interface.

Thank you,
Roy Bynum


At 09:22 AM 1/2/2002 -0800, C. M. Heard wrote:
>On Mon, 31 Dec 2001, Roy Bynum wrote:
> > Because there is becoming a likely hood that the WIS overhead definition
> > will be adopted as a separate functional optical link protocol for optical
> > switched networks, I would like to see more of a divorce between the WIS
> > MIB and SONET.  By making references to the SONET MIB, there is still the
> > perception that the WIS is part of SONET.  It is not.  Neither is it part
> > of SDH.   I would like to see a totally separate set of definitions for the
> > WIS MIB, not references to the SONET MIB or to the SDH MIB.  Personally, I
> > think that it should be on a separate AIN branch from SONET or SDH.
>
>Although the WIS is not a subset of SONET or SDH, it does use the same
>frame structure as SONET, as is explicitly stated in the following
>excerpt from 802.3ae subclause 50.1.1:
>
>   "The WIS maps the encoded Ethernet data received (transmitted) from (to)
>    the PCS into a frame structure that has the same format as that defined
>    by T1.416-1999, implementing a minimal number of the standard SONET
>    overhead fields and functions.  The WIS does not adhere to the electrical
>    and optical aspects of SONET specified by T1.416-1999, as it is intended
>    to be used with PHYs that conform to the corresponding parameters defined
>    by the 10GBASE-W standard."
>
>A consequence of this fact is that the objects in the SONET-MIB's
>sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2,
>sonetFarEndLineStuff2, sonetPathStuff2, and sonetFarEndPathStuff2
>object groups are valid for the WIS, although only a subset of the
>possible values apply for some of the objects.  Furthermore, these
>objects are already used in systems where 10 Gb/s Ethernet interfaces
>likely to be deployed, and this argues strongly for re-use of these
>objects.  Two specific examples of such systems are:
>
>(a) Routers.  It's common now for PoS (PPP over SONET) and ATM over
>SONET to be used on a router's WAN interfaces, and the standard means
>for managing the SONET sublayers is the SONET-MIB.  Both management
>applications and agents exist that know how to deal with it.  Using
>the SONET-MIB to manage the WIS would be a way to leverage on that
>technology.
>
>(b) SONET transport NEs.  It's common for such NEs to have non-SONET
>interfaces, i.e., line cards that map non-SONET signals (such as DS3)
>into SONET payloads and that perform SONET multiplexing.  A 10GBASE-W
>Ethernet interface would technically be a non-SONET interface (since
>the optical specs and jitter specs are not SONET-compliant), but thanks
>to the use of the WIS there is no format conversion in the payload
>mapping.  If such an NE offers an SNMP management interface, then the
>SONET-MIB is once again the standard way to manage the SONET interfaces.
>Using the SONET-MIB to manage 10GBASE-W tributary interfaces would be
>a win in this case, too.
>
> > Because of developments that are taking place in T1X1 and ITU regarding the
> > development of a "path relay" type of "Lite LTE" or as it is known to
> > 802.3ae an "ELTE" as a standard, it will be better that these two MIBs not
> > have references to each other.  The proposed "path relay" may well have two
> > separate MIBs, or incorporate only the WIS MIB.  The "path relay" will also
> > likely be part of actively managed wavelength transponders, which may be a
> > lot less expensive than current LTEs or the proposed Digital Wrapper
> > systems.  Over a period of time, this would make the WIS MIB a part of a
> > much larger market than it has been previously believed.
>
>The path relay function is in no way unique to ELTE but exists in any
>any network element that contains LTE -- in other words, it exists in
>any network element that strips off section and line overhead and
>extracts the Synchronous Payload Envelope (SPE) at one interface and
>inserts that SPE into a different SONET frame (with newly generated
>section and line overhead) at another interface.  A typical realization
>of ELTE in a SONET ADM would be a 10GBASE-W tributary interface, which
>would differ from an OC-192c tributary interface in using different
>optics and complying with different jitter specs, but would be essentially
>the same in its processing of the section and line overhead.  Thus, the
>SONET-MIB's sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, and
>sonetFarEndLineStuff2 object groups can be used to manage a 10GBASE-W
>tributary interface just as well as they can be used to manage an OC-192c
>tributary interface.  [Note, however, that the proposed WIS MIB does not
>address the management of ELTE, which only contains a subset of the WIS.
>This was considered out-of-scope for the present standardization effort.]
>
> > Referencing any of the Existing SONET or SDH MIBs is a mistake.  Even if
> > there are objects in the WIS MIB that may have the same function, and
> > possibly the same "text", as objects in the SONET or SDH MIBs, they should
> > be separate and inclusive within themselves.
>
>To many of us it is anathema to duplicate the definitions of managed
>objects in different MIB modules for exactly the same reason that people
>frown on cloning text from one standard to another.  802.3ae incorporates
>by reference the appropriate definitions from T1.416-1999 rather than
>cloning the text.  Similarly, the proposed WIS MIB incorporates by
>reference applicable objects from the SONET-MIB.  The same reasons for
>doing so apply in both cases.
>
>Thanks,
>
>Mike



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Jan  8 04:57:47 2002
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 EAA18189
	for <hubmib-archive@odin.ietf.org>; Tue, 8 Jan 2002 04:57:46 -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 EAA22015;
	Tue, 8 Jan 2002 04:56:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21987
	for <hubmib@ns.ietf.org>; Tue, 8 Jan 2002 04:56:51 -0500 (EST)
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 EAA18177
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:56:49 -0500 (EST)
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 EAA03300
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:55:26 -0500 (EST)
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 EAA03272
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:55:25 -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_01C1982A.AD29B9B7"
Date: Tue, 8 Jan 2002 11:56:00 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D038@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Preliminary Minutes of the SLC Hubmib Meeting
Thread-Index: AcGYKshTjg6nfkqqTkW4FYwTNUZomQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Preliminary Minutes of the SLC Hubmib Meeting
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1982A.AD29B9B7
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the preliminary minutes of the SLC hubmib meeting.
Please send your comments and corrections, before I submit these. Thanks
to KC for the diligent note taking work.

Also, presenters are required to send their presentations to
minutes@ietf.org, for inclusion in the proceedings.

Regards,

Dan

HUBMIB WG  IETF 52,  Salt Lake City
Monday afternoon session II
Notes
K.C. - Minutes taker
Dan Romascanu  discussion leader

The agenda from the main agenda link is invalid.  IETF isn't concerned.
The real hubmib agenda can be found at:
http://www.ietf.org/ietf/01dec/hubmib.txt

*	IEEE 802.3 Status Report
*	two IEEE meetings since London
*	802.ae=20
*	draft 34 in ballot between 11/17 and 12/3
*	Sponsor Ballot to follow
*	Standard expected 3/02 and 6/02
*	802.3af
*	D3.0 in Ballot between 11/16 & 12/30
*	Standard expected between 9/02 and 11/02
*	Standard slightly behind time
*	Changes expected
*	802.3ah  (Ethernet first mile)
*	WG formed - 9/01
*	Four tracks:
*	=B7        Fiber p2p
*	=B7        Copper p2p
*	=B7        Fiber p2mp
*	=B7        OAM
*	Far from IETF involved still too early in IEEE
*	RFC=92s
*	1515 - should be obsolete by 2668 - was not.
*	2108
*	2665
*	2666
*	2668
*	Confusion is there due to duplication of rfc=92s.
*	Next rfc on MAU mib will obsolete 1515 and 2668
*	Need implementation reports.
*	Enterasys wanted some issues answered before they implement
implementation
*	reports.
*	Would be nice to get implementation reports of where
*	John Flick - Problems with hardware help decide that
non-essential items will not be discussed.

	*	Etherlike MIBS
			o	What do we do with the test oids now
that the table is gone? - Deprecate?
			o	What about multiple manager stations?=20
			o	rfc1229 Interfaces extensions
mib->rfc1273->deprecated for no implementations.  We now have test oids
not in use.  Recommended to deprecate and start a loopback test object.
Will post new object to mailing list.
			o	Is the IFMTU clear.  Someone requested
clarification to this, but it seems clear.  It was decided that the
person who doesn=92t understand it to give example.  It was decided to
leave as is until the person can produce the info.
			o	IfAdminStatus (down) needs to be
clarified  Mike Mcfadden brought up the issue in the bridge wg where
multiple vendors have multiple reactions to this.  Fiber was not tested.
There needs to be clarification needed from IEEE.  John will write text
to ask and Dan will make the request.
			o	issue on rfc1643 - 2 current versions of
the Ethernet mib. - do we move it to historic, full standard?  Should we
put in our current draft an explanation of why there are 2 drafts.  Some
vendors are using rfc1643 with private mibs.

	*	MAU MIB
			o	Some outstanding edits are still here.
There are some issues in the WIS MIB and SONET that will affect some
text.
			o	Some issues from the InterWorking labs
test summit may affect this.  We will have to wait until at least the
end of January to get its information. Do we wait?=20
			o	Issues that could come up are
misunderstanding in the implementation? Some packets and octets that
could have misunderstanding.  It was decided to wait for the test
summit.
			o	Some SONET entry in the ifStackEntry
stackables issues.  This goes along with the WIS MIB work.  Where do we
do the clarification?  Decided we would discuss this in the WIS mib
meeting.
			o	discussed the implementation of the
auto-negotiation duplex info.  Some are implementing the MAU mib as is.
Others are implementing this in the private mibs due to being
cumbersome.  GBIC swap may only be partly relevant to the configuration.
Use a enumerated integer for setting? This is what some people are
doing.  John had posted to the wg how HP is doing their proprietary mib
as a suggestion.
			o	Forcing the autonegotiation down
configuration came up.  Once again, not having implementation reports to
review against doesn=92t help solve the issue. We need more =
implementation
reports.  There are some vendors that have implemented the way as
written.
			o	Dan proposed that we do the updates to
the mib as posted previously by John as recommendation of the committee
and let people see it. Mike H. suggested some new oid=92s written to =
help
out with this.  People could help by reviewing the jack type
enumeration.


			o	Power MIB
			o	latest draft published November 2001
			o	Misc spelling and compile warning errors
were noted.
			o	Changes resulting from
IEEEportPortPowerPairs object deleted.
			o	Delete off option of the power port
detection control object
			o	add new objects to powerdetectionstatus
object.
			o	delete powerportclassificationobject
			o	update naming of objects
			o	Reviewed some implementation notes from
PowerDsine that will be added to next version.
			o	The IETF document status is stable. We
don=92t know what the IEEE is going to do. For this reason just respin =
the
draft and wait for the IEEE to go on.
			o	Last-call may happen in Feb 02 depending
on the IEEE.

The goal is to finish all for the IETF in Minneapolis. in March.

Goals and Milestones
Dec 01 - Gather implementation experience
Jan 02 - Issue revised drafts - Missed
Jan 02 - Forward drafts to AD/IESG - pushed to Feb.
Feb 02 - Last call in Feb.


------_=_NextPart_001_01C1982A.AD29B9B7
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Preliminary Minutes of the SLC Hubmib Meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please find attached the =
preliminary minutes of the SLC hubmib meeting. Please send your comments =
and corrections, before I submit these. Thanks to KC for the diligent =
note taking work.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Also, presenters are required =
to send their presentations to minutes@ietf.org, for inclusion in the =
proceedings.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">HUBMIB WG&nbsp; IETF =
52,&nbsp; Salt Lake City</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Monday afternoon =
session II</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Notes</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">K.C. - Minutes =
taker</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Dan Romascanu&nbsp; =
discussion leader</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">The agenda from the =
main agenda link is invalid.&nbsp; IETF isn't concerned.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">The real hubmib agenda =
can be found at:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New"><A =
HREF=3D"http://www.ietf.org/ietf/01dec/hubmib.txt">http://www.ietf.org/ie=
tf/01dec/hubmib.txt</A></FONT></P>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">IEEE 802.3 Status =
Report</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">two IEEE meetings =
since London</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">802.ae =
</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">draft 34 in =
ballot between 11/17 and 12/3</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Sponsor Ballot to =
follow</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard expected =
3/02 and 6/02</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3af</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">D3.0 in Ballot =
between 11/16 &amp; 12/30</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard expected =
between 9/02 and 11/02</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard slightly =
behind time</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Changes =
expected</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">802.3ah&nbsp; =
(Ethernet first mile)</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">WG formed - =
9/01</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Four =
tracks:</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fiber =
p2p</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Copper =
p2p</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fiber =
p2mp</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OAM</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Far from IETF =
involved still too early in IEEE</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">RFC=92s</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">1515 - should be =
obsolete by 2668 - was not.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2108</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2665</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2666</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2668</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Confusion is =
there due to duplication of rfc=92s.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Next rfc on MAU =
mib will obsolete 1515 and 2668</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Need =
implementation reports.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Enterasys wanted =
some issues answered before they implement =
implementation</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">reports.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Would be nice to =
get implementation reports of where</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">John Flick - =
Problems with hardware help decide that non-essential items will not be =
discussed.</FONT></LI></DIV>
<BR>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">Etherlike MIBS</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What do we do with the test =
oids now that the table is gone? - Deprecate?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What about multiple manager =
stations? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rfc1229 Interfaces extensions =
mib-&gt;rfc1273-&gt;deprecated for no implementations.&nbsp; We now have =
test oids not in use.&nbsp; Recommended to deprecate and start a =
loopback test object. Will post new object to mailing =
list.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the IFMTU clear.&nbsp; =
Someone requested clarification to this, but it seems clear.&nbsp; It =
was decided that the person who doesn=92t understand it to give =
example.&nbsp; It was decided to leave as is until the person can =
produce the info.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IfAdminStatus (down) needs to =
be clarified&nbsp; Mike Mcfadden brought up the issue in the bridge wg =
where multiple vendors have multiple reactions to this.&nbsp; Fiber was =
not tested.&nbsp; There needs to be clarification needed from =
IEEE.&nbsp; John will write text to ask and Dan will make the =
request.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; issue on rfc1643 - 2 current =
versions of the Ethernet mib. - do we move it to historic, full =
standard?&nbsp; Should we put in our current draft an explanation of why =
there are 2 drafts.&nbsp; Some vendors are using rfc1643 with private =
mibs.</FONT></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">MAU MIB</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some outstanding edits are =
still here.&nbsp; There are some issues in the WIS MIB and SONET that =
will affect some text.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some issues from the =
InterWorking labs test summit may affect this.&nbsp; We will have to =
wait until at least the end of January to get its information. Do we =
wait? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Issues that could come up are =
misunderstanding in the implementation? Some packets and octets that =
could have misunderstanding.&nbsp; It was decided to wait for the test =
summit.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some SONET entry in the =
ifStackEntry stackables issues.&nbsp; This goes along with the WIS MIB =
work.&nbsp; Where do we do the clarification?&nbsp; Decided we would =
discuss this in the WIS mib meeting.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussed the implementation =
of the auto-negotiation duplex info.&nbsp; Some are implementing the MAU =
mib as is.&nbsp; Others are implementing this in the private mibs due to =
being cumbersome.&nbsp; GBIC swap may only be partly relevant to the =
configuration.&nbsp; Use a enumerated integer for setting? This is what =
some people are doing.&nbsp; John had posted to the wg how HP is doing =
their proprietary mib as a suggestion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Forcing the autonegotiation =
down configuration came up.&nbsp; Once again, not having implementation =
reports to review against doesn=92t help solve the issue. We need more =
implementation reports.&nbsp; There are some vendors that have =
implemented the way as written.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dan proposed that we do the =
updates to the mib as posted previously by John as recommendation of the =
committee and let people see it. Mike H. suggested some new oid=92s =
written to help out with this.&nbsp; People could help by reviewing the =
jack type enumeration.</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Power MIB</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latest draft published =
November 2001</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Misc spelling and compile =
warning errors were noted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Changes resulting from =
IEEEportPortPowerPairs object deleted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Delete off option of the =
power port detection control object</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; add new objects to =
powerdetectionstatus object.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delete =
powerportclassificationobject</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; update naming of =
objects</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reviewed some implementation =
notes from PowerDsine that will be added to next =
version.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The IETF document status is =
stable. We don=92t know what the IEEE is going to do. For this reason =
just respin the draft and wait for the IEEE to go on.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last-call may happen in Feb =
02 depending on the IEEE.</FONT></SPAN></P>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The goal is to finish all for the IETF in Minneapolis. in =
March.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Goals and Milestones</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dec 01 - Gather implementation experience</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Issue revised drafts - Missed</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Forward drafts to AD/IESG - pushed to =
Feb.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Feb 02 - Last call in Feb.</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1982A.AD29B9B7--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From hubmib-admin@ietf.org  Tue Jan  8 05:09:17 2002
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 FAA18359
	for <hubmib-archive@odin.ietf.org>; Tue, 8 Jan 2002 05:09: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 FAA22637;
	Tue, 8 Jan 2002 05:08:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22605
	for <hubmib@ns.ietf.org>; Tue, 8 Jan 2002 05:08:51 -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 FAA18352
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:08:49 -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 g08A7Un01705
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:07:30 -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 g08A7TO01692
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:07:29 -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_01C1982C.58F8002C"
Date: Tue, 8 Jan 2002 12:07:58 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF53FEC@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Preliminary Minutes of the SLC Joint Meeting of hubmib and atommib
Thread-Index: AcGYLHQa1pdvUMGeSv2yBDriXTd7VQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Preliminary Minutes of the SLC Joint Meeting of hubmib and atommib
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1982C.58F8002C
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the preliminary minutes of the SLC joint meeting of
atommib and hubmib. Please send your comments and corrections, before I
submit these. Thanks to Orly and Kam for the diligent note taking work.
Also, presenters are required to send their presentations to
minutes@ietf.org, for inclusion in the proceedings.
Regards,
Dan



52 IETF, Salt Lake City
=20
Ethernet Interfaces and Hub MIB WG & AToM MIB WG (hubmib & atommib)

TUESDAY, December 11 at 1700-1800
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CHAIRS:	Dan Romascanu <dromasca@avaya.com>
		Faye Ly <fayely98@hotmail.com>
		Nathan Kohn <mvnk@lucent.com>

The Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB
(atommib) WG=20
held a joint meeting at the 52nd IETF in Salt Lake City. The main
purpose of=20
the meeting was to report on the work from the design team formed by
members=20
of the two WGs in order to provide recommendations for the WAN Interface

Sublayer (WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update
were=20
also presented. It was noted that the WIS MIB is depended on the SONET
MIB for=20
the STS-192c update. Therefore the updated SONET-MIB should be
republished in=20
time regardless it is republished with or without advancement.

The participants in the meeting approved the approach presented in the=20
Internet-Drafts issued by the Design Team. The participants in the
meeting=20
proposed that the design team be transformed into an editor team to
further=20
the document. The open issues posted by the design team and the
recommendations=20
for resolution from the discussion are listed below. These issues and
proposed=20
resolution will be posted to the two WG lists, and to the IEEE 802.3ae
list.=20
The Hub MIB WG chair will request a slot for a presentation of the work
and open=20
issues at the interim meeting of the IEEE in January 2002, in order to
receive=20
more feedback from the IEEE. If now special problems show up, the next
version of=20
the Internet-Draft is aimed for WG Last Call.

Summary:

1. Introductions and Agenda Bashing. Three topics were covered;

2. IEEE 802.3 Update / - Dan Romascanu.
Between London  IETF and SLC, there were two meetings of the 802.3ae
group.
Between the two meetings, people response to the documents and draft
3.4c
was out for ballot. Now it is time for Sponsor ballot. According to the
number of iterations the document went through, it looks like it should
be
closed by March time frame, or June the latest.
An interoperability test is expected for Bridge, VLAN, Interface, and
Ether-like MIB.  The result of the tests will provide feedback on
current
documents. This might cause a delay for other document submitting time
including WIS-MIB.

3. Results of AToMMIB's SONET-MIB status discussion /-  Mike Heard
A draft is ready, will be submitted next week. There are only few minor
changes. It is important to get the document published since WIS-MIB
depends
on it. There are no implementation reports of 2558, so if no progress
will
be shown in advancing the documents toward draft standard, it will be
published again as proposed.=20
The goal is to get reports by February.

4. Report from the Design Team and Open Issues for WIS MIB /-  KC
Norseth,
Mike Heard
There were three issues to resolve:
-What is the layering model and how should it be mapped to IF-MIB.
-How do we map SNMP objects to GDMO objects of WIS defined in 802.3ae
clause
30.
- How does the solution manage with ETH/RMON free running counters as
well
as 15 =20
 min interval  SONET counters.

The proposal is to use what exist in ETH, MAU and SONET, as much as
possible.

The WIS MIB can use many of the SONET table.
If Stack table should have the following: LLC, MAC, reconciliation, PHY
coding, Path, Line, Section and 802.3 WAN PMA/PMD.
The objects for PM are taken from 3 MIBS.
The solution needs no special HW beyond what is required in 802.3ae.

=B7	Not everyone in the team agreed to the layering model of having
Ethernet on top of SONET. The suggestion was to add a layer between
CSMACD
to SONET Path to indicate what kind of ETH over SONET payload mapping is
used.

Issues and Proposed Resolutions:=20

1. Layering Model:=20

Because the WIS payload mapping (i.e., 64B/66B encoded=20
Ehternet data mapped directly into the STS-192c payload capacity, with
C2=20
set to '00011010'b) is just one of several Ethernet over SONET payload=20
mappings, it has been suggested that an additional ifStackTable layer in

between ethernetCsmacd(6) and sonetPath(50) should be present to
indicate=20
what type of Ethernet over SONET payload mapping is being used. An
alternative=20
suggestion is to use ifMauType and ifMauDefaultType for this purpose.

Proposed Resolution: Keep the layering as currently defined in the=20
internet-draft and use ifMauType and ifMauDefaultType to indicate the
type=20
of Ethernet over SONET.

2. Compliance:=20

Should the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W

interfaces? An alternative would be to make them optional. In that case=20
10GBASE-W interfaces would require a multi-layer ifStackTable only if
ETHER-WIS=20
and SONET-MIB were supported; if not, then the usual single-layer model
would apply.

Proposed Resolution: Keep all the ETHER-WIS and SONET-MIB objects
mandatory as=20
currently defined in the internet-draft.

3. Relationship with MAU-MIB:=20

The next Mau-MIB draft should specify what happens to the ifStackTable
if=20
ifMauDefaultType is changed from dot3MauType10GigBaseR to
dot3MauType10GigBaseW=20
or vice-versa.

Proposed Resolution: The suggested was agreed. Mike Heard will provide
the=20
text to be added to the Mau-MIB.=20

4. Clarification on Compliance:=20

Clarification text for compliance description in Section 3.1 is needed.

Proposed Resolution: Mike Heard will provide the clarification text for=20
Section 3.1 regarding compliance.
It was decided to host the document in the HUBMIB group.

Internet Draft:
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis
-mib
-01.txt>



------_=_NextPart_001_01C1982C.58F8002C
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Preliminary Minutes of the SLC Joint Meeting of hubmib and =
atommib</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find attached the preliminary minutes of the SLC joint meeting of =
atommib and hubmib. Please send your comments and corrections, before I =
submit these. Thanks to Orly and Kam for the diligent note taking =
work.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Also, =
presenters are required to send their presentations to minutes@ietf.org, =
for inclusion in the proceedings.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>
<BR>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">52 IETF, =
Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
Interfaces and Hub MIB WG &amp; AToM MIB WG (hubmib &amp; =
atommib)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, =
December 11 at 1700-1800</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">CHAIRS: Dan =
Romascanu &lt;dromasca@avaya.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"he">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Faye Ly &lt;fayely98@hotmail.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"he">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Nathan Kohn &lt;mvnk@lucent.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB (atommib) WG =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">held a =
joint meeting at the 52nd IETF in Salt Lake City. The main purpose of =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the meeting =
was to report on the work from the design team formed by members =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">of the two =
WGs in order to provide recommendations for the WAN Interface =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Sublayer =
(WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update were =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">also =
presented. It was noted that the WIS MIB is depended on the SONET MIB =
for </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
STS-192c update. Therefore the updated SONET-MIB should be republished =
in </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">time =
regardless it is republished with or without =
advancement.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
participants in the meeting approved the approach presented in the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts issued by the Design Team. The =
participants in the meeting </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">proposed =
that the design team be transformed into an editor team to further =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
document. The open issues posted by the design team and the =
recommendations </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">for =
resolution from the discussion are listed below. These issues and =
proposed </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">resolution =
will be posted to the two WG lists, and to the IEEE 802.3ae list. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The Hub MIB =
WG chair will request a slot for a presentation of the work and open =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">issues at =
the interim meeting of the IEEE in January 2002, in order to receive =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">more =
feedback from the IEEE. If now special problems show up, the next =
version of </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
Internet-Draft is aimed for WG Last Call.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Summary:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Introductions and Agenda Bashing. Three topics were =
covered;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">2. IEEE =
802.3 Update / - Dan Romascanu.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Between =
London&nbsp; IETF and SLC, there were two meetings of the 802.3ae =
group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Between the =
two meetings, people response to the documents and draft =
3.4c</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">was out for =
ballot. Now it is time for Sponsor ballot. According to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">number of =
iterations the document went through, it looks like it should =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">closed by =
March time frame, or June the latest.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">An =
interoperability test is expected for Bridge, VLAN, Interface, =
and</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ether-like =
MIB.&nbsp; The result of the tests will provide feedback on =
current</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">documents. =
This might cause a delay for other document submitting =
time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">including =
WIS-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">3. Results =
of AToMMIB's SONET-MIB status discussion /-&nbsp; Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">A draft is =
ready, will be submitted next week. There are only few =
minor</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">changes. It =
is important to get the document published since WIS-MIB =
depends</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">on it. =
There are no implementation reports of 2558, so if no progress =
will</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">be shown in =
advancing the documents toward draft standard, it will =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">published =
again as proposed. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The goal is =
to get reports by February.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">4. Report =
from the Design Team and Open Issues for WIS MIB /-&nbsp; KC =
Norseth,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">There were =
three issues to resolve:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">-What is =
the layering model and how should it be mapped to =
IF-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">-How do we =
map SNMP objects to GDMO objects of WIS defined in 802.3ae =
clause</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">30.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">- How does =
the solution manage with ETH/RMON free running counters as =
well</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">as 15&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;min =
interval&nbsp; SONET counters.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
proposal is to use what exist in ETH, MAU and SONET, as much =
as</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">possible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The WIS MIB =
can use many of the SONET table.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">If Stack =
table should have the following: LLC, MAC, reconciliation, =
PHY</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">coding, =
Path, Line, Section and 802.3 WAN PMA/PMD.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The objects =
for PM are taken from 3 MIBS.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
solution needs no special HW beyond what is required in =
802.3ae.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Not everyone in =
the team agreed to the layering model of having</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet on =
top of SONET. The suggestion was to add a layer between =
CSMACD</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">to SONET =
Path to indicate what kind of ETH over SONET payload mapping =
is</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">used.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Issues and =
Proposed Resolutions: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">1. Layering =
Model: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Because the =
WIS payload mapping (i.e., 64B/66B encoded </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ehternet =
data mapped directly into the STS-192c payload capacity, with C2 =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">set to =
'00011010'b) is just one of several Ethernet over SONET payload =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">mappings, =
it has been suggested that an additional ifStackTable layer in =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">between =
ethernetCsmacd(6) and sonetPath(50) should be present to indicate =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">what type =
of Ethernet over SONET payload mapping is being used. An alternative =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">suggestion =
is to use ifMauType and ifMauDefaultType for this =
purpose.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep the layering as currently defined in the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">internet-draft and use ifMauType and ifMauDefaultType to =
indicate the type </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">of Ethernet =
over SONET.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">2. =
Compliance: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Should the =
ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">interfaces? =
An alternative would be to make them optional. In that case =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">10GBASE-W =
interfaces would require a multi-layer ifStackTable only if ETHER-WIS =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">and =
SONET-MIB were supported; if not, then the usual single-layer model =
would apply.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep all the ETHER-WIS and SONET-MIB objects mandatory as =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">currently =
defined in the internet-draft.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Relationship with MAU-MIB: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The next =
Mau-MIB draft should specify what happens to the ifStackTable if =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">ifMauDefaultType is changed from dot3MauType10GigBaseR to =
dot3MauType10GigBaseW </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">or =
vice-versa.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: The suggested was agreed. Mike Heard will provide the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">text to be =
added to the Mau-MIB. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Clarification on Compliance: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Clarification text for compliance description in Section =
3.1 is needed.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Mike Heard will provide the clarification text for =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Section 3.1 =
regarding compliance.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">It was =
decided to host the document in the HUBMIB group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Internet =
Draft:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">&lt;http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">-01.txt&gt;</FONT></SPAN></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1982C.58F8002C--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Tue Jan  8 05:09:22 2002
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 FAA18366
	for <hubmib-archive@odin.ietf.org>; Tue, 8 Jan 2002 05:09:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA22677
	for hubmib-archive@odin.ietf.org; Tue, 8 Jan 2002 05:09:19 -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 FAA22637;
	Tue, 8 Jan 2002 05:08:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22605
	for <hubmib@ns.ietf.org>; Tue, 8 Jan 2002 05:08:51 -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 FAA18352
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:08:49 -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 g08A7Un01705
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:07:30 -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 g08A7TO01692
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 05:07:29 -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_01C1982C.58F8002C"
Date: Tue, 8 Jan 2002 12:07:58 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF53FEC@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Preliminary Minutes of the SLC Joint Meeting of hubmib and atommib
Thread-Index: AcGYLHQa1pdvUMGeSv2yBDriXTd7VQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Preliminary Minutes of the SLC Joint Meeting of hubmib and atommib
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1982C.58F8002C
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the preliminary minutes of the SLC joint meeting of
atommib and hubmib. Please send your comments and corrections, before I
submit these. Thanks to Orly and Kam for the diligent note taking work.
Also, presenters are required to send their presentations to
minutes@ietf.org, for inclusion in the proceedings.
Regards,
Dan



52 IETF, Salt Lake City
=20
Ethernet Interfaces and Hub MIB WG & AToM MIB WG (hubmib & atommib)

TUESDAY, December 11 at 1700-1800
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CHAIRS:	Dan Romascanu <dromasca@avaya.com>
		Faye Ly <fayely98@hotmail.com>
		Nathan Kohn <mvnk@lucent.com>

The Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB
(atommib) WG=20
held a joint meeting at the 52nd IETF in Salt Lake City. The main
purpose of=20
the meeting was to report on the work from the design team formed by
members=20
of the two WGs in order to provide recommendations for the WAN Interface

Sublayer (WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update
were=20
also presented. It was noted that the WIS MIB is depended on the SONET
MIB for=20
the STS-192c update. Therefore the updated SONET-MIB should be
republished in=20
time regardless it is republished with or without advancement.

The participants in the meeting approved the approach presented in the=20
Internet-Drafts issued by the Design Team. The participants in the
meeting=20
proposed that the design team be transformed into an editor team to
further=20
the document. The open issues posted by the design team and the
recommendations=20
for resolution from the discussion are listed below. These issues and
proposed=20
resolution will be posted to the two WG lists, and to the IEEE 802.3ae
list.=20
The Hub MIB WG chair will request a slot for a presentation of the work
and open=20
issues at the interim meeting of the IEEE in January 2002, in order to
receive=20
more feedback from the IEEE. If now special problems show up, the next
version of=20
the Internet-Draft is aimed for WG Last Call.

Summary:

1. Introductions and Agenda Bashing. Three topics were covered;

2. IEEE 802.3 Update / - Dan Romascanu.
Between London  IETF and SLC, there were two meetings of the 802.3ae
group.
Between the two meetings, people response to the documents and draft
3.4c
was out for ballot. Now it is time for Sponsor ballot. According to the
number of iterations the document went through, it looks like it should
be
closed by March time frame, or June the latest.
An interoperability test is expected for Bridge, VLAN, Interface, and
Ether-like MIB.  The result of the tests will provide feedback on
current
documents. This might cause a delay for other document submitting time
including WIS-MIB.

3. Results of AToMMIB's SONET-MIB status discussion /-  Mike Heard
A draft is ready, will be submitted next week. There are only few minor
changes. It is important to get the document published since WIS-MIB
depends
on it. There are no implementation reports of 2558, so if no progress
will
be shown in advancing the documents toward draft standard, it will be
published again as proposed.=20
The goal is to get reports by February.

4. Report from the Design Team and Open Issues for WIS MIB /-  KC
Norseth,
Mike Heard
There were three issues to resolve:
-What is the layering model and how should it be mapped to IF-MIB.
-How do we map SNMP objects to GDMO objects of WIS defined in 802.3ae
clause
30.
- How does the solution manage with ETH/RMON free running counters as
well
as 15 =20
 min interval  SONET counters.

The proposal is to use what exist in ETH, MAU and SONET, as much as
possible.

The WIS MIB can use many of the SONET table.
If Stack table should have the following: LLC, MAC, reconciliation, PHY
coding, Path, Line, Section and 802.3 WAN PMA/PMD.
The objects for PM are taken from 3 MIBS.
The solution needs no special HW beyond what is required in 802.3ae.

=B7	Not everyone in the team agreed to the layering model of having
Ethernet on top of SONET. The suggestion was to add a layer between
CSMACD
to SONET Path to indicate what kind of ETH over SONET payload mapping is
used.

Issues and Proposed Resolutions:=20

1. Layering Model:=20

Because the WIS payload mapping (i.e., 64B/66B encoded=20
Ehternet data mapped directly into the STS-192c payload capacity, with
C2=20
set to '00011010'b) is just one of several Ethernet over SONET payload=20
mappings, it has been suggested that an additional ifStackTable layer in

between ethernetCsmacd(6) and sonetPath(50) should be present to
indicate=20
what type of Ethernet over SONET payload mapping is being used. An
alternative=20
suggestion is to use ifMauType and ifMauDefaultType for this purpose.

Proposed Resolution: Keep the layering as currently defined in the=20
internet-draft and use ifMauType and ifMauDefaultType to indicate the
type=20
of Ethernet over SONET.

2. Compliance:=20

Should the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W

interfaces? An alternative would be to make them optional. In that case=20
10GBASE-W interfaces would require a multi-layer ifStackTable only if
ETHER-WIS=20
and SONET-MIB were supported; if not, then the usual single-layer model
would apply.

Proposed Resolution: Keep all the ETHER-WIS and SONET-MIB objects
mandatory as=20
currently defined in the internet-draft.

3. Relationship with MAU-MIB:=20

The next Mau-MIB draft should specify what happens to the ifStackTable
if=20
ifMauDefaultType is changed from dot3MauType10GigBaseR to
dot3MauType10GigBaseW=20
or vice-versa.

Proposed Resolution: The suggested was agreed. Mike Heard will provide
the=20
text to be added to the Mau-MIB.=20

4. Clarification on Compliance:=20

Clarification text for compliance description in Section 3.1 is needed.

Proposed Resolution: Mike Heard will provide the clarification text for=20
Section 3.1 regarding compliance.
It was decided to host the document in the HUBMIB group.

Internet Draft:
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis
-mib
-01.txt>



------_=_NextPart_001_01C1982C.58F8002C
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Preliminary Minutes of the SLC Joint Meeting of hubmib and =
atommib</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find attached the preliminary minutes of the SLC joint meeting of =
atommib and hubmib. Please send your comments and corrections, before I =
submit these. Thanks to Orly and Kam for the diligent note taking =
work.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Also, =
presenters are required to send their presentations to minutes@ietf.org, =
for inclusion in the proceedings.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>
<BR>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">52 IETF, =
Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
Interfaces and Hub MIB WG &amp; AToM MIB WG (hubmib &amp; =
atommib)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, =
December 11 at 1700-1800</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">CHAIRS: Dan =
Romascanu &lt;dromasca@avaya.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"he">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Faye Ly &lt;fayely98@hotmail.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"he">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Nathan Kohn &lt;mvnk@lucent.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB (atommib) WG =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">held a =
joint meeting at the 52nd IETF in Salt Lake City. The main purpose of =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the meeting =
was to report on the work from the design team formed by members =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">of the two =
WGs in order to provide recommendations for the WAN Interface =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Sublayer =
(WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update were =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">also =
presented. It was noted that the WIS MIB is depended on the SONET MIB =
for </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
STS-192c update. Therefore the updated SONET-MIB should be republished =
in </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">time =
regardless it is republished with or without =
advancement.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
participants in the meeting approved the approach presented in the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts issued by the Design Team. The =
participants in the meeting </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">proposed =
that the design team be transformed into an editor team to further =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
document. The open issues posted by the design team and the =
recommendations </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">for =
resolution from the discussion are listed below. These issues and =
proposed </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">resolution =
will be posted to the two WG lists, and to the IEEE 802.3ae list. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The Hub MIB =
WG chair will request a slot for a presentation of the work and open =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">issues at =
the interim meeting of the IEEE in January 2002, in order to receive =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">more =
feedback from the IEEE. If now special problems show up, the next =
version of </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">the =
Internet-Draft is aimed for WG Last Call.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Summary:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Introductions and Agenda Bashing. Three topics were =
covered;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">2. IEEE =
802.3 Update / - Dan Romascanu.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Between =
London&nbsp; IETF and SLC, there were two meetings of the 802.3ae =
group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Between the =
two meetings, people response to the documents and draft =
3.4c</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">was out for =
ballot. Now it is time for Sponsor ballot. According to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">number of =
iterations the document went through, it looks like it should =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">closed by =
March time frame, or June the latest.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">An =
interoperability test is expected for Bridge, VLAN, Interface, =
and</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ether-like =
MIB.&nbsp; The result of the tests will provide feedback on =
current</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">documents. =
This might cause a delay for other document submitting =
time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">including =
WIS-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">3. Results =
of AToMMIB's SONET-MIB status discussion /-&nbsp; Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">A draft is =
ready, will be submitted next week. There are only few =
minor</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">changes. It =
is important to get the document published since WIS-MIB =
depends</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">on it. =
There are no implementation reports of 2558, so if no progress =
will</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">be shown in =
advancing the documents toward draft standard, it will =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">published =
again as proposed. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The goal is =
to get reports by February.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">4. Report =
from the Design Team and Open Issues for WIS MIB /-&nbsp; KC =
Norseth,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">There were =
three issues to resolve:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">-What is =
the layering model and how should it be mapped to =
IF-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">-How do we =
map SNMP objects to GDMO objects of WIS defined in 802.3ae =
clause</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">30.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">- How does =
the solution manage with ETH/RMON free running counters as =
well</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">as 15&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;min =
interval&nbsp; SONET counters.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
proposal is to use what exist in ETH, MAU and SONET, as much =
as</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">possible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The WIS MIB =
can use many of the SONET table.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">If Stack =
table should have the following: LLC, MAC, reconciliation, =
PHY</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">coding, =
Path, Line, Section and 802.3 WAN PMA/PMD.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The objects =
for PM are taken from 3 MIBS.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The =
solution needs no special HW beyond what is required in =
802.3ae.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Not everyone in =
the team agreed to the layering model of having</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet on =
top of SONET. The suggestion was to add a layer between =
CSMACD</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">to SONET =
Path to indicate what kind of ETH over SONET payload mapping =
is</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">used.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Issues and =
Proposed Resolutions: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">1. Layering =
Model: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Because the =
WIS payload mapping (i.e., 64B/66B encoded </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Ehternet =
data mapped directly into the STS-192c payload capacity, with C2 =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">set to =
'00011010'b) is just one of several Ethernet over SONET payload =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">mappings, =
it has been suggested that an additional ifStackTable layer in =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">between =
ethernetCsmacd(6) and sonetPath(50) should be present to indicate =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">what type =
of Ethernet over SONET payload mapping is being used. An alternative =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">suggestion =
is to use ifMauType and ifMauDefaultType for this =
purpose.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep the layering as currently defined in the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">internet-draft and use ifMauType and ifMauDefaultType to =
indicate the type </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">of Ethernet =
over SONET.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">2. =
Compliance: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Should the =
ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">interfaces? =
An alternative would be to make them optional. In that case =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">10GBASE-W =
interfaces would require a multi-layer ifStackTable only if ETHER-WIS =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">and =
SONET-MIB were supported; if not, then the usual single-layer model =
would apply.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep all the ETHER-WIS and SONET-MIB objects mandatory as =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">currently =
defined in the internet-draft.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Relationship with MAU-MIB: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">The next =
Mau-MIB draft should specify what happens to the ifStackTable if =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">ifMauDefaultType is changed from dot3MauType10GigBaseR to =
dot3MauType10GigBaseW </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">or =
vice-versa.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: The suggested was agreed. Mike Heard will provide the =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">text to be =
added to the Mau-MIB. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Clarification on Compliance: </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">Clarification text for compliance description in Section =
3.1 is needed.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Mike Heard will provide the clarification text for =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Section 3.1 =
regarding compliance.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">It was =
decided to host the document in the HUBMIB group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 FACE=3D"Arial">Internet =
Draft:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">&lt;http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"he"><FONT SIZE=3D2 =
FACE=3D"Arial">-01.txt&gt;</FONT></SPAN></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1982C.58F8002C--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From daemon@ns.ietf.org  Tue Jan  8 05:55:16 2002
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 EAA18197
	for <hubmib-archive@odin.ietf.org>; Tue, 8 Jan 2002 04:57:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22067
	for hubmib-archive@odin.ietf.org; Tue, 8 Jan 2002 04:57:49 -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 EAA22015;
	Tue, 8 Jan 2002 04:56:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21987
	for <hubmib@ns.ietf.org>; Tue, 8 Jan 2002 04:56:51 -0500 (EST)
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 EAA18177
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:56:49 -0500 (EST)
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 EAA03300
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:55:26 -0500 (EST)
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 EAA03272
	for <hubmib@ietf.org>; Tue, 8 Jan 2002 04:55:25 -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_01C1982A.AD29B9B7"
Date: Tue, 8 Jan 2002 11:56:00 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F60D038@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Preliminary Minutes of the SLC Hubmib Meeting
Thread-Index: AcGYKshTjg6nfkqqTkW4FYwTNUZomQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Preliminary Minutes of the SLC Hubmib Meeting
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1982A.AD29B9B7
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the preliminary minutes of the SLC hubmib meeting.
Please send your comments and corrections, before I submit these. Thanks
to KC for the diligent note taking work.

Also, presenters are required to send their presentations to
minutes@ietf.org, for inclusion in the proceedings.

Regards,

Dan

HUBMIB WG  IETF 52,  Salt Lake City
Monday afternoon session II
Notes
K.C. - Minutes taker
Dan Romascanu  discussion leader

The agenda from the main agenda link is invalid.  IETF isn't concerned.
The real hubmib agenda can be found at:
http://www.ietf.org/ietf/01dec/hubmib.txt

*	IEEE 802.3 Status Report
*	two IEEE meetings since London
*	802.ae=20
*	draft 34 in ballot between 11/17 and 12/3
*	Sponsor Ballot to follow
*	Standard expected 3/02 and 6/02
*	802.3af
*	D3.0 in Ballot between 11/16 & 12/30
*	Standard expected between 9/02 and 11/02
*	Standard slightly behind time
*	Changes expected
*	802.3ah  (Ethernet first mile)
*	WG formed - 9/01
*	Four tracks:
*	=B7        Fiber p2p
*	=B7        Copper p2p
*	=B7        Fiber p2mp
*	=B7        OAM
*	Far from IETF involved still too early in IEEE
*	RFC=92s
*	1515 - should be obsolete by 2668 - was not.
*	2108
*	2665
*	2666
*	2668
*	Confusion is there due to duplication of rfc=92s.
*	Next rfc on MAU mib will obsolete 1515 and 2668
*	Need implementation reports.
*	Enterasys wanted some issues answered before they implement
implementation
*	reports.
*	Would be nice to get implementation reports of where
*	John Flick - Problems with hardware help decide that
non-essential items will not be discussed.

	*	Etherlike MIBS
			o	What do we do with the test oids now
that the table is gone? - Deprecate?
			o	What about multiple manager stations?=20
			o	rfc1229 Interfaces extensions
mib->rfc1273->deprecated for no implementations.  We now have test oids
not in use.  Recommended to deprecate and start a loopback test object.
Will post new object to mailing list.
			o	Is the IFMTU clear.  Someone requested
clarification to this, but it seems clear.  It was decided that the
person who doesn=92t understand it to give example.  It was decided to
leave as is until the person can produce the info.
			o	IfAdminStatus (down) needs to be
clarified  Mike Mcfadden brought up the issue in the bridge wg where
multiple vendors have multiple reactions to this.  Fiber was not tested.
There needs to be clarification needed from IEEE.  John will write text
to ask and Dan will make the request.
			o	issue on rfc1643 - 2 current versions of
the Ethernet mib. - do we move it to historic, full standard?  Should we
put in our current draft an explanation of why there are 2 drafts.  Some
vendors are using rfc1643 with private mibs.

	*	MAU MIB
			o	Some outstanding edits are still here.
There are some issues in the WIS MIB and SONET that will affect some
text.
			o	Some issues from the InterWorking labs
test summit may affect this.  We will have to wait until at least the
end of January to get its information. Do we wait?=20
			o	Issues that could come up are
misunderstanding in the implementation? Some packets and octets that
could have misunderstanding.  It was decided to wait for the test
summit.
			o	Some SONET entry in the ifStackEntry
stackables issues.  This goes along with the WIS MIB work.  Where do we
do the clarification?  Decided we would discuss this in the WIS mib
meeting.
			o	discussed the implementation of the
auto-negotiation duplex info.  Some are implementing the MAU mib as is.
Others are implementing this in the private mibs due to being
cumbersome.  GBIC swap may only be partly relevant to the configuration.
Use a enumerated integer for setting? This is what some people are
doing.  John had posted to the wg how HP is doing their proprietary mib
as a suggestion.
			o	Forcing the autonegotiation down
configuration came up.  Once again, not having implementation reports to
review against doesn=92t help solve the issue. We need more =
implementation
reports.  There are some vendors that have implemented the way as
written.
			o	Dan proposed that we do the updates to
the mib as posted previously by John as recommendation of the committee
and let people see it. Mike H. suggested some new oid=92s written to =
help
out with this.  People could help by reviewing the jack type
enumeration.


			o	Power MIB
			o	latest draft published November 2001
			o	Misc spelling and compile warning errors
were noted.
			o	Changes resulting from
IEEEportPortPowerPairs object deleted.
			o	Delete off option of the power port
detection control object
			o	add new objects to powerdetectionstatus
object.
			o	delete powerportclassificationobject
			o	update naming of objects
			o	Reviewed some implementation notes from
PowerDsine that will be added to next version.
			o	The IETF document status is stable. We
don=92t know what the IEEE is going to do. For this reason just respin =
the
draft and wait for the IEEE to go on.
			o	Last-call may happen in Feb 02 depending
on the IEEE.

The goal is to finish all for the IETF in Minneapolis. in March.

Goals and Milestones
Dec 01 - Gather implementation experience
Jan 02 - Issue revised drafts - Missed
Jan 02 - Forward drafts to AD/IESG - pushed to Feb.
Feb 02 - Last call in Feb.


------_=_NextPart_001_01C1982A.AD29B9B7
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Preliminary Minutes of the SLC Hubmib Meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Please find attached the =
preliminary minutes of the SLC hubmib meeting. Please send your comments =
and corrections, before I submit these. Thanks to KC for the diligent =
note taking work.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Also, presenters are required =
to send their presentations to minutes@ietf.org, for inclusion in the =
proceedings.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">HUBMIB WG&nbsp; IETF =
52,&nbsp; Salt Lake City</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Monday afternoon =
session II</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Notes</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">K.C. - Minutes =
taker</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">Dan Romascanu&nbsp; =
discussion leader</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">The agenda from the =
main agenda link is invalid.&nbsp; IETF isn't concerned.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New">The real hubmib agenda =
can be found at:</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Courier New"><A =
HREF=3D"http://www.ietf.org/ietf/01dec/hubmib.txt">http://www.ietf.org/ie=
tf/01dec/hubmib.txt</A></FONT></P>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">IEEE 802.3 Status =
Report</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">two IEEE meetings =
since London</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">802.ae =
</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">draft 34 in =
ballot between 11/17 and 12/3</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Sponsor Ballot to =
follow</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard expected =
3/02 and 6/02</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3af</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">D3.0 in Ballot =
between 11/16 &amp; 12/30</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard expected =
between 9/02 and 11/02</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Standard slightly =
behind time</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Changes =
expected</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">802.3ah&nbsp; =
(Ethernet first mile)</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">WG formed - =
9/01</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Four =
tracks:</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fiber =
p2p</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Copper =
p2p</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fiber =
p2mp</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OAM</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Far from IETF =
involved still too early in IEEE</FONT></LI></DIV>
</UL>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">RFC=92s</FONT></LI></DIV>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">1515 - should be =
obsolete by 2668 - was not.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2108</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2665</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2666</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">2668</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Confusion is =
there due to duplication of rfc=92s.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Next rfc on MAU =
mib will obsolete 1515 and 2668</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Need =
implementation reports.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Enterasys wanted =
some issues answered before they implement =
implementation</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier =
New">reports.</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">Would be nice to =
get implementation reports of where</FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Courier New">John Flick - =
Problems with hardware help decide that non-essential items will not be =
discussed.</FONT></LI></DIV>
<BR>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">Etherlike MIBS</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What do we do with the test =
oids now that the table is gone? - Deprecate?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What about multiple manager =
stations? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rfc1229 Interfaces extensions =
mib-&gt;rfc1273-&gt;deprecated for no implementations.&nbsp; We now have =
test oids not in use.&nbsp; Recommended to deprecate and start a =
loopback test object. Will post new object to mailing =
list.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the IFMTU clear.&nbsp; =
Someone requested clarification to this, but it seems clear.&nbsp; It =
was decided that the person who doesn=92t understand it to give =
example.&nbsp; It was decided to leave as is until the person can =
produce the info.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IfAdminStatus (down) needs to =
be clarified&nbsp; Mike Mcfadden brought up the issue in the bridge wg =
where multiple vendors have multiple reactions to this.&nbsp; Fiber was =
not tested.&nbsp; There needs to be clarification needed from =
IEEE.&nbsp; John will write text to ask and Dan will make the =
request.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; issue on rfc1643 - 2 current =
versions of the Ethernet mib. - do we move it to historic, full =
standard?&nbsp; Should we put in our current draft an explanation of why =
there are 2 drafts.&nbsp; Some vendors are using rfc1643 with private =
mibs.</FONT></SPAN></P>
</UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">&#183;<FONT FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT> <FONT SIZE=3D2 =
FACE=3D"Courier New">MAU MIB</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some outstanding edits are =
still here.&nbsp; There are some issues in the WIS MIB and SONET that =
will affect some text.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some issues from the =
InterWorking labs test summit may affect this.&nbsp; We will have to =
wait until at least the end of January to get its information. Do we =
wait? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Issues that could come up are =
misunderstanding in the implementation? Some packets and octets that =
could have misunderstanding.&nbsp; It was decided to wait for the test =
summit.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Some SONET entry in the =
ifStackEntry stackables issues.&nbsp; This goes along with the WIS MIB =
work.&nbsp; Where do we do the clarification?&nbsp; Decided we would =
discuss this in the WIS mib meeting.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discussed the implementation =
of the auto-negotiation duplex info.&nbsp; Some are implementing the MAU =
mib as is.&nbsp; Others are implementing this in the private mibs due to =
being cumbersome.&nbsp; GBIC swap may only be partly relevant to the =
configuration.&nbsp; Use a enumerated integer for setting? This is what =
some people are doing.&nbsp; John had posted to the wg how HP is doing =
their proprietary mib as a suggestion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Forcing the autonegotiation =
down configuration came up.&nbsp; Once again, not having implementation =
reports to review against doesn=92t help solve the issue. We need more =
implementation reports.&nbsp; There are some vendors that have =
implemented the way as written.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Dan proposed that we do the =
updates to the mib as posted previously by John as recommendation of the =
committee and let people see it. Mike H. suggested some new oid=92s =
written to help out with this.&nbsp; People could help by reviewing the =
jack type enumeration.</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Power MIB</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latest draft published =
November 2001</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Misc spelling and compile =
warning errors were noted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Changes resulting from =
IEEEportPortPowerPairs object deleted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Delete off option of the =
power port detection control object</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; add new objects to =
powerdetectionstatus object.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delete =
powerportclassificationobject</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; update naming of =
objects</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reviewed some implementation =
notes from PowerDsine that will be added to next =
version.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The IETF document status is =
stable. We don=92t know what the IEEE is going to do. For this reason =
just respin the draft and wait for the IEEE to go on.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last-call may happen in Feb =
02 depending on the IEEE.</FONT></SPAN></P>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The goal is to finish all for the IETF in Minneapolis. in =
March.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Goals and Milestones</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dec 01 - Gather implementation experience</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Issue revised drafts - Missed</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Forward drafts to AD/IESG - pushed to =
Feb.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Feb 02 - Last call in Feb.</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1982A.AD29B9B7--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Sat Jan 12 02:46:08 2002
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 CAA18001
	for <hubmib-archive@odin.ietf.org>; Sat, 12 Jan 2002 02:46:08 -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 CAA10482;
	Sat, 12 Jan 2002 02:45: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 CAA10451
	for <hubmib@optimus.ietf.org>; Sat, 12 Jan 2002 02:45:33 -0500 (EST)
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 CAA17985;
	Sat, 12 Jan 2002 02:45:29 -0500 (EST)
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 CAA19028;
	Sat, 12 Jan 2002 02:44:08 -0500 (EST)
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 CAA19017;
	Sat, 12 Jan 2002 02:44:06 -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_01C19B3C.FE98AC7A"
Date: Sat, 12 Jan 2002 09:44:41 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54049@IS0004AVEXU1.global.avaya.com>
Thread-Topic: SLC Hubmib Minutes
Thread-Index: AcGbPReoKt1KKBdfSlWULMmAV+FHIA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <minutes@ietf.org>
Cc: <hubmib@ietf.org>
Subject: [Hubmib] SLC Hubmib Minutes
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19B3C.FE98AC7A
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the minutes of the SLC hubmib meeting.=20
Regards,
Dan
HUBMIB WG IETF 52, Salt Lake City
Monday afternoon session II
Notes
K.C. - Minutes taker
Dan Romascanu discussion leader
The agenda from the main agenda link is invalid. IETF isn't concerned.
The real hubmib agenda can be found at:
<http://www.ietf.org/ietf/01dec/hubmib.txt>
*	IEEE 802.3 Status Report=20
*	two IEEE meetings since London=20
*	802.ae=20
*	draft 34 in ballot between 11/17 and 12/3=20
*	Sponsor Ballot to follow=20
*	Standard expected 3/02 and 6/02
*	802.3af=20
*	D3.0 in Ballot between 11/16 & 12/30=20
*	Standard expected between 9/02 and 11/02=20
*	Standard slightly behind time=20
*	Changes expected
*	802.3ah (Ethernet first mile)=20
*	WG formed - 9/01=20
*	Four tracks:=20
*	=B7 Fiber p2p=20
*	=B7 Copper p2p=20
*	=B7 Fiber p2mp=20
*	=B7 OAM=20
*	Far from IETF involved still too early in IEEE
*	RFC=92s=20
*	1515 - should be obsolete by 2668 - was not.=20
*	2108=20
*	2665=20
*	2666=20
*	2668=20
*	Confusion is there due to duplication of rfc=92s.=20
*	Next rfc on MAU mib will obsolete 1515 and 2668=20
*	Need implementation reports.=20
*	Enterasys wanted some issues answered before they implement
implementation=20
*	reports.=20
*	Would be nice to get implementation reports of where=20
*	John Flick - Problems with hardware help decide that
non-essential items will not be discussed.
		=B7 Etherlike MIBS
				o What do we do with the test oids now
that the table is gone? - Deprecate?
				o What about multiple manager stations?=20
				o rfc1229 Interfaces extensions
mib->rfc1273->deprecated for no implementations. We now have test oids
not in use. Recommended to deprecate and start a loopback test object.
Will post new object to mailing list.
				o Is the IFMTU clear. Someone requested
clarification to this, but it seems clear. It was decided that the
person who doesn=92t understand it to give example. It was decided to
leave as is until the person can produce the info.
				o IfAdminStatus (down) needs to be
clarified Mike Mcfadden brought up the issue in the bridge wg where
multiple vendors have multiple reactions to this. Fiber was not tested.
There needs to be clarification needed from IEEE. John will write text
to ask and Dan will make the request.
				o issue on rfc1643 - 2 current versions
of the Ethernet mib. - do we move it to historic, full standard? Should
we put in our current draft an explanation of why there are 2 drafts.
Some vendors are using rfc1643 with private mibs.
		=B7 MAU MIB
				o Some outstanding edits are still here.
There are some issues in the WIS MIB and SONET that will affect some
text.
				o Some issues from the InterWorking labs
test summit may affect this. We will have to wait until at least the end
of January to get its information. Do we wait?=20
				o Issues that could come up are
misunderstanding in the implementation? Some packets and octets that
could have misunderstanding. It was decided to wait for the test summit.
				o Some SONET entry in the ifStackEntry
stackables issues. This goes along with the WIS MIB work. Where do we do
the clarification? Decided we would discuss this in the WIS mib meeting.
				o discussed the implementation of the
auto-negotiation duplex info. Some are implementing the MAU mib as is.
Others are implementing this in the private mibs due to being
cumbersome. GBIC swap may only be partly relevant to the configuration.
Use a enumerated integer for setting? This is what some people are
doing. John had posted to the wg how HP is doing their proprietary mib
as a suggestion.
				o Forcing the autonegotiation down
configuration came up. Once again, not having implementation reports to
review against doesn=92t help solve the issue. We need more =
implementation
reports. There are some vendors that have implemented the way as
written.
				o Dan proposed that we do the updates to
the mib as posted previously by John as recommendation of the committee
and let people see it. Mike H. suggested some new oid=92s written to =
help
out with this. People could help by reviewing the jack type enumeration.

				o Power MIB
				o latest draft published November 2001
				o Misc spelling and compile warning
errors were noted.
				o Changes resulting from
IEEEportPortPowerPairs object deleted.
				o Delete off option of the power port
detection control object
				o add new objects to
powerdetectionstatus object.
				o delete powerportclassificationobject
				o update naming of objects
				o Reviewed some implementation notes
from PowerDsine that will be added to next version.
				o The IETF document status is stable. We
don=92t know what the IEEE is going to do. For this reason just respin =
the
draft and wait for the IEEE to go on.
				o Last-call may happen in Feb 02
depending on the IEEE.
The goal is to finish all for the IETF in Minneapolis. in March.
Goals and Milestones
Dec 01 - Gather implementation experience
Jan 02 - Issue revised drafts - Missed
Jan 02 - Forward drafts to AD/IESG - pushed to Feb.
Feb 02 - Last call in Feb.


------_=_NextPart_001_01C19B3C.FE98AC7A
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>SLC Hubmib Minutes</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find attached the minutes of the SLC hubmib meeting. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">HUBMIB WG IETF 52, Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Monday afternoon session II</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Notes</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">K.C. - Minutes taker</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dan Romascanu discussion leader</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The agenda from the main agenda link is invalid. IETF isn't =
concerned.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The real hubmib agenda can be found at:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&lt;<A =
HREF=3D"http://www.ietf.org/ietf/01dec/hubmib.txt">http://www.ietf.org/ie=
tf/01dec/hubmib.txt</A>&gt;</FONT></U></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">IEEE 802.3 Status Report</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">two IEEE meetings since London</FONT><FONT FACE=3D"Times New =
Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.ae</FONT> </SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">draft 34 in ballot between 11/17 and 12/3</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Sponsor Ballot to follow</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard expected 3/02 and 6/02</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3af</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">D3.0 in Ballot between 11/16 &amp; 12/30</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard expected between 9/02 and 11/02</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard slightly behind time</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Changes expected</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3ah (Ethernet first mile)</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">WG formed - 9/01</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Four tracks:</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Fiber p2p</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Copper p2p</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Fiber p2mp</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 OAM</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Far from IETF involved still too early in =
IEEE</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">RFC=92s</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">1515 - should be obsolete by 2668 - was not.</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2108</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2665</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2666</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2668</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Confusion is there due to duplication of rfc=92s.</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Next rfc on MAU mib will obsolete 1515 and 2668</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Need implementation reports.</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Enterasys wanted some issues answered before they implement =
implementation</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">reports.</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Would be nice to get implementation reports of where</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">John Flick - Problems with hardware help decide that non-essential =
items will not be discussed.</FONT></SPAN></LI></DIV>
</UL></UL></UL></UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">=B7</FONT><FONT SIZE=3D2 FACE=3D"Courier New"> Etherlike =
MIBS</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
What do we do with the test oids now that the table is gone? - =
Deprecate?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
What about multiple manager stations?</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
rfc1229 Interfaces extensions mib-&gt;rfc1273-&gt;deprecated for no =
implementations. We now have test oids not in use. Recommended to =
deprecate and start a loopback test object. Will post new object to =
mailing list.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Is the IFMTU clear. Someone requested clarification to this, but it =
seems clear. It was decided that the person who doesn=92t understand it =
to give example. It was decided to leave as is until the person can =
produce the info.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
IfAdminStatus (down) needs to be clarified Mike Mcfadden brought up the =
issue in the bridge wg where multiple vendors have multiple reactions to =
this. Fiber was not tested. There needs to be clarification needed from =
IEEE. John will write text to ask and Dan will make the =
request.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
issue on rfc1643 - 2 current versions of the Ethernet mib. - do we move =
it to historic, full standard? Should we put in our current draft an =
explanation of why there are 2 drafts. Some vendors are using rfc1643 =
with private mibs.</FONT></SPAN></P>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">=B7</FONT><FONT SIZE=3D2 FACE=3D"Courier New"> MAU =
MIB</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some outstanding edits are still here. There are some issues in the WIS =
MIB and SONET that will affect some text.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some issues from the InterWorking labs test summit may affect this. We =
will have to wait until at least the end of January to get its =
information. Do we wait?</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Issues that could come up are misunderstanding in the implementation? =
Some packets and octets that could have misunderstanding. It was decided =
to wait for the test summit.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some SONET entry in the ifStackEntry stackables issues. This goes along =
with the WIS MIB work. Where do we do the clarification? Decided we =
would discuss this in the WIS mib meeting.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
discussed the implementation of the auto-negotiation duplex info. Some =
are implementing the MAU mib as is. Others are implementing this in the =
private mibs due to being cumbersome. GBIC swap may only be partly =
relevant to the configuration. Use a enumerated integer for setting? =
This is what some people are doing. John had posted to the wg how HP is =
doing their proprietary mib as a suggestion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Forcing the autonegotiation down configuration came up. Once again, not =
having implementation reports to review against doesn=92t help solve the =
issue. We need more implementation reports. There are some vendors that =
have implemented the way as written.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Dan proposed that we do the updates to the mib as posted previously by =
John as recommendation of the committee and let people see it. Mike H. =
suggested some new oid=92s written to help out with this. People could =
help by reviewing the jack type enumeration.</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Power MIB</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
latest draft published November 2001</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Misc spelling and compile warning errors were noted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Changes resulting from IEEEportPortPowerPairs object =
deleted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Delete off option of the power port detection control =
object</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
add new objects to powerdetectionstatus object.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
delete powerportclassificationobject</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
update naming of objects</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Reviewed some implementation notes from PowerDsine that will be added to =
next version.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
The IETF document status is stable. We don=92t know what the IEEE is =
going to do. For this reason just respin the draft and wait for the IEEE =
to go on.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Last-call may happen in Feb 02 depending on the IEEE.</FONT></SPAN></P>
</UL></UL></UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The goal is to finish all for the IETF in Minneapolis. in =
March.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Goals and Milestones</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dec 01 - Gather implementation experience</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Issue revised drafts - Missed</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Forward drafts to AD/IESG - pushed to =
Feb.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Feb 02 - Last call in Feb.</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C19B3C.FE98AC7A--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From hubmib-admin@ietf.org  Sat Jan 12 02:49:52 2002
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 CAA18075
	for <hubmib-archive@odin.ietf.org>; Sat, 12 Jan 2002 02:49:52 -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 CAA10624;
	Sat, 12 Jan 2002 02:49:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10597
	for <hubmib@optimus.ietf.org>; Sat, 12 Jan 2002 02:49:17 -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 CAA18056;
	Sat, 12 Jan 2002 02:49:14 -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 g0C7lxl00389;
	Sat, 12 Jan 2002 02:47: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 g0C7lwd00383;
	Sat, 12 Jan 2002 02:47: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_01C19B3D.84D1C77E"
Date: Sat, 12 Jan 2002 09:48:26 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF5404A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Miutes of the Joint atommib and hubmib meeting in SLC
Thread-Index: AcGbPZ2mN9lI78gMQVyAF8KsUhzGrw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <minutes@ietf.org>
Cc: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Miutes of the Joint atommib and hubmib meeting in SLC
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19B3D.84D1C77E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find in the following the minutes of the joint meeting of hubmib
and atommib in SLC . Regards, Dan

52 IETF, Salt Lake City
Ethernet Interfaces and Hub MIB WG & AToM MIB WG (hubmib & atommib)
TUESDAY, December 11 at 1700-1800
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CHAIRS: Dan Romascanu <dromasca@avaya.com>
Faye Ly <fayely98@hotmail.com>
Nathan Kohn <mvnk@lucent.com>
The Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB
(atommib) WG=20
held a joint meeting at the 52nd IETF in Salt Lake City. The main
purpose of=20
the meeting was to report on the work from the design team formed by
members=20
of the two WGs in order to provide recommendations for the WAN Interface

Sublayer (WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update
were=20
also presented. It was noted that the WIS MIB is depended on the SONET
MIB for=20
the STS-192c update. Therefore the updated SONET-MIB should be
republished in=20
time regardless it is republished with or without advancement.
The participants in the meeting approved the approach presented in the=20
Internet-Drafts issued by the Design Team. The participants in the
meeting=20
proposed that the design team be transformed into an editor team to
further=20
the document. The open issues posted by the design team and the
recommendations=20
for resolution from the discussion are listed below. These issues and
proposed=20
resolution will be posted to the two WG lists, and to the IEEE 802.3ae
list.=20
The Hub MIB WG chair will request a slot for a presentation of the work
and open=20
issues at the interim meeting of the IEEE in January 2002, in order to
receive=20
more feedback from the IEEE. If now special problems show up, the next
version of=20
the Internet-Draft is aimed for WG Last Call.
Summary:
1. Introductions and Agenda Bashing. Three topics were covered;
2. IEEE 802.3 Update / - Dan Romascanu.
Between London IETF and SLC, there were two meetings of the 802.3ae
group.
Between the two meetings, people response to the documents and draft
3.4c
was out for ballot. Now it is time for Sponsor ballot. According to the
number of iterations the document went through, it looks like it should
be
closed by March time frame, or June the latest.
An interoperability test is expected for Bridge, VLAN, Interface, and
Ether-like MIB. The result of the tests will provide feedback on current
documents. This might cause a delay for other document submitting time
including WIS-MIB.
3. Results of AToMMIB's SONET-MIB status discussion /- Mike Heard
A draft is ready, will be submitted next week. There are only few minor
changes. It is important to get the document published since WIS-MIB
depends
on it. There are no implementation reports of 2558, so if no progress
will
be shown in advancing the documents toward draft standard, it will be
published again as proposed.=20
The goal is to get reports by February.
4. Report from the Design Team and Open Issues for WIS MIB /- KC
Norseth,
Mike Heard
There were three issues to resolve:
-What is the layering model and how should it be mapped to IF-MIB.
-How do we map SNMP objects to GDMO objects of WIS defined in 802.3ae
clause
30.
- How does the solution manage with ETH/RMON free running counters as
well
as 15=20
min interval SONET counters.
The proposal is to use what exist in ETH, MAU and SONET, as much as
possible.
The WIS MIB can use many of the SONET table.
If Stack table should have the following: LLC, MAC, reconciliation, PHY
coding, Path, Line, Section and 802.3 WAN PMA/PMD.
The objects for PM are taken from 3 MIBS.
The solution needs no special HW beyond what is required in 802.3ae.
=B7 Not everyone in the team agreed to the layering model of having
Ethernet on top of SONET. The suggestion was to add a layer between
CSMACD
to SONET Path to indicate what kind of ETH over SONET payload mapping is
used.
Issues and Proposed Resolutions:=20
1. Layering Model:=20
Because the WIS payload mapping (i.e., 64B/66B encoded=20
Ehternet data mapped directly into the STS-192c payload capacity, with
C2=20
set to '00011010'b) is just one of several Ethernet over SONET payload=20
mappings, it has been suggested that an additional ifStackTable layer in

between ethernetCsmacd(6) and sonetPath(50) should be present to
indicate=20
what type of Ethernet over SONET payload mapping is being used. An
alternative=20
suggestion is to use ifMauType and ifMauDefaultType for this purpose.
Proposed Resolution: Keep the layering as currently defined in the=20
internet-draft and use ifMauType and ifMauDefaultType to indicate the
type=20
of Ethernet over SONET.
2. Compliance:=20
Should the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W

interfaces? An alternative would be to make them optional. In that case=20
10GBASE-W interfaces would require a multi-layer ifStackTable only if
ETHER-WIS=20
and SONET-MIB were supported; if not, then the usual single-layer model
would apply.
Proposed Resolution: Keep all the ETHER-WIS and SONET-MIB objects
mandatory as=20
currently defined in the internet-draft.
3. Relationship with MAU-MIB:=20
The next Mau-MIB draft should specify what happens to the ifStackTable
if=20
ifMauDefaultType is changed from dot3MauType10GigBaseR to
dot3MauType10GigBaseW=20
or vice-versa.
Proposed Resolution: The suggested was agreed. Mike Heard will provide
the=20
text to be added to the Mau-MIB.=20
4. Clarification on Compliance:=20
Clarification text for compliance description in Section 3.1 is needed.
Proposed Resolution: Mike Heard will provide the clarification text for=20
Section 3.1 regarding compliance.
It was decided to host the document in the HUBMIB group.
Internet Draft:
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis
-mib
-01.txt>


------_=_NextPart_001_01C19B3D.84D1C77E
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Miutes of the Joint atommib and hubmib meeting in SLC</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find in the following the minutes of the joint meeting of hubmib and =
atommib in SLC . Regards, Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">52 IETF, =
Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
Interfaces and Hub MIB WG &amp; AToM MIB WG (hubmib &amp; =
atommib)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, =
December 11 at 1700-1800</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">CHAIRS: =
Dan Romascanu &lt;dromasca@avaya.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Faye Ly =
&lt;fayely98@hotmail.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Nathan =
Kohn &lt;mvnk@lucent.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB (atommib) =
WG</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">held a =
joint meeting at the 52nd IETF in Salt Lake City. The main purpose =
of</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
meeting was to report on the work from the design team formed by =
members</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of the =
two WGs in order to provide recommendations for the WAN Interface</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sublayer =
(WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update =
were</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">also =
presented. It was noted that the WIS MIB is depended on the SONET MIB =
for</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
STS-192c update. Therefore the updated SONET-MIB should be republished =
in</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">time =
regardless it is republished with or without =
advancement.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
participants in the meeting approved the approach presented in =
the</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts issued by the Design Team. The =
participants in the meeting</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">proposed =
that the design team be transformed into an editor team to =
further</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
document. The open issues posted by the design team and the =
recommendations</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">for =
resolution from the discussion are listed below. These issues and =
proposed</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">resolution will be posted to the two WG lists, and to the =
IEEE 802.3ae list.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The Hub =
MIB WG chair will request a slot for a presentation of the work and =
open</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">issues =
at the interim meeting of the IEEE in January 2002, in order to =
receive</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">more =
feedback from the IEEE. If now special problems show up, the next =
version of</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
Internet-Draft is aimed for WG Last Call.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Summary:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Introductions and Agenda Bashing. Three topics were =
covered;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">2. IEEE =
802.3 Update / - Dan Romascanu.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Between =
London IETF and SLC, there were two meetings of the 802.3ae =
group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Between =
the two meetings, people response to the documents and draft =
3.4c</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">was out =
for ballot. Now it is time for Sponsor ballot. According to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">number =
of iterations the document went through, it looks like it should =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">closed =
by March time frame, or June the latest.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">An =
interoperability test is expected for Bridge, VLAN, Interface, =
and</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Ether-like MIB. The result of the tests will provide =
feedback on current</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">documents. This might cause a delay for other document =
submitting time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">including WIS-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Results of AToMMIB's SONET-MIB status discussion /- Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">A draft =
is ready, will be submitted next week. There are only few =
minor</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">changes. =
It is important to get the document published since WIS-MIB =
depends</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">on it. =
There are no implementation reports of 2558, so if no progress =
will</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">be shown =
in advancing the documents toward draft standard, it will =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">published again as proposed.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The goal =
is to get reports by February.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Report from the Design Team and Open Issues for WIS MIB /- KC =
Norseth,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">There =
were three issues to resolve:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-What is =
the layering model and how should it be mapped to =
IF-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-How do =
we map SNMP objects to GDMO objects of WIS defined in 802.3ae =
clause</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">30.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">- How =
does the solution manage with ETH/RMON free running counters as =
well</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">as =
15</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">min =
interval SONET counters.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
proposal is to use what exist in ETH, MAU and SONET, as much =
as</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">possible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The WIS =
MIB can use many of the SONET table.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If Stack =
table should have the following: LLC, MAC, reconciliation, =
PHY</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">coding, =
Path, Line, Section and 802.3 WAN PMA/PMD.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
objects for PM are taken from 3 MIBS.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
solution needs no special HW beyond what is required in =
802.3ae.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">=B7 Not =
everyone in the team agreed to the layering model of =
having</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
on top of SONET. The suggestion was to add a layer between =
CSMACD</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">to SONET =
Path to indicate what kind of ETH over SONET payload mapping =
is</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">used.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Issues =
and Proposed Resolutions:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Layering Model:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Because =
the WIS payload mapping (i.e., 64B/66B encoded</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ehternet =
data mapped directly into the STS-192c payload capacity, with C2</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">set to =
'00011010'b) is just one of several Ethernet over SONET payload</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">mappings, it has been suggested that an additional =
ifStackTable layer in</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">between =
ethernetCsmacd(6) and sonetPath(50) should be present to indicate</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">what =
type of Ethernet over SONET payload mapping is being used. An =
alternative</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">suggestion is to use ifMauType and ifMauDefaultType for =
this purpose.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep the layering as currently defined in the</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">internet-draft and use ifMauType and ifMauDefaultType to =
indicate the type</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of =
Ethernet over SONET.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">2. =
Compliance:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Should =
the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">interfaces? An alternative would be to make them =
optional. In that case</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">10GBASE-W interfaces would require a multi-layer =
ifStackTable only if ETHER-WIS</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and =
SONET-MIB were supported; if not, then the usual single-layer model =
would apply.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep all the ETHER-WIS and SONET-MIB objects mandatory =
as</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">currently defined in the =
internet-draft.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Relationship with MAU-MIB:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The next =
Mau-MIB draft should specify what happens to the ifStackTable if</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ifMauDefaultType is changed from dot3MauType10GigBaseR to =
dot3MauType10GigBaseW</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">or =
vice-versa.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: The suggested was agreed. Mike Heard will provide the</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">text to =
be added to the Mau-MIB.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Clarification on Compliance:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Clarification text for compliance description in Section =
3.1 is needed.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Mike Heard will provide the clarification text for</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Section =
3.1 regarding compliance.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">It was =
decided to host the document in the HUBMIB group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Internet =
Draft:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&lt;http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">-01.txt&gt;</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C19B3D.84D1C77E--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Sat Jan 12 02:49:53 2002
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 CAA18084
	for <hubmib-archive@odin.ietf.org>; Sat, 12 Jan 2002 02:49:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA10652
	for hubmib-archive@odin.ietf.org; Sat, 12 Jan 2002 02:49:55 -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 CAA10624;
	Sat, 12 Jan 2002 02:49:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10597
	for <hubmib@optimus.ietf.org>; Sat, 12 Jan 2002 02:49:17 -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 CAA18056;
	Sat, 12 Jan 2002 02:49:14 -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 g0C7lxl00389;
	Sat, 12 Jan 2002 02:47: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 g0C7lwd00383;
	Sat, 12 Jan 2002 02:47: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_01C19B3D.84D1C77E"
Date: Sat, 12 Jan 2002 09:48:26 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF5404A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Miutes of the Joint atommib and hubmib meeting in SLC
Thread-Index: AcGbPZ2mN9lI78gMQVyAF8KsUhzGrw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <minutes@ietf.org>
Cc: <hubmib@ietf.org>, <atommib@research.telcordia.com>
Subject: [Hubmib] Miutes of the Joint atommib and hubmib meeting in SLC
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19B3D.84D1C77E
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find in the following the minutes of the joint meeting of hubmib
and atommib in SLC . Regards, Dan

52 IETF, Salt Lake City
Ethernet Interfaces and Hub MIB WG & AToM MIB WG (hubmib & atommib)
TUESDAY, December 11 at 1700-1800
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CHAIRS: Dan Romascanu <dromasca@avaya.com>
Faye Ly <fayely98@hotmail.com>
Nathan Kohn <mvnk@lucent.com>
The Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB
(atommib) WG=20
held a joint meeting at the 52nd IETF in Salt Lake City. The main
purpose of=20
the meeting was to report on the work from the design team formed by
members=20
of the two WGs in order to provide recommendations for the WAN Interface

Sublayer (WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update
were=20
also presented. It was noted that the WIS MIB is depended on the SONET
MIB for=20
the STS-192c update. Therefore the updated SONET-MIB should be
republished in=20
time regardless it is republished with or without advancement.
The participants in the meeting approved the approach presented in the=20
Internet-Drafts issued by the Design Team. The participants in the
meeting=20
proposed that the design team be transformed into an editor team to
further=20
the document. The open issues posted by the design team and the
recommendations=20
for resolution from the discussion are listed below. These issues and
proposed=20
resolution will be posted to the two WG lists, and to the IEEE 802.3ae
list.=20
The Hub MIB WG chair will request a slot for a presentation of the work
and open=20
issues at the interim meeting of the IEEE in January 2002, in order to
receive=20
more feedback from the IEEE. If now special problems show up, the next
version of=20
the Internet-Draft is aimed for WG Last Call.
Summary:
1. Introductions and Agenda Bashing. Three topics were covered;
2. IEEE 802.3 Update / - Dan Romascanu.
Between London IETF and SLC, there were two meetings of the 802.3ae
group.
Between the two meetings, people response to the documents and draft
3.4c
was out for ballot. Now it is time for Sponsor ballot. According to the
number of iterations the document went through, it looks like it should
be
closed by March time frame, or June the latest.
An interoperability test is expected for Bridge, VLAN, Interface, and
Ether-like MIB. The result of the tests will provide feedback on current
documents. This might cause a delay for other document submitting time
including WIS-MIB.
3. Results of AToMMIB's SONET-MIB status discussion /- Mike Heard
A draft is ready, will be submitted next week. There are only few minor
changes. It is important to get the document published since WIS-MIB
depends
on it. There are no implementation reports of 2558, so if no progress
will
be shown in advancing the documents toward draft standard, it will be
published again as proposed.=20
The goal is to get reports by February.
4. Report from the Design Team and Open Issues for WIS MIB /- KC
Norseth,
Mike Heard
There were three issues to resolve:
-What is the layering model and how should it be mapped to IF-MIB.
-How do we map SNMP objects to GDMO objects of WIS defined in 802.3ae
clause
30.
- How does the solution manage with ETH/RMON free running counters as
well
as 15=20
min interval SONET counters.
The proposal is to use what exist in ETH, MAU and SONET, as much as
possible.
The WIS MIB can use many of the SONET table.
If Stack table should have the following: LLC, MAC, reconciliation, PHY
coding, Path, Line, Section and 802.3 WAN PMA/PMD.
The objects for PM are taken from 3 MIBS.
The solution needs no special HW beyond what is required in 802.3ae.
=B7 Not everyone in the team agreed to the layering model of having
Ethernet on top of SONET. The suggestion was to add a layer between
CSMACD
to SONET Path to indicate what kind of ETH over SONET payload mapping is
used.
Issues and Proposed Resolutions:=20
1. Layering Model:=20
Because the WIS payload mapping (i.e., 64B/66B encoded=20
Ehternet data mapped directly into the STS-192c payload capacity, with
C2=20
set to '00011010'b) is just one of several Ethernet over SONET payload=20
mappings, it has been suggested that an additional ifStackTable layer in

between ethernetCsmacd(6) and sonetPath(50) should be present to
indicate=20
what type of Ethernet over SONET payload mapping is being used. An
alternative=20
suggestion is to use ifMauType and ifMauDefaultType for this purpose.
Proposed Resolution: Keep the layering as currently defined in the=20
internet-draft and use ifMauType and ifMauDefaultType to indicate the
type=20
of Ethernet over SONET.
2. Compliance:=20
Should the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W

interfaces? An alternative would be to make them optional. In that case=20
10GBASE-W interfaces would require a multi-layer ifStackTable only if
ETHER-WIS=20
and SONET-MIB were supported; if not, then the usual single-layer model
would apply.
Proposed Resolution: Keep all the ETHER-WIS and SONET-MIB objects
mandatory as=20
currently defined in the internet-draft.
3. Relationship with MAU-MIB:=20
The next Mau-MIB draft should specify what happens to the ifStackTable
if=20
ifMauDefaultType is changed from dot3MauType10GigBaseR to
dot3MauType10GigBaseW=20
or vice-versa.
Proposed Resolution: The suggested was agreed. Mike Heard will provide
the=20
text to be added to the Mau-MIB.=20
4. Clarification on Compliance:=20
Clarification text for compliance description in Section 3.1 is needed.
Proposed Resolution: Mike Heard will provide the clarification text for=20
Section 3.1 regarding compliance.
It was decided to host the document in the HUBMIB group.
Internet Draft:
<http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-wis
-mib
-01.txt>


------_=_NextPart_001_01C19B3D.84D1C77E
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Miutes of the Joint atommib and hubmib meeting in SLC</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find in the following the minutes of the joint meeting of hubmib and =
atommib in SLC . Regards, Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">52 IETF, =
Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
Interfaces and Hub MIB WG &amp; AToM MIB WG (hubmib &amp; =
atommib)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">TUESDAY, =
December 11 at 1700-1800</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">CHAIRS: =
Dan Romascanu &lt;dromasca@avaya.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Faye Ly =
&lt;fayely98@hotmail.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Nathan =
Kohn &lt;mvnk@lucent.com&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
Ethernet Interfaces and Hub MIB (hubmib) WG and the ATM MIB (atommib) =
WG</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">held a =
joint meeting at the 52nd IETF in Salt Lake City. The main purpose =
of</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
meeting was to report on the work from the design team formed by =
members</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of the =
two WGs in order to provide recommendations for the WAN Interface</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sublayer =
(WIS) MIB. Status of the IEEE 802.3ae and the SONET MIB update =
were</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">also =
presented. It was noted that the WIS MIB is depended on the SONET MIB =
for</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
STS-192c update. Therefore the updated SONET-MIB should be republished =
in</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">time =
regardless it is republished with or without =
advancement.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
participants in the meeting approved the approach presented in =
the</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Internet-Drafts issued by the Design Team. The =
participants in the meeting</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">proposed =
that the design team be transformed into an editor team to =
further</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
document. The open issues posted by the design team and the =
recommendations</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">for =
resolution from the discussion are listed below. These issues and =
proposed</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">resolution will be posted to the two WG lists, and to the =
IEEE 802.3ae list.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The Hub =
MIB WG chair will request a slot for a presentation of the work and =
open</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">issues =
at the interim meeting of the IEEE in January 2002, in order to =
receive</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">more =
feedback from the IEEE. If now special problems show up, the next =
version of</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">the =
Internet-Draft is aimed for WG Last Call.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Summary:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Introductions and Agenda Bashing. Three topics were =
covered;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">2. IEEE =
802.3 Update / - Dan Romascanu.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Between =
London IETF and SLC, there were two meetings of the 802.3ae =
group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Between =
the two meetings, people response to the documents and draft =
3.4c</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">was out =
for ballot. Now it is time for Sponsor ballot. According to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">number =
of iterations the document went through, it looks like it should =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">closed =
by March time frame, or June the latest.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">An =
interoperability test is expected for Bridge, VLAN, Interface, =
and</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Ether-like MIB. The result of the tests will provide =
feedback on current</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">documents. This might cause a delay for other document =
submitting time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">including WIS-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Results of AToMMIB's SONET-MIB status discussion /- Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">A draft =
is ready, will be submitted next week. There are only few =
minor</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">changes. =
It is important to get the document published since WIS-MIB =
depends</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">on it. =
There are no implementation reports of 2558, so if no progress =
will</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">be shown =
in advancing the documents toward draft standard, it will =
be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">published again as proposed.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The goal =
is to get reports by February.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Report from the Design Team and Open Issues for WIS MIB /- KC =
Norseth,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Mike =
Heard</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">There =
were three issues to resolve:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-What is =
the layering model and how should it be mapped to =
IF-MIB.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-How do =
we map SNMP objects to GDMO objects of WIS defined in 802.3ae =
clause</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">30.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">- How =
does the solution manage with ETH/RMON free running counters as =
well</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">as =
15</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">min =
interval SONET counters.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
proposal is to use what exist in ETH, MAU and SONET, as much =
as</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">possible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The WIS =
MIB can use many of the SONET table.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If Stack =
table should have the following: LLC, MAC, reconciliation, =
PHY</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">coding, =
Path, Line, Section and 802.3 WAN PMA/PMD.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
objects for PM are taken from 3 MIBS.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
solution needs no special HW beyond what is required in =
802.3ae.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">=B7 Not =
everyone in the team agreed to the layering model of =
having</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ethernet =
on top of SONET. The suggestion was to add a layer between =
CSMACD</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">to SONET =
Path to indicate what kind of ETH over SONET payload mapping =
is</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">used.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Issues =
and Proposed Resolutions:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">1. =
Layering Model:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Because =
the WIS payload mapping (i.e., 64B/66B encoded</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ehternet =
data mapped directly into the STS-192c payload capacity, with C2</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">set to =
'00011010'b) is just one of several Ethernet over SONET payload</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">mappings, it has been suggested that an additional =
ifStackTable layer in</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">between =
ethernetCsmacd(6) and sonetPath(50) should be present to indicate</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">what =
type of Ethernet over SONET payload mapping is being used. An =
alternative</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">suggestion is to use ifMauType and ifMauDefaultType for =
this purpose.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep the layering as currently defined in the</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">internet-draft and use ifMauType and ifMauDefaultType to =
indicate the type</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">of =
Ethernet over SONET.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">2. =
Compliance:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Should =
the ETHER-WIS and SONET-MIB objects be required for all 10GBASE-W</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">interfaces? An alternative would be to make them =
optional. In that case</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">10GBASE-W interfaces would require a multi-layer =
ifStackTable only if ETHER-WIS</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">and =
SONET-MIB were supported; if not, then the usual single-layer model =
would apply.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Keep all the ETHER-WIS and SONET-MIB objects mandatory =
as</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">currently defined in the =
internet-draft.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">3. =
Relationship with MAU-MIB:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The next =
Mau-MIB draft should specify what happens to the ifStackTable if</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ifMauDefaultType is changed from dot3MauType10GigBaseR to =
dot3MauType10GigBaseW</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">or =
vice-versa.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: The suggested was agreed. Mike Heard will provide the</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">text to =
be added to the Mau-MIB.</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">4. =
Clarification on Compliance:</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Clarification text for compliance description in Section =
3.1 is needed.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Proposed =
Resolution: Mike Heard will provide the clarification text for</FONT> =
</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Section =
3.1 regarding compliance.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">It was =
decided to host the document in the HUBMIB group.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Internet =
Draft:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&lt;http://www.ietf.cnri.reston.va.us/internet-drafts/draf=
t-ietf-hubmib-wis-mib</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">-01.txt&gt;</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C19B3D.84D1C77E--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From daemon@optimus.ietf.org  Sat Jan 12 03:44:12 2002
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 CAA18009
	for <hubmib-archive@odin.ietf.org>; Sat, 12 Jan 2002 02:46:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA10513
	for hubmib-archive@odin.ietf.org; Sat, 12 Jan 2002 02:46:11 -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 CAA10482;
	Sat, 12 Jan 2002 02:45: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 CAA10451
	for <hubmib@optimus.ietf.org>; Sat, 12 Jan 2002 02:45:33 -0500 (EST)
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 CAA17985;
	Sat, 12 Jan 2002 02:45:29 -0500 (EST)
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 CAA19028;
	Sat, 12 Jan 2002 02:44:08 -0500 (EST)
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 CAA19017;
	Sat, 12 Jan 2002 02:44:06 -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_01C19B3C.FE98AC7A"
Date: Sat, 12 Jan 2002 09:44:41 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54049@IS0004AVEXU1.global.avaya.com>
Thread-Topic: SLC Hubmib Minutes
Thread-Index: AcGbPReoKt1KKBdfSlWULMmAV+FHIA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <minutes@ietf.org>
Cc: <hubmib@ietf.org>
Subject: [Hubmib] SLC Hubmib Minutes
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C19B3C.FE98AC7A
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Please find attached the minutes of the SLC hubmib meeting.=20
Regards,
Dan
HUBMIB WG IETF 52, Salt Lake City
Monday afternoon session II
Notes
K.C. - Minutes taker
Dan Romascanu discussion leader
The agenda from the main agenda link is invalid. IETF isn't concerned.
The real hubmib agenda can be found at:
<http://www.ietf.org/ietf/01dec/hubmib.txt>
*	IEEE 802.3 Status Report=20
*	two IEEE meetings since London=20
*	802.ae=20
*	draft 34 in ballot between 11/17 and 12/3=20
*	Sponsor Ballot to follow=20
*	Standard expected 3/02 and 6/02
*	802.3af=20
*	D3.0 in Ballot between 11/16 & 12/30=20
*	Standard expected between 9/02 and 11/02=20
*	Standard slightly behind time=20
*	Changes expected
*	802.3ah (Ethernet first mile)=20
*	WG formed - 9/01=20
*	Four tracks:=20
*	=B7 Fiber p2p=20
*	=B7 Copper p2p=20
*	=B7 Fiber p2mp=20
*	=B7 OAM=20
*	Far from IETF involved still too early in IEEE
*	RFC=92s=20
*	1515 - should be obsolete by 2668 - was not.=20
*	2108=20
*	2665=20
*	2666=20
*	2668=20
*	Confusion is there due to duplication of rfc=92s.=20
*	Next rfc on MAU mib will obsolete 1515 and 2668=20
*	Need implementation reports.=20
*	Enterasys wanted some issues answered before they implement
implementation=20
*	reports.=20
*	Would be nice to get implementation reports of where=20
*	John Flick - Problems with hardware help decide that
non-essential items will not be discussed.
		=B7 Etherlike MIBS
				o What do we do with the test oids now
that the table is gone? - Deprecate?
				o What about multiple manager stations?=20
				o rfc1229 Interfaces extensions
mib->rfc1273->deprecated for no implementations. We now have test oids
not in use. Recommended to deprecate and start a loopback test object.
Will post new object to mailing list.
				o Is the IFMTU clear. Someone requested
clarification to this, but it seems clear. It was decided that the
person who doesn=92t understand it to give example. It was decided to
leave as is until the person can produce the info.
				o IfAdminStatus (down) needs to be
clarified Mike Mcfadden brought up the issue in the bridge wg where
multiple vendors have multiple reactions to this. Fiber was not tested.
There needs to be clarification needed from IEEE. John will write text
to ask and Dan will make the request.
				o issue on rfc1643 - 2 current versions
of the Ethernet mib. - do we move it to historic, full standard? Should
we put in our current draft an explanation of why there are 2 drafts.
Some vendors are using rfc1643 with private mibs.
		=B7 MAU MIB
				o Some outstanding edits are still here.
There are some issues in the WIS MIB and SONET that will affect some
text.
				o Some issues from the InterWorking labs
test summit may affect this. We will have to wait until at least the end
of January to get its information. Do we wait?=20
				o Issues that could come up are
misunderstanding in the implementation? Some packets and octets that
could have misunderstanding. It was decided to wait for the test summit.
				o Some SONET entry in the ifStackEntry
stackables issues. This goes along with the WIS MIB work. Where do we do
the clarification? Decided we would discuss this in the WIS mib meeting.
				o discussed the implementation of the
auto-negotiation duplex info. Some are implementing the MAU mib as is.
Others are implementing this in the private mibs due to being
cumbersome. GBIC swap may only be partly relevant to the configuration.
Use a enumerated integer for setting? This is what some people are
doing. John had posted to the wg how HP is doing their proprietary mib
as a suggestion.
				o Forcing the autonegotiation down
configuration came up. Once again, not having implementation reports to
review against doesn=92t help solve the issue. We need more =
implementation
reports. There are some vendors that have implemented the way as
written.
				o Dan proposed that we do the updates to
the mib as posted previously by John as recommendation of the committee
and let people see it. Mike H. suggested some new oid=92s written to =
help
out with this. People could help by reviewing the jack type enumeration.

				o Power MIB
				o latest draft published November 2001
				o Misc spelling and compile warning
errors were noted.
				o Changes resulting from
IEEEportPortPowerPairs object deleted.
				o Delete off option of the power port
detection control object
				o add new objects to
powerdetectionstatus object.
				o delete powerportclassificationobject
				o update naming of objects
				o Reviewed some implementation notes
from PowerDsine that will be added to next version.
				o The IETF document status is stable. We
don=92t know what the IEEE is going to do. For this reason just respin =
the
draft and wait for the IEEE to go on.
				o Last-call may happen in Feb 02
depending on the IEEE.
The goal is to finish all for the IETF in Minneapolis. in March.
Goals and Milestones
Dec 01 - Gather implementation experience
Jan 02 - Issue revised drafts - Missed
Jan 02 - Forward drafts to AD/IESG - pushed to Feb.
Feb 02 - Last call in Feb.


------_=_NextPart_001_01C19B3C.FE98AC7A
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>SLC Hubmib Minutes</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Please =
find attached the minutes of the SLC hubmib meeting. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dan</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">HUBMIB WG IETF 52, Salt Lake City</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Monday afternoon session II</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Notes</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">K.C. - Minutes taker</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dan Romascanu discussion leader</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The agenda from the main agenda link is invalid. IETF isn't =
concerned.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The real hubmib agenda can be found at:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">&lt;<A =
HREF=3D"http://www.ietf.org/ietf/01dec/hubmib.txt">http://www.ietf.org/ie=
tf/01dec/hubmib.txt</A>&gt;</FONT></U></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">IEEE 802.3 Status Report</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">two IEEE meetings since London</FONT><FONT FACE=3D"Times New =
Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.ae</FONT> </SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">draft 34 in ballot between 11/17 and 12/3</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Sponsor Ballot to follow</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard expected 3/02 and 6/02</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3af</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">D3.0 in Ballot between 11/16 &amp; 12/30</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard expected between 9/02 and 11/02</FONT><FONT FACE=3D"Times =
New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Standard slightly behind time</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Changes expected</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">802.3ah (Ethernet first mile)</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">WG formed - 9/01</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Four tracks:</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Fiber p2p</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Copper p2p</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 Fiber p2mp</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">=B7 OAM</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Far from IETF involved still too early in =
IEEE</FONT></SPAN></LI></DIV>
</UL></UL>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">RFC=92s</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>
<UL DIR=3DLTR>
<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">1515 - should be obsolete by 2668 - was not.</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2108</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2665</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2666</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">2668</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Confusion is there due to duplication of rfc=92s.</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Next rfc on MAU mib will obsolete 1515 and 2668</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Need implementation reports.</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Enterasys wanted some issues answered before they implement =
implementation</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">reports.</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Would be nice to get implementation reports of where</FONT><FONT =
FACE=3D"Times New Roman"> </FONT></SPAN></LI></DIV>

<DIV DIR=3DLTR><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">John Flick - Problems with hardware help decide that non-essential =
items will not be discussed.</FONT></SPAN></LI></DIV>
</UL></UL></UL></UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">=B7</FONT><FONT SIZE=3D2 FACE=3D"Courier New"> Etherlike =
MIBS</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
What do we do with the test oids now that the table is gone? - =
Deprecate?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
What about multiple manager stations?</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
rfc1229 Interfaces extensions mib-&gt;rfc1273-&gt;deprecated for no =
implementations. We now have test oids not in use. Recommended to =
deprecate and start a loopback test object. Will post new object to =
mailing list.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Is the IFMTU clear. Someone requested clarification to this, but it =
seems clear. It was decided that the person who doesn=92t understand it =
to give example. It was decided to leave as is until the person can =
produce the info.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
IfAdminStatus (down) needs to be clarified Mike Mcfadden brought up the =
issue in the bridge wg where multiple vendors have multiple reactions to =
this. Fiber was not tested. There needs to be clarification needed from =
IEEE. John will write text to ask and Dan will make the =
request.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
issue on rfc1643 - 2 current versions of the Ethernet mib. - do we move =
it to historic, full standard? Should we put in our current draft an =
explanation of why there are 2 drafts. Some vendors are using rfc1643 =
with private mibs.</FONT></SPAN></P>
</UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Symbol">=B7</FONT><FONT SIZE=3D2 FACE=3D"Courier New"> MAU =
MIB</FONT></SPAN></P>
<UL DIR=3DLTR><UL DIR=3DLTR><UL DIR=3DLTR>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some outstanding edits are still here. There are some issues in the WIS =
MIB and SONET that will affect some text.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some issues from the InterWorking labs test summit may affect this. We =
will have to wait until at least the end of January to get its =
information. Do we wait?</FONT> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Issues that could come up are misunderstanding in the implementation? =
Some packets and octets that could have misunderstanding. It was decided =
to wait for the test summit.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Some SONET entry in the ifStackEntry stackables issues. This goes along =
with the WIS MIB work. Where do we do the clarification? Decided we =
would discuss this in the WIS mib meeting.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
discussed the implementation of the auto-negotiation duplex info. Some =
are implementing the MAU mib as is. Others are implementing this in the =
private mibs due to being cumbersome. GBIC swap may only be partly =
relevant to the configuration. Use a enumerated integer for setting? =
This is what some people are doing. John had posted to the wg how HP is =
doing their proprietary mib as a suggestion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Forcing the autonegotiation down configuration came up. Once again, not =
having implementation reports to review against doesn=92t help solve the =
issue. We need more implementation reports. There are some vendors that =
have implemented the way as written.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Dan proposed that we do the updates to the mib as posted previously by =
John as recommendation of the committee and let people see it. Mike H. =
suggested some new oid=92s written to help out with this. People could =
help by reviewing the jack type enumeration.</FONT></SPAN></P>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Power MIB</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
latest draft published November 2001</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Misc spelling and compile warning errors were noted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Changes resulting from IEEEportPortPowerPairs object =
deleted.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Delete off option of the power port detection control =
object</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
add new objects to powerdetectionstatus object.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
delete powerportclassificationobject</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
update naming of objects</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Reviewed some implementation notes from PowerDsine that will be added to =
next version.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
The IETF document status is stable. We don=92t know what the IEEE is =
going to do. For this reason just respin the draft and wait for the IEEE =
to go on.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier New">o =
Last-call may happen in Feb 02 depending on the IEEE.</FONT></SPAN></P>
</UL></UL></UL></UL></UL>
<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">The goal is to finish all for the IETF in Minneapolis. in =
March.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Goals and Milestones</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Dec 01 - Gather implementation experience</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Issue revised drafts - Missed</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Jan 02 - Forward drafts to AD/IESG - pushed to =
Feb.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Courier =
New">Feb 02 - Last call in Feb.</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C19B3C.FE98AC7A--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Jan 15 13:30:58 2002
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 NAA08488
	for <hubmib-archive@odin.ietf.org>; Tue, 15 Jan 2002 13:30:57 -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 NAA17363;
	Tue, 15 Jan 2002 13:30:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17332
	for <hubmib@optimus.ietf.org>; Tue, 15 Jan 2002 13:30:24 -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 NAA08452
	for <hubmib@ietf.org>; Tue, 15 Jan 2002 13:30:21 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA19709;
	Tue, 15 Jan 2002 10:30:20 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 15 Jan 2002 10:30:19 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: HSSG Reflector <stds-802-3-hssg@ieee.org>,
        Hubmib Reflector <hubmib@ietf.org>
Message-ID: <Pine.LNX.4.10.10201151006370.7137-110000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-737074695-1011118008=:7137"
Content-ID: <Pine.LNX.4.10.10201151016100.7137@shell4.bayarea.net>
Subject: [Hubmib] I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt (fwd)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---2133786286-737074695-1011118008=:7137
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.10.10201151016101.7137@shell4.bayarea.net>

Colleagues,

The above-named draft is the updated SONET-MIB that is incorporated by
reference into the draft SNMP WIS MIB currently under discussion (see
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt).

Regards,

Mike Heard

---2133786286-737074695-1011118008=:7137
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.10.10201151006400.7137@shell4.bayarea.net>
Content-Description: I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt (fwd)
Content-Disposition: INLINE

Return-Path: <atommib-request@research.telcordia.com>
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id DAA15052
	for <heard@shell4.bayarea.net>; Tue, 15 Jan 2002 03:39:18 -0800
	(envelope-from atommib-request@research.telcordia.com)
Received: from wormwood.pobox.com (wormwood.pobox.com [208.210.125.20])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id DAA55004
	for <heard@bayarea.net>; Tue, 15 Jan 2002 03:39:17 -0800 (PST)
	(envelope-from atommib-request@research.telcordia.com)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by wormwood.pobox.com (Postfix) with ESMTP id 8638872511
	for <heard@pobox.com>; Tue, 15 Jan 2002 06:39:12 -0500 (EST)
Received: (from slmgr@localhost)
	by thumper.research.telcordia.com (8.12.1/8.12.1) id g0FBTKSL022688;
	Tue, 15 Jan 2002 06:29:20 -0500 (EST)
Resent-Date: Tue, 15 Jan 2002 06:29:20 -0500 (EST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g0FBPojh022287
	for <atommib@research.telcordia.com>; Tue, 15 Jan 2002 06:25:50 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17521;
	Tue, 15 Jan 2002 06:25:48 -0500 (EST)
Message-Id: <200201151125.GAA17521@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: atommib@research.telcordia.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt
Date: Tue, 15 Jan 2002 06:25:47 -0500
Sender: nsyracus@cnri.reston.va.us
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Resent-Message-ID: <35Uji.A.fcF.CHBR8@thumper>
Resent-From: atommib@research.telcordia.com
X-Mailing-List: <atommib@research.telcordia.com> 
X-Loop: atommib@research.telcordia.com
Precedence: list
Resent-Sender: atommib-request@research.telcordia.com


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the AToM MIB Working Group of the IETF.

	Title		: Definitions of Managed Objects for the SONET/SDH 
                          Interface Type
	Author(s)	: K. Tesink
	Filename	: draft-ietf-atommib-rfc2558bis-00.txt
	Pages		: 92
	Date		: 14-Jan-02
	
This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-
based internets.  In particular, it defines objects for
managing Synchronous Optical Network/Synchronous Digital
Hierarchy (SONET/SDH) interfaces.  This document is a
companion to the documents that define Managed Objects for the
DS1/E1/DS2/E2 and DS3/E3 Interface Types [RFC2496][RFC2495].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-atommib-rfc2558bis-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020114174738.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-atommib-rfc2558bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020114174738.I-D@ietf.org>

--OtherAccess--

--NextPart--


---2133786286-737074695-1011118008=:7137--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Tue Jan 15 13:30:58 2002
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 NAA08497
	for <hubmib-archive@odin.ietf.org>; Tue, 15 Jan 2002 13:30:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA17530
	for hubmib-archive@odin.ietf.org; Tue, 15 Jan 2002 13:30:59 -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 NAA17363;
	Tue, 15 Jan 2002 13:30:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17332
	for <hubmib@optimus.ietf.org>; Tue, 15 Jan 2002 13:30:24 -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 NAA08452
	for <hubmib@ietf.org>; Tue, 15 Jan 2002 13:30:21 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA19709;
	Tue, 15 Jan 2002 10:30:20 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 15 Jan 2002 10:30:19 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: HSSG Reflector <stds-802-3-hssg@ieee.org>,
        Hubmib Reflector <hubmib@ietf.org>
Message-ID: <Pine.LNX.4.10.10201151006370.7137-110000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-2133786286-737074695-1011118008=:7137"
Content-ID: <Pine.LNX.4.10.10201151016100.7137@shell4.bayarea.net>
Subject: [Hubmib] I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt (fwd)
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---2133786286-737074695-1011118008=:7137
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.10.10201151016101.7137@shell4.bayarea.net>

Colleagues,

The above-named draft is the updated SONET-MIB that is incorporated by
reference into the draft SNMP WIS MIB currently under discussion (see
http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-01.txt).

Regards,

Mike Heard

---2133786286-737074695-1011118008=:7137
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.10.10201151006400.7137@shell4.bayarea.net>
Content-Description: I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt (fwd)
Content-Disposition: INLINE

Return-Path: <atommib-request@research.telcordia.com>
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id DAA15052
	for <heard@shell4.bayarea.net>; Tue, 15 Jan 2002 03:39:18 -0800
	(envelope-from atommib-request@research.telcordia.com)
Received: from wormwood.pobox.com (wormwood.pobox.com [208.210.125.20])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id DAA55004
	for <heard@bayarea.net>; Tue, 15 Jan 2002 03:39:17 -0800 (PST)
	(envelope-from atommib-request@research.telcordia.com)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by wormwood.pobox.com (Postfix) with ESMTP id 8638872511
	for <heard@pobox.com>; Tue, 15 Jan 2002 06:39:12 -0500 (EST)
Received: (from slmgr@localhost)
	by thumper.research.telcordia.com (8.12.1/8.12.1) id g0FBTKSL022688;
	Tue, 15 Jan 2002 06:29:20 -0500 (EST)
Resent-Date: Tue, 15 Jan 2002 06:29:20 -0500 (EST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g0FBPojh022287
	for <atommib@research.telcordia.com>; Tue, 15 Jan 2002 06:25:50 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17521;
	Tue, 15 Jan 2002 06:25:48 -0500 (EST)
Message-Id: <200201151125.GAA17521@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: atommib@research.telcordia.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-atommib-rfc2558bis-00.txt
Date: Tue, 15 Jan 2002 06:25:47 -0500
Sender: nsyracus@cnri.reston.va.us
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Resent-Message-ID: <35Uji.A.fcF.CHBR8@thumper>
Resent-From: atommib@research.telcordia.com
X-Mailing-List: <atommib@research.telcordia.com> 
X-Loop: atommib@research.telcordia.com
Precedence: list
Resent-Sender: atommib-request@research.telcordia.com


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the AToM MIB Working Group of the IETF.

	Title		: Definitions of Managed Objects for the SONET/SDH 
                          Interface Type
	Author(s)	: K. Tesink
	Filename	: draft-ietf-atommib-rfc2558bis-00.txt
	Pages		: 92
	Date		: 14-Jan-02
	
This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-
based internets.  In particular, it defines objects for
managing Synchronous Optical Network/Synchronous Digital
Hierarchy (SONET/SDH) interfaces.  This document is a
companion to the documents that define Managed Objects for the
DS1/E1/DS2/E2 and DS3/E3 Interface Types [RFC2496][RFC2495].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-atommib-rfc2558bis-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020114174738.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-atommib-rfc2558bis-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-atommib-rfc2558bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020114174738.I-D@ietf.org>

--OtherAccess--

--NextPart--


---2133786286-737074695-1011118008=:7137--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 16 07:19:32 2002
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 HAA05117
	for <hubmib-archive@odin.ietf.org>; Wed, 16 Jan 2002 07:19: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 HAA28421;
	Wed, 16 Jan 2002 07:18:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA28390
	for <hubmib@optimus.ietf.org>; Wed, 16 Jan 2002 07:18:53 -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 HAA05105
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:18:50 -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 g0GCHYd22009
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:17:34 -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 g0GCHX322005
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:17:33 -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"
Date: Wed, 16 Jan 2002 14:18:01 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54075@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit
Thread-Index: AcGeLsnQR4wIgkWZTzauCJtnZFXFsgAWLBcQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA28391
Subject: [Hubmib] FW: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

Please note the following announcement about the Bridge and Interfaces
MIB Test Summit organized by InterWorking Labs. The test plan includes
partial testing of RFC 2665. Chris Wellens graciously agreed to
contribute to our WG with a report on results and issues related to RFC
2665 that will be discovered during the testing. These results should be
available prior to the March IETF meeting in Minneapolis.

Regards,

Dan


-----Original Message-----
From: Chris Wellens [mailto:chrisw@iwl.com]
Sent: Wednesday, January 16, 2002 3:38 AM
To: bridge-mib@ietf.org
Subject: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit




The Draft Test Plan for the Bridge & Interfaces MIB Test Summit is now
available for comment at http://www.iwl.com/Info/test_plan.html

Some areas of RFC 2674 are very difficult to test and suggestions for
how to best do this are welcome and should be posted to the mailing
list.

Phase One -- *FREE* Meeting to Discuss Test Plan

1:30 - 4:30 p.m.
Monday, January 28th
Wyndham Hotel
1350 North First Street
San Jose, California

The purpose of the meeting will be to ask all the implementors to come
together to discuss the test plan and offer suggestions on the areas
where testing is highly problematic, due to precision timing issues,
and massive network reconfiguration.

Phase Two:  -- Actual Test Summit

March 5, 6, 7, 2002
InterWorking Labs
Scotts Valley, California

Participants will test their products implementing (RFCs 2665, 2233,
2863, 2674,
and/or 1493) for conformance and interoperability with other
implementations.
Participants will also identify and clarify areas of confusion in the
RFCs where
implementations differ.






_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 16 07:19:32 2002
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 HAA05126
	for <hubmib-archive@odin.ietf.org>; Wed, 16 Jan 2002 07:19:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA28467
	for hubmib-archive@odin.ietf.org; Wed, 16 Jan 2002 07:19:35 -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 HAA28421;
	Wed, 16 Jan 2002 07:18:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA28390
	for <hubmib@optimus.ietf.org>; Wed, 16 Jan 2002 07:18:53 -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 HAA05105
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:18:50 -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 g0GCHYd22009
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:17:34 -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 g0GCHX322005
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 07:17:33 -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"
Date: Wed, 16 Jan 2002 14:18:01 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54075@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit
Thread-Index: AcGeLsnQR4wIgkWZTzauCJtnZFXFsgAWLBcQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA28391
Subject: [Hubmib] FW: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

Please note the following announcement about the Bridge and Interfaces
MIB Test Summit organized by InterWorking Labs. The test plan includes
partial testing of RFC 2665. Chris Wellens graciously agreed to
contribute to our WG with a report on results and issues related to RFC
2665 that will be discovered during the testing. These results should be
available prior to the March IETF meeting in Minneapolis.

Regards,

Dan


-----Original Message-----
From: Chris Wellens [mailto:chrisw@iwl.com]
Sent: Wednesday, January 16, 2002 3:38 AM
To: bridge-mib@ietf.org
Subject: [Bridge-mib] Draft Test Plan for the Bridge MIB Test Summit




The Draft Test Plan for the Bridge & Interfaces MIB Test Summit is now
available for comment at http://www.iwl.com/Info/test_plan.html

Some areas of RFC 2674 are very difficult to test and suggestions for
how to best do this are welcome and should be posted to the mailing
list.

Phase One -- *FREE* Meeting to Discuss Test Plan

1:30 - 4:30 p.m.
Monday, January 28th
Wyndham Hotel
1350 North First Street
San Jose, California

The purpose of the meeting will be to ask all the implementors to come
together to discuss the test plan and offer suggestions on the areas
where testing is highly problematic, due to precision timing issues,
and massive network reconfiguration.

Phase Two:  -- Actual Test Summit

March 5, 6, 7, 2002
InterWorking Labs
Scotts Valley, California

Participants will test their products implementing (RFCs 2665, 2233,
2863, 2674,
and/or 1493) for conformance and interoperability with other
implementations.
Participants will also identify and clarify areas of confusion in the
RFCs where
implementations differ.






_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
http://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 16 13:32:03 2002
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 NAA16962
	for <hubmib-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:31:58 -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 NAA13701;
	Wed, 16 Jan 2002 13:28:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13670
	for <hubmib@optimus.ietf.org>; Wed, 16 Jan 2002 13:28:02 -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 NAA16761
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 13:27:59 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA01565;
	Wed, 16 Jan 2002 10:28:00 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 16 Jan 2002 10:27:59 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
Message-ID: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Colleagues,

FYI: the following contribution to T1X1.5 (written by Tom
Alexander, David Martin, and Steve Gorshe) may be of interest,
as it presents a detailed argument that ELTE can be
realized within existing NEs -- e.g. as a 10GBASE-W line
card -- and does not require a separate external piece of
equipment.  That was exactly the message of the last slide
in the WIS MIB design team's IETF52 presentation (see
http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
illustrating a 10GBASE-W interface on a SONET ADM.

Regards,

Mike Heard

CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating 
Equipment (ELTE) function and its realization within existing SONET 
equipment
DESC: This contribution clarifies the issues that have been raised with 
regards to the proposed ELTE function, needed to adapt a 10GBASE-W 
Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In 
particular, we demonstrate that such adaptation does not need 
additional NEs; that is, the ELTE function can be realized by existing 
NEs, and does not require new equipment to be added to a SONET/SDH 
network.
CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
SOURCE: Nortel Networks, PMC-Sierra


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 16 13:32:04 2002
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 NAA16980
	for <hubmib-archive@odin.ietf.org>; Wed, 16 Jan 2002 13:32:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14230
	for hubmib-archive@odin.ietf.org; Wed, 16 Jan 2002 13:32:05 -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 NAA13701;
	Wed, 16 Jan 2002 13:28:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13670
	for <hubmib@optimus.ietf.org>; Wed, 16 Jan 2002 13:28:02 -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 NAA16761
	for <hubmib@ietf.org>; Wed, 16 Jan 2002 13:27:59 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA01565;
	Wed, 16 Jan 2002 10:28:00 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 16 Jan 2002 10:27:59 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
Message-ID: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Colleagues,

FYI: the following contribution to T1X1.5 (written by Tom
Alexander, David Martin, and Steve Gorshe) may be of interest,
as it presents a detailed argument that ELTE can be
realized within existing NEs -- e.g. as a 10GBASE-W line
card -- and does not require a separate external piece of
equipment.  That was exactly the message of the last slide
in the WIS MIB design team's IETF52 presentation (see
http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
illustrating a 10GBASE-W interface on a SONET ADM.

Regards,

Mike Heard

CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating 
Equipment (ELTE) function and its realization within existing SONET 
equipment
DESC: This contribution clarifies the issues that have been raised with 
regards to the proposed ELTE function, needed to adapt a 10GBASE-W 
Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In 
particular, we demonstrate that such adaptation does not need 
additional NEs; that is, the ELTE function can be realized by existing 
NEs, and does not require new equipment to be added to a SONET/SDH 
network.
CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
SOURCE: Nortel Networks, PMC-Sierra


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Thu Jan 17 23:17:14 2002
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 XAA21390
	for <hubmib-archive@odin.ietf.org>; Thu, 17 Jan 2002 23:17:14 -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 XAA09870;
	Thu, 17 Jan 2002 23:16:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA03097
	for <hubmib@optimus.ietf.org>; Thu, 17 Jan 2002 20:24:42 -0500 (EST)
Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16903
	for <hubmib@ietf.org>; Thu, 17 Jan 2002 20:24:40 -0500 (EST)
Received: from user-2ivf7db.dialup.mindspring.com ([165.247.157.171] helo=RABHPNOTEBK.mindspring.com)
	by granger.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16RNln-0005UC-00; Thu, 17 Jan 2002 20:24:40 -0500
Message-Id: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 17 Jan 2002 10:50:56 -0600
To: "C. M. Heard" <heard@pobox.com>, Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n
 et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

There is a single point of failure that prevents a WIS as defined by IEEE 
from ever being an interface on SONET ADM.  The client interface on a SONET 
ADM requires clock synchronization either through "loop timing" or 
"PRS".  Neither of these are available in the WIS.  This lack of 
synchronization to a transmission network prevents the ADM from being able 
to multiplex the WIS signal into a SONET signal.
As defined, the WIS can never be a client of a SONET or SDH system.  It can 
be a "peer" on an optical network only.  The T1X1.5 proposal provides for a 
"peering" between a WIS and a SONET managed optical network.  It does not 
provide for the WIS to be an interface on a SONET system.

Thank you,
Roy Bynum
Orbital View LLC

At 10:27 AM 1/16/2002 -0800, C. M. Heard wrote:

>Colleagues,
>
>FYI: the following contribution to T1X1.5 (written by Tom
>Alexander, David Martin, and Steve Gorshe) may be of interest,
>as it presents a detailed argument that ELTE can be
>realized within existing NEs -- e.g. as a 10GBASE-W line
>card -- and does not require a separate external piece of
>equipment.  That was exactly the message of the last slide
>in the WIS MIB design team's IETF52 presentation (see
>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>illustrating a 10GBASE-W interface on a SONET ADM.
>
>Regards,
>
>Mike Heard
>
>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>Equipment (ELTE) function and its realization within existing SONET
>equipment
>DESC: This contribution clarifies the issues that have been raised with
>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>particular, we demonstrate that such adaptation does not need
>additional NEs; that is, the ELTE function can be realized by existing
>NEs, and does not require new equipment to be added to a SONET/SDH
>network.
>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Thu Jan 17 23:17:15 2002
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 XAA21400
	for <hubmib-archive@odin.ietf.org>; Thu, 17 Jan 2002 23:17:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA09966
	for hubmib-archive@odin.ietf.org; Thu, 17 Jan 2002 23:17: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 XAA09870;
	Thu, 17 Jan 2002 23:16:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA03097
	for <hubmib@optimus.ietf.org>; Thu, 17 Jan 2002 20:24:42 -0500 (EST)
Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16903
	for <hubmib@ietf.org>; Thu, 17 Jan 2002 20:24:40 -0500 (EST)
Received: from user-2ivf7db.dialup.mindspring.com ([165.247.157.171] helo=RABHPNOTEBK.mindspring.com)
	by granger.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16RNln-0005UC-00; Thu, 17 Jan 2002 20:24:40 -0500
Message-Id: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 17 Jan 2002 10:50:56 -0600
To: "C. M. Heard" <heard@pobox.com>, Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n
 et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

There is a single point of failure that prevents a WIS as defined by IEEE 
from ever being an interface on SONET ADM.  The client interface on a SONET 
ADM requires clock synchronization either through "loop timing" or 
"PRS".  Neither of these are available in the WIS.  This lack of 
synchronization to a transmission network prevents the ADM from being able 
to multiplex the WIS signal into a SONET signal.
As defined, the WIS can never be a client of a SONET or SDH system.  It can 
be a "peer" on an optical network only.  The T1X1.5 proposal provides for a 
"peering" between a WIS and a SONET managed optical network.  It does not 
provide for the WIS to be an interface on a SONET system.

Thank you,
Roy Bynum
Orbital View LLC

At 10:27 AM 1/16/2002 -0800, C. M. Heard wrote:

>Colleagues,
>
>FYI: the following contribution to T1X1.5 (written by Tom
>Alexander, David Martin, and Steve Gorshe) may be of interest,
>as it presents a detailed argument that ELTE can be
>realized within existing NEs -- e.g. as a 10GBASE-W line
>card -- and does not require a separate external piece of
>equipment.  That was exactly the message of the last slide
>in the WIS MIB design team's IETF52 presentation (see
>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>illustrating a 10GBASE-W interface on a SONET ADM.
>
>Regards,
>
>Mike Heard
>
>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>Equipment (ELTE) function and its realization within existing SONET
>equipment
>DESC: This contribution clarifies the issues that have been raised with
>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>particular, we demonstrate that such adaptation does not need
>additional NEs; that is, the ELTE function can be realized by existing
>NEs, and does not require new equipment to be added to a SONET/SDH
>network.
>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Fri Jan 18 02:21:44 2002
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 CAA02835
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:21:40 -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 CAA27851;
	Fri, 18 Jan 2002 02:21:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27825
	for <hubmib@optimus.ietf.org>; Fri, 18 Jan 2002 02:21:03 -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 CAA02827
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 02:21:01 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id XAA17783;
	Thu, 17 Jan 2002 23:21:02 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 17 Jan 2002 23:21:02 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
Message-ID: <Pine.LNX.4.10.10201171849420.19030-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Thu, 17 Jan 2002, Roy Bynum wrote:
> There is a single point of failure that prevents a WIS as defined
> by IEEE from ever being an interface on SONET ADM.  The client
> interface on a SONET ADM requires clock synchronization either
> through "loop timing" or "PRS".  Neither of these are available in
> the WIS.  This lack of synchronization to a transmission network
> prevents the ADM from being able to multiplex the WIS signal into
> a SONET signal.

That conclusion is false.  It is is possible to multiplex the WIS
SPE into a higher-order SONET signal because the WIS transmit clock
is required to meet the SONET minimum clock frequency accurracy of
+/- 20 ppm.  That is good enough to ensure that pointer justifications
can absorb the timing differences between the WIS clock and the
stratum clock used by a SONET ADM.  It is not necessary that the WIS
be loop timed or synchronized to a stratum clock in order to do that.
All this is spelled out in Section 2.4 of the T1X1.5 contribution.

> As defined, the WIS can never be a client of a SONET or SDH system.
> It can be a "peer" on an optical network only.  The T1X1.5 proposal
> provides for a "peering" between a WIS and a SONET managed optical
> network.  It does not provide for the WIS to be an interface on a
> SONET system.

I don't think that the authors of T1X1.5/2002-027 would necessarily
agree, since that contribution explicitly states that "[ ... ] the
ELTE function is intended to be realized within a SONET/SDH NE
(potentially on a line card)."

Regards,

Mike Heard


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Fri Jan 18 02:21:45 2002
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 CAA02850
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 02:21:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA27906
	for hubmib-archive@odin.ietf.org; Fri, 18 Jan 2002 02:21:46 -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 CAA27851;
	Fri, 18 Jan 2002 02:21:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27825
	for <hubmib@optimus.ietf.org>; Fri, 18 Jan 2002 02:21:03 -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 CAA02827
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 02:21:01 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id XAA17783;
	Thu, 17 Jan 2002 23:21:02 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 17 Jan 2002 23:21:02 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
Message-ID: <Pine.LNX.4.10.10201171849420.19030-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Thu, 17 Jan 2002, Roy Bynum wrote:
> There is a single point of failure that prevents a WIS as defined
> by IEEE from ever being an interface on SONET ADM.  The client
> interface on a SONET ADM requires clock synchronization either
> through "loop timing" or "PRS".  Neither of these are available in
> the WIS.  This lack of synchronization to a transmission network
> prevents the ADM from being able to multiplex the WIS signal into
> a SONET signal.

That conclusion is false.  It is is possible to multiplex the WIS
SPE into a higher-order SONET signal because the WIS transmit clock
is required to meet the SONET minimum clock frequency accurracy of
+/- 20 ppm.  That is good enough to ensure that pointer justifications
can absorb the timing differences between the WIS clock and the
stratum clock used by a SONET ADM.  It is not necessary that the WIS
be loop timed or synchronized to a stratum clock in order to do that.
All this is spelled out in Section 2.4 of the T1X1.5 contribution.

> As defined, the WIS can never be a client of a SONET or SDH system.
> It can be a "peer" on an optical network only.  The T1X1.5 proposal
> provides for a "peering" between a WIS and a SONET managed optical
> network.  It does not provide for the WIS to be an interface on a
> SONET system.

I don't think that the authors of T1X1.5/2002-027 would necessarily
agree, since that contribution explicitly states that "[ ... ] the
ELTE function is intended to be realized within a SONET/SDH NE
(potentially on a line card)."

Regards,

Mike Heard


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Fri Jan 18 17:06:57 2002
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 RAA28846
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 17:06:57 -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 RAA06491;
	Fri, 18 Jan 2002 17:00: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 QAA05263
	for <hubmib@ns.ietf.org>; Fri, 18 Jan 2002 16:26:20 -0500 (EST)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27715
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 16:26:17 -0500 (EST)
Received: from toque.cisco.com (toque.cisco.com [161.44.201.11])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id g0ILNao28890;
	Fri, 18 Jan 2002 13:23:36 -0800 (PST)
Received: from GNICHOLL-W2K.cisco.com (dhcp-kta2-161-44-198-151.cisco.com [161.44.198.151])
	by toque.cisco.com (Mirapoint)
	with ESMTP id AAC15538;
	Fri, 18 Jan 2002 16:21:15 -0500 (EST)
Message-Id: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
X-Sender: gnicholl@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Jan 2002 16:23:30 -0500
To: "C. M. Heard" <heard@pobox.com>
From: Gary Nicholl <gnicholl@cisco.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n
 et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Here are some of my thoughts on the T1X1 contribution.

Gary Nicholl

I would argue that the synchronization requirements and associated ELTE 
functionality are different depending on whether the 10GBASE-W is connected 
to an OC192c tributary port on a SONET ADM or to an OC192c transponder port 
on a DWDM system.

The T1X1 contribution focuses on the first of these, i.e. connecting to an 
OC192c port on an ADM. Such a port is actually section/line terminating and 
includes a full pointer processor. In this case I agree with the argument 
in the contribution that the necessary 'ELTE path relay function' 
essentially comes for free. It should therefore be possible to directly 
connect a 10GBASE-W interface to an  OC-192c port on a sonet ADM, and it 
should pass traffic error free.

But even here there is one wrinkle that is not addressed in the 
contribution. The 10GBASE-W uses a 20ppm clock source (not in itself an 
issue as this complies with the sonet minimum system clock specification, 
and is what has been used successfully on POS interfaces in the past) . 
However, unlike POS, the 10GBASE-W specification does not allow loop (i.e. 
line) timing. So the only option is to configure the interface for 
'internal' timing using the free-running 20ppm clock source. If you connect 
such an interface to an OC-192c port on a sonet ADM then, although the 
traffic will still pass error free (as described above and in the 
contribution),  you will get continuous pointer adjustments (PJCs) at a 
rate equal to the difference in frequency between the 10GBASE-W interface 
clock and the sonet network clock (likely to be Stratum 1). These PJCs will 
be detected and reported at every node in the network that the OC192c 
signal passes through. While the PJCs in themselves are not a major issue 
(i.e. do not cause any bit errors), they do represent an operational 
challenge for the network operator. In a synchronous sonet network the 
operator would not expect to see continuous PJCs reported from any node. 
Continuous PJCs in such a network are usually an indication of a 
synchronization failure and that one of the nodes has lost traceability to 
the Startum 1 network clock. As such monitoring PJCs is one of the few 
tools available to the operator to detect and isolate synchronization 
failures in the network.  A network operator would find it difficult (if 
not impossible) to distinguish between PJCs resulting from a true 
synchronization failure and those from a free-running 10GBASE-W interface 
connected to the network. For these reasons I find it hard to believe that 
any operator would allow a free running 20ppm 10GBASE-W interface to be 
connected to the network. I think if 10GBASE-W is ever to be widely adopted 
then 802.3 will eventually have to give in and support loop (line) timing.

Now connecting to a OC192c transponder port on a DWDM system is a little 
different. An OC192c transponder port is not the same as an  OC192c port on 
an ADM. It is not section/line terminating. It does not provide any pointer 
processing. It is really a simple 3R (OEO) regenerator. In this case the 
free running 20ppm clock is not the issue, as all DWDM systems are designed 
to lock onto and track to a sonet minimum clock, which is also 20ppm (note 
that this would have been a big issue with the original 802.3 plan to use a 
100ppm clock for the 10GBASE-W). The potential issue this time is related 
to jitter. The transponder interface is a simple OEO converter, and as such 
the jitter on the output (which is ultimately fed into the long haul dwdm 
network) is directly related to the jitter on the input (i.e. unlike an ADM 
the transponder interface on a dwdm system does not 'reset' the jitter 
budget). All OC192c transponder interfaces that I am aware of are designed 
under the assumption that the OC192 client signal (be it from an ADM or a 
POS interface on a router) complies with standard sonet jitter 
specifications (as defined in GR253 and whatever the equivalent ITU 
document is).  However the 10GBASE-W interface is based on ethernet jitter 
specifications and this might ultimately limit the performance of the DWDM 
System (note that the 10G ethernet specs allow up to 3X the jitter of an 
OC192 interface).

I am not saying that  it is impossible to  directly connect a 10GBASE-W 
interface to an existing OC192 DWDM system, but it is certainly not a 'no 
brainer' and would require some analysis to understand the impact of the 
ethernet jitter specs on the overall dwdm network design (i.e the 
additional jitter from the ethernet interface may be what ultimately limits 
the transmission distance).

The other approach would be to design a new 10GBASE-W transponder interface 
that 'cleans up' the jitter on the input and presents the line side of the 
dwdm system with similar specs to those from a standard OC-192 signal. 
However this obviously requires a new plug in card specific  to the 10GBASE-W.





At 01:27 PM 1/16/2002, C. M. Heard wrote:

>Colleagues,
>
>FYI: the following contribution to T1X1.5 (written by Tom
>Alexander, David Martin, and Steve Gorshe) may be of interest,
>as it presents a detailed argument that ELTE can be
>realized within existing NEs -- e.g. as a 10GBASE-W line
>card -- and does not require a separate external piece of
>equipment.  That was exactly the message of the last slide
>in the WIS MIB design team's IETF52 presentation (see
>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>illustrating a 10GBASE-W interface on a SONET ADM.
>
>Regards,
>
>Mike Heard
>
>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>Equipment (ELTE) function and its realization within existing SONET
>equipment
>DESC: This contribution clarifies the issues that have been raised with
>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>particular, we demonstrate that such adaptation does not need
>additional NEs; that is, the ELTE function can be realized by existing
>NEs, and does not require new equipment to be added to a SONET/SDH
>network.
>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Fri Jan 18 17:06:57 2002
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 RAA28855
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 17:06:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA07359
	for hubmib-archive@odin.ietf.org; Fri, 18 Jan 2002 17:07:00 -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 RAA06491;
	Fri, 18 Jan 2002 17:00: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 QAA05263
	for <hubmib@ns.ietf.org>; Fri, 18 Jan 2002 16:26:20 -0500 (EST)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27715
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 16:26:17 -0500 (EST)
Received: from toque.cisco.com (toque.cisco.com [161.44.201.11])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id g0ILNao28890;
	Fri, 18 Jan 2002 13:23:36 -0800 (PST)
Received: from GNICHOLL-W2K.cisco.com (dhcp-kta2-161-44-198-151.cisco.com [161.44.198.151])
	by toque.cisco.com (Mirapoint)
	with ESMTP id AAC15538;
	Fri, 18 Jan 2002 16:21:15 -0500 (EST)
Message-Id: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
X-Sender: gnicholl@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 Jan 2002 16:23:30 -0500
To: "C. M. Heard" <heard@pobox.com>
From: Gary Nicholl <gnicholl@cisco.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n
 et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Here are some of my thoughts on the T1X1 contribution.

Gary Nicholl

I would argue that the synchronization requirements and associated ELTE 
functionality are different depending on whether the 10GBASE-W is connected 
to an OC192c tributary port on a SONET ADM or to an OC192c transponder port 
on a DWDM system.

The T1X1 contribution focuses on the first of these, i.e. connecting to an 
OC192c port on an ADM. Such a port is actually section/line terminating and 
includes a full pointer processor. In this case I agree with the argument 
in the contribution that the necessary 'ELTE path relay function' 
essentially comes for free. It should therefore be possible to directly 
connect a 10GBASE-W interface to an  OC-192c port on a sonet ADM, and it 
should pass traffic error free.

But even here there is one wrinkle that is not addressed in the 
contribution. The 10GBASE-W uses a 20ppm clock source (not in itself an 
issue as this complies with the sonet minimum system clock specification, 
and is what has been used successfully on POS interfaces in the past) . 
However, unlike POS, the 10GBASE-W specification does not allow loop (i.e. 
line) timing. So the only option is to configure the interface for 
'internal' timing using the free-running 20ppm clock source. If you connect 
such an interface to an OC-192c port on a sonet ADM then, although the 
traffic will still pass error free (as described above and in the 
contribution),  you will get continuous pointer adjustments (PJCs) at a 
rate equal to the difference in frequency between the 10GBASE-W interface 
clock and the sonet network clock (likely to be Stratum 1). These PJCs will 
be detected and reported at every node in the network that the OC192c 
signal passes through. While the PJCs in themselves are not a major issue 
(i.e. do not cause any bit errors), they do represent an operational 
challenge for the network operator. In a synchronous sonet network the 
operator would not expect to see continuous PJCs reported from any node. 
Continuous PJCs in such a network are usually an indication of a 
synchronization failure and that one of the nodes has lost traceability to 
the Startum 1 network clock. As such monitoring PJCs is one of the few 
tools available to the operator to detect and isolate synchronization 
failures in the network.  A network operator would find it difficult (if 
not impossible) to distinguish between PJCs resulting from a true 
synchronization failure and those from a free-running 10GBASE-W interface 
connected to the network. For these reasons I find it hard to believe that 
any operator would allow a free running 20ppm 10GBASE-W interface to be 
connected to the network. I think if 10GBASE-W is ever to be widely adopted 
then 802.3 will eventually have to give in and support loop (line) timing.

Now connecting to a OC192c transponder port on a DWDM system is a little 
different. An OC192c transponder port is not the same as an  OC192c port on 
an ADM. It is not section/line terminating. It does not provide any pointer 
processing. It is really a simple 3R (OEO) regenerator. In this case the 
free running 20ppm clock is not the issue, as all DWDM systems are designed 
to lock onto and track to a sonet minimum clock, which is also 20ppm (note 
that this would have been a big issue with the original 802.3 plan to use a 
100ppm clock for the 10GBASE-W). The potential issue this time is related 
to jitter. The transponder interface is a simple OEO converter, and as such 
the jitter on the output (which is ultimately fed into the long haul dwdm 
network) is directly related to the jitter on the input (i.e. unlike an ADM 
the transponder interface on a dwdm system does not 'reset' the jitter 
budget). All OC192c transponder interfaces that I am aware of are designed 
under the assumption that the OC192 client signal (be it from an ADM or a 
POS interface on a router) complies with standard sonet jitter 
specifications (as defined in GR253 and whatever the equivalent ITU 
document is).  However the 10GBASE-W interface is based on ethernet jitter 
specifications and this might ultimately limit the performance of the DWDM 
System (note that the 10G ethernet specs allow up to 3X the jitter of an 
OC192 interface).

I am not saying that  it is impossible to  directly connect a 10GBASE-W 
interface to an existing OC192 DWDM system, but it is certainly not a 'no 
brainer' and would require some analysis to understand the impact of the 
ethernet jitter specs on the overall dwdm network design (i.e the 
additional jitter from the ethernet interface may be what ultimately limits 
the transmission distance).

The other approach would be to design a new 10GBASE-W transponder interface 
that 'cleans up' the jitter on the input and presents the line side of the 
dwdm system with similar specs to those from a standard OC-192 signal. 
However this obviously requires a new plug in card specific  to the 10GBASE-W.





At 01:27 PM 1/16/2002, C. M. Heard wrote:

>Colleagues,
>
>FYI: the following contribution to T1X1.5 (written by Tom
>Alexander, David Martin, and Steve Gorshe) may be of interest,
>as it presents a detailed argument that ELTE can be
>realized within existing NEs -- e.g. as a 10GBASE-W line
>card -- and does not require a separate external piece of
>equipment.  That was exactly the message of the last slide
>in the WIS MIB design team's IETF52 presentation (see
>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>illustrating a 10GBASE-W interface on a SONET ADM.
>
>Regards,
>
>Mike Heard
>
>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>Equipment (ELTE) function and its realization within existing SONET
>equipment
>DESC: This contribution clarifies the issues that have been raised with
>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>particular, we demonstrate that such adaptation does not need
>additional NEs; that is, the ELTE function can be realized by existing
>NEs, and does not require new equipment to be added to a SONET/SDH
>network.
>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Fri Jan 18 17:42:29 2002
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 RAA29586
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 17:42:29 -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 RAA08163;
	Fri, 18 Jan 2002 17:40:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA08136
	for <hubmib@ns.ietf.org>; Fri, 18 Jan 2002 17:40:40 -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 RAA29522
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 17:40:36 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA29313;
	Fri, 18 Jan 2002 14:40:38 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Fri, 18 Jan 2002 14:40:38 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>, "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
Message-ID: <Pine.LNX.4.10.10201181404540.13238-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Fri, 18 Jan 2002, Gary Nicholl wrote:
<snip>
[ If you connect a 10GBASE-W interface to a port on a SONET ADM] then,
> although the traffic will still pass error free (as described above
> and in the contribution),  you will get continuous pointer adjustments
> (PJCs) at a rate equal to the difference in frequency between the
> 10GBASE-W interface clock and the sonet network clock (likely to be
> Stratum 1). These PJCs will be detected and reported at every node in
> the network that the OC192c signal passes through. While the PJCs in
> themselves are not a major issue (i.e. do not cause any bit errors),
> they do represent an operational challenge for the network operator.
> In a synchronous sonet network the operator would not expect to see
> continuous PJCs reported from any node.  Continuous PJCs in such a
> network are usually an indication of a synchronization failure and
> that one of the nodes has lost traceability to the Startum 1 network
> clock. As such monitoring PJCs is one of the few tools available to the
> operator to detect and isolate synchronization failures in the network.

That is a very good point.

> A network operator would find it difficult (if not impossible) to
> distinguish between PJCs resulting from a true synchronization failure
> and those from a free-running 10GBASE-W interface connected to the
> network.  For these reasons I find it hard to believe that any operator
> would allow a free running 20ppm 10GBASE-W interface to be connected to
> the network. I think if 10GBASE-W is ever to be widely adopted then
> 802.3 will eventually have to give in and support loop (line) timing.

Is the situation really all that bleak?  The PJC-related performance
parameters defined in ANSI T1.231 include counts of pointer justifications
detected, pointer justifications generated, and the difference between
them.  I would think that the important statistic is the difference between
PJCs detected and PJCs generated, because that will be large at only at the
point where the timing sources at the input and output do not match ... in
other words at the points where a synchronization failure exists.  By
contrast, PJCs detected and PJCs generated will be tend to be large, but
differences will be small, at points downstream from the failure.  Now, in
the case of a 10GBASE-W interfaces connected to SONET ADMs, the PJC
difference would normally large only at ingress nodes where the 10GBASE-W
tributary interfaces exist.  It seems to me that it would not be all that
difficult to suppress PJC-difference alerts for those specific tributary
interfaces.  Wouldn't that adequately address the operational concerns?

Regards,

Mike Heard




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Fri Jan 18 17:42:30 2002
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 RAA29597
	for <hubmib-archive@odin.ietf.org>; Fri, 18 Jan 2002 17:42:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA08254
	for hubmib-archive@odin.ietf.org; Fri, 18 Jan 2002 17:42: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 RAA08163;
	Fri, 18 Jan 2002 17:40:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA08136
	for <hubmib@ns.ietf.org>; Fri, 18 Jan 2002 17:40:40 -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 RAA29522
	for <hubmib@ietf.org>; Fri, 18 Jan 2002 17:40:36 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA29313;
	Fri, 18 Jan 2002 14:40:38 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Fri, 18 Jan 2002 14:40:38 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>, "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
Message-ID: <Pine.LNX.4.10.10201181404540.13238-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Fri, 18 Jan 2002, Gary Nicholl wrote:
<snip>
[ If you connect a 10GBASE-W interface to a port on a SONET ADM] then,
> although the traffic will still pass error free (as described above
> and in the contribution),  you will get continuous pointer adjustments
> (PJCs) at a rate equal to the difference in frequency between the
> 10GBASE-W interface clock and the sonet network clock (likely to be
> Stratum 1). These PJCs will be detected and reported at every node in
> the network that the OC192c signal passes through. While the PJCs in
> themselves are not a major issue (i.e. do not cause any bit errors),
> they do represent an operational challenge for the network operator.
> In a synchronous sonet network the operator would not expect to see
> continuous PJCs reported from any node.  Continuous PJCs in such a
> network are usually an indication of a synchronization failure and
> that one of the nodes has lost traceability to the Startum 1 network
> clock. As such monitoring PJCs is one of the few tools available to the
> operator to detect and isolate synchronization failures in the network.

That is a very good point.

> A network operator would find it difficult (if not impossible) to
> distinguish between PJCs resulting from a true synchronization failure
> and those from a free-running 10GBASE-W interface connected to the
> network.  For these reasons I find it hard to believe that any operator
> would allow a free running 20ppm 10GBASE-W interface to be connected to
> the network. I think if 10GBASE-W is ever to be widely adopted then
> 802.3 will eventually have to give in and support loop (line) timing.

Is the situation really all that bleak?  The PJC-related performance
parameters defined in ANSI T1.231 include counts of pointer justifications
detected, pointer justifications generated, and the difference between
them.  I would think that the important statistic is the difference between
PJCs detected and PJCs generated, because that will be large at only at the
point where the timing sources at the input and output do not match ... in
other words at the points where a synchronization failure exists.  By
contrast, PJCs detected and PJCs generated will be tend to be large, but
differences will be small, at points downstream from the failure.  Now, in
the case of a 10GBASE-W interfaces connected to SONET ADMs, the PJC
difference would normally large only at ingress nodes where the 10GBASE-W
tributary interfaces exist.  It seems to me that it would not be all that
difficult to suppress PJC-difference alerts for those specific tributary
interfaces.  Wouldn't that adequately address the operational concerns?

Regards,

Mike Heard




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Jan 22 15:09:28 2002
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 PAA08588
	for <hubmib-archive@odin.ietf.org>; Tue, 22 Jan 2002 15:09:28 -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 PAA09213;
	Tue, 22 Jan 2002 15:01:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA25922
	for <hubmib@optimus.ietf.org>; Sat, 19 Jan 2002 22:42:28 -0500 (EST)
Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27518
	for <hubmib@ietf.org>; Sat, 19 Jan 2002 22:42:23 -0500 (EST)
Received: from sdn-ar-002nctarbp171.dialsprint.net ([206.133.80.211] helo=RABHPNOTEBK.mindspring.com)
	by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16S8sB-0003wD-00; Sat, 19 Jan 2002 22:42:23 -0500
Message-Id: <5.1.0.14.2.20020119213408.02437528@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 19 Jan 2002 21:42:19 -0600
To: Gary Nicholl <gnicholl@cisco.com>, "C. M. Heard" <heard@pobox.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
References: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Gary,

I hate to burst your balloon.  "PJCs" do cause data errors.  The PJC is in 
response to the buildup of data block alignment offset.  That means that 
somewhere between PJCs, the data starts to get "bit" errors.  The more of 
them that there, the more that the data will be unreliable.  This was seen 
in the early POS interfaces (OC3/STM1) interfaces that I deployed before 
the vendor has "loop" timing working properly.

Repeatedly,  the 802.3ae Task Force has stated that the 10G Ethernet WAN 
PHY was not intended to be a "client" signal on an ADM.  Trying to "shoe 
horn" it into an ADM is in violation of the purposes and intentions that 
the Task Force had for the WAN PHY.  The only recognized and supported use 
of the 10G WAN PHY was to be a "peer" on an optical network though the 
"ELTE".  The "ELTE" is reflected in part by the T1X1.5 contribution of the 
non-isosynchronous "path relay".

Thank you,
Roy Bynum



At 04:23 PM 1/18/2002 -0500, Gary Nicholl wrote:

>Here are some of my thoughts on the T1X1 contribution.
>
>Gary Nicholl
>
>I would argue that the synchronization requirements and associated ELTE 
>functionality are different depending on whether the 10GBASE-W is 
>connected to an OC192c tributary port on a SONET ADM or to an OC192c 
>transponder port on a DWDM system.
>
>The T1X1 contribution focuses on the first of these, i.e. connecting to an 
>OC192c port on an ADM. Such a port is actually section/line terminating 
>and includes a full pointer processor. In this case I agree with the 
>argument in the contribution that the necessary 'ELTE path relay function' 
>essentially comes for free. It should therefore be possible to directly 
>connect a 10GBASE-W interface to an  OC-192c port on a sonet ADM, and it 
>should pass traffic error free.
>
>But even here there is one wrinkle that is not addressed in the 
>contribution. The 10GBASE-W uses a 20ppm clock source (not in itself an 
>issue as this complies with the sonet minimum system clock specification, 
>and is what has been used successfully on POS interfaces in the past) . 
>However, unlike POS, the 10GBASE-W specification does not allow loop (i.e. 
>line) timing. So the only option is to configure the interface for 
>'internal' timing using the free-running 20ppm clock source. If you 
>connect such an interface to an OC-192c port on a sonet ADM then, although 
>the traffic will still pass error free (as described above and in the 
>contribution),  you will get continuous pointer adjustments (PJCs) at a 
>rate equal to the difference in frequency between the 10GBASE-W interface 
>clock and the sonet network clock (likely to be Stratum 1). These PJCs 
>will be detected and reported at every node in the network that the OC192c 
>signal passes through. While the PJCs in themselves are not a major issue 
>(i.e. do not cause any bit errors), they do represent an operational 
>challenge for the network operator. In a synchronous sonet network the 
>operator would not expect to see continuous PJCs reported from any node. 
>Continuous PJCs in such a network are usually an indication of a 
>synchronization failure and that one of the nodes has lost traceability to 
>the Startum 1 network clock. As such monitoring PJCs is one of the few 
>tools available to the operator to detect and isolate synchronization 
>failures in the network.  A network operator would find it difficult (if 
>not impossible) to distinguish between PJCs resulting from a true 
>synchronization failure and those from a free-running 10GBASE-W interface 
>connected to the network. For these reasons I find it hard to believe that 
>any operator would allow a free running 20ppm 10GBASE-W interface to be 
>connected to the network. I think if 10GBASE-W is ever to be widely 
>adopted then 802.3 will eventually have to give in and support loop (line) 
>timing.
>
>Now connecting to a OC192c transponder port on a DWDM system is a little 
>different. An OC192c transponder port is not the same as an  OC192c port 
>on an ADM. It is not section/line terminating. It does not provide any 
>pointer processing. It is really a simple 3R (OEO) regenerator. In this 
>case the free running 20ppm clock is not the issue, as all DWDM systems 
>are designed to lock onto and track to a sonet minimum clock, which is 
>also 20ppm (note that this would have been a big issue with the original 
>802.3 plan to use a 100ppm clock for the 10GBASE-W). The potential issue 
>this time is related to jitter. The transponder interface is a simple OEO 
>converter, and as such the jitter on the output (which is ultimately fed 
>into the long haul dwdm network) is directly related to the jitter on the 
>input (i.e. unlike an ADM the transponder interface on a dwdm system does 
>not 'reset' the jitter budget). All OC192c transponder interfaces that I 
>am aware of are designed under the assumption that the OC192 client signal 
>(be it from an ADM or a POS interface on a router) complies with standard 
>sonet jitter specifications (as defined in GR253 and whatever the 
>equivalent ITU document is).  However the 10GBASE-W interface is based on 
>ethernet jitter specifications and this might ultimately limit the 
>performance of the DWDM System (note that the 10G ethernet specs allow up 
>to 3X the jitter of an OC192 interface).
>
>I am not saying that  it is impossible to  directly connect a 10GBASE-W 
>interface to an existing OC192 DWDM system, but it is certainly not a 'no 
>brainer' and would require some analysis to understand the impact of the 
>ethernet jitter specs on the overall dwdm network design (i.e the 
>additional jitter from the ethernet interface may be what ultimately 
>limits the transmission distance).
>
>The other approach would be to design a new 10GBASE-W transponder 
>interface that 'cleans up' the jitter on the input and presents the line 
>side of the dwdm system with similar specs to those from a standard OC-192 
>signal. However this obviously requires a new plug in card specific  to 
>the 10GBASE-W.
>
>
>
>
>
>At 01:27 PM 1/16/2002, C. M. Heard wrote:
>
>>Colleagues,
>>
>>FYI: the following contribution to T1X1.5 (written by Tom
>>Alexander, David Martin, and Steve Gorshe) may be of interest,
>>as it presents a detailed argument that ELTE can be
>>realized within existing NEs -- e.g. as a 10GBASE-W line
>>card -- and does not require a separate external piece of
>>equipment.  That was exactly the message of the last slide
>>in the WIS MIB design team's IETF52 presentation (see
>>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>>illustrating a 10GBASE-W interface on a SONET ADM.
>>
>>Regards,
>>
>>Mike Heard
>>
>>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>>Equipment (ELTE) function and its realization within existing SONET
>>equipment
>>DESC: This contribution clarifies the issues that have been raised with
>>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>>particular, we demonstrate that such adaptation does not need
>>additional NEs; that is, the ELTE function can be realized by existing
>>NEs, and does not require new equipment to be added to a SONET/SDH
>>network.
>>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Tue Jan 22 15:09:29 2002
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 PAA08602
	for <hubmib-archive@odin.ietf.org>; Tue, 22 Jan 2002 15:09:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA09490
	for hubmib-archive@odin.ietf.org; Tue, 22 Jan 2002 15:09: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 PAA09213;
	Tue, 22 Jan 2002 15:01:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA25922
	for <hubmib@optimus.ietf.org>; Sat, 19 Jan 2002 22:42:28 -0500 (EST)
Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27518
	for <hubmib@ietf.org>; Sat, 19 Jan 2002 22:42:23 -0500 (EST)
Received: from sdn-ar-002nctarbp171.dialsprint.net ([206.133.80.211] helo=RABHPNOTEBK.mindspring.com)
	by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16S8sB-0003wD-00; Sat, 19 Jan 2002 22:42:23 -0500
Message-Id: <5.1.0.14.2.20020119213408.02437528@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 19 Jan 2002 21:42:19 -0600
To: Gary Nicholl <gnicholl@cisco.com>, "C. M. Heard" <heard@pobox.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <4.3.2.7.2.20020118151929.06c89840@toque.cisco.com>
References: <Pine.LNX.4.10.10201161018560.28679-100000@shell4.bayarea.n et>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: [802.3ae] Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Gary,

I hate to burst your balloon.  "PJCs" do cause data errors.  The PJC is in 
response to the buildup of data block alignment offset.  That means that 
somewhere between PJCs, the data starts to get "bit" errors.  The more of 
them that there, the more that the data will be unreliable.  This was seen 
in the early POS interfaces (OC3/STM1) interfaces that I deployed before 
the vendor has "loop" timing working properly.

Repeatedly,  the 802.3ae Task Force has stated that the 10G Ethernet WAN 
PHY was not intended to be a "client" signal on an ADM.  Trying to "shoe 
horn" it into an ADM is in violation of the purposes and intentions that 
the Task Force had for the WAN PHY.  The only recognized and supported use 
of the 10G WAN PHY was to be a "peer" on an optical network though the 
"ELTE".  The "ELTE" is reflected in part by the T1X1.5 contribution of the 
non-isosynchronous "path relay".

Thank you,
Roy Bynum



At 04:23 PM 1/18/2002 -0500, Gary Nicholl wrote:

>Here are some of my thoughts on the T1X1 contribution.
>
>Gary Nicholl
>
>I would argue that the synchronization requirements and associated ELTE 
>functionality are different depending on whether the 10GBASE-W is 
>connected to an OC192c tributary port on a SONET ADM or to an OC192c 
>transponder port on a DWDM system.
>
>The T1X1 contribution focuses on the first of these, i.e. connecting to an 
>OC192c port on an ADM. Such a port is actually section/line terminating 
>and includes a full pointer processor. In this case I agree with the 
>argument in the contribution that the necessary 'ELTE path relay function' 
>essentially comes for free. It should therefore be possible to directly 
>connect a 10GBASE-W interface to an  OC-192c port on a sonet ADM, and it 
>should pass traffic error free.
>
>But even here there is one wrinkle that is not addressed in the 
>contribution. The 10GBASE-W uses a 20ppm clock source (not in itself an 
>issue as this complies with the sonet minimum system clock specification, 
>and is what has been used successfully on POS interfaces in the past) . 
>However, unlike POS, the 10GBASE-W specification does not allow loop (i.e. 
>line) timing. So the only option is to configure the interface for 
>'internal' timing using the free-running 20ppm clock source. If you 
>connect such an interface to an OC-192c port on a sonet ADM then, although 
>the traffic will still pass error free (as described above and in the 
>contribution),  you will get continuous pointer adjustments (PJCs) at a 
>rate equal to the difference in frequency between the 10GBASE-W interface 
>clock and the sonet network clock (likely to be Stratum 1). These PJCs 
>will be detected and reported at every node in the network that the OC192c 
>signal passes through. While the PJCs in themselves are not a major issue 
>(i.e. do not cause any bit errors), they do represent an operational 
>challenge for the network operator. In a synchronous sonet network the 
>operator would not expect to see continuous PJCs reported from any node. 
>Continuous PJCs in such a network are usually an indication of a 
>synchronization failure and that one of the nodes has lost traceability to 
>the Startum 1 network clock. As such monitoring PJCs is one of the few 
>tools available to the operator to detect and isolate synchronization 
>failures in the network.  A network operator would find it difficult (if 
>not impossible) to distinguish between PJCs resulting from a true 
>synchronization failure and those from a free-running 10GBASE-W interface 
>connected to the network. For these reasons I find it hard to believe that 
>any operator would allow a free running 20ppm 10GBASE-W interface to be 
>connected to the network. I think if 10GBASE-W is ever to be widely 
>adopted then 802.3 will eventually have to give in and support loop (line) 
>timing.
>
>Now connecting to a OC192c transponder port on a DWDM system is a little 
>different. An OC192c transponder port is not the same as an  OC192c port 
>on an ADM. It is not section/line terminating. It does not provide any 
>pointer processing. It is really a simple 3R (OEO) regenerator. In this 
>case the free running 20ppm clock is not the issue, as all DWDM systems 
>are designed to lock onto and track to a sonet minimum clock, which is 
>also 20ppm (note that this would have been a big issue with the original 
>802.3 plan to use a 100ppm clock for the 10GBASE-W). The potential issue 
>this time is related to jitter. The transponder interface is a simple OEO 
>converter, and as such the jitter on the output (which is ultimately fed 
>into the long haul dwdm network) is directly related to the jitter on the 
>input (i.e. unlike an ADM the transponder interface on a dwdm system does 
>not 'reset' the jitter budget). All OC192c transponder interfaces that I 
>am aware of are designed under the assumption that the OC192 client signal 
>(be it from an ADM or a POS interface on a router) complies with standard 
>sonet jitter specifications (as defined in GR253 and whatever the 
>equivalent ITU document is).  However the 10GBASE-W interface is based on 
>ethernet jitter specifications and this might ultimately limit the 
>performance of the DWDM System (note that the 10G ethernet specs allow up 
>to 3X the jitter of an OC192 interface).
>
>I am not saying that  it is impossible to  directly connect a 10GBASE-W 
>interface to an existing OC192 DWDM system, but it is certainly not a 'no 
>brainer' and would require some analysis to understand the impact of the 
>ethernet jitter specs on the overall dwdm network design (i.e the 
>additional jitter from the ethernet interface may be what ultimately 
>limits the transmission distance).
>
>The other approach would be to design a new 10GBASE-W transponder 
>interface that 'cleans up' the jitter on the input and presents the line 
>side of the dwdm system with similar specs to those from a standard OC-192 
>signal. However this obviously requires a new plug in card specific  to 
>the 10GBASE-W.
>
>
>
>
>
>At 01:27 PM 1/16/2002, C. M. Heard wrote:
>
>>Colleagues,
>>
>>FYI: the following contribution to T1X1.5 (written by Tom
>>Alexander, David Martin, and Steve Gorshe) may be of interest,
>>as it presents a detailed argument that ELTE can be
>>realized within existing NEs -- e.g. as a 10GBASE-W line
>>card -- and does not require a separate external piece of
>>equipment.  That was exactly the message of the last slide
>>in the WIS MIB design team's IETF52 presentation (see
>>http://norseth.org/ietf/hubmib/ietf52wisMibPresentation.PDF)
>>illustrating a 10GBASE-W interface on a SONET ADM.
>>
>>Regards,
>>
>>Mike Heard
>>
>>CONTRIBUTION#: T1X1.5/2002-027 (2X150270)
>>LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=2X150270&NW=Y
>>TITLE: Clarification of the 10GBASE-W Ethernet Line Terminating
>>Equipment (ELTE) function and its realization within existing SONET
>>equipment
>>DESC: This contribution clarifies the issues that have been raised with
>>regards to the proposed ELTE function, needed to adapt a 10GBASE-W
>>Ethernet WAN-PHY signal to a SONET/SDH STS-192c/VC-4-64c signal. In
>>particular, we demonstrate that such adaptation does not need
>>additional NEs; that is, the ELTE function can be realized by existing
>>NEs, and does not require new equipment to be added to a SONET/SDH
>>network.
>>CONTACT(S): Steve Gorshe (Steve_Gorshe@pmc-sierra.com (503) 431-7440)
>>SOURCE: Nortel Networks, PMC-Sierra



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Jan 22 15:15:22 2002
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 PAA08751
	for <hubmib-archive@odin.ietf.org>; Tue, 22 Jan 2002 15:15: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 PAA09230;
	Tue, 22 Jan 2002 15:01:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA25762
	for <hubmib@optimus.ietf.org>; Sat, 19 Jan 2002 22:32:35 -0500 (EST)
Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27467
	for <hubmib@ietf.org>; Sat, 19 Jan 2002 22:32:30 -0500 (EST)
Received: from sdn-ar-002nctarbp171.dialsprint.net ([206.133.80.211] helo=RABHPNOTEBK.mindspring.com)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16S8iY-0001yD-00; Sat, 19 Jan 2002 22:32:27 -0500
Message-Id: <5.1.0.14.2.20020119212316.0243ce90@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 19 Jan 2002 21:32:23 -0600
To: "C. M. Heard" <heard@pobox.com>, Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201171849420.19030-100000@shell4.bayarea.n
 et>
References: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

Please read the specifications for the use of +/- 20 PPM clock for a 
"client" signal.  It is for maintenance (read "temporary") use only.  A 
non-bit stuffed client at +/-20 PPM still has too many clock offsets and 
pointer adjustments to be stable from and "Ethernet" viewpoint.  The +/- 20 
PPM T1/T3 signals that become payload DS1/DS3 clients are "bit stuffed" 
rate adjusted to allow them to be inserted into a PRS synchronous client 
signal on a SONET/SDH ADM.  10G Ethernet WAN PHY does not do that.

Any equipment vendor or service provider that attempts to use the WAN PHY 
as a "client" signal will have dissatisfied customers.  It will give a bad 
perception of  the reliability of Ethernet over optical transmission 
services.  Changing the clock tolerance to +/- 20 PPM only created the 
perception of interoperability, not the reality.  That was the reason that 
I apposed it.

Thank you,
Roy Bynum

At 11:21 PM 1/17/2002 -0800, C. M. Heard wrote:
>On Thu, 17 Jan 2002, Roy Bynum wrote:
> > There is a single point of failure that prevents a WIS as defined
> > by IEEE from ever being an interface on SONET ADM.  The client
> > interface on a SONET ADM requires clock synchronization either
> > through "loop timing" or "PRS".  Neither of these are available in
> > the WIS.  This lack of synchronization to a transmission network
> > prevents the ADM from being able to multiplex the WIS signal into
> > a SONET signal.
>
>That conclusion is false.  It is is possible to multiplex the WIS
>SPE into a higher-order SONET signal because the WIS transmit clock
>is required to meet the SONET minimum clock frequency accurracy of
>+/- 20 ppm.  That is good enough to ensure that pointer justifications
>can absorb the timing differences between the WIS clock and the
>stratum clock used by a SONET ADM.  It is not necessary that the WIS
>be loop timed or synchronized to a stratum clock in order to do that.
>All this is spelled out in Section 2.4 of the T1X1.5 contribution.
>
> > As defined, the WIS can never be a client of a SONET or SDH system.
> > It can be a "peer" on an optical network only.  The T1X1.5 proposal
> > provides for a "peering" between a WIS and a SONET managed optical
> > network.  It does not provide for the WIS to be an interface on a
> > SONET system.
>
>I don't think that the authors of T1X1.5/2002-027 would necessarily
>agree, since that contribution explicitly states that "[ ... ] the
>ELTE function is intended to be realized within a SONET/SDH NE
>(potentially on a line card)."
>
>Regards,
>
>Mike Heard



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Tue Jan 22 15:15:22 2002
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 PAA08761
	for <hubmib-archive@odin.ietf.org>; Tue, 22 Jan 2002 15:15:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10549
	for hubmib-archive@odin.ietf.org; Tue, 22 Jan 2002 15:15:25 -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 PAA09230;
	Tue, 22 Jan 2002 15:01:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA25762
	for <hubmib@optimus.ietf.org>; Sat, 19 Jan 2002 22:32:35 -0500 (EST)
Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27467
	for <hubmib@ietf.org>; Sat, 19 Jan 2002 22:32:30 -0500 (EST)
Received: from sdn-ar-002nctarbp171.dialsprint.net ([206.133.80.211] helo=RABHPNOTEBK.mindspring.com)
	by barry.mail.mindspring.net with esmtp (Exim 3.33 #1)
	id 16S8iY-0001yD-00; Sat, 19 Jan 2002 22:32:27 -0500
Message-Id: <5.1.0.14.2.20020119212316.0243ce90@pop.mindspring.com>
X-Sender: rabynum@mindspring.com@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 19 Jan 2002 21:32:23 -0600
To: "C. M. Heard" <heard@pobox.com>, Hubmib Mailing List <hubmib@ietf.org>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Roy Bynum <rabynum@mindspring.com>
Cc: HSSG Reflector <stds-802-3-hssg@ieee.org>
In-Reply-To: <Pine.LNX.4.10.10201171849420.19030-100000@shell4.bayarea.n
 et>
References: <5.1.0.14.2.20020117104439.00b63a70@pop.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Hubmib] Re: Clarification of the 10GBASE-W ELTE function
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

Please read the specifications for the use of +/- 20 PPM clock for a 
"client" signal.  It is for maintenance (read "temporary") use only.  A 
non-bit stuffed client at +/-20 PPM still has too many clock offsets and 
pointer adjustments to be stable from and "Ethernet" viewpoint.  The +/- 20 
PPM T1/T3 signals that become payload DS1/DS3 clients are "bit stuffed" 
rate adjusted to allow them to be inserted into a PRS synchronous client 
signal on a SONET/SDH ADM.  10G Ethernet WAN PHY does not do that.

Any equipment vendor or service provider that attempts to use the WAN PHY 
as a "client" signal will have dissatisfied customers.  It will give a bad 
perception of  the reliability of Ethernet over optical transmission 
services.  Changing the clock tolerance to +/- 20 PPM only created the 
perception of interoperability, not the reality.  That was the reason that 
I apposed it.

Thank you,
Roy Bynum

At 11:21 PM 1/17/2002 -0800, C. M. Heard wrote:
>On Thu, 17 Jan 2002, Roy Bynum wrote:
> > There is a single point of failure that prevents a WIS as defined
> > by IEEE from ever being an interface on SONET ADM.  The client
> > interface on a SONET ADM requires clock synchronization either
> > through "loop timing" or "PRS".  Neither of these are available in
> > the WIS.  This lack of synchronization to a transmission network
> > prevents the ADM from being able to multiplex the WIS signal into
> > a SONET signal.
>
>That conclusion is false.  It is is possible to multiplex the WIS
>SPE into a higher-order SONET signal because the WIS transmit clock
>is required to meet the SONET minimum clock frequency accurracy of
>+/- 20 ppm.  That is good enough to ensure that pointer justifications
>can absorb the timing differences between the WIS clock and the
>stratum clock used by a SONET ADM.  It is not necessary that the WIS
>be loop timed or synchronized to a stratum clock in order to do that.
>All this is spelled out in Section 2.4 of the T1X1.5 contribution.
>
> > As defined, the WIS can never be a client of a SONET or SDH system.
> > It can be a "peer" on an optical network only.  The T1X1.5 proposal
> > provides for a "peering" between a WIS and a SONET managed optical
> > network.  It does not provide for the WIS to be an interface on a
> > SONET system.
>
>I don't think that the authors of T1X1.5/2002-027 would necessarily
>agree, since that contribution explicitly states that "[ ... ] the
>ELTE function is intended to be realized within a SONET/SDH NE
>(potentially on a line card)."
>
>Regards,
>
>Mike Heard



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Tue Jan 29 23:55:09 2002
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 XAA01572
	for <hubmib-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:55:09 -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 XAA21273;
	Tue, 29 Jan 2002 23:54:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA21245
	for <hubmib@ns.ietf.org>; Tue, 29 Jan 2002 23:54:38 -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 XAA01557
	for <hubmib@ietf.org>; Tue, 29 Jan 2002 23:54:33 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id UAA20053;
	Tue, 29 Jan 2002 20:54:01 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 29 Jan 2002 20:54:00 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: AToMMIB Mailing List <atommib@research.telcordia.com>
cc: Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: <3C4DBBB7.178B7E24@lucent.com>
Message-ID: <Pine.LNX.4.10.10201292007270.11274-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Tue, 22 Jan 2002, Nathan Kohn wrote:
> it may be seem early,  but then again anything before the last minute
> usually is.
> 
> the 53rd is in Minneapolis, MN, Mar 17-22, 2002.
> 
> for mtg details: http://www.ietf.org/meetings/IETF-53.html
> 
> i'll be happy to collect agenda items as they occur to you, 
> i.e. sooner rather than ...
> 
> we will probably have two sessions again, one for just AToMMIB (one hour), 
> and another jointly with hubmib (one hour). 

If we stick by our schedule we expect to have the WIS MIB in WG last call
before the Minneapolis meeting.  My understanding from Dan Romascanu was
that the IEEE was by and large satisfied with our draft (and the proposed
resolutions of the four issues posted earlier).  There may be some changes
to the IEEE managed objects that we will need to fold in to the object
mapping section of the document, depending on how Lucent's comments got
resolved, but it should take long to fold in whatever changes are necessary
once the next 802.3ae draft shows up (this will be before the Feb 13-14
802.3ae interim meeting). I don't anticipate anything controversial coming
out of this.

My sense is that we will probably not need a joint hubmib/atommib session
to discuss issues with the WIS MIB (although that could change if
controversy arises in WG last call).  However ...

... the WIS MIB does need for the updated SONET-MIB (2558bis) to
be published concurrently.  We have received three implementation
reports on the list, but only one (Marconi's) claims support for
sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
of those conformance groups in order to advance to draft.

If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
forthcoming by the time the WIS MIB has passed WG last call then my
inclination would be to request that the SONET-MIB be recycled at
proposed with the changes now in the 2558bis draft, with advancement
to be requested when the reports are in hand.

So, I'd like to propose a tentative agenda item (probably just for the
main AToMMIB meeting) to discuss the implementation reports for the
SONET-MIB and what to do about publication.  Hopefully Faye will have
received more reports by then.

Note that if we are able to advance 2558bis we will need to advance
RFC 2493 at the same time.  It does not need any technical changes
but might need to get the boilerplate properly updated as it does not
reference the latest RFCs.

Regards,

Mike


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Tue Jan 29 23:55:10 2002
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 XAA01582
	for <hubmib-archive@odin.ietf.org>; Tue, 29 Jan 2002 23:55:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA21347
	for hubmib-archive@odin.ietf.org; Tue, 29 Jan 2002 23:55:14 -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 XAA21273;
	Tue, 29 Jan 2002 23:54:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA21245
	for <hubmib@ns.ietf.org>; Tue, 29 Jan 2002 23:54:38 -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 XAA01557
	for <hubmib@ietf.org>; Tue, 29 Jan 2002 23:54:33 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id UAA20053;
	Tue, 29 Jan 2002 20:54:01 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 29 Jan 2002 20:54:00 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: AToMMIB Mailing List <atommib@research.telcordia.com>
cc: Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: <3C4DBBB7.178B7E24@lucent.com>
Message-ID: <Pine.LNX.4.10.10201292007270.11274-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Tue, 22 Jan 2002, Nathan Kohn wrote:
> it may be seem early,  but then again anything before the last minute
> usually is.
> 
> the 53rd is in Minneapolis, MN, Mar 17-22, 2002.
> 
> for mtg details: http://www.ietf.org/meetings/IETF-53.html
> 
> i'll be happy to collect agenda items as they occur to you, 
> i.e. sooner rather than ...
> 
> we will probably have two sessions again, one for just AToMMIB (one hour), 
> and another jointly with hubmib (one hour). 

If we stick by our schedule we expect to have the WIS MIB in WG last call
before the Minneapolis meeting.  My understanding from Dan Romascanu was
that the IEEE was by and large satisfied with our draft (and the proposed
resolutions of the four issues posted earlier).  There may be some changes
to the IEEE managed objects that we will need to fold in to the object
mapping section of the document, depending on how Lucent's comments got
resolved, but it should take long to fold in whatever changes are necessary
once the next 802.3ae draft shows up (this will be before the Feb 13-14
802.3ae interim meeting). I don't anticipate anything controversial coming
out of this.

My sense is that we will probably not need a joint hubmib/atommib session
to discuss issues with the WIS MIB (although that could change if
controversy arises in WG last call).  However ...

... the WIS MIB does need for the updated SONET-MIB (2558bis) to
be published concurrently.  We have received three implementation
reports on the list, but only one (Marconi's) claims support for
sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
of those conformance groups in order to advance to draft.

If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
forthcoming by the time the WIS MIB has passed WG last call then my
inclination would be to request that the SONET-MIB be recycled at
proposed with the changes now in the 2558bis draft, with advancement
to be requested when the reports are in hand.

So, I'd like to propose a tentative agenda item (probably just for the
main AToMMIB meeting) to discuss the implementation reports for the
SONET-MIB and what to do about publication.  Hopefully Faye will have
received more reports by then.

Note that if we are able to advance 2558bis we will need to advance
RFC 2493 at the same time.  It does not need any technical changes
but might need to get the boilerplate properly updated as it does not
reference the latest RFCs.

Regards,

Mike


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 30 04:53:36 2002
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 EAA13424
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:53: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 EAA14028;
	Wed, 30 Jan 2002 04:52:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13999
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 04:52:53 -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 EAA13413
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:52:51 -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 g0U9pQg22834
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:51:26 -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 g0U9pPj22830
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:51:26 -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"
Date: Wed, 30 Jan 2002 11:51:54 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54189@IS0004AVEXU1.global.avaya.com>
Thread-Topic: 53rd AToMIB agenda items 
Thread-Index: AcGpShwwSTayJkPZQFKl2yJF3czcRgAKVsSg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>,
        "AToMMIB Mailing List" <atommib@research.telcordia.com>
Cc: "Hubmib Mailing List" <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA14000
Subject: [Hubmib] RE: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

> 
> My sense is that we will probably not need a joint 
> hubmib/atommib session
> to discuss issues with the WIS MIB (although that could change if
> controversy arises in WG last call).  
> 

I would actually suggest that we ask for a meeting slot, and if it
proves that we do not need it, cancel the meeting prior tot he
Minneapolis meeting. This is much easier than realizing that we need a
meeting after the deadline expired.

Regards,

Dan

> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 30 04:53:37 2002
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 EAA13433
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:53:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA14075
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 04:53:38 -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 EAA14028;
	Wed, 30 Jan 2002 04:52:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA13999
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 04:52:53 -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 EAA13413
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:52:51 -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 g0U9pQg22834
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:51:26 -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 g0U9pPj22830
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:51:26 -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"
Date: Wed, 30 Jan 2002 11:51:54 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF54189@IS0004AVEXU1.global.avaya.com>
Thread-Topic: 53rd AToMIB agenda items 
Thread-Index: AcGpShwwSTayJkPZQFKl2yJF3czcRgAKVsSg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>,
        "AToMMIB Mailing List" <atommib@research.telcordia.com>
Cc: "Hubmib Mailing List" <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA14000
Subject: [Hubmib] RE: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 8bit

> 
> My sense is that we will probably not need a joint 
> hubmib/atommib session
> to discuss issues with the WIS MIB (although that could change if
> controversy arises in WG last call).  
> 

I would actually suggest that we ask for a meeting slot, and if it
proves that we do not need it, cancel the meeting prior tot he
Minneapolis meeting. This is much easier than realizing that we need a
meeting after the deadline expired.

Regards,

Dan

> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 30 04:59:16 2002
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 EAA13549
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:59:11 -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 EAA14234;
	Wed, 30 Jan 2002 04:58:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA14193
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 04:58: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 EAA13534
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:58:00 -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 g0U9ugg24692
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:56:42 -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 g0U9ufj24688
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:56:42 -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_01C1A974.7C103EDC"
Date: Wed, 30 Jan 2002 11:57:10 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF5418B@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis
Thread-Index: AcGpdJTAo6kDU2rqTRyUFKlzig85zg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1A974.7C103EDC
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I suggest that we require for a meeting slot in Minneapolis. The main
issues on the agenda:

*	Report from the InterWorking Labs tests=20
*	Status of the 10 GBE and Power Ethernet MIB documents

I estimate that we will not need more than a one hour meeting slot.

Questions, Comments?

Regards,

Dan


------_=_NextPart_001_01C1A974.7C103EDC
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I suggest that we require for =
a meeting slot in Minneapolis. The main issues on the agenda:</FONT></P>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Arial">Report from the =
InterWorking Labs tests </FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Arial">Status of the 10 GBE =
and Power Ethernet MIB documents</FONT></LI></DIV>
<BR>
</UL>
<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I estimate that we will not =
need more than a one hour meeting slot.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Questions, =
Comments?</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A974.7C103EDC--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 30 04:59:21 2002
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 EAA13557
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 04:59:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA14328
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 04:59: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 EAA14234;
	Wed, 30 Jan 2002 04:58:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA14193
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 04:58: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 EAA13534
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:58:00 -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 g0U9ugg24692
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:56:42 -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 g0U9ufj24688
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 04:56:42 -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_01C1A974.7C103EDC"
Date: Wed, 30 Jan 2002 11:57:10 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2FF5418B@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis
Thread-Index: AcGpdJTAo6kDU2rqTRyUFKlzig85zg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <hubmib@ietf.org>
Subject: [Hubmib] Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1A974.7C103EDC
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I suggest that we require for a meeting slot in Minneapolis. The main
issues on the agenda:

*	Report from the InterWorking Labs tests=20
*	Status of the 10 GBE and Power Ethernet MIB documents

I estimate that we will not need more than a one hour meeting slot.

Questions, Comments?

Regards,

Dan


------_=_NextPart_001_01C1A974.7C103EDC
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4720.25">
<TITLE>Ethernet Interfaces and Hub MIB WG Meeting in Minneapolis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I suggest that we require for =
a meeting slot in Minneapolis. The main issues on the agenda:</FONT></P>

<UL DIR=3DLTR>
<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Arial">Report from the =
InterWorking Labs tests </FONT></LI></DIV>

<DIV DIR=3DLTR><LI><FONT SIZE=3D2 FACE=3D"Arial">Status of the 10 GBE =
and Power Ethernet MIB documents</FONT></LI></DIV>
<BR>
</UL>
<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">I estimate that we will not =
need more than a one hour meeting slot.</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Questions, =
Comments?</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT></P>

<P DIR=3DLTR><FONT SIZE=3D2 FACE=3D"Arial">Dan</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1A974.7C103EDC--

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 30 13:13:49 2002
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 NAA27845
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 13:13:44 -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 MAA11888;
	Wed, 30 Jan 2002 12:43:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11866
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 12:43:36 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26952
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 12:43:34 -0500 (EST)
Received: from shannon.research.telcordia.com (shannon [128.96.73.2])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g0UHgwID011812;
	Wed, 30 Jan 2002 12:42:58 -0500 (EST)
Received: from kaj-100.research.telcordia.com (nv-ktesink.cc.telcordia.com [128.96.82.9])
	by shannon.research.telcordia.com (8.8.8/8.8.8) with ESMTP id MAA01667;
	Wed, 30 Jan 2002 12:42:57 -0500 (EST)
Message-Id: <4.3.2.7.0.20020130115144.020189a0@shannon.research.telcordia.com>
X-Sender: kaj@shannon.research.telcordia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 30 Jan 2002 12:02:12 -0500
To: "C. M. Heard" <heard@pobox.com>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

At 08:54 PM 1/29/2002 -0800, C. M. Heard wrote:


>... the WIS MIB does need for the updated SONET-MIB (2558bis) to
>be published concurrently.  We have received three implementation
>reports on the list, but only one (Marconi's) claims support for
>sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
>of those conformance groups in order to advance to draft.
>
>If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
>forthcoming by the time the WIS MIB has passed WG last call then my
>inclination would be to request that the SONET-MIB be recycled at
>proposed with the changes now in the 2558bis draft, with advancement
>to be requested when the reports are in hand.

the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
is that, as per the conformance clause, you dont implement
it when you dont support VTs. so its optional in the sense of
you only support it when you need it. i see your logic but
i havent seen this logic applied in other cases yet.
it would be both a pity and a problem if you cant advance
the spec because of this; if you dont get the implementation feedback
now you may not get it two years from now either. in that case
the logical conclusion would be to dump the sonetVTStuff2 and
sonetFarEndVTStuff2? lets hope we can get some additional
implementation feedback.

we'll need some AD wisdom here on the process.

kaj




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From hubmib-admin@ietf.org  Wed Jan 30 13:31:44 2002
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 NAA28303
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 13:31:40 -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 NAA14300;
	Wed, 30 Jan 2002 13:31:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14271
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 13:31:25 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28284
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 13:31:23 -0500 (EST)
Received: from ec02-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g0UIUMa05352;
	Wed, 30 Jan 2002 12:30:22 -0600 (CST)
Received: by ec02-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <DHLX7CZG>; Wed, 30 Jan 2002 12:30:40 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710760@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: AToMMIB Mailing List <atommib@research.telcordia.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] Re: 53rd AToMIB agenda items
Date: Wed, 30 Jan 2002 12:30:39 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: C. M. Heard [mailto:heard@pobox.com] 
> Sent: Tuesday, January 29, 2002 08:54 PM

> resolved, but it should take long to fold in whatever changes 

	I think you meant "it should not take long"...?


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 30 13:31:45 2002
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 NAA28324
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 13:31:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA14348
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 13:31:46 -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 NAA14300;
	Wed, 30 Jan 2002 13:31:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14271
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 13:31:25 -0500 (EST)
Received: from creeper.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28284
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 13:31:23 -0500 (EST)
Received: from ec02-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g0UIUMa05352;
	Wed, 30 Jan 2002 12:30:22 -0600 (CST)
Received: by ec02-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <DHLX7CZG>; Wed, 30 Jan 2002 12:30:40 -0600
Message-ID: <D77353F1D8FCD411AC3400105A640BB5710760@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: AToMMIB Mailing List <atommib@research.telcordia.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] Re: 53rd AToMIB agenda items
Date: Wed, 30 Jan 2002 12:30:39 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> From: C. M. Heard [mailto:heard@pobox.com] 
> Sent: Tuesday, January 29, 2002 08:54 PM

> resolved, but it should take long to fold in whatever changes 

	I think you meant "it should not take long"...?


/|/|ike

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From daemon@optimus.ietf.org  Wed Jan 30 14:05:15 2002
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 NAA27855
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 13:13:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA13385
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 13:13:50 -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 MAA11888;
	Wed, 30 Jan 2002 12:43:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11866
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 12:43:36 -0500 (EST)
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26952
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 12:43:34 -0500 (EST)
Received: from shannon.research.telcordia.com (shannon [128.96.73.2])
	by thumper.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g0UHgwID011812;
	Wed, 30 Jan 2002 12:42:58 -0500 (EST)
Received: from kaj-100.research.telcordia.com (nv-ktesink.cc.telcordia.com [128.96.82.9])
	by shannon.research.telcordia.com (8.8.8/8.8.8) with ESMTP id MAA01667;
	Wed, 30 Jan 2002 12:42:57 -0500 (EST)
Message-Id: <4.3.2.7.0.20020130115144.020189a0@shannon.research.telcordia.com>
X-Sender: kaj@shannon.research.telcordia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 30 Jan 2002 12:02:12 -0500
To: "C. M. Heard" <heard@pobox.com>,
        AToMMIB Mailing List <atommib@research.telcordia.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Cc: Hubmib Mailing List <hubmib@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by AMaViS-perl11-milter
 (http://amavis.org/)
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

At 08:54 PM 1/29/2002 -0800, C. M. Heard wrote:


>... the WIS MIB does need for the updated SONET-MIB (2558bis) to
>be published concurrently.  We have received three implementation
>reports on the list, but only one (Marconi's) claims support for
>sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
>of those conformance groups in order to advance to draft.
>
>If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
>forthcoming by the time the WIS MIB has passed WG last call then my
>inclination would be to request that the SONET-MIB be recycled at
>proposed with the changes now in the 2558bis draft, with advancement
>to be requested when the reports are in hand.

the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
is that, as per the conformance clause, you dont implement
it when you dont support VTs. so its optional in the sense of
you only support it when you need it. i see your logic but
i havent seen this logic applied in other cases yet.
it would be both a pity and a problem if you cant advance
the spec because of this; if you dont get the implementation feedback
now you may not get it two years from now either. in that case
the logical conclusion would be to dump the sonetVTStuff2 and
sonetFarEndVTStuff2? lets hope we can get some additional
implementation feedback.

we'll need some AD wisdom here on the process.

kaj




_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 30 14:09:50 2002
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 OAA29633
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 14:09:49 -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 NAA15707;
	Wed, 30 Jan 2002 13:58:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15679
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 13:58:49 -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 NAA29139
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 13:58:47 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA23712;
	Wed, 30 Jan 2002 10:58:43 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 30 Jan 2002 10:58:42 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: AToMMIB Mailing List <atommib@research.telcordia.com>
cc: Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: <D77353F1D8FCD411AC3400105A640BB5710760@es01-sjc.bmc.com>
Message-ID: <Pine.LNX.4.10.10201301055490.32673-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Wed, 30 Jan 2002, Ayers, Mike wrote:
> 
> > From: C. M. Heard [mailto:heard@pobox.com] 
> > Sent: Tuesday, January 29, 2002 08:54 PM
> 
> > resolved, but it should take long to fold in whatever changes 
> 
> 	I think you meant "it should not take long"...?

Indeed.  My apologies for the error.

//cmh


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 30 14:09:50 2002
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 OAA29642
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 14:09:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA17069
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 14:09:51 -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 NAA15707;
	Wed, 30 Jan 2002 13:58:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15679
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 13:58:49 -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 NAA29139
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 13:58:47 -0500 (EST)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id KAA23712;
	Wed, 30 Jan 2002 10:58:43 -0800
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 30 Jan 2002 10:58:42 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: AToMMIB Mailing List <atommib@research.telcordia.com>
cc: Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: <D77353F1D8FCD411AC3400105A640BB5710760@es01-sjc.bmc.com>
Message-ID: <Pine.LNX.4.10.10201301055490.32673-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Wed, 30 Jan 2002, Ayers, Mike wrote:
> 
> > From: C. M. Heard [mailto:heard@pobox.com] 
> > Sent: Tuesday, January 29, 2002 08:54 PM
> 
> > resolved, but it should take long to fold in whatever changes 
> 
> 	I think you meant "it should not take long"...?

Indeed.  My apologies for the error.

//cmh


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Wed Jan 30 16:04:31 2002
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 QAA02093
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 16:04:31 -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 PAA22605;
	Wed, 30 Jan 2002 15:59:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08419
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 11:56:40 -0500 (EST)
Received: from hotmail.com (f140.law11.hotmail.com [64.4.17.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25092
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 11:56:38 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 30 Jan 2002 08:56:10 -0800
Received: from 216.103.88.23 by lw11fd.law11.hotmail.msn.com with HTTP;
	Wed, 30 Jan 2002 16:56:09 GMT
X-Originating-IP: [216.103.88.23]
From: "Faye Ly" <fayely98@hotmail.com>
To: heard@pobox.com, atommib@research.telcordia.com
Cc: hubmib@ietf.org
Date: Wed, 30 Jan 2002 08:56:09 -0800
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F140v1cO9MH7CSEI5Wz0000f3bf@hotmail.com>
X-OriginalArrivalTime: 30 Jan 2002 16:56:10.0294 (UTC) FILETIME=[047FCD60:01C1A9AF]
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

The reports I received from Cisco and Nortel don't
support SonetVTStuff2, SonetFarEndVTStuff2 and
sonetVTCurrentWidth.  Sorry I missed a lot of the
conversation but would love to hold the implementation
report pending 2558bis updates.

-faye


>From: "C. M. Heard" <heard@pobox.com>
>To: AToMMIB Mailing List <atommib@research.telcordia.com>
>CC: Hubmib Mailing List <hubmib@ietf.org>
>Subject: Re: 53rd AToMIB agenda items
>Date: Tue, 29 Jan 2002 20:54:00 -0800 (PST)
>
>On Tue, 22 Jan 2002, Nathan Kohn wrote:
> > it may be seem early,  but then again anything before the last minute
> > usually is.
> >
> > the 53rd is in Minneapolis, MN, Mar 17-22, 2002.
> >
> > for mtg details: http://www.ietf.org/meetings/IETF-53.html
> >
> > i'll be happy to collect agenda items as they occur to you,
> > i.e. sooner rather than ...
> >
> > we will probably have two sessions again, one for just AToMMIB (one 
>hour),
> > and another jointly with hubmib (one hour).
>
>If we stick by our schedule we expect to have the WIS MIB in WG last call
>before the Minneapolis meeting.  My understanding from Dan Romascanu was
>that the IEEE was by and large satisfied with our draft (and the proposed
>resolutions of the four issues posted earlier).  There may be some changes
>to the IEEE managed objects that we will need to fold in to the object
>mapping section of the document, depending on how Lucent's comments got
>resolved, but it should take long to fold in whatever changes are necessary
>once the next 802.3ae draft shows up (this will be before the Feb 13-14
>802.3ae interim meeting). I don't anticipate anything controversial coming
>out of this.
>
>My sense is that we will probably not need a joint hubmib/atommib session
>to discuss issues with the WIS MIB (although that could change if
>controversy arises in WG last call).  However ...
>
>... the WIS MIB does need for the updated SONET-MIB (2558bis) to
>be published concurrently.  We have received three implementation
>reports on the list, but only one (Marconi's) claims support for
>sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
>of those conformance groups in order to advance to draft.
>
>If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
>forthcoming by the time the WIS MIB has passed WG last call then my
>inclination would be to request that the SONET-MIB be recycled at
>proposed with the changes now in the 2558bis draft, with advancement
>to be requested when the reports are in hand.
>
>So, I'd like to propose a tentative agenda item (probably just for the
>main AToMMIB meeting) to discuss the implementation reports for the
>SONET-MIB and what to do about publication.  Hopefully Faye will have
>received more reports by then.
>
>Note that if we are able to advance 2558bis we will need to advance
>RFC 2493 at the same time.  It does not need any technical changes
>but might need to get the boilerplate properly updated as it does not
>reference the latest RFCs.
>
>Regards,
>
>Mike
>


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@optimus.ietf.org  Wed Jan 30 17:01:57 2002
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 QAA02104
	for <hubmib-archive@odin.ietf.org>; Wed, 30 Jan 2002 16:04:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23213
	for hubmib-archive@odin.ietf.org; Wed, 30 Jan 2002 16:04: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 PAA22605;
	Wed, 30 Jan 2002 15:59:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08419
	for <hubmib@optimus.ietf.org>; Wed, 30 Jan 2002 11:56:40 -0500 (EST)
Received: from hotmail.com (f140.law11.hotmail.com [64.4.17.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25092
	for <hubmib@ietf.org>; Wed, 30 Jan 2002 11:56:38 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 30 Jan 2002 08:56:10 -0800
Received: from 216.103.88.23 by lw11fd.law11.hotmail.msn.com with HTTP;
	Wed, 30 Jan 2002 16:56:09 GMT
X-Originating-IP: [216.103.88.23]
From: "Faye Ly" <fayely98@hotmail.com>
To: heard@pobox.com, atommib@research.telcordia.com
Cc: hubmib@ietf.org
Date: Wed, 30 Jan 2002 08:56:09 -0800
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F140v1cO9MH7CSEI5Wz0000f3bf@hotmail.com>
X-OriginalArrivalTime: 30 Jan 2002 16:56:10.0294 (UTC) FILETIME=[047FCD60:01C1A9AF]
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

Mike,

The reports I received from Cisco and Nortel don't
support SonetVTStuff2, SonetFarEndVTStuff2 and
sonetVTCurrentWidth.  Sorry I missed a lot of the
conversation but would love to hold the implementation
report pending 2558bis updates.

-faye


>From: "C. M. Heard" <heard@pobox.com>
>To: AToMMIB Mailing List <atommib@research.telcordia.com>
>CC: Hubmib Mailing List <hubmib@ietf.org>
>Subject: Re: 53rd AToMIB agenda items
>Date: Tue, 29 Jan 2002 20:54:00 -0800 (PST)
>
>On Tue, 22 Jan 2002, Nathan Kohn wrote:
> > it may be seem early,  but then again anything before the last minute
> > usually is.
> >
> > the 53rd is in Minneapolis, MN, Mar 17-22, 2002.
> >
> > for mtg details: http://www.ietf.org/meetings/IETF-53.html
> >
> > i'll be happy to collect agenda items as they occur to you,
> > i.e. sooner rather than ...
> >
> > we will probably have two sessions again, one for just AToMMIB (one 
>hour),
> > and another jointly with hubmib (one hour).
>
>If we stick by our schedule we expect to have the WIS MIB in WG last call
>before the Minneapolis meeting.  My understanding from Dan Romascanu was
>that the IEEE was by and large satisfied with our draft (and the proposed
>resolutions of the four issues posted earlier).  There may be some changes
>to the IEEE managed objects that we will need to fold in to the object
>mapping section of the document, depending on how Lucent's comments got
>resolved, but it should take long to fold in whatever changes are necessary
>once the next 802.3ae draft shows up (this will be before the Feb 13-14
>802.3ae interim meeting). I don't anticipate anything controversial coming
>out of this.
>
>My sense is that we will probably not need a joint hubmib/atommib session
>to discuss issues with the WIS MIB (although that could change if
>controversy arises in WG last call).  However ...
>
>... the WIS MIB does need for the updated SONET-MIB (2558bis) to
>be published concurrently.  We have received three implementation
>reports on the list, but only one (Marconi's) claims support for
>sonetVTStuff2 and sonetFarEndVTStuff2.  We need a second implementation
>of those conformance groups in order to advance to draft.
>
>If the second report for sonetVTStuff2 and sonetFarEndVTStuff2 is not
>forthcoming by the time the WIS MIB has passed WG last call then my
>inclination would be to request that the SONET-MIB be recycled at
>proposed with the changes now in the 2558bis draft, with advancement
>to be requested when the reports are in hand.
>
>So, I'd like to propose a tentative agenda item (probably just for the
>main AToMMIB meeting) to discuss the implementation reports for the
>SONET-MIB and what to do about publication.  Hopefully Faye will have
>received more reports by then.
>
>Note that if we are able to advance 2558bis we will need to advance
>RFC 2493 at the same time.  It does not need any technical changes
>but might need to get the boilerplate properly updated as it does not
>reference the latest RFCs.
>
>Regards,
>
>Mike
>


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From hubmib-admin@ietf.org  Thu Jan 31 16:32:41 2002
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 QAA13182
	for <hubmib-archive@odin.ietf.org>; Thu, 31 Jan 2002 16:32: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 QAA25312;
	Thu, 31 Jan 2002 16:32:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19997
	for <hubmib@optimus.ietf.org>; Thu, 31 Jan 2002 09:46:25 -0500 (EST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28067
	for <hubmib@ietf.org>; Thu, 31 Jan 2002 09:46:19 -0500 (EST)
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA22298;
	Thu, 31 Jan 2002 06:46:17 -0800 (PST)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id g0VEkFF09857;
	Thu, 31 Jan 2002 15:46:15 +0100 (MET)
Date: Thu, 31 Jan 2002 15:42:36 +0100 (CET)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
To: Kaj Tesink <kaj@research.telcordia.com>, bwijnen@lucent.com
Cc: "C. M. Heard" <heard@pobox.com>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: "Your message with ID" <4.3.2.7.0.20020130115144.020189a0@shannon.research.telcordia.com>
Message-ID: <Roam.SIMC.2.0.6.1012488156.7291.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
> is that, as per the conformance clause, you dont implement
> it when you dont support VTs. so its optional in the sense of
> you only support it when you need it. i see your logic but
> i havent seen this logic applied in other cases yet.
> it would be both a pity and a problem if you cant advance
> the spec because of this; if you dont get the implementation feedback
> now you may not get it two years from now either. in that case
> the logical conclusion would be to dump the sonetVTStuff2 and
> sonetFarEndVTStuff2? lets hope we can get some additional
> implementation feedback.

Perhaps Bert can comment on the MIB specific issues of how to handle
this.

In cases where there are some parts of a proposed standard that do not
have multiple interoperable implementations where the result has been
that those pieces have been lifted out of into a separate specification.

Then the core part can be advanced to draft standard while the other 
specification can be a proposed standard.

Of course, the fact that there isn't two independent interoperable 
implementations might mean that the feature isn't useful and it might
make sense to drop it completely. But there is this middle ground of 
separating out the less implemented parts.

  Erik



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From hubmib-admin@ietf.org  Thu Jan 31 16:54:45 2002
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 QAA13836
	for <hubmib-archive@odin.ietf.org>; Thu, 31 Jan 2002 16:54:45 -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 QAA26153;
	Thu, 31 Jan 2002 16:49:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26122
	for <hubmib@ns.ietf.org>; Thu, 31 Jan 2002 16:49:03 -0500 (EST)
Received: from gnat.inet.org (inet.org [63.108.254.91] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13645
	for <hubmib@ietf.org>; Thu, 31 Jan 2002 16:48:57 -0500 (EST)
Received: from mosquito.inet.org (unknown [10.18.3.102])
	by gnat.inet.org (Postfix) with ESMTP
	id 605EC67117; Thu, 31 Jan 2002 17:04:12 -0500 (EST)
Date: Thu, 31 Jan 2002 16:48:14 -0500
Subject: Re: [Hubmib] Re: 53rd AToMIB agenda items
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v480)
Cc: bwijnen@lucent.com, AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Roam.SIMC.2.0.6.1012488156.7291.nordmark@bebop.france>
Message-Id: <3AA64334-1694-11D6-8640-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


On Thursday, January 31, 2002, at 09:42 , Erik Nordmark wrote:
>> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
>> is that, as per the conformance clause, you dont implement
>> it when you dont support VTs. so its optional in the sense of
>> you only support it when you need it. i see your logic but
>> i havent seen this logic applied in other cases yet.
>> it would be both a pity and a problem if you cant advance
>> the spec because of this; if you dont get the implementation feedback
>> now you may not get it two years from now either. in that case
>> the logical conclusion would be to dump the sonetVTStuff2 and
>> sonetFarEndVTStuff2? lets hope we can get some additional
>> implementation feedback.
>
> Perhaps Bert can comment on the MIB specific issues of how to handle
> this.
>
> In cases where there are some parts of a proposed standard that do not
> have multiple interoperable implementations where the result has been
> that those pieces have been lifted out of into a separate specification.
>
> Then the core part can be advanced to draft standard while the other
> specification can be a proposed standard.

I'm wondering if the pain of splitting the stuff into separate documents
might be avoidable in this case by editing the MIB document to indicate
which OIDs are mandatory-to-implement and which are optional-to-implement.
I thought that was one use of the Conformance Clause, but might be 
confused.

Ran
rja@extremenetworks.com


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib


From daemon@ns.ietf.org  Thu Jan 31 16:54:46 2002
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 QAA13845
	for <hubmib-archive@odin.ietf.org>; Thu, 31 Jan 2002 16:54:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA26856
	for hubmib-archive@odin.ietf.org; Thu, 31 Jan 2002 16:54:51 -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 QAA26153;
	Thu, 31 Jan 2002 16:49:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26122
	for <hubmib@ns.ietf.org>; Thu, 31 Jan 2002 16:49:03 -0500 (EST)
Received: from gnat.inet.org (inet.org [63.108.254.91] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13645
	for <hubmib@ietf.org>; Thu, 31 Jan 2002 16:48:57 -0500 (EST)
Received: from mosquito.inet.org (unknown [10.18.3.102])
	by gnat.inet.org (Postfix) with ESMTP
	id 605EC67117; Thu, 31 Jan 2002 17:04:12 -0500 (EST)
Date: Thu, 31 Jan 2002 16:48:14 -0500
Subject: Re: [Hubmib] Re: 53rd AToMIB agenda items
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v480)
Cc: bwijnen@lucent.com, AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
From: RJ Atkinson <rja@extremenetworks.com>
In-Reply-To: <Roam.SIMC.2.0.6.1012488156.7291.nordmark@bebop.france>
Message-Id: <3AA64334-1694-11D6-8640-00039357A82A@extremenetworks.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org
Content-Transfer-Encoding: 7bit


On Thursday, January 31, 2002, at 09:42 , Erik Nordmark wrote:
>> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
>> is that, as per the conformance clause, you dont implement
>> it when you dont support VTs. so its optional in the sense of
>> you only support it when you need it. i see your logic but
>> i havent seen this logic applied in other cases yet.
>> it would be both a pity and a problem if you cant advance
>> the spec because of this; if you dont get the implementation feedback
>> now you may not get it two years from now either. in that case
>> the logical conclusion would be to dump the sonetVTStuff2 and
>> sonetFarEndVTStuff2? lets hope we can get some additional
>> implementation feedback.
>
> Perhaps Bert can comment on the MIB specific issues of how to handle
> this.
>
> In cases where there are some parts of a proposed standard that do not
> have multiple interoperable implementations where the result has been
> that those pieces have been lifted out of into a separate specification.
>
> Then the core part can be advanced to draft standard while the other
> specification can be a proposed standard.

I'm wondering if the pain of splitting the stuff into separate documents
might be avoidable in this case by editing the MIB document to indicate
which OIDs are mandatory-to-implement and which are optional-to-implement.
I thought that was one use of the Conformance Clause, but might be 
confused.

Ran
rja@extremenetworks.com


_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



From daemon@ns.ietf.org  Thu Jan 31 17:32:04 2002
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 QAA13192
	for <hubmib-archive@odin.ietf.org>; Thu, 31 Jan 2002 16:32:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA25402
	for hubmib-archive@odin.ietf.org; Thu, 31 Jan 2002 16:32:46 -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 QAA25312;
	Thu, 31 Jan 2002 16:32:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19997
	for <hubmib@optimus.ietf.org>; Thu, 31 Jan 2002 09:46:25 -0500 (EST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28067
	for <hubmib@ietf.org>; Thu, 31 Jan 2002 09:46:19 -0500 (EST)
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA22298;
	Thu, 31 Jan 2002 06:46:17 -0800 (PST)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id g0VEkFF09857;
	Thu, 31 Jan 2002 15:46:15 +0100 (MET)
Date: Thu, 31 Jan 2002 15:42:36 +0100 (CET)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
To: Kaj Tesink <kaj@research.telcordia.com>, bwijnen@lucent.com
Cc: "C. M. Heard" <heard@pobox.com>,
        AToMMIB Mailing List <atommib@research.telcordia.com>,
        Hubmib Mailing List <hubmib@ietf.org>
In-Reply-To: "Your message with ID" <4.3.2.7.0.20020130115144.020189a0@shannon.research.telcordia.com>
Message-ID: <Roam.SIMC.2.0.6.1012488156.7291.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Subject: [Hubmib] Re: 53rd AToMIB agenda items
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org


> the problem with the sonetVTStuff2 and sonetFarEndVTStuff2
> is that, as per the conformance clause, you dont implement
> it when you dont support VTs. so its optional in the sense of
> you only support it when you need it. i see your logic but
> i havent seen this logic applied in other cases yet.
> it would be both a pity and a problem if you cant advance
> the spec because of this; if you dont get the implementation feedback
> now you may not get it two years from now either. in that case
> the logical conclusion would be to dump the sonetVTStuff2 and
> sonetFarEndVTStuff2? lets hope we can get some additional
> implementation feedback.

Perhaps Bert can comment on the MIB specific issues of how to handle
this.

In cases where there are some parts of a proposed standard that do not
have multiple interoperable implementations where the result has been
that those pieces have been lifted out of into a separate specification.

Then the core part can be advanced to draft standard while the other 
specification can be a proposed standard.

Of course, the fact that there isn't two independent interoperable 
implementations might mean that the feature isn't useful and it might
make sense to drop it completely. But there is this middle ground of 
separating out the less implemented parts.

  Erik



_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib



