[IANA #954288] General Request for Assignment (IANA-MAU-MIB)
David, Adam, all,
These registrations are complete. Please see
https://www.iana.org/assignments/ianamau-mib
Best regards,
Amanda Baber
Lead IANA Services Specialist
PTI
On Tue Mar 21 14:41:55 2017, stds-802-3-mib@xxxxxxxx wrote:
>
> Contact Name:
> IEEE 802.3 Ethernet Working Group
>
> Contact Email:
> stds-802-3-mib@xxxxxxxx
>
> Type of Assignment:
> Assignment of the following additions to the IANAifMauTypeListBits
> textual convention, immediately following b100GbaseER4(78) --
> 100GBASE-ER4:
>
> b1000baseT1(??) -- 1000BASE-T1
> b1000basePX30D(??) -- 1000BASE-PX30D
> b1000basePX30U(??) -- 1000BASE-PX30U
> b1000basePX40D(??) -- 1000BASE-PX40D
> b1000basePX40U(??) -- 1000BASE-PX40U
> b10G1GbasePRXD4(??) -- 10/1GBASE-PRX-D4
> b10G1GbasePRXU4(??) -- 10/1GBASE-PRX-U4
> b10GbasePRD4(??) -- 10GBASE-PRD4
> b10GbasePRU4(??) -- 10GBASE-PRU4
> b25GbaseCR(??) -- 25GBASE-CR
> b25GbaseCRS(??) -- 25GBASE-CR-S
> b25GbaseKR(??) -- 25GBASE-KR
> b25GbaseKRS(??) -- 25GBASE-KR-S
> b25GbaseR(??) -- 25GBASE-R
> b25GbaseSR(??) -- 25GBASE-SR
> b25GbaseT(??) -- 25GBASE-T
> b40GbaseER4(??) -- 40GBASE-ER4
> b40GbaseR(??) -- 40GBASE-R
> b40GbaseT(??) -- 40GBASE-T
> b100GbaseCR4(??) -- 100GBASE-CR4
> b100GbaseKR4(??) -- 100GBASE-KR4
> b100GbaseKP4(??) -- 100GBASE-KP4
> b100GbaseR(??) -- 100GBASE-R
> b100GbaseSR4(??) -- 100GBASE-SR4
>
> Assignment of the following additions to the IANAifMauAutoNegCapBits
> textual convention, immediately following b100GbaseCR10(22) --
> 100GBASE-CR10:
>
> b1000baseT1(??) -- 1000BASE-T1
> b25GbaseRS(??) -- 25GBASE-CR-S or 25GBASE-KR-S
> b25GbaseR(??) -- 25GBASE-CR or 25GBASE-KR
> bRSFEC25Greq(??) -- 25Gb/s RS-FEC
> bBaseFEC25Greq(??) -- 25Gb/s BASE-R FEC
> b25GbaseT(??) -- 25GBASE-T
> b40GbaseT(??) -- 40GBASE-T
> b100GbaseCR4(??) -- 100GBASE-CR4
> b100GbaseKR4(??) -- 100GBASE-KR4
> b100GbaseKP4(??) -- 100GBASE-KP4
> bForceMS(??) -- 1000BASE-T1 Force MS
>
> Assignment of the following additions to the dot3MauType object
> identities,
> immediately following dot3MauType100GbaseER4 OBJECT-IDENTITY... ::= {
> dot3MauType
> 78 }:
>
> dot3MauType1000baseT1 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "1000BASE-T1 single balanced twisted-pair copper cabling
> PHY"
> REFERENCE "IEEE Std 802.3, Clause 96"
> ::= { dot3MauType xx }
>
> dot3MauType1000basePX30D OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber EPON OLT, 20km, 1:32 split ratio"
> REFERENCE "IEEE Std 802.3, Clause 60"
> ::= { dot3MauType xx }
>
> dot3MauType1000basePX30U OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber EPON ONU, 20km, 1:32 split ratio"
> REFERENCE "IEEE Std 802.3, Clause 60"
> ::= { dot3MauType xx }
>
> dot3MauType1000basePX40D OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber EPON OLT, 20km, 1:64 split ratio"
> REFERENCE "IEEE Std 802.3, Clause 60"
> ::= { dot3MauType xx }
>
> dot3MauType1000basePX40U OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber EPON ONU, 20km, 1:64 split ratio"
> REFERENCE "IEEE Std 802.3, Clause 60"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXD4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate EPON OLT,
> supporting
> extended power budget (PRX40)"
> REFERENCE "IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10G1GbasePRXU4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber asymmetric-rate EPON ONU,
> supporting
> extended power budget (PRX40)"
> REFERENCE "IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRD4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON OLT,
> supporting
> extended power budget (PR40)"
> REFERENCE "IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType10GbasePRU4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "One single-mode fiber symmetric-rate EPON ONU,
> supporting
> extended power budget (PR40)"
> REFERENCE "IEEE Std 802.3, Clause 75"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseCR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over shielded balanced copper cable"
> REFERENCE "IEEE Std 802.3, Clause 110"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseCRS OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over shielded balanced copper cable
> without RS-FEC"
> REFERENCE "IEEE Std 802.3, Clause 110"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseKR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over an electrical backplane"
> REFERENCE "IEEE Std 802.3, Clause 111"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseKRS OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over an electrical backplane without
> RS-FEC"
> REFERENCE "IEEE Std 802.3, Clause 111"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over undefined PMD"
> REFERENCE "IEEE Std 802.3, Clause 107 and 109"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseSR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "25GBASE-R PCS/PMA over multimode fiber"
> REFERENCE "IEEE Std 802.3, Clause 112"
> ::= { dot3MauType xx }
>
> dot3MauType25GbaseT OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "Four-pair twisted-pair balanced copper cabling"
> REFERENCE "IEEE Std 802.3, Clause 113"
> ::= { dot3MauType xx }
>
> dot3MauType40GbaseER4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "40GBASE-R PCS/PMA over 4 WDM lane single mode fiber"
> REFERENCE "IEEE Std 802.3, Clause 82"
> ::= { dot3MauType xx }
>
> dot3MauType40GbaseR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "40GBASE-R PCS as over undefined PMA/PMD"
> REFERENCE "IEEE Std 802.3, Clause 82"
> ::= { dot3MauType xx }
>
> dot3MauType40GbaseT OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "Four-pair twisted-pair balanced copper cabling"
> REFERENCE "IEEE Std 802.3, Clause 113"
> ::= { dot3MauType xx }
>
> dot3MauType100GbaseCR4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION " 100GBASE-R PCS/PMA over 4 lane shielded copper balanced
> cable"
> REFERENCE "IEEE Std 802.3, Clause 92"
> ::= { dot3MauType xx }
>
> dot3MauType100GbaseKR4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "100GBASE-R PCS/PMA over an electrical backplane"
> REFERENCE "IEEE Std 802.3, Clause 93"
> ::= { dot3MauType xx }
>
> dot3MauType100GbaseKP4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "100GBASE-P PCS/PMA over an electrical backplane PMD"
> REFERENCE "IEEE Std 802.3, Clause 94"
> ::= { dot3MauType xx }
>
> dot3MauType100GbaseR OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "100GBASE-R Multi-lane PCS over undefined PMA/PMD"
> REFERENCE "IEEE Std 802.3, Clause 82"
> ::= { dot3MauType xx }
>
> dot3MauType100GbaseSR4 OBJECT-IDENTITY
> STATUS current
> DESCRIPTION "100GBASE-R PCS/PMA over 4 lane multimode fiber"
> REFERENCE "IEEE Std 802.3, Clause 95"
> ::= { dot3MauType xx }
>
> Registry:
> The assignment of the IANAifMauTypeListBits and
> IANAifMauAutoNegCapBits textual conventions as well as the dot3MauType
> object identities contained in the IANA-MAU-MIB.
>
> Description:
> The new MAU types and the associated AutoNeg capability bits listed
> above were specified in the IEEE 802.3 amendments IEEE Std 802.3bk-
> 2013, IEEE Std 802.3bj-2014 and IEEE Std 802.3bm-2015, which are now
> published in IEEE Std 802.3-2015, as well as IEEE Std 802.3bw-2015,
> IEEE Std 802.3by-2016, IEEE Std 802.3bq-2016 and IEEE Std 802.3bp-
> 2016.
>
> 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 are imported and referenced in the IEEE8023-MAU-MIB, which
> is defined in Clause 13 of IEEE Std 802.3.1-2013, 'IEEE Standard for
> Management Information Base (MIB) Definitions for Ethernet'.
>
>
> Additional Info:
> IEEE Std 802.3-2015, subclauses 30.5.1.1.2 aMAUType and 30.6.1.1.5
> aAutoNegLocalTechnologyAbility, as amended by IEEE Std 802.3bw-2015,
> IEEE Std 802.3by-2016, IEEE Std 802.3bq-2016 and IEEE Std 802.3bp-
> 2016.