draft-ietf-mpls-tc-mib-09.txt   draft-ietf-mpls-tc-mib-10.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: February 2004 J. Cucchiara Expires: April 2004 J. Cucchiara
Artel Artel
(Editors) (Editors)
August 2003 October 2003
Definitions of Textual Conventions for Multiprotocol Label Definitions of Textual Conventions for Multiprotocol Label
Switching (MPLS) Management Switching (MPLS) Management
<draft-ietf-mpls-tc-mib-09.txt> <draft-ietf-mpls-tc-mib-10.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 4, line 46 skipping to change at page 4, line 46
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32, Integer32, transmission MODULE-IDENTITY, Unsigned32, Integer32, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
mplsTCStdMIB MODULE-IDENTITY mplsTCStdMIB MODULE-IDENTITY
LAST-UPDATED "200308061200Z" -- 6 August 2003 12:00:00 GMT LAST-UPDATED "200310201200Z" -- 20 October 2003 12:00:00 GMT
ORGANIZATION ORGANIZATION
"IETF Multiprotocol Label Switching (MPLS) Working "IETF Multiprotocol Label Switching (MPLS) Working
Group." Group."
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
tnadeau@cisco.com tnadeau@cisco.com
Joan Cucchiara Joan Cucchiara
Artel Artel
skipping to change at page 5, line 41 skipping to change at page 5, line 41
mpls@uu.net." mpls@uu.net."
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2003). This "Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
This MIB module defines Textual Conventions This MIB module defines Textual Conventions
for concepts used in Multi-Protocol Label for concepts used in Multi-Protocol Label
Switching (MPLS) networks." Switching (MPLS) networks."
REVISION "200308061200Z" -- 6 August 2003 12:00:00 GMT REVISION "200310201200Z" -- 20 October 2003 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested mplsStdMIB subId is 1, e.g. -- The requested mplsStdMIB subId is 1, e.g.
-- ::= { mplsStdMIB 1 } -- ::= { mplsStdMIB 1 }
::= { mplsStdMIB XXX } -- to be assigned by IANA ::= { mplsStdMIB XXX } -- to be assigned by IANA
mplsStdMIB OBJECT IDENTIFIER mplsStdMIB OBJECT IDENTIFIER
skipping to change at page 16, line 23 skipping to change at page 16, line 23
(RFC3291). (RFC3291).
asnumber(3) An Autonomous System (AS) number as asnumber(3) An Autonomous System (AS) number as
defined by the TeHopAddressAS defined by the TeHopAddressAS
TEXTUAL-CONVENTION. TEXTUAL-CONVENTION.
unnum(4) An unnumbered interface index as unnum(4) An unnumbered interface index as
defined by the TeHopAddressUnnum defined by the TeHopAddressUnnum
TEXTUAL-CONVETION. TEXTUAL-CONVETION.
lspid(5) An LSP ID for CR-LDP Tunnels lspid(5) An LSP ID for TE Tunnels
(RFC3212) as defined by the (RFC3212) as defined by the
MplsLSPID TEXTUAL-CONVENTION. MplsLSPID TEXTUAL-CONVENTION.
Each definition of a concrete TeHopAddressType Each definition of a concrete TeHopAddressType
value must be accompanied by a definition value must be accompanied by a definition
of a textual convention for use with that of a textual convention for use with that
TeHopAddress. TeHopAddress.
To support future extensions, the TeHopAddressType To support future extensions, the TeHopAddressType
TEXTUAL-CONVENTION SHOULD NOT be sub-typed in TEXTUAL-CONVENTION SHOULD NOT be sub-typed in
object type definitions. It MAY be sub-typed in object type definitions. It MAY be sub-typed in
compliance statements in order to require only a compliance statements in order to require only a
subset of these address types for a compliant subset of these address types for a compliant
implementation. implementation.
Implementations must ensure that TeHopAddressType Implementations must ensure that TeHopAddressType
objects and any dependent objects objects and any dependent objects
(e.g. TeHopAddress objects) are consistent. (e.g. TeHopAddress objects) are consistent.
An inconsistentValue error must be generated An inconsistentValue error must be generated
if an attempt to change a TeHopAddressType object if an attempt to change a TeHopAddressType
would, for example, lead to an undefined object would, for example, lead to an
TeHopAddress value. In particular, undefined TeHopAddress value that is
not defined herein. In particular,
TeHopAddressType/TeHopAddress pairs TeHopAddressType/TeHopAddress pairs
must be changed together if the address type must be changed together if the address
changes (e.g. from ipv6(2) to ipv4(1))." type changes (e.g. from ipv6(2) to ipv4(1))."
REFERENCE REFERENCE
"Textual Conventions for Internet Network "Textual Conventions for Internet Network
Addresses, RFC3291. Addresses, RFC3291.
Constraint-Based LSP Setup using LDP, Constraint-Based LSP Setup using LDP,
RFC3212." RFC3212."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
ipv4(1), ipv4(1),
ipv6(2), ipv6(2),
asnumber(3), asnumber(3),
unnum(4), unnum(4),
lspid(5) lspid(5)
} }
TeHopAddress ::= TEXTUAL-CONVENTION TeHopAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a generic Tunnel hop address. "Denotes a generic Tunnel hop address,
that is, the address of a node which
an LSP traverses, including the source
and destination nodes. An address may be
very concrete, for example, an IPv4 host
address (i.e., with prefix length 32);
if this IPv4 address is an interface
address, then that particular interface
must be traversed. An address may also
specify an 'abstract node', for example,
an IPv4 address with prefix length
less than 32, in which case, the LSP
can traverse any node whose address
falls in that range. An address may
also specify an Autonomous System (AS),
in which case the LSP can traverse any
node that falls within that AS.
A TeHopAddress value is always interpreted within A TeHopAddress value is always interpreted within
the context of an TeHopAddressType value. Every the context of an TeHopAddressType value. Every
usage of the TeHopAddress TEXTUAL-CONVENTION usage of the TeHopAddress TEXTUAL-CONVENTION
is required to specify the TeHopAddressType object is required to specify the TeHopAddressType object
which provides the context. It is suggested that which provides the context. It is suggested that
the TeHopAddressType object is logically registered the TeHopAddressType object is logically registered
before the object(s) which use the TeHopAddress before the object(s) which use the TeHopAddress
TEXTUAL-CONVENTION if they appear in the TEXTUAL-CONVENTION if they appear in the
same logical row. same logical row.
 End of changes. 

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