draft-ietf-hubmib-rfc3636bis-02.txt | draft-ietf-hubmib-rfc3636bis-03.txt | |||
---|---|---|---|---|
Network Working Group E. Beili | Network Working Group E. Beili | |||
Internet-Draft Actelis Networks | Internet-Draft Actelis Networks | |||
Expires: April 27, 2006 October 24, 2005 | Expires: December 9, 2006 June 07, 2006 | |||
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units | Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units | |||
(MAUs) | (MAUs) | |||
draft-ietf-hubmib-rfc3636bis-02.txt | draft-ietf-hubmib-rfc3636bis-03.txt | |||
Status of this Memo | Status of this Memo | |||
By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
applicable patent or other IPR claims of which he or she is aware | applicable patent or other IPR claims of which he or she is aware | |||
have been or will be disclosed, and any of which he or she becomes | have been or will be disclosed, and any of which he or she becomes | |||
aware will be disclosed, in accordance with Section 6 of BCP 79. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
skipping to change at page 1, line 34 | skipping to change at page 1, line 34 | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on April 27, 2006. | This Internet-Draft will expire on December 9, 2006. | |||
Copyright Notice | Copyright Notice | |||
Copyright (C) The Internet Society (2005). | Copyright (C) The Internet Society (2006). | |||
Abstract | Abstract | |||
This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
In particular, it defines objects for managing IEEE 802.3 Medium | In particular, it defines objects for managing IEEE 802.3 Medium | |||
Attachment Units (MAUs). This memo obsoletes RFC 3636. It amends | Attachment Units (MAUs). This memo obsoletes RFC 3636. It amends | |||
that specification by moving MAU type OBJECT-IDENTITY definitions and | that specification by moving MAU type OBJECT-IDENTITY definitions and | |||
relevant textual conventions into a separate Internet Assigned Number | relevant textual conventions into a separate Internet Assigned Number | |||
Authority (IANA) maintained MIB module. In addition, management | Authority (IANA) maintained MIB module. In addition, management | |||
skipping to change at page 2, line 23 | skipping to change at page 2, line 23 | |||
3.3. Relationship to RFC 2239 . . . . . . . . . . . . . . . . . 5 | 3.3. Relationship to RFC 2239 . . . . . . . . . . . . . . . . . 5 | |||
3.4. Relationship to RFC 1515 . . . . . . . . . . . . . . . . . 5 | 3.4. Relationship to RFC 1515 . . . . . . . . . . . . . . . . . 5 | |||
3.5. Relationship to other MIBs . . . . . . . . . . . . . . . . 5 | 3.5. Relationship to other MIBs . . . . . . . . . . . . . . . . 5 | |||
3.5.1. Relationship to the Interfaces MIB . . . . . . . . . . 6 | 3.5.1. Relationship to the Interfaces MIB . . . . . . . . . . 6 | |||
3.5.2. Relationship to the 802.3 Repeater MIB module . . . . 6 | 3.5.2. Relationship to the 802.3 Repeater MIB module . . . . 6 | |||
3.6. Management of Internal MAUs . . . . . . . . . . . . . . . 7 | 3.6. Management of Internal MAUs . . . . . . . . . . . . . . . 7 | |||
3.7. Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 | 3.7. Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 | |||
3.8. Addition of new MAU Types . . . . . . . . . . . . . . . . 8 | 3.8. Addition of new MAU Types . . . . . . . . . . . . . . . . 8 | |||
3.8.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 | 3.8.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 | |||
3.8.2. IANAifMauTypeListBits Textual Convention . . . . . . . 9 | 3.8.2. IANAifMauTypeListBits Textual Convention . . . . . . . 9 | |||
3.8.3. JackType Textual Convention . . . . . . . . . . . . . 9 | 3.8.3. IANAifMauMediaAvailable Textual Convention . . . . . . 9 | |||
4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9 | 3.8.4. IANAifMauAutoNegCapBits Textual Convention . . . . . . 9 | |||
5. IANA-maintained MAU TC Definitions . . . . . . . . . . . . . . 51 | 3.8.5. JackType Textual Convention . . . . . . . . . . . . . 9 | |||
4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10 | ||||
5. IANA-maintained MAU TC Definitions . . . . . . . . . . . . . . 46 | ||||
6. Security Considerations . . . . . . . . . . . . . . . . . . . 62 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 62 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 | |||
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 | 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63 | |||
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 | |||
9.1. Normative References . . . . . . . . . . . . . . . . . . . 64 | 9.1. Normative References . . . . . . . . . . . . . . . . . . . 64 | |||
9.2. Informative References . . . . . . . . . . . . . . . . . . 66 | 9.2. Informative References . . . . . . . . . . . . . . . . . . 66 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 67 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 67 | |||
Intellectual Property and Copyright Statements . . . . . . . . . . 68 | Intellectual Property and Copyright Statements . . . . . . . . . . 68 | |||
1. Introduction | 1. Introduction | |||
This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
skipping to change at page 4, line 30 | skipping to change at page 4, line 30 | |||
2004 [IEEE802.3ah] and IEEE Std. 802.3ak-2004 [IEEE802.3ak]. This | 2004 [IEEE802.3ah] and IEEE Std. 802.3ak-2004 [IEEE802.3ak]. This | |||
specification is intended to provide for management of all types of | specification is intended to provide for management of all types of | |||
Ethernet/802.3 MAUs. | Ethernet/802.3 MAUs. | |||
3.1. Relationship to RFC 3636 | 3.1. Relationship to RFC 3636 | |||
The management definitions provided in this memo are intended to be a | The management definitions provided in this memo are intended to be a | |||
superset of those defined by RFC 3636 [RFC3636]. | superset of those defined by RFC 3636 [RFC3636]. | |||
In order to decrease re-issues of this document due to the new MAU | In order to decrease re-issues of this document due to the new MAU | |||
type and/or Jack type introduction, all relevant object identities | type, Media Available state, Auto Negotiation capability and/or Jack | |||
and textual conventions have been moved to a separate, IANA- | type introduction, all relevant object identities and textual | |||
maintained MIB module IANA-MAU-MIB, the first version of which is | conventions have been moved to a separate, IANA-maintained MIB module | |||
defined in this memo. Thus when a new MAU type and/or Jack type is | IANA-MAU-MIB, the first version of which is defined in this memo. | |||
defined by the IEEE 802.3 working group, only the IANA-maintained | Thus when a new MAU type, Media Available state, Auto Negotiation | |||
module needs to be revised, leaving the basic MAU-MIB module defined | capability and/or Jack type is defined by the IEEE 802.3 working | |||
in this memo unchanged. | group, only the IANA-maintained module needs to be revised, leaving | |||
the basic MAU-MIB module defined in this memo unchanged. | ||||
In addition, the new definitions are added to the IANA-maintained MIB | In addition, the new definitions are added to the IANA-maintained MIB | |||
module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4 | module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4 | |||
interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE | interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE | |||
Std 802.3ak-2004 [IEEE802.3ak] respectively. | Std 802.3ak-2004 [IEEE802.3ak] respectively. | |||
It should be noted that the changes made in this revision will not be | It should be noted that the changes made in this revision will not be | |||
entirely backward-compatible with MIB modules that currently import | entirely backward-compatible with MIB modules that currently import | |||
MAU type object identity descriptors from the MAU-MIB; such modules | MAU type object identity descriptors from the MAU-MIB; such modules | |||
will need to be revised to import those DESCRIPTORS from the IANA- | will need to be revised to import those DESCRIPTORS from the IANA- | |||
MAU-MIB. Similarly, any management applications that process the | MAU-MIB. Similarly, any management applications that process the | |||
object identity definitions (e.g., to present the DESCRIPTION text to | object identity definitions (e.g., to present the DESCRIPTION text to | |||
a user) will need to be get those definitions from the IANA-MAU-MIB | a user) will need to be get those definitions from the IANA-MAU-MIB | |||
instead of the MAU-MIB. While it is true that changes that require | instead of the MAU-MIB. While it is true that changes that require | |||
such adjustments are not strictly compliant with the SMIv2 rules | such adjustments are not strictly compliant with the SMIv2 rules | |||
governing MIB module revisions (see [RFC2578] Section 10), in this | governing MIB module revisions (see [RFC2578] Section 10), in this | |||
case continued high maintenance costs that would result from not | case continued high maintenance costs that would result from not | |||
making these changes maked the deviation from the rules justified. | making these changes make the deviation from the rules justified. It | |||
It should be noted that the working group was not able to find any | should be noted that the working group was not able to find any | |||
examples of MIB modules or management applications that would | examples of MIB modules or management applications that would | |||
actually be negatively affected by the changes. | actually be negatively affected by the changes. | |||
3.2. Relationship to RFC 2668 | 3.2. Relationship to RFC 2668 | |||
RFC 3636 was a replacement for RFC 2668 [RFC2668]. RFC 3636 included | RFC 3636 was a replacement for RFC 2668 [RFC2668]. RFC 3636 included | |||
all of the objects contained in RFC 2668, plus new and updated | all of the objects contained in RFC 2668, plus new and updated | |||
definitions to provide management support for 10 Gb/s devices. | definitions to provide management support for 10 Gb/s devices. | |||
3.3. Relationship to RFC 2239 | 3.3. Relationship to RFC 2239 | |||
skipping to change at page 8, line 51 | skipping to change at page 8, line 51 | |||
3.8.1. dot3MauType OBJECT-IDENTITIES | 3.8.1. dot3MauType OBJECT-IDENTITIES | |||
The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions | The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions | |||
has been moved from the MAU-MIB into the IANA-maintained IANA-MAU- | has been moved from the MAU-MIB into the IANA-maintained IANA-MAU- | |||
MIB, first version of which is defined in this memo. | MIB, first version of which is defined in this memo. | |||
When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of | When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of | |||
IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its | IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its | |||
matching IANAifMauTypeListBits textual convention value and, | matching IANAifMauTypeListBits textual convention value and, | |||
possibly, with a new IANAifJackType value. | possibly, with new IANAifMauMediaAvailable, IANAifMauAutoNegCapBits | |||
and/or IANAifJackType values. | ||||
An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for | An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for | |||
the addition of the new MAU and/or Jack types. | the addition of the new MAU, Media Available states, Auto Negotiation | |||
capabilities and/or Jack types. | ||||
In some cases new MAU types may require additional managed objects or | In some cases new MAU types may require additional managed objects or | |||
may have side effects on the behavior of existing managed objects. | may have side effects on the behavior of existing managed objects. | |||
In such cases a standards-track specification (which may be a new | In such cases a standards-track specification (which may be a new | |||
document or a revision of this document) is also REQUIRED. Any such | document or a revision of this document) is also REQUIRED. Any such | |||
document is REQUIRED to note any special properties of the MAU types | document is REQUIRED to note any special properties of the MAU types | |||
that it defines - for example, side effects on the ifStackTable as | that it defines - for example, side effects on the ifStackTable as | |||
noted in this document for 10GBASE-W MAUs. | noted in this document for 10GBASE-W MAUs. | |||
3.8.2. IANAifMauTypeListBits Textual Convention | 3.8.2. IANAifMauTypeListBits Textual Convention | |||
The syntax of ifMauTypeListBits is changed to be a textual | The syntax of ifMauTypeListBits is changed to be a textual | |||
convention, such that the enumerated integer values are now defined | convention, such that the enumerated integer values are now defined | |||
in the textual convention, IANAifMauTypeListBits, which can be re- | in the textual convention, IANAifMauTypeListBits, which can be re- | |||
specified (with additional values) in the IANA-maintained MIB module, | specified (with additional values, when defined by IEEE 802.3) in the | |||
without issuing a new version of this document. | IANA-maintained MIB module, without issuing a new version of this | |||
document. | ||||
3.8.3. JackType Textual Convention | 3.8.3. IANAifMauMediaAvailable Textual Convention | |||
The syntax of ifMauMediaAvailable and rpMauMediaAvailable is changed | ||||
a textual convention, such that the enumerated integer values are now | ||||
defined in the textual convention, IANAifMauMediaAvailable, which can | ||||
be re-specified (with additional values, when defined by IEEE 802.3) | ||||
in the IANA-maintained MIB module, without issuing a new version of | ||||
this document. | ||||
3.8.4. IANAifMauAutoNegCapBits Textual Convention | ||||
The syntax of ifMauAutoNegCapabilityBits, | ||||
ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapReceivedBits objects | ||||
is changed to be a textual convention, such that the enumerated | ||||
integer values are now defined in the textual convention, | ||||
IANAifMauAutoNegCapBits, which can be re-specified (with additional | ||||
values, when defined by IEEE 802.3) in the IANA-maintained MIB | ||||
module, without issuing a new version of this document. | ||||
3.8.5. JackType Textual Convention | ||||
The JackType Textual Convention has been deprecated in favor of | The JackType Textual Convention has been deprecated in favor of | |||
IANAifJackType defined in the IANA-maintained MIB module, so the new | IANAifJackType defined in the IANA-maintained MIB module, so the new | |||
Jack types can be added (when defined by IEEE 802.3) without issuing | Jack types can be added (when defined by IEEE 802.3) without issuing | |||
a new version of this document. | a new version of this document. | |||
4. MAU MIB Definitions | 4. MAU MIB Definitions | |||
MAU-MIB DEFINITIONS ::= BEGIN | MAU-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
Counter32, Integer32, Counter64, | Counter32, Integer32, Counter64, | |||
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 | OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 | |||
FROM SNMPv2-SMI -- RFC 2578 | FROM SNMPv2-SMI -- RFC 2578 | |||
TruthValue, AutonomousType, TEXTUAL-CONVENTION | TruthValue, AutonomousType, TEXTUAL-CONVENTION | |||
FROM SNMPv2-TC -- RFC 2579 | FROM SNMPv2-TC -- RFC 2579 | |||
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP | OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP | |||
FROM SNMPv2-CONF -- RFC 2580 | FROM SNMPv2-CONF -- RFC 2580 | |||
InterfaceIndex | InterfaceIndex | |||
FROM IF-MIB -- RFC 2863 | FROM IF-MIB -- RFC 2863 | |||
IANAifMauTypeListBits, IANAifJackType | IANAifMauTypeListBits, IANAifMauMediaAvailable, | |||
IANAifMauAutoNegCapBits, IANAifJackType | ||||
FROM IANA-MAU-MIB -- RFC 3636bis | FROM IANA-MAU-MIB -- RFC 3636bis | |||
-- EdNote: Replace RFC 3636bis above with the URL of the | -- EdNote: Replace RFC 3636bis above with the URL of the | |||
-- actual IANA-maintained module & remove this note. | -- actual IANA-maintained module & remove this note. | |||
; | ; | |||
mauMod MODULE-IDENTITY | mauMod MODULE-IDENTITY | |||
LAST-UPDATED "200510240000Z" -- Oct 24, 2005 | LAST-UPDATED "200606070000Z" -- June 07, 2006 | |||
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" | ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
"WG charter: | "WG charter: | |||
http://www.ietf.org/html.charters/hubmib-charter.html | http://www.ietf.org/html.charters/hubmib-charter.html | |||
Mailing Lists: | Mailing Lists: | |||
General Discussion: hubmib@ietf.org | General Discussion: hubmib@ietf.org | |||
To Subscribe: hubmib-request@ietf.org | To Subscribe: hubmib-request@ietf.org | |||
In Body: subscribe your_email_address | In Body: subscribe your_email_address | |||
skipping to change at page 11, line 8 | skipping to change at page 11, line 29 | |||
and physical layer specifications', as | and physical layer specifications', as | |||
amended by IEEE Std 802.3ae-2002: | amended by IEEE Std 802.3ae-2002: | |||
'Amendment: Media Access Control (MAC) | 'Amendment: Media Access Control (MAC) | |||
Parameters, Physical Layer, and Management | Parameters, Physical Layer, and Management | |||
Parameters for 10 Gb/s Operation', August, | Parameters for 10 Gb/s Operation', August, | |||
2002. | 2002. | |||
Of particular interest is Clause 30, '10Mb/s, | Of particular interest is Clause 30, '10Mb/s, | |||
100Mb/s, 1000Mb/s and 10 Gb/s Management'. | 100Mb/s, 1000Mb/s and 10 Gb/s Management'. | |||
Copyright (C) The Internet Society (2004). This | Copyright (C) The Internet Society (2006). This | |||
version of this MIB module is part of RFC XXXX; | version of this MIB module is part of RFC XXXX; | |||
see the RFC itself for full legal notices." | see the RFC itself for full legal notices." | |||
REVISION "200510240000Z" -- Oct 24, 2005 | REVISION "200606070000Z" -- June 07, 2006 | |||
DESCRIPTION "Updated to reference IANA maintaned textual | DESCRIPTION "Updated to reference IANA maintaned textual | |||
conventions for MAU types and jack types, | conventions for MAU types and jack types, | |||
instead of using internally defined values. | instead of using internally defined values. | |||
This version is published as RFC XXXX." | This version is published as RFC XXXX." | |||
-- EdNote: Replace XXXX with the actual RFC number | -- EdNote: Replace XXXX with the actual RFC number | |||
-- & remove this note. | -- & remove this note. | |||
REVISION "200309190000Z" -- September 19, 2003 | REVISION "200309190000Z" -- September 19, 2003 | |||
DESCRIPTION "Updated to include support for 10 Gb/s MAUs. | DESCRIPTION "Updated to include support for 10 Gb/s MAUs. | |||
skipping to change at page 13, line 38 | skipping to change at page 14, line 13 | |||
} | } | |||
::= { rpMauTable 1 } | ::= { rpMauTable 1 } | |||
RpMauEntry ::= | RpMauEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
rpMauGroupIndex Integer32, | rpMauGroupIndex Integer32, | |||
rpMauPortIndex Integer32, | rpMauPortIndex Integer32, | |||
rpMauIndex Integer32, | rpMauIndex Integer32, | |||
rpMauType AutonomousType, | rpMauType AutonomousType, | |||
rpMauStatus INTEGER, | rpMauStatus INTEGER, | |||
rpMauMediaAvailable INTEGER, | rpMauMediaAvailable IANAifMauMediaAvailable, | |||
rpMauMediaAvailableStateExits Counter32, | rpMauMediaAvailableStateExits Counter32, | |||
rpMauJabberState INTEGER, | rpMauJabberState INTEGER, | |||
rpMauJabberingStateEnters Counter32, | rpMauJabberingStateEnters Counter32, | |||
rpMauFalseCarriers Counter32 | rpMauFalseCarriers Counter32 | |||
} | } | |||
rpMauGroupIndex OBJECT-TYPE | rpMauGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only -- read-only since originally an | MAX-ACCESS read-only -- read-only since originally an | |||
-- SMIv1 index | -- SMIv1 index | |||
skipping to change at page 16, line 21 | skipping to change at page 16, line 44 | |||
causes the MAU to assume the respective state | causes the MAU to assume the respective state | |||
except that setting a mixing-type MAU or an AUI | except that setting a mixing-type MAU or an AUI | |||
to standby(4) will cause the MAU to enter the | to standby(4) will cause the MAU to enter the | |||
shutdown state." | shutdown state." | |||
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, | REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, | |||
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | |||
acResetMAU." | acResetMAU." | |||
::= { rpMauEntry 5 } | ::= { rpMauEntry 5 } | |||
rpMauMediaAvailable OBJECT-TYPE | rpMauMediaAvailable OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX IANAifMauMediaAvailable | |||
other(1), | ||||
unknown(2), | ||||
available(3), | ||||
notAvailable(4), | ||||
remoteFault(5), | ||||
invalidSignal(6), | ||||
remoteJabber(7), | ||||
remoteLinkLoss(8), | ||||
remoteTest(9), | ||||
offline(10), | ||||
autoNegError(11) | ||||
} | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "If the MAU is a link or fiber type (FOIRL, | DESCRIPTION "This object identifies Media Available state of | |||
10BASE-T, 10BASE-F) then this is equivalent to | the MAU, complementary to the rpMauStatus. Values | |||
the link test fail state/low light function. | for the standard IEEE 802.3 Media Available states | |||
For an AUI or a coax (including broadband) MAU | are defined in the IANA maintained IANA-MAU-MIB | |||
this indicates whether or not loopback is | module, as IANAifMauMediaAvailable TC." | |||
detected on the DI circuit. The value of this | ||||
attribute persists between packets for MAU types | ||||
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. | ||||
The value other(1) is returned if the | ||||
mediaAvailable state is not one of 2 through 11. | ||||
The value unknown(2) is returned when the MAU's | ||||
true state is unknown; for example, when it is | ||||
being initialized. At power-up or following a | ||||
reset, the value of this attribute will be | ||||
unknown for AUI, coax, and 10BASE-FP MAUs. For | ||||
these MAUs loopback will be tested on each | ||||
transmission during which no collision is | ||||
detected. If DI is receiving input when DO | ||||
returns to IDL after a transmission and there | ||||
has been no collision during the transmission | ||||
then loopback will be detected. The value of | ||||
this attribute will only change during | ||||
non-collided transmissions for AUI, coax, and | ||||
10BASE-FP MAUs. | ||||
For 100Mbps and 1000Mbps MAUs, the enumerations | ||||
match the states within the respective link | ||||
integrity state diagrams, fig 32-16, 23-12 and | ||||
24-15 of sections 32, 23 and 24 of [IEEE802.3]. | ||||
Any MAU which implements management of | ||||
auto-negotiation will map remote fault | ||||
indication to remote fault. | ||||
The value available(3) indicates that the link, | ||||
light, or loopback is normal. The value | ||||
notAvailable(4) indicates link loss, low light, | ||||
or no loopback. | ||||
The value remoteFault(5) indicates that a fault | ||||
has been detected at the remote end of the link. | ||||
This value applies to 10BASE-FB, 100BASE-T4 Far | ||||
End Fault Indication and non-specified remote | ||||
faults from a system running auto-negotiation. | ||||
The values remoteJabber(7), remoteLinkLoss(8), | ||||
and remoteTest(9) SHOULD be used instead of | ||||
remoteFault(5) where the reason for remote fault | ||||
is identified in the remote signaling protocol. | ||||
The value invalidSignal(6) indicates that an | ||||
invalid signal has been received from the other | ||||
end of the link. invalidSignal(6) applies only | ||||
to MAUs of type 10BASE-FB. | ||||
Where an IEEE Std 802.3-2002 clause 22 MII | ||||
is present, a logic one in the remote fault bit | ||||
(reference section 22.2.4.2.8 of that document) | ||||
maps to the value remoteFault(5), and a logic | ||||
zero in the link status bit (reference section | ||||
22.2.4.2.10 of that document) maps to the value | ||||
notAvailable(4). The value notAvailable(4) | ||||
takes precedence over the value remoteFault(5). | ||||
Any MAU that implements management of clause 37 | ||||
Auto-Negotiation will map the received Remote | ||||
Fault (RF1 and RF2) bit values for Offline to | ||||
offline(10), Link Failure to remoteFault(5) and | ||||
Auto-Negotiation Error to autoNegError(11)." | ||||
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." | REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." | |||
::= { rpMauEntry 6 } | ::= { rpMauEntry 6 } | |||
rpMauMediaAvailableStateExits OBJECT-TYPE | rpMauMediaAvailableStateExits OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of the number of times that | DESCRIPTION "A count of the number of times that | |||
rpMauMediaAvailable for this MAU instance leaves | rpMauMediaAvailable for this MAU instance leaves | |||
the state available(3). | the state available(3). | |||
skipping to change at page 21, line 38 | skipping to change at page 20, line 32 | |||
ifMauIndex | ifMauIndex | |||
} | } | |||
::= { ifMauTable 1 } | ::= { ifMauTable 1 } | |||
IfMauEntry ::= | IfMauEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
ifMauIfIndex InterfaceIndex, | ifMauIfIndex InterfaceIndex, | |||
ifMauIndex Integer32, | ifMauIndex Integer32, | |||
ifMauType AutonomousType, | ifMauType AutonomousType, | |||
ifMauStatus INTEGER, | ifMauStatus INTEGER, | |||
ifMauMediaAvailable INTEGER, | ifMauMediaAvailable IANAifMauMediaAvailable, | |||
ifMauMediaAvailableStateExits Counter32, | ifMauMediaAvailableStateExits Counter32, | |||
ifMauJabberState INTEGER, | ifMauJabberState INTEGER, | |||
ifMauJabberingStateEnters Counter32, | ifMauJabberingStateEnters Counter32, | |||
ifMauFalseCarriers Counter32, | ifMauFalseCarriers Counter32, | |||
ifMauTypeList Integer32, | ifMauTypeList Integer32, | |||
ifMauDefaultType AutonomousType, | ifMauDefaultType AutonomousType, | |||
ifMauAutoNegSupported TruthValue, | ifMauAutoNegSupported TruthValue, | |||
ifMauTypeListBits IANAifMauTypeListBits, | ifMauTypeListBits IANAifMauTypeListBits, | |||
ifMauHCFalseCarriers Counter64 | ifMauHCFalseCarriers Counter64 | |||
} | } | |||
skipping to change at page 24, line 13 | skipping to change at page 23, line 7 | |||
causes the MAU to assume the respective state | causes the MAU to assume the respective state | |||
except that setting a mixing-type MAU or an AUI | except that setting a mixing-type MAU or an AUI | |||
to standby(4) will cause the MAU to enter the | to standby(4) will cause the MAU to enter the | |||
shutdown state." | shutdown state." | |||
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, | REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, | |||
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | |||
acResetMAU." | acResetMAU." | |||
::= { ifMauEntry 4 } | ::= { ifMauEntry 4 } | |||
ifMauMediaAvailable OBJECT-TYPE | ifMauMediaAvailable OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX IANAifMauMediaAvailable | |||
other(1), | ||||
unknown(2), | ||||
available(3), | ||||
notAvailable(4), | ||||
remoteFault(5), | ||||
invalidSignal(6), | ||||
remoteJabber(7), | ||||
remoteLinkLoss(8), | ||||
remoteTest(9), | ||||
offline(10), | ||||
autoNegError(11), | ||||
pmdLinkFault(12), | ||||
wisFrameLoss(13), | ||||
wisSignalLoss(14), | ||||
pcsLinkFault(15), | ||||
excessiveBER(16), | ||||
dxsLinkFault(17), | ||||
pxsLinkFault(18) | ||||
} | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "If the MAU is a link or fiber type (FOIRL, | DESCRIPTION "This object identifies Media Available state of | |||
10BASE-T, 10BASE-F) then this is equivalent to | the MAU, complementary to the ifMauStatus. Values | |||
the link test fail state/low light function. | for the standard IEEE 802.3 Media Available states | |||
For an AUI or a coax (including broadband) MAU | are defined in the IANA maintained IANA-MAU-MIB | |||
this indicates whether or not loopback is | module, as IANAifMauMediaAvailable TC." | |||
detected on the DI circuit. The value of this | ||||
attribute persists between packets for MAU types | ||||
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. | ||||
The value other(1) is returned if the | ||||
mediaAvailable state is not one of 2 through 18. | ||||
The value unknown(2) is returned when the MAU's | ||||
true state is unknown; for example, when it is | ||||
being initialized. At power-up or following a | ||||
reset, the value of this attribute will be | ||||
unknown for AUI, coax, and 10BASE-FP MAUs. For | ||||
these MAUs loopback will be tested on each | ||||
transmission during which no collision is | ||||
detected. If DI is receiving input when DO | ||||
returns to IDL after a transmission and there | ||||
has been no collision during the transmission | ||||
then loopback will be detected. The value of | ||||
this attribute will only change during | ||||
non-collided transmissions for AUI, coax, and | ||||
10BASE-FP MAUs. | ||||
For 100Mbps and 1000Mbps MAUs, the enumerations | ||||
match the states within the respective link | ||||
integrity state diagrams, fig 32-16, 23-12 and | ||||
24-15 of sections 32, 23 and 24 of [IEEE802.3]. | ||||
Any MAU which implements management of | ||||
auto-negotiation will map remote fault | ||||
indication to remote fault. | ||||
The value available(3) indicates that the link, | ||||
light, or loopback is normal. The value | ||||
notAvailable(4) indicates link loss, low light, | ||||
or no loopback. | ||||
The value remoteFault(5) indicates that a fault | ||||
has been detected at the remote end of the link. | ||||
This value applies to 10BASE-FB, 100BASE-T4 Far | ||||
End Fault Indication and non-specified remote | ||||
faults from a system running auto-negotiation. | ||||
The values remoteJabber(7), remoteLinkLoss(8), | ||||
and remoteTest(9) SHOULD be used instead of | ||||
remoteFault(5) where the reason for remote fault | ||||
is identified in the remote signaling protocol. | ||||
The value invalidSignal(6) indicates that an | ||||
invalid signal has been received from the other | ||||
end of the link. invalidSignal(6) applies only | ||||
to MAUs of type 10BASE-FB. | ||||
Where an IEEE Std 802.3-2002 clause 22 MII | ||||
is present, a logic one in the remote fault bit | ||||
(reference section 22.2.4.2.8 of that document) | ||||
maps to the value remoteFault(5), and a logic | ||||
zero in the link status bit (reference section | ||||
22.2.4.2.10 of that document) maps to the value | ||||
notAvailable(4). The value notAvailable(4) | ||||
takes precedence over the value remoteFault(5). | ||||
Any MAU that implements management of clause 37 | ||||
Auto-Negotiation will map the received RF1 and | ||||
RF2 bit values for Offline to offline(10), Link | ||||
Failure to remoteFault(5) and Auto-Negotiation | ||||
Error to autoNegError(11). | ||||
For 10 Gb/s, the enumerations map to the states | ||||
within the Reconciliation Sublayer state diagram | ||||
as follows: | ||||
NoFault maps to the enumeration 'available(3)' | ||||
LocalFault maps to the enumeration | ||||
'notAvailable(4)' | ||||
RemoteFault maps to the enumeration | ||||
'remoteFault(5)' | ||||
The enumerations 'pmdLinkFault(12)', | ||||
'wisFrameLoss(13)', 'wisSignalLoss(14)', | ||||
'pcsLinkFault(15)', 'excessiveBER(16)', and | ||||
'dxsLinkFault(17)' and 'pxsLinkFault(18)' should | ||||
be used instead of the enumeration | ||||
'notAvailable(4)' where the reason for the local | ||||
fault can be identified through the use of the | ||||
MDIO Interface. Where multiple reasons for the | ||||
local fault state can be identified only the | ||||
highest precedence error should be reported. | ||||
The precedence in descending order is as | ||||
follows: | ||||
pxsLinkFault | ||||
pmdLinkFault | ||||
wisFrameLoss | ||||
wisSignalLoss | ||||
pcsLinkFault | ||||
excessiveBER | ||||
dxsLinkFault" | ||||
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." | REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." | |||
::= { ifMauEntry 5 } | ::= { ifMauEntry 5 } | |||
ifMauMediaAvailableStateExits OBJECT-TYPE | ifMauMediaAvailableStateExits OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of the number of times that | DESCRIPTION "A count of the number of times that | |||
ifMauMediaAvailable for this MAU instance leaves | ifMauMediaAvailable for this MAU instance leaves | |||
the state available(3). | the state available(3). | |||
skipping to change at page 33, line 25 | skipping to change at page 29, line 51 | |||
IfMauAutoNegEntry ::= | IfMauAutoNegEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
ifMauAutoNegAdminStatus INTEGER, | ifMauAutoNegAdminStatus INTEGER, | |||
ifMauAutoNegRemoteSignaling INTEGER, | ifMauAutoNegRemoteSignaling INTEGER, | |||
ifMauAutoNegConfig INTEGER, | ifMauAutoNegConfig INTEGER, | |||
ifMauAutoNegCapability Integer32, | ifMauAutoNegCapability Integer32, | |||
ifMauAutoNegCapAdvertised Integer32, | ifMauAutoNegCapAdvertised Integer32, | |||
ifMauAutoNegCapReceived Integer32, | ifMauAutoNegCapReceived Integer32, | |||
ifMauAutoNegRestart INTEGER, | ifMauAutoNegRestart INTEGER, | |||
ifMauAutoNegCapabilityBits BITS, | ifMauAutoNegCapabilityBits IANAifMauAutoNegCapBits, | |||
ifMauAutoNegCapAdvertisedBits BITS, | ifMauAutoNegCapAdvertisedBits IANAifMauAutoNegCapBits, | |||
ifMauAutoNegCapReceivedBits BITS, | ifMauAutoNegCapReceivedBits IANAifMauAutoNegCapBits, | |||
ifMauAutoNegRemoteFaultAdvertised INTEGER, | ifMauAutoNegRemoteFaultAdvertised INTEGER, | |||
ifMauAutoNegRemoteFaultReceived INTEGER | ifMauAutoNegRemoteFaultReceived INTEGER | |||
} | } | |||
ifMauAutoNegAdminStatus OBJECT-TYPE | ifMauAutoNegAdminStatus OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
enabled(1), | enabled(1), | |||
disabled(2) | disabled(2) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
skipping to change at page 37, line 18 | skipping to change at page 33, line 44 | |||
to begin link renegotiation. If auto-negotiation | to begin link renegotiation. If auto-negotiation | |||
signaling is disabled, a write to this object | signaling is disabled, a write to this object | |||
has no effect. | has no effect. | |||
Setting the value of this object to norestart(2) | Setting the value of this object to norestart(2) | |||
has no effect." | has no effect." | |||
REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, | REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, | |||
acAutoNegRestartAutoConfig." | acAutoNegRestartAutoConfig." | |||
::= { ifMauAutoNegEntry 8 } | ::= { ifMauAutoNegEntry 8 } | |||
ifMauAutoNegCapabilityBits OBJECT-TYPE | ifMauAutoNegCapabilityBits OBJECT-TYPE | |||
SYNTAX BITS { | SYNTAX IANAifMauAutoNegCapBits | |||
bOther(0), -- other or unknown | ||||
b10baseT(1), -- 10BASE-T half duplex mode | ||||
b10baseTFD(2), -- 10BASE-T full duplex mode | ||||
b100baseT4(3), -- 100BASE-T4 | ||||
b100baseTX(4), -- 100BASE-TX half duplex mode | ||||
b100baseTXFD(5), -- 100BASE-TX full duplex mode | ||||
b100baseT2(6), -- 100BASE-T2 half duplex mode | ||||
b100baseT2FD(7), -- 100BASE-T2 full duplex mode | ||||
bfdxPause(8), -- PAUSE for full-duplex links | ||||
bfdxAPause(9), -- Asymmetric PAUSE for full-duplex | ||||
-- links | ||||
bfdxSPause(10), -- Symmetric PAUSE for full-duplex | ||||
-- links | ||||
bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for | ||||
-- full-duplex links | ||||
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half | ||||
-- duplex mode | ||||
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full | ||||
-- duplex mode | ||||
b1000baseT(14), -- 1000BASE-T half duplex mode | ||||
b1000baseTFD(15) -- 1000BASE-T full duplex mode | ||||
} | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A value that uniquely identifies the set of | DESCRIPTION "A value that uniquely identifies the set of | |||
capabilities of the local auto-negotiation | capabilities of the local auto-negotiation | |||
entity. Note that interfaces that support this | entity. Note that interfaces that support this | |||
MIB may have capabilities that extend beyond the | MIB may have capabilities that extend beyond the | |||
scope of this MIB. | scope of this MIB. | |||
Note that the local auto-negotiation entity may | Note that the local auto-negotiation entity may | |||
support some capabilities beyond the scope of | support some capabilities beyond the scope of | |||
this MIB. This is indicated by returning the | this MIB. This is indicated by returning the | |||
bit value bOther in addition to any bit values | bit value bOther in addition to any bit values | |||
for capabilities that are listed above." | for standard capabilities that are listed in the | |||
IANAifMauAutoNegCapBits TC." | ||||
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, | REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, | |||
aAutoNegLocalTechnologyAbility." | aAutoNegLocalTechnologyAbility." | |||
::= { ifMauAutoNegEntry 9 } | ::= { ifMauAutoNegEntry 9 } | |||
ifMauAutoNegCapAdvertisedBits OBJECT-TYPE | ifMauAutoNegCapAdvertisedBits OBJECT-TYPE | |||
SYNTAX IANAifMauAutoNegCapBits | ||||
SYNTAX BITS { | ||||
bOther(0), -- other or unknown | ||||
b10baseT(1), -- 10BASE-T half duplex mode | ||||
b10baseTFD(2), -- 10BASE-T full duplex mode | ||||
b100baseT4(3), -- 100BASE-T4 | ||||
b100baseTX(4), -- 100BASE-TX half duplex mode | ||||
b100baseTXFD(5), -- 100BASE-TX full duplex mode | ||||
b100baseT2(6), -- 100BASE-T2 half duplex mode | ||||
b100baseT2FD(7), -- 100BASE-T2 full duplex mode | ||||
bFdxPause(8), -- PAUSE for full-duplex links | ||||
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxSPause(10), -- Symmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for | ||||
-- full-duplex links | ||||
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half | ||||
-- duplex mode | ||||
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full | ||||
-- duplex mode | ||||
b1000baseT(14), -- 1000BASE-T half duplex mode | ||||
b1000baseTFD(15) -- 1000BASE-T full duplex mode | ||||
} | ||||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION "A value that uniquely identifies the set of | DESCRIPTION "A value that uniquely identifies the set of | |||
capabilities advertised by the local | capabilities advertised by the local | |||
auto-negotiation entity. | auto-negotiation entity. | |||
Capabilities in this object that are not | Capabilities in this object that are not | |||
available in ifMauAutoNegCapabilityBits cannot | available in ifMauAutoNegCapabilityBits cannot | |||
be enabled. | be enabled. | |||
Note that the local auto-negotiation entity may | Note that the local auto-negotiation entity may | |||
advertise some capabilities beyond the scope of | advertise some capabilities beyond the scope of | |||
this MIB. This is indicated by returning the | this MIB. This is indicated by returning the | |||
bit value bOther in addition to any bit values | bit value bOther in addition to any bit values | |||
for capabilities that are listed above." | for standard capabilities that are listed in the | |||
IANAifMauAutoNegCapBits TC." | ||||
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, | REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, | |||
aAutoNegAdvertisedTechnologyAbility." | aAutoNegAdvertisedTechnologyAbility." | |||
::= { ifMauAutoNegEntry 10 } | ::= { ifMauAutoNegEntry 10 } | |||
ifMauAutoNegCapReceivedBits OBJECT-TYPE | ifMauAutoNegCapReceivedBits OBJECT-TYPE | |||
SYNTAX BITS { | SYNTAX IANAifMauAutoNegCapBits | |||
bOther(0), -- other or unknown | ||||
b10baseT(1), -- 10BASE-T half duplex mode | ||||
b10baseTFD(2), -- 10BASE-T full duplex mode | ||||
b100baseT4(3), -- 100BASE-T4 | ||||
b100baseTX(4), -- 100BASE-TX half duplex mode | ||||
b100baseTXFD(5), -- 100BASE-TX full duplex mode | ||||
b100baseT2(6), -- 100BASE-T2 half duplex mode | ||||
b100baseT2FD(7), -- 100BASE-T2 full duplex mode | ||||
bFdxPause(8), -- PAUSE for full-duplex links | ||||
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxSPause(10), -- Symmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for | ||||
-- full-duplex links | ||||
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half | ||||
-- duplex mode | ||||
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full | ||||
-- duplex mode | ||||
b1000baseT(14), -- 1000BASE-T half duplex mode | ||||
b1000baseTFD(15) -- 1000BASE-T full duplex mode | ||||
} | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A value that uniquely identifies the set of | DESCRIPTION "A value that uniquely identifies the set of | |||
capabilities received from the remote | capabilities received from the remote | |||
auto-negotiation entity. | auto-negotiation entity. | |||
Note that interfaces that support this MIB may | Note that interfaces that support this MIB may | |||
be attached to remote auto-negotiation entities | be attached to remote auto-negotiation entities | |||
which have capabilities beyond the scope of this | which have capabilities beyond the scope of this | |||
MIB. This is indicated by returning the bit | MIB. This is indicated by returning the bit | |||
value bOther in addition to any bit values for | value bOther in addition to any bit values for | |||
capabilities that are listed above." | for standard capabilities that are listed in the | |||
IANAifMauAutoNegCapBits TC." | ||||
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, | REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, | |||
aAutoNegReceivedTechnologyAbility." | aAutoNegReceivedTechnologyAbility." | |||
::= { ifMauAutoNegEntry 11 } | ::= { ifMauAutoNegEntry 11 } | |||
ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE | ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
noError(1), | noError(1), | |||
offline(2), | offline(2), | |||
linkFailure(3), | linkFailure(3), | |||
autoNegError(4) | autoNegError(4) | |||
skipping to change at page 51, line 36 | skipping to change at page 47, line 4 | |||
5. IANA-maintained MAU TC Definitions | 5. IANA-maintained MAU TC Definitions | |||
IANA-MAU-MIB DEFINITIONS ::= BEGIN | IANA-MAU-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 | MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 | |||
FROM SNMPv2-SMI | FROM SNMPv2-SMI | |||
TEXTUAL-CONVENTION | TEXTUAL-CONVENTION | |||
FROM SNMPv2-TC | FROM SNMPv2-TC | |||
; | ; | |||
ianaMauMIB MODULE-IDENTITY | ianaMauMIB MODULE-IDENTITY | |||
LAST-UPDATED "200510240000Z" -- Oct 24, 2005 | LAST-UPDATED "200606070000Z" -- Jun 07, 2006 | |||
ORGANIZATION "IANA" | ORGANIZATION "IANA" | |||
CONTACT-INFO " Internet Assigned Numbers Authority | CONTACT-INFO " Internet Assigned Numbers Authority | |||
Postal: ICANN | Postal: ICANN | |||
4676 Admiralty Way, Suite 330 | 4676 Admiralty Way, Suite 330 | |||
Marina del Rey, CA 90292 | Marina del Rey, CA 90292 | |||
Tel: +1 310 823 9358 | Tel: +1 310 823 9358 | |||
E-Mail: iana@iana.org" | E-Mail: iana@iana.org" | |||
DESCRIPTION | DESCRIPTION | |||
"This MIB module defines dot3MauType OBJECT-IDENTITIES and | "This MIB module defines dot3MauType OBJECT-IDENTITIES and | |||
IANAifMauListBits and IANAifJackType Textual Conventions, | IANAifMauListBits, IANAifMauMediaAvailable, | |||
specifying enumerated values of the ifMauTypeListBits and | IANAifMauAutoNegCapBits and IANAifJackType Textual Conventions, | |||
ifJackType objects respectively, defined in the MAU-MIB. | specifying enumerated values of the ifMauTypeListBits, | |||
ifMauMediaAvailable / rpMauMediaAvailable, | ||||
ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits / | ||||
ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects | ||||
respectively, defined in the MAU-MIB. | ||||
It is intended that each new MAU type and/or Jack type defined | It is intended that each new MAU type, Media Availability | |||
by the IEEE 802.3 working group and approved for publication | state, Auto Negotiation capability and/or Jack type defined by | |||
in a revision of IEEE Std 802.3 will be added to this MIB | the IEEE 802.3 working group and approved for publication in a | |||
module, provided that it is suitable for being managed by the | revision of IEEE Std 802.3 will be added to this MIB module, | |||
base objects in the MAU-MIB. An Expert Review, as defined in | provided that it is suitable for being managed by the base | |||
objects in the MAU-MIB. An Expert Review, as defined in | ||||
RFC 2434 [RFC2434], is REQUIRED for such additions. | RFC 2434 [RFC2434], is REQUIRED for such additions. | |||
The following reference is used throughout this MIB module: | The following reference is used throughout this MIB module: | |||
[IEEE 802.3 Std] refers to: | [IEEE 802.3 Std] refers to: | |||
IEEE Std 802.3, 2002 Edition: 'IEEE Standard for | IEEE Std 802.3, 2002 Edition: 'IEEE Standard for | |||
Information technology - Telecommunications and information | Information technology - Telecommunications and information | |||
exchange between systems - Local and metropolitan area | exchange between systems - Local and metropolitan area | |||
networks - Specific requirements - | networks - Specific requirements - | |||
Part 3: Carrier sense multiple access with collision | Part 3: Carrier sense multiple access with collision | |||
skipping to change at page 52, line 43 | skipping to change at page 48, line 12 | |||
Physical Layer, and Management Parameters for 10 Gb/s | Physical Layer, and Management Parameters for 10 Gb/s | |||
Operation, Type 10GBASE-CX4', March 2004; | Operation, Type 10GBASE-CX4', March 2004; | |||
IEEE Std 802.3ah-2004: | IEEE Std 802.3ah-2004: | |||
'Amendment: Media Access Control Parameters, Physical | 'Amendment: Media Access Control Parameters, Physical | |||
Layers and Management Parameters for Subscriber Access | Layers and Management Parameters for Subscriber Access | |||
Networks', September 2004;. | Networks', September 2004;. | |||
This reference should be updated as appropriate when new | This reference should be updated as appropriate when new | |||
MAU types and/or Jack types are added to this MIB module. | MAU types and/or Jack types are added to this MIB module. | |||
Copyright (C) The Internet Society (2005). | Copyright (C) The Internet Society (2006). | |||
The initial version of this MIB module was published in | The initial version of this MIB module was published in | |||
RFC XXXX; for full legal notices see the RFC itself. | RFC XXXX; for full legal notices see the RFC itself. | |||
Supplementary information may be available at: | Supplementary information may be available at: | |||
http://www.ietf.org/copyrights/ianamib.html" | http://www.ietf.org/copyrights/ianamib.html" | |||
REVISION "200510240000Z" -- Oct 24, 2005 | REVISION "200606070000Z" -- Jun 07, 2006 | |||
DESCRIPTION "Initial version of this MIB as published in | DESCRIPTION "Initial version of this MIB as published in | |||
RFC XXX." | RFC XXX." | |||
-- EdNote: Replace XXXX with the actual RFC number & remove this note | -- EdNote: Replace XXXX with the actual RFC number & remove this note | |||
::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1 | ::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1 | |||
-- Textual Conventions | -- Textual Conventions | |||
IANAifMauTypeListBits ::= TEXTUAL-CONVENTION | IANAifMauTypeListBits ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 54, line 38 | skipping to change at page 50, line 7 | |||
b100BaseLX10(46), -- 100BASE-LX10 | b100BaseLX10(46), -- 100BASE-LX10 | |||
b1000BaseBX10D(47), -- 1000BASE-BX10D | b1000BaseBX10D(47), -- 1000BASE-BX10D | |||
b1000BaseBX10U(48), -- 1000BASE-BX10U | b1000BaseBX10U(48), -- 1000BASE-BX10U | |||
b1000BaseLX10(49), -- 1000BASE-LX10 | b1000BaseLX10(49), -- 1000BASE-LX10 | |||
b1000BasePX10D(50), -- 1000BASE-PX10D | b1000BasePX10D(50), -- 1000BASE-PX10D | |||
b1000BasePX10U(51), -- 1000BASE-PX10U | b1000BasePX10U(51), -- 1000BASE-PX10U | |||
b1000BasePX20D(52), -- 1000BASE-PX20D | b1000BasePX20D(52), -- 1000BASE-PX20D | |||
b1000BasePX20U(53) -- 1000BASE-PX20U | b1000BasePX20U(53) -- 1000BASE-PX20U | |||
} | } | |||
IANAifMauMediaAvailable ::= TEXTUAL-CONVENTION | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This data type is used as the syntax of the | ||||
ifMauMediaAvailable and rpMauMediaAvailable objects in the | ||||
(updated) definition of MAU-MIB's ifMauTable and rpMauTable | ||||
respectively. | ||||
Possible values are: | ||||
other(1) - undefined (not listed below) | ||||
unknown(2) - MAU's true state is unknown; e.g. | ||||
during initialization | ||||
available(3) - link, light, or loopback is normal | ||||
notAvailable(4) - link loss, low light, or no loopback | ||||
remoteFault(5) - a fault has been detected at the | ||||
remote end of the link. This value | ||||
applies to 10BASE-FB, 100BASE-T4 Far | ||||
End Fault Indication and non-specified | ||||
remote faults from a system running | ||||
auto-negotiation | ||||
invalidSignal(6) - invalid signal has been received from | ||||
the other end of the link, 10BASE-FB | ||||
only | ||||
remoteJabber(7) - remote fault, due to jabber | ||||
remoteLinkLoss(8) - remote fault, due to link loss | ||||
remoteTest(9) - remote fault, due to test | ||||
offline(10) - offline, Clause 37 Auto-Negotiation | ||||
only | ||||
autoNegError(11) - Auto-Negotiation Error, Clause 37 | ||||
Auto-Negotiation only | ||||
pmdLinkFault(12) - PMA/PMD receive link fault. In case of | ||||
PAF, all PMA/PMDs in the aggregation | ||||
group have detected a link fault | ||||
wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only | ||||
wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only | ||||
pcsLinkFault(15) - PCS receive link fault | ||||
excessiveBER(16) - PCS Bit Error Ratio monitor | ||||
reporting excessive error ratio | ||||
dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only | ||||
pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only | ||||
availableReduced(19) - link normal, reduced bandwidth, | ||||
2BASE-TL / 10PASS-TS only | ||||
ready(20) - at least one PME available, | ||||
2BASE-TL / 10PASS-TS only | ||||
If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T, | ||||
10BASE-F), then this is equivalent to the link test fail | ||||
state/low light function. For an AUI, 10BASE2, 10BASE5, or | ||||
10BROAD36 MAU, this indicates whether or not loopback is | ||||
detected on the DI circuit. The value of this attribute | ||||
persists between packets for MAU types AUI, 10BASE5, 10BASE2, | ||||
10BROAD36, and 10BASEFP. | ||||
At power-up or following a reset, the Media Available state | ||||
will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and | ||||
10BASE-FP MAUs. For these MAUs loopback will be tested on each | ||||
transmission during which no collision is detected. | ||||
If DI is receiving input when DO returns to IDL after a | ||||
transmission and there has been no collision during the | ||||
transmission, then loopback will be detected. The Media | ||||
Available state will only change during noncollided | ||||
transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and | ||||
10BASE-FP MAUs. | ||||
For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX, | ||||
100BASE-LX10 and 100BASE-BX10 PHYs the enumerations match the | ||||
states within the link integrity state diagram. Any MAU that | ||||
implements management of Clause 28 Auto-Negotiation will map | ||||
remote fault indication to remoteFault(5). | ||||
Any MAU that implements management of Clause 37 | ||||
Auto-Negotiation will map the received RF1 and RF2 bits as | ||||
follows: Offline maps to offline(10), Link_Failure maps to | ||||
remoteFault(5) and Auto-Negotiation Error maps to | ||||
autoNegError(11). | ||||
The value remoteFault(5) applies to 10BASE-FB remote | ||||
fault indication, the 100BASE-X far-end fault indication and | ||||
nonspecified remote faults from a system running Clause 28 | ||||
Auto-Negotiation. | ||||
The value remoteJabber(7), remoteLink loss(8), or remoteTest(9) | ||||
SHOULD be used instead of remoteFault() where the reason for | ||||
remote fault is identified in the remote signaling protocol. | ||||
Where a Clause 22 MII or Clause 35 GMII is present, a logic | ||||
one in the remote fault bit maps to the value remoteFault(5), | ||||
a logic zero in the link status bit maps to the enumeration | ||||
notAvailable(4). The value notAvailable(4) takes precedence | ||||
over remoteFault(5). | ||||
For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to | ||||
the condition where the PHY is initializing, the value | ||||
ready(20) maps to the condition where at least one PME is | ||||
available and is ready for handshake, the value available(3) | ||||
maps to the condition where, at the PCS, at least one PME is | ||||
operationally linked, the value notAvailable(4) maps to the | ||||
condition where the PCS is not operationally linked, the value | ||||
availableReduced(19) maps to the condition where a link fault | ||||
is detected at the receive direction by one or more PMEs in the | ||||
aggregation group and the enumeration pmdLinkFault(12) maps to | ||||
the condition where a link fault is detected at the receive | ||||
direction by all of the PMA/PMDs in the aggregation group. | ||||
For 10 Gb/s the enumerations map to value of the link_fault | ||||
variable within the Link Fault Signaling state diagram | ||||
as follows: the value OK maps to the value available(3), | ||||
the value Local Fault maps to the value notAvailable(4) | ||||
and the value Remote Fault maps to the value remoteFault(). | ||||
The value pmdLinkFault(12), wisFrameLoss(13), | ||||
wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16) or | ||||
dxsLinkFault(17) SHOULD be used instead of the value | ||||
notAvailable(4) where the reason for the Local Fault state can | ||||
be identified through the use of the Clause 45 MDIO Interface. | ||||
Where multiple reasons for the Local Fault state can be | ||||
identified only the highest precedence error SHOULD be | ||||
reported. This precedence in descending order is as follows: | ||||
pxsLinkFault | ||||
pmdLinkFault | ||||
wisFrameLoss | ||||
wisSignalLoss | ||||
pcsLinkFault | ||||
excessiveBER | ||||
dxsLinkFault. | ||||
Where a Clause 45 MDIO interface is present a logic zero in | ||||
the PMA/PMD Receive link status bit ([IEEE Std 802.3ah-2004] | ||||
Section 45.2.1.2.2) maps to the | ||||
value pmdLinkFault(12), a logic one in the LOF status bit | ||||
(Section 45.2.2.10.4) maps to the value wisFrameLoss(13), | ||||
a logic one in the LOS status bit (Section 45.2.2.10.5) maps | ||||
to the value wisSignalLoss, a logic zero in the PCS Receive | ||||
link status bit (Section 45.2.3.2.2) maps to the value | ||||
pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched | ||||
high BER status bit (Section 45.2.3.12.2) maps to the value | ||||
excessiveBER, a logic zero in the DTE XS receive link status | ||||
bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17) | ||||
and a logic zero in the PHY XS transmit link status bit | ||||
(Section 45.2.4.2.2) maps to the value pxsLinkFault(18). | ||||
The most recent version of this textual convention is | ||||
available in the on-line version of this MIB module | ||||
on the IANA web site. | ||||
Requests for new values should be made to IANA via email | ||||
(iana@iana.org)." | ||||
SYNTAX INTEGER { | ||||
other(1), | ||||
unknown(2), | ||||
available(3), | ||||
notAvailable(4), | ||||
remoteFault(5), | ||||
invalidSignal(6), | ||||
remoteJabber(7), | ||||
remoteLinkLoss(8), | ||||
remoteTest(9), | ||||
offline(10), | ||||
autoNegError(11), | ||||
pmdLinkFault(12), | ||||
wisFrameLoss(13), | ||||
wisSignalLoss(14), | ||||
pcsLinkFault(15), | ||||
excessiveBER(16), | ||||
dxsLinkFault(17), | ||||
pxsLinkFault(18), | ||||
availableReduced(19), | ||||
ready(20) | ||||
} | ||||
IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This data type is used as the syntax of the | ||||
ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits and | ||||
ifMauAutoNegCapReceivedBits objects in the (updated) definition | ||||
of MAU-MIB's ifMauAutoNegTable. | ||||
The most recent version of this textual convention is | ||||
available in the on-line version of this MIB module | ||||
on the IANA web site. | ||||
Requests for new values should be made to IANA via email | ||||
(iana@iana.org)." | ||||
SYNTAX BITS { | ||||
bOther(0), -- other or unknown | ||||
b10baseT(1), -- 10BASE-T half duplex mode | ||||
b10baseTFD(2), -- 10BASE-T full duplex mode | ||||
b100baseT4(3), -- 100BASE-T4 | ||||
b100baseTX(4), -- 100BASE-TX half duplex mode | ||||
b100baseTXFD(5), -- 100BASE-TX full duplex mode | ||||
b100baseT2(6), -- 100BASE-T2 half duplex mode | ||||
b100baseT2FD(7), -- 100BASE-T2 full duplex mode | ||||
bFdxPause(8), -- PAUSE for full-duplex links | ||||
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxSPause(10), -- Symmetric PAUSE for full-duplex | ||||
-- links | ||||
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for | ||||
-- full-duplex links | ||||
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half | ||||
-- duplex mode | ||||
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full | ||||
-- duplex mode | ||||
b1000baseT(14), -- 1000BASE-T half duplex mode | ||||
b1000baseTFD(15) -- 1000BASE-T full duplex mode | ||||
} | ||||
IANAifJackType ::= TEXTUAL-CONVENTION | IANAifJackType ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Common enumeration values for repeater and interface MAU | "Common enumeration values for repeater and interface MAU | |||
jack types. This data type is used as the syntax of the | jack types. This data type is used as the syntax of the | |||
ifJackType and rpJackType objects in the (updated) definition | ifJackType and rpJackType objects in the (updated) definition | |||
of MAU-MIB's ifJackTable and RpJackTable respectively. | of MAU-MIB's ifJackTable and rpJackTable respectively. | |||
Possible values are: | ||||
other(1) - undefined or unknown | ||||
rj45(2) - RJ45 | ||||
rj45S(3) - RJ45 shielded | ||||
db9(4) - DB9 | ||||
bnc(5) - BNC | ||||
fAUI(6) - AUI female | ||||
mAUI(7) - AUI male | ||||
fiberSC(8) - SC fiber | ||||
fiberMIC(9) - MIC fiber | ||||
fiberST(10) - ST fiber | ||||
telco(11) - Telco | ||||
mtrj(12) - MT-RJ fiber | ||||
hssdc(13) - fiber channel style-2 | ||||
fiberLC(14) - LC fiber | ||||
cx4(15) - IB4X for 10GBASE-CX4 | ||||
The most recent version of this textual convention is | The most recent version of this textual convention is | |||
available in the on-line version of this MIB module | available in the on-line version of this MIB module | |||
on the IANA web site. | on the IANA web site. | |||
Requests for new values should be made to IANA via email | Requests for new values should be made to IANA via email | |||
(iana@iana.org)." | (iana@iana.org)." | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
rj45(2), | rj45(2), | |||
rj45S(3), -- rj45 shielded | rj45S(3), | |||
db9(4), | db9(4), | |||
bnc(5), | bnc(5), | |||
fAUI(6), -- female aui | fAUI(6), | |||
mAUI(7), -- male aui | mAUI(7), | |||
fiberSC(8), | fiberSC(8), | |||
fiberMIC(9), | fiberMIC(9), | |||
fiberST(10), | fiberST(10), | |||
telco(11), | telco(11), | |||
mtrj(12), -- fiber MT-RJ | mtrj(12), | |||
hssdc(13), -- fiber channel style-2 | hssdc(13), | |||
fiberLC(14), | fiberLC(14), | |||
-- new since RFC 3636 | -- new since RFC 3636 | |||
cx4(15) -- IB4X for 10GBASE-CX4 | cx4(15) | |||
} | } | |||
-- OBJECT IDENTITIES for MAU types | -- OBJECT IDENTITIES for MAU types | |||
-- (see rpMauType and ifMauType of MAU-MIB for usage) | -- (see rpMauType and ifMauType of MAU-MIB for usage) | |||
-- The following definitions has been moved from RFC 3636 and | -- The following definitions has been moved from RFC 3636 and | |||
-- no longer appear in its revision. | -- no longer appear in its revision. | |||
dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 } | dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 } | |||
dot3MauTypeAUI OBJECT-IDENTITY | dot3MauTypeAUI OBJECT-IDENTITY | |||
skipping to change at page 63, line 43 | skipping to change at page 63, line 36 | |||
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | |||
enable cryptographic security. It is then a customer/operator | enable cryptographic security. It is then a customer/operator | |||
responsibility to ensure that the SNMP entity giving access to an | responsibility to ensure that the SNMP entity giving access to an | |||
instance of this MIB module is properly configured to give access to | instance of this MIB module is properly configured to give access to | |||
the objects only to those principals (users) that have legitimate | the objects only to those principals (users) that have legitimate | |||
rights to indeed GET or SET (change/create/delete) them. | rights to indeed GET or SET (change/create/delete) them. | |||
7. IANA Considerations | 7. IANA Considerations | |||
This document defines first version of the IANA-maintained MIB | This document defines first version of the IANA-maintained MIB | |||
module. It is intended that each new MAU type and/or Jack type | module. It is intended that each new MAU type, Media Available | |||
defined by the IEEE 802.3 working group and approved for publication | state, Auto Negotiation capability and/or Jack type defined by the | |||
in a revision of IEEE Std 802.3 will be added to the IANA-maintaned | IEEE 802.3 working group and approved for publication in a revision | |||
module. An Expert Review, as defined in RFC 2434 [RFC2434], is | of IEEE Std 802.3 will be added to the IANA-maintaned module. An | |||
REQUIRED. | Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED. | |||
8. Acknowledgments | 8. Acknowledgments | |||
This document was produced by the IETF Ethernet Interfaces and Hub | This document was produced by the IETF Ethernet Interfaces and Hub | |||
MIB Working Group, whose efforts were greatly advanced by the | MIB Working Group, whose efforts were greatly advanced by the | |||
contributions of the following people: | contributions of the following people: | |||
Mike Heard | Mike Heard | |||
John Flick | John Flick | |||
Dan Romascanu | Dan Romascanu | |||
This document is based on the Proposed Standard MAU MIB, RFC 3636 | This document is based on the Proposed Standard MAU MIB, RFC 3636 | |||
[RFC3636], edited by John Flick of Hewlett-Packard, and produced by | [RFC3636], edited by John Flick of Hewlett-Packard, and produced by | |||
the Ethernet Interfaces and Hub MIB Working Group. It extends that | the Ethernet Interfaces and Hub MIB Working Group. It extends that | |||
document by moving the object identities and textual conventions for | document by moving the object identities and textual conventions for | |||
MAU types into a IANA-maintained MIB module. In addition, support is | MAU types into a IANA-maintained MIB module. In addition, support is | |||
provided for the EFM and 10GBASE-CX4 MAUs as defined in [IEEE802.3ah] | provided for the EFM and 10GBASE-CX4 MAUs as defined in [IEEE802.3ah] | |||
skipping to change at page 68, line 41 | skipping to change at page 68, line 41 | |||
This document and the information contained herein are provided on an | This document and the information contained herein are provided on an | |||
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | |||
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET | OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET | |||
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, | ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, | |||
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE | INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE | |||
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | |||
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
Copyright Statement | Copyright Statement | |||
Copyright (C) The Internet Society (2005). This document is subject | Copyright (C) The Internet Society (2006). This document is subject | |||
to the rights, licenses and restrictions contained in BCP 78, and | to the rights, licenses and restrictions contained in BCP 78, and | |||
except as set forth therein, the authors retain all their rights. | except as set forth therein, the authors retain all their rights. | |||
Acknowledgment | Acknowledgment | |||
Funding for the RFC Editor function is currently provided by the | Funding for the RFC Editor function is currently provided by the | |||
Internet Society. | Internet Society. | |||
End of changes. 47 change blocks. | ||||
330 lines changed or deleted | 324 lines changed or added | |||
This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |