Ethernet Interfaces and Hub MIB (hubmib)

Romascanu, Dan (Dan | 1 Oct 2003 09:27

WG Status

As you have probably seen, the IESG put out the WG charter revision for comments. I expect this to be approved in the next few weeks.

In any case, I would like to remind to the volunteering editors that they must submit the initial Internet-Drafts as individual submissions until October 20. As I need to announce the initial submission (draft -00 documents) we need names. Here is what I suggest:

draft-squire-hubmib-efm-mib-00.txt

draft-khermosh-hubmib-epon-mib-00.txt

draft-beilis-hubmib-efm-copper-mib-00.txt

Last, it looks like there is no enough interest for a WG meeting at the Minneapolis IETF meeting in November, because of the conflict with the IEEE plenary scheduled for the same week in Albuquerque. I suggest that the WG does not meet in Minneapolis. We can consider either organizing for an interim meeting in January in Vancouver (during the IEEE interim meting week, and a meeting at the next IETF meeting in March 2003, in Korea.

Regards,

Dan

headers

Romascanu, Dan (Dan | 1 Oct 2003 09:30

Permission

The following three Internet-Drafts are planned to be submitted before the 10/20 cut-off dates:

draft-squire-hubmib-efm-mib-00.txt

draft-khermosh-hubmib-epon-mib-00.txt

draft-beilis-hubmib-efm-copper-mib-00.txt

These are individual submissions including strawman proposals for future Ethernet Interfaces and Hub MIB (hubmib) WG items.

Regards,

Dan

headers

rfc-editor | 1 Oct 2003 20:31

RFC 3635 on Definitions of Managed Objects for the Ethernet-like Interface Types


A new Request for Comments is now available in online RFC libraries.

        RFC 3635

        Title:      Definitions of Managed Objects for
                    the Ethernet-like Interface Types
        Author(s):  J. Flick
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    johnf <at> rose.hp.com
        Pages:      64
        Characters: 154476
        Obsoletes:  2665

        I-D Tag:    draft-ietf-hubmib-etherif-mib-v3-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3635.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing Ethernet-like
interfaces.  This memo obsoletes RFC 2665.  It updates that
specification by including management information useful for the
management of 10 Gigabit per second (Gb/s) Ethernet interfaces.

This document is a product of the Ethernet Interfaces and Hub MIB
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Attachment: message/external-body, 102 bytes

Attachment (rfc3635.txt): message/external-body, 71 bytes

headers

rfc-editor | 1 Oct 2003 20:35

RFC 3637 on Definitions of Managed Objects for the Ethernet WAN Interface Sublayer


A new Request for Comments is now available in online RFC libraries.

        RFC 3637

        Title:      Definitions of Managed Objects
                    for the Ethernet WAN Interface Sublayer
        Author(s):  C.M. Heard, Ed.
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    heard <at> pobox.com
        Pages:      37
        Characters: 78785
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-hubmib-wis-mib-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3637.txt

This document 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 the
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).

The MIB module defined in this memo is an extension of the Synchronous
Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface
MIB and is implemented in conjunction with it and with the
Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, the
Interfaces Group MIB, and the Inverted Stack Table MIB.

This document is a product of the Ethernet Interfaces and Hub MIB
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Attachment: message/external-body, 102 bytes

Attachment (rfc3637.txt): message/external-body, 71 bytes

headers

rfc-editor | 1 Oct 2003 20:37

RFC 3638 on Applicability Statement for Reclassification of RFC 1643 to Historic Status


A new Request for Comments is now available in online RFC libraries.

        RFC 3638

        Title:      Applicability Statement for Reclassification of
                    RFC 1643 to Historic Status
        Author(s):  J. Flick, C. M. Heard
        Status:     Informational
        Date:       September 2003
        Mailbox:    johnf <at> rose.hp.com, heard <at> pobox.com
        Pages:      5
        Characters: 8676
        Obsoletes:  1643

        I-D Tag:    draft-ietf-hubmib-1643-to-historic-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3638.txt

This memo recommends that RFC 1643 be reclassified as an Historic
document and provides the supporting motivation for that
recommendation.

This document is a product of the Ethernet Interfaces and Hub MIB
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Attachment: message/external-body, 102 bytes

Attachment (rfc3638.txt): message/external-body, 71 bytes

headers

rfc-editor | 1 Oct 2003 20:33

RFC 3636 on Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)


A new Request for Comments is now available in online RFC libraries.

        RFC 3636

        Title:      Definitions of Managed Objects for
                    IEEE 802.3 Medium Attachment Units (MAUs)
        Author(s):  J. Flick
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    johnf <at> rose.hp.com
        Pages:      62
        Characters: 139990
        Obsoletes:  2668, 1515

        I-D Tag:    draft-ietf-hubmib-mau-mib-v3-04.txt  

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs).  This memo obsoletes RFC 2668.  This memo
extends that specification by including management information useful
for the management of 10 gigabit per second (Gb/s) MAUs.  This memo
also obsoletes RFC 1515.

This document is a product of the Ethernet Interfaces and HubMIB
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Attachment: message/external-body, 102 bytes

Attachment (rfc3636.txt): message/external-body, 71 bytes

headers

Romascanu, Dan (Dan | 2 Oct 2003 08:52

RFCs 3635 - 3638

As you must have seen in the announcements that went out in the last few hours, RFC 3635 to 3638 are out. With this most of our current charter items were executed. Please allow me to thank the editors, contributors, and the whole WG for the efforts invested. We are allowed to open and share a virtual bottle of champagne to celebrate this event!

I hope that the same dedication and sustained effort will lead to the success of our new activities related to the EFM MIBs.

Regards,

Dan

headers

Frank Strauss | 2 Oct 2003 14:34

RFC3637 ETHER-WIS MIB module name

Hi!

Is it a bug or a feature that the ETHER-WIS MIB (RFC 3637) is named
ETHER-WIS and not ETHER-WIS-MIB?

draft-ietf-ops-mib-review-guidelines-02 suggests in Appendix C names
of the form XXX-MIB.

Sorry for my talent to ask questions too late. :-/ I found no easily
searchable mailinglist archive to answer this question myself.

 -frank

headers

Romascanu, Dan (Dan | 2 Oct 2003 14:44

RE: RFC3637 ETHER-WIS MIB module name

As Mike Heard is both the author of the MIB Review Guidelines, as well as the editor of the WIS MIB he is at best
possible place to answer this 

My take is that this is a recommendation, it would have been nice to catch this earlier, but does not require a
re-spin of the RFC. Sure, it would help if the tools would be extended to catch this.

Dan

> -----Original Message-----
> From: Frank Strauss [mailto:strauss <at> ibr.cs.tu-bs.de]
> Sent: 02 October, 2003 3:34 PM
> To: Romascanu, Dan (Dan); hubmib <at> ietf.org
> Cc: mibs <at> ops.ietf.org
> Subject: RFC3637 ETHER-WIS MIB module name
> 
> 
> Hi!
> 
> Is it a bug or a feature that the ETHER-WIS MIB (RFC 3637) is named
> ETHER-WIS and not ETHER-WIS-MIB?
> 
> draft-ietf-ops-mib-review-guidelines-02 suggests in Appendix C names
> of the form XXX-MIB.
> 
> Sorry for my talent to ask questions too late. :-/ I found no easily
> searchable mailinglist archive to answer this question myself.
> 
>  -frank
>

headers

C. M. Heard | 2 Oct 2003 17:25

Re: RFC3637 ETHER-WIS MIB module name

On 2 Oct 2003, Frank Strauss wrote:
> Is it a bug or a feature that the ETHER-WIS MIB (RFC 3637) is named
> ETHER-WIS and not ETHER-WIS-MIB?
> 
> draft-ietf-ops-mib-review-guidelines-02 suggests in Appendix C names
> of the form XXX-MIB.
> 
> Sorry for my talent to ask questions too late. :-/ I found no easily
> searchable mailinglist archive to answer this question myself.

I don't think the question was ever discussed, either by the WIS
design team or on the Hub MIB WG mailing list ... at any rate my
personal archive does not contain any such discussion.

As for the history, ETHER-WIS was the module name that Mike Ayers
chose in an early WG draft, and I left it as-is when I took over the
editing duties.  The recommendations on module names in the MIB
review guidelines came somewhat later.  I never changed the name
because no one asked me to and because it did not seem to me to be
a very important issue.

Mike

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

1	January 2013
1	September 2012
2	July 2012
1	November 2011
2	August 2011
18	July 2011
1	May 2011
2	March 2011
2	February 2011
1	November 2010
1	September 2008
4	November 2007
2	October 2007
4	September 2007
4	August 2007
11	July 2007
3	June 2007
15	May 2007
6	April 2007
6	March 2007
15	February 2007
9	January 2007
8	December 2006
12	November 2006
31	October 2006
23	September 2006
8	August 2006
14	July 2006
22	June 2006
17	May 2006
4	April 2006
3	March 2006
18	February 2006
18	January 2006
2	December 2005
5	November 2005
13	October 2005
3	September 2005
6	August 2005
4	July 2005
7	June 2005
14	April 2005
33	March 2005
7	February 2005
39	January 2005
21	December 2004
9	November 2004
9	October 2004
12	September 2004
22	August 2004
17	July 2004
6	June 2004
8	May 2004
3	April 2004
23	March 2004
32	February 2004
7	January 2004
15	December 2003
4	November 2003
42	October 2003
14	September 2003
10	August 2003
12	July 2003
28	June 2003
25	May 2003
6	April 2003
7	March 2003
1	February 2003
13	January 2003
8	December 2002
22	November 2002
4	September 2002
4	August 2002
3	July 2002
6	June 2002
17	May 2002
10	April 2002