From mailman-owner@ietf.org  Sat Jun  1 05:33: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 FAA12858
	for <hubmib-archive@odin.ietf.org>; Sat, 1 Jun 2002 05:33:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA01074
	for <hubmib-archive@lists.ietf.org>; Sat, 1 Jun 2002 05:33:41 -0400 (EDT)
Date: Sat, 1 Jun 2002 05:33:41 -0400 (EDT)
Message-Id: <200206010933.FAA01074@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      
https://www1.ietf.org/mailman/options/hubmib/hubmib-archive@lists.ietf.org


From hubmib-admin@ietf.org  Thu Jun 13 21:42: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 VAA07394
	for <hubmib-archive@odin.ietf.org>; Thu, 13 Jun 2002 21:42:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA04910;
	Thu, 13 Jun 2002 21:36:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA04885
	for <hubmib@optimus.ietf.org>; Thu, 13 Jun 2002 21:36:12 -0400 (EDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07231
	for <hubmib@ietf.org>; Thu, 13 Jun 2002 21:35:36 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id SAA21726;
	Thu, 13 Jun 2002 18:36:11 -0700
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 13 Jun 2002 18:36:10 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: hubmib@ietf.org
cc: atommib@research.telcordia.com
Message-ID: <Pine.LNX.4.10.10206131826080.18095-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
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 details can be found here:

http://grouper.ieee.org/groups/802/3/10G_study/email/msg05633.html

This clears the way for the hubmib drafts submitted to the IESG in
May to move forward (except for the WIS MIB, which also needs for
the SONET-MIB update to pass WG and IESG approval).

Regards,

Mike



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


From daemon@optimus.ietf.org  Thu Jun 13 21:42:51 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 VAA07403
	for <hubmib-archive@odin.ietf.org>; Thu, 13 Jun 2002 21:42:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA05110
	for hubmib-archive@odin.ietf.org; Thu, 13 Jun 2002 21:43:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA04910;
	Thu, 13 Jun 2002 21:36:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA04885
	for <hubmib@optimus.ietf.org>; Thu, 13 Jun 2002 21:36:12 -0400 (EDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07231
	for <hubmib@ietf.org>; Thu, 13 Jun 2002 21:35:36 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id SAA21726;
	Thu, 13 Jun 2002 18:36:11 -0700
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 13 Jun 2002 18:36:10 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: hubmib@ietf.org
cc: atommib@research.telcordia.com
Message-ID: <Pine.LNX.4.10.10206131826080.18095-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
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 details can be found here:

http://grouper.ieee.org/groups/802/3/10G_study/email/msg05633.html

This clears the way for the hubmib drafts submitted to the IESG in
May to move forward (except for the WIS MIB, which also needs for
the SONET-MIB update to pass WG and IESG approval).

Regards,

Mike



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



From hubmib-admin@ietf.org  Fri Jun 14 03:37: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 DAA22170
	for <hubmib-archive@odin.ietf.org>; Fri, 14 Jun 2002 03:37:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25582;
	Fri, 14 Jun 2002 03:31:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25559
	for <hubmib@optimus.ietf.org>; Fri, 14 Jun 2002 03:31:45 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22102
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:30:57 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g5E7TH804190
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:29:17 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g5E7T7N04087
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:29:07 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
Date: Fri, 14 Jun 2002 10:28:24 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A476@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
Thread-Index: AcITQ9AF6WjIJ0e5SH2RL1inKahjgQAMSyGg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>, <hubmib@ietf.org>
Cc: <atommib@research.telcordia.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA25560
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



> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]
> Sent: Friday, June 14, 2002 4:36 AM
> To: hubmib@ietf.org
> Cc: atommib@research.telcordia.com
> Subject: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE 
> standards board
> 
> 
> The details can be found here:
> 
> http://grouper.ieee.org/groups/802/3/10G_study/email/msg05633.html
> 
> This clears the way for the hubmib drafts submitted to the IESG in
> May to move forward 

As the IEEE standards will be published, the references need to be updated. I trust that the editors will do this in the next spin, after the IESG review.

>(except for the WIS MIB, which also needs for
> the SONET-MIB update to pass WG and IESG approval).

It would be useful if you can provide to the hubmib folks who are not on atommib a short report on status and plans wrt. the SONET MIB.

> 
> Regards,
> 
> Mike
> 
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

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


From daemon@optimus.ietf.org  Fri Jun 14 03:38:02 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 DAA22181
	for <hubmib-archive@odin.ietf.org>; Fri, 14 Jun 2002 03:37:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA25734
	for hubmib-archive@odin.ietf.org; Fri, 14 Jun 2002 03:38:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25582;
	Fri, 14 Jun 2002 03:31:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25559
	for <hubmib@optimus.ietf.org>; Fri, 14 Jun 2002 03:31:45 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22102
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:30:57 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g5E7TH804190
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:29:17 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g5E7T7N04087
	for <hubmib@ietf.org>; Fri, 14 Jun 2002 03:29:07 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
Date: Fri, 14 Jun 2002 10:28:24 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A476@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards board
Thread-Index: AcITQ9AF6WjIJ0e5SH2RL1inKahjgQAMSyGg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>, <hubmib@ietf.org>
Cc: <atommib@research.telcordia.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA25560
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



> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]
> Sent: Friday, June 14, 2002 4:36 AM
> To: hubmib@ietf.org
> Cc: atommib@research.telcordia.com
> Subject: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE 
> standards board
> 
> 
> The details can be found here:
> 
> http://grouper.ieee.org/groups/802/3/10G_study/email/msg05633.html
> 
> This clears the way for the hubmib drafts submitted to the IESG in
> May to move forward 

As the IEEE standards will be published, the references need to be updated. I trust that the editors will do this in the next spin, after the IESG review.

>(except for the WIS MIB, which also needs for
> the SONET-MIB update to pass WG and IESG approval).

It would be useful if you can provide to the hubmib folks who are not on atommib a short report on status and plans wrt. the SONET MIB.

> 
> Regards,
> 
> Mike
> 
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

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



From hubmib-admin@ietf.org  Mon Jun 17 19:27:20 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 TAA23453
	for <hubmib-archive@odin.ietf.org>; Mon, 17 Jun 2002 19:27:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23723;
	Mon, 17 Jun 2002 19:20:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23704
	for <hubmib@optimus.ietf.org>; Mon, 17 Jun 2002 19:20:36 -0400 (EDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23365
	for <hubmib@ietf.org>; Mon, 17 Jun 2002 19:19:57 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id QAA05656;
	Mon, 17 Jun 2002 16:20:33 -0700
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Mon, 17 Jun 2002 16:20:32 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards
 board
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A476@IS0004AVEXU1.global.avaya.com>
Message-ID: <Pine.LNX.4.10.10206171601450.19709-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Fri, 14 Jun 2002, Romascanu, Dan (Dan) wrote:
> As the IEEE standards will be published, the references
> need to be updated. I trust that the editors will do this
> in the next spin, after the IESG review.

Speaking as WIS MIB lead editor:  I plan either to do exactly
that or else to ask the RFC Editor to do so.  This item is
present in the "to-do" list in the current WIS MIB I-D.

> [ Mike Heard wrote: ]
> > ([ ... ] the WIS MIB [ ... ] also needs for the
> > SONET-MIB update to pass WG and IESG approval).
> 
> It would be useful if you can provide to the hubmib
> folks who are not on atommib a short report on status
> and plans wrt. the SONET MIB.

The current SONET-MIB update, "Definitions of Managed Objects for
the SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-00.txt>,
and the current PerfHistTC-MIB update, "Textual Conventions for MIB
Modules Using Performance History Based on 15 Minute Intervals",
<draft-ietf-atommib-rfc2493bis-00.txt>, both went to WG last call in
the AToMMIB group today, with the last call to expire on July 1st.
Sufficient implementation reports have been collected to advance the
documents to draft standard;  see the slides in the IETF 53 proceedings
for details.  Although nothing is ever assured, I think that the chances
are very good that these documents will be approved without undue delay.

Regards,

Mike


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


From daemon@optimus.ietf.org  Mon Jun 17 20:24:43 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 TAA23462
	for <hubmib-archive@odin.ietf.org>; Mon, 17 Jun 2002 19:27:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA24008
	for hubmib-archive@odin.ietf.org; Mon, 17 Jun 2002 19:27:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23723;
	Mon, 17 Jun 2002 19:20:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23704
	for <hubmib@optimus.ietf.org>; Mon, 17 Jun 2002 19:20:36 -0400 (EDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23365
	for <hubmib@ietf.org>; Mon, 17 Jun 2002 19:19:57 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id QAA05656;
	Mon, 17 Jun 2002 16:20:33 -0700
	(envelope-from heard@pobox.com)
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Mon, 17 Jun 2002 16:20:32 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Hubmib Mailing List <hubmib@ietf.org>
Subject: RE: [Hubmib] 802.3ae (10 Gb/s Ethernet) approved by IEEE standards
 board
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A476@IS0004AVEXU1.global.avaya.com>
Message-ID: <Pine.LNX.4.10.10206171601450.19709-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hubmib-admin@ietf.org
Errors-To: hubmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <hubmib.ietf.org>
X-BeenThere: hubmib@ietf.org

On Fri, 14 Jun 2002, Romascanu, Dan (Dan) wrote:
> As the IEEE standards will be published, the references
> need to be updated. I trust that the editors will do this
> in the next spin, after the IESG review.

Speaking as WIS MIB lead editor:  I plan either to do exactly
that or else to ask the RFC Editor to do so.  This item is
present in the "to-do" list in the current WIS MIB I-D.

> [ Mike Heard wrote: ]
> > ([ ... ] the WIS MIB [ ... ] also needs for the
> > SONET-MIB update to pass WG and IESG approval).
> 
> It would be useful if you can provide to the hubmib
> folks who are not on atommib a short report on status
> and plans wrt. the SONET MIB.

The current SONET-MIB update, "Definitions of Managed Objects for
the SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-00.txt>,
and the current PerfHistTC-MIB update, "Textual Conventions for MIB
Modules Using Performance History Based on 15 Minute Intervals",
<draft-ietf-atommib-rfc2493bis-00.txt>, both went to WG last call in
the AToMMIB group today, with the last call to expire on July 1st.
Sufficient implementation reports have been collected to advance the
documents to draft standard;  see the slides in the IETF 53 proceedings
for details.  Although nothing is ever assured, I think that the chances
are very good that these documents will be approved without undue delay.

Regards,

Mike


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



From hubmib-admin@ietf.org  Thu Jun 27 04:29:20 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 EAA06237
	for <hubmib-archive@odin.ietf.org>; Thu, 27 Jun 2002 04:29:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11327;
	Thu, 27 Jun 2002 04:22:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11301
	for <hubmib@optimus.ietf.org>; Thu, 27 Jun 2002 04:22:34 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06071
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:21:48 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA28576
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:20:43 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA28561
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:20:42 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Date: Thu, 27 Jun 2002 11:22:28 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A59A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Bridge-mib] Support of  LAN FCS in Ethernet packet over ATM AAL5.
Thread-Index: AcIds0tojUMlZnvERjugcslkx6xElAAACeyg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
Cc: <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA11302
Subject: [Hubmib] RE: [Bridge-mib] Support of  LAN FCS in Ethernet packet over ATM AAL5.
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

Nurit,

Please take this discussion off the hubmib list. I do not think this is relevant for this working group, which focuses on management of Ethernet interfaces and devices. 

Thanks,

Dan


> -----Original Message-----
> From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]
> Sent: Thursday, June 27, 2002 11:19 AM
> To: 'Manuel Stol'; PPPoE Mailing List (E-mail)
> Cc: 'bridge-mib@ietf.org'; 'hubmib@ietf.org'
> Subject: [Bridge-mib] Support of LAN FCS in Ethernet packet over ATM
> AAL5.
> 
> 
> In RFC 2684 on Multiprotocol Encapsulation over ATM 
> Adaptation Layer 5, the
> Payload Format for Bridged Ethernet/802.3 PDUs is defined as follows:
> 
>                 +-------------------------------+
>                 |    MAC destination address    |
>                 +-------------------------------+
>                 |                               |
>                 |   (remainder of MAC frame)    |
>                 |                               |
>                 +-------------------------------+
>                 |  LAN FCS (if PID is 0x00-01)  |
>                 +-------------------------------+
>  
> The LAN FCS option is VC dependent. 
> In case that the LAN FCS is supported, duplicate checksum 
> calculations are
> performed: one for the AAL5 frame and one for the Ethernet frame.
> 
> In what cases is it required/suggested/worth to support the 
> LAN FCS when
> transmitting a packet within an AAL5 packet over an ATM network? 
> 
> Can a bridge that resides at the end of the ATM, de-capsulate 
> the ATM packet
> and transmit the Ethernet packet over a LAN, calculate the 
> LAN FCS and set
> it in the Ethernet packet (if required)?
> 
> Thanks in advance, 
> Nurit Sprecher
> 
> 
> _______________________________________________
> Bridge-mib mailing list
> Bridge-mib@ietf.org
> https://www1.ietf.org/mailman/listinfo/bridge-mib
> 

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


From daemon@optimus.ietf.org  Thu Jun 27 04:29:20 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 EAA06243
	for <hubmib-archive@odin.ietf.org>; Thu, 27 Jun 2002 04:29:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA11942
	for hubmib-archive@odin.ietf.org; Thu, 27 Jun 2002 04:30:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11327;
	Thu, 27 Jun 2002 04:22:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11301
	for <hubmib@optimus.ietf.org>; Thu, 27 Jun 2002 04:22:34 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06071
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:21:48 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA28576
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:20:43 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA28561
	for <hubmib@ietf.org>; Thu, 27 Jun 2002 04:20:42 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Date: Thu, 27 Jun 2002 11:22:28 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A59A@IS0004AVEXU1.global.avaya.com>
Thread-Topic: [Bridge-mib] Support of  LAN FCS in Ethernet packet over ATM AAL5.
Thread-Index: AcIds0tojUMlZnvERjugcslkx6xElAAACeyg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
Cc: <hubmib@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA11302
Subject: [Hubmib] RE: [Bridge-mib] Support of  LAN FCS in Ethernet packet over ATM AAL5.
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

Nurit,

Please take this discussion off the hubmib list. I do not think this is relevant for this working group, which focuses on management of Ethernet interfaces and devices. 

Thanks,

Dan


> -----Original Message-----
> From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]
> Sent: Thursday, June 27, 2002 11:19 AM
> To: 'Manuel Stol'; PPPoE Mailing List (E-mail)
> Cc: 'bridge-mib@ietf.org'; 'hubmib@ietf.org'
> Subject: [Bridge-mib] Support of LAN FCS in Ethernet packet over ATM
> AAL5.
> 
> 
> In RFC 2684 on Multiprotocol Encapsulation over ATM 
> Adaptation Layer 5, the
> Payload Format for Bridged Ethernet/802.3 PDUs is defined as follows:
> 
>                 +-------------------------------+
>                 |    MAC destination address    |
>                 +-------------------------------+
>                 |                               |
>                 |   (remainder of MAC frame)    |
>                 |                               |
>                 +-------------------------------+
>                 |  LAN FCS (if PID is 0x00-01)  |
>                 +-------------------------------+
>  
> The LAN FCS option is VC dependent. 
> In case that the LAN FCS is supported, duplicate checksum 
> calculations are
> performed: one for the AAL5 frame and one for the Ethernet frame.
> 
> In what cases is it required/suggested/worth to support the 
> LAN FCS when
> transmitting a packet within an AAL5 packet over an ATM network? 
> 
> Can a bridge that resides at the end of the ATM, de-capsulate 
> the ATM packet
> and transmit the Ethernet packet over a LAN, calculate the 
> LAN FCS and set
> it in the Ethernet packet (if required)?
> 
> Thanks in advance, 
> Nurit Sprecher
> 
> 
> _______________________________________________
> Bridge-mib mailing list
> Bridge-mib@ietf.org
> https://www1.ietf.org/mailman/listinfo/bridge-mib
> 

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



