draft-ietf-ccamp-gmpls-tc-mib-08.txt   draft-ietf-ccamp-gmpls-tc-mib-09.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: April 2006 Adrian Farrel, Ed. Expires: April 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
October 2005 October 2005
Definitions of Textual Conventions for Generalized Multiprotocol Definitions of Textual Conventions for Generalized Multiprotocol
Label Switching (GMPLS) Management Label Switching (GMPLS) Management
draft-ietf-ccamp-gmpls-tc-mib-08.txt draft-ietf-ccamp-gmpls-tc-mib-09.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 3, line 25 skipping to change at page 3, line 25
MODULE-IDENTITY MODULE-IDENTITY
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
; ;
gmplsTCStdMIB MODULE-IDENTITY gmplsTCStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200510130001Z" -- 13 October 2005 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
skipping to change at page 3, line 49 skipping to change at page 3, line 49
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2005). This version of "Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC XXX; see the RFC itself for
full legal notices. full legal notices.
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module defines TEXTUAL-CONVENTIONs for concepts used in This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
Generalized Multiprotocol Label Switching (GMPLS) networks." Generalized Multiprotocol Label Switching (GMPLS) networks."
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200510130001Z" -- 13 October 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC Editor: Please see the IANA Considerations Section. -- RFC Editor: Please see the IANA Considerations Section.
-- This MIB module is contained in the OID sub-tree -- This MIB module is contained in the OID sub-tree
-- rooted at mplsStdMIB. -- rooted at mplsStdMIB.
"Initial version published as part of RFC XXX." "Initial version published as part of RFC XXX."
::= { mib-2 YYY }
::= { mplsStdMIB YYY } ::= { mplsStdMIB YYY }
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note -- and remove this note
GmplsFreeformLabel ::= TEXTUAL-CONVENTION GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Textual Convention can be used as the syntax of an object "This Textual Convention can be used as the syntax of an object
that contains any GMPLS label. Objects with this syntax can be that contains any GMPLS label. Objects with this syntax can be
used to represent labels that have label types that are not used to represent labels that have label types that are not
defined in any RFCs. The freeform GMPLS Label may also be used defined in any RFCs. The freeform GMPLS Label may also be used
by systems that do not wish to represent labels that have by systems that do not wish to represent labels that have
label types defined in RFCs using type-specific syntaxes." label types defined in RFCs using type-specific syntaxes."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2." Functional Description, RFC 3471, section 3.2."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
GmplsLabelType ::= TEXTUAL-CONVENTION GmplsLabelTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Determines the interpretation that should be applied to an "Determines the interpretation that should be applied to an
object that encodes a label. The possible types are: object that encodes a label. The possible types are:
gmplsMplsLabel(1) - The label is an MPLS packet, cell, gmplsMplsLabel(1) - The label is an MPLS packet, cell,
or frame label and is encoded as or frame label and is encoded as
described for the Textual described for the Textual
Convention MplsLabel defined in Convention MplsLabel defined in
RFC 3811. RFC 3811.
skipping to change at page 5, line 27 skipping to change at page 5, line 24
Digital Hierarchy (SDH) Control, RFC 3946, section 3." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
SYNTAX INTEGER { SYNTAX INTEGER {
gmplsMplsLabel(1), gmplsMplsLabel(1),
gmplsPortWavelengthLabel(2), gmplsPortWavelengthLabel(2),
gmplsFreeformGeneralizedLabel(3), gmplsFreeformGeneralizedLabel(3),
gmplsSonetLabel(4), gmplsSonetLabel(4),
gmplsSdhLabel(5), gmplsSdhLabel(5),
gmplsWavebandLabel(6) gmplsWavebandLabel(6)
} }
GmplsSegmentDirection ::= TEXTUAL-CONVENTION GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The direction of data flow on an LSP segment with respect to the "The direction of data flow on an LSP segment with respect to the
head of the LSP. head of the LSP.
Where an LSP is signaled using a conventional signaling Where an LSP is signaled using a conventional signaling
protocol, the 'head' of the LSP is the source of the signaling protocol, the 'head' of the LSP is the source of the signaling
(also known as the ingress) and the 'tail' is the destination (also known as the ingress) and the 'tail' is the destination
(also known as the egress). For unidirectional LSPs, this (also known as the egress). For unidirectional LSPs, this
usually matches the direction of flow of data. usually matches the direction of flow of data.
 End of changes. 7 change blocks. 
7 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/