RE: [802.3.1_MIBS] FW: [IANA #299307] AutoReply: General Request for Assignments
These will probably be referred to Bert as last chair of the Ethernet
MIB WG (now concluded) and/or to me as Area Director.
Dan
> -----Original Message-----
> From: Howard Frazier [mailto:hfrazier@xxxxxxxxxxxx]
> Sent: Wednesday, February 10, 2010 3:50 AM
> To: STDS-802-3-MIB@xxxxxxxxxxxxxxxxx
> Subject: [802.3.1_MIBS] FW: [IANA #299307] AutoReply: General
> Request for Assignments
>
>
>
> In accordance with the directions of the IEEE 802.3 Ethernet
> Working Group and the IEEE 802.3.1 MIB Task Force, I have
> submitted a request to IANA for additions to the
> IANAifMauTypeListBits textual convention, additions to the
> IANAifMauAutoNegCapBits textual convention, and additions to
> the dot3MauType object identities.
>
> The contents of the request are included below, in an
> automated response from IANA.
>
> Howard Frazier
> Chair, IEEE 802.3.1 MIB Task Force
>
> -----Original Message-----
> From: IANA General Enquiries via RT [mailto:iana-questions@xxxxxxxx]
> Sent: Tuesday, February 09, 2010 5:41 PM
> To: Howard Frazier
> Subject: [IANA #299307] AutoReply: General Request for Assignments
>
> To whom it may concern:
>
> This is an automatically generated message to notify you that
> we have received your request, and it has been recorded in
> our ticketing system with a reference number of 299307.
>
> There is no need to reply to this message right now. IANA
> staff will review your message shortly.
>
> If this message is in reply to a previously submitted ticket,
> it is possible that the previous ticket has been marked as
> closed. As we review this ticket, we will also review
> previous correspondence and take appropriate action.
>
> To expedite processing, and ensure our staff can view the
> full history of this request, please make sure you include
> the follow exact text in the subject line of all future
> correspondence on this issue:
>
> [IANA #299307]
>
> You can also simply reply to this message, as this tag is
> already in the subject line.
>
> Thank you,
>
> The Internet Assigned Numbers Authority
> iana-questions@xxxxxxxx
>
> --------------------------------------------------------------
> -----------
> Contact Name :
> Howard Frazier
>
> Contact Email :
> hfrazier@xxxxxxxxxxxx
>
> Type of Assignment :
> Assignment of the following additions to the
> IANAifMauTypeListBits textual convention, immediately
> following b1000BasePX20U(53) -- 1000BASE-PX20U:
>
> b10GbaseT(xx) -- 10GBASE-T
> b10GbaseLRM(xx) -- 10GBASE-LRM
> b1000baseKX(xx) -- 1000BASE-KX
> b10GbaseKX4(xx) -- 10GBASE-KX4
> b10GbaseKR(xx) -- 10GBASE-KR
> b10G1GbasePRXD1(xx) -- 10/1GBASE-PRX-D1
> b10G1GbasePRXD2(xx) -- 10/1GBASE-PRX-D2
> b10G1GbasePRXD3(xx) -- 10/1GBASE-PRX-D3
> b10G1GbasePRXU1(xx) -- 10/1GBASE-PRX-U1
> b10G1GbasePRXU2(xx) -- 10/1GBASE-PRX-U2
> b10G1GbasePRXU3(xx) -- 10/1GBASE-PRX-U3
> b10GbasePRD1(xx) -- 10GBASE-PR-D1
> b10GbasePRD2(xx) -- 10GBASE-PR-D2
> b10GbasePRD3(xx) -- 10GBASE-PR-D3
> b10GbasePRU1(xx) -- 10GBASE-PR-U1
> b10GbasePRU3(xx) -- 10GBASE-PR-U3
>
> Assignment of the following additions to the
> IANAifMauAutoNegCapBits textual convention, immediately
> following b1000baseTFD(15) -- 1000BASE-T full duplex mode:
>
> b10GbaseT(xx) -- 10GBASE-T
> b1000baseKX(xx) -- 1000BASE-KX
> b10GbaseKX4(xx) -- 10GBASE-KX4
> b10GbaseKR(xx) -- 10GBASE-KR
>
> Assignment of the following additions to the dot3MauType
> object identities, immediately following
> dot3MauType1000BasePX20U OBJECT-IDENTITY ...
> ::= { dot3MauType 53 }:
>
> dot3MauType10GbaseT OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "Four-pair Category 6A or better, full
> duplex mode only"
> REFERENCE "IEEE Std 802.3, Clause 55"
> ::= { dot3MauType xx }
>
> dot3MauType10GbaseLRM OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "R multimode fiber over 1310 nm optics"
> REFERENCE "IEEE Std 802.3, Clause 68"
> ::= { dot3MauType xx }
>
> dot3MauType1000baseKX OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "X backplane, full duplex mode only"
> REFERENCE "IEEE Std 802.3, Clause 70"
> ::= { dot3MauType xx }
>
> dot3MauType10GbaseKX4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "4 lane X backplane, full duplex mode only"
> REFERENCE "IEEE Std 802.3, Clause 71"
> ::= { dot3MauType xx }
>
> dot3MauType10GbaseKR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "R backplane, full duplex mode only"
> REFERENCE " IEEE Std 802.3, Clause 72"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXD1 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON OLT, supporting low
> power budget (PRX10)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXD2 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON OLT, supporting medium
> power budget (PRX20)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXD3 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON OLT, supporting high
> power budget (PRX30)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXU1 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON ONU, supporting low
> power budget (PRX10)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXU2 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON ONU, supporting medium
> power budget (PRX20)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXU3 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate
> EPON ONU, supporting high
> power budget (PRX30)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRD1 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON
> OLT, supporting low
> power budget (PR10)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRD2 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON
> OLT, supporting medium
> power budget (PR20)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRD3 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON
> OLT, supporting high
> power budget (PR30)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRU1 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON
> ONU, supporting low and
> medium power budget (PR10 and PR20)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRU3 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON
> ONU, supporting high
> power budget (PR30)"
> REFERENCE " IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
>
> Registry :
> The assignment of the IANAifMauTypeListBits and
> IANAifMauAutoNegCapBits textual conventions as well as the
> dot3MauType object identities is contained in the
> IANA-MAU-MIB, which is currently published as IETF RFC 4836.
> The IEEE 802.3 Ethernet Working Group is currently working on
> a project, known as IEEE P802.3.1, that will update and
> republish the IETF RFCs that are relevant to the management
> of Ethernet interfaces, including the contents of RFC 4836.
>
> Description :
> The new MAU types and the associated AutoNeg capability bits
> listed above were specified in recently approved amendments
> to IEEE Std 802.3, including IEEE Std 802.3an-2006, IEEE Std
> 802.3aq-2007, IEEE Std 802.3ap-2007, and IEEE Std
> 802.3av-2009. The description of the IANAifMauTypeListBits
> textual convention states that "...changes in this textual
> convention SHALL be synchronized with relevant changes in the
> dot3MauType OBJECT-IDENTITIES." The assignments will be
> reflected in Clause 14 of IEEE P802.3.1, "IEEE Draft Standard
> for Management Information Base (MIB) definitions for Ethernet."
>
>
> Additional Info :
> IEEE Std 802.3-2008, subclauses 30.5.1.1.2 aMAUType and
> 30.6.1.1.5 aAutoNegLocalTechnologyAbility, as amended by IEEE
> Std 802.3av-2009.
>