[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-nadeau-ccamp-gmpls-tc-mib) 00 01 03 04 05 06 07 08 09 10 11 RFC 4801

Network Working Group                                   Thomas D. Nadeau
Internet Draft                                       Cisco Systems, Inc.
Proposed Status: Standards Track
Expires: December 2004                                 Cheenu Srinivasan
                                                          Bloomberg L.P.

                                                           Adrian Farrel
                                                      Old Dog Consulting

                                                                Tim Hall
                                                             Ed Harrison
                                                    Data Connection Ltd.

                                                               June 2004



     Definitions of Textual Conventions for Generalized Multiprotocol
                   Label Switching (GMPLS) Management

                  draft-ietf-ccamp-gmpls-tc-mib-05.txt



Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC 2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.


Abstract

   This document defines a Management Information Base (MIB) module
   which contains Textual Conventions to represent commonly used
   Generalized Multiprotocol Label Switching (GMPLS) management
   information. The intent is that these TEXTUAL CONVENTIONS (TCs) will
   be imported and used in GMPLS related MIB modules that would
   otherwise define their own representations.







Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 1]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

Table of Contents

   1. Introduction                                     2
   2. The SNMP Management Framework                    2
   3. GMPLS Textual Conventions MIB Definitions        3
   4. Security Considerations                          5
   5. IANA Considerations                              5
   6. References                                       5
   6.1. Normative References                           5
   6.2. Informational References                       6
   7. Acknowledgments                                  7
   8. Authors' Addresses                               7
   9. Intellectual Property Notice                     7
   9.1. IPR Disclosure Acknowledgement                 8
   10. Full Copyright Statement                        8

1. Introduction

   This document defines a MIB module which contains Textual Conventions
   for Generalized Multiprotocol Label Switching (GMPLS) networks.
   These Textual Conventions should be imported by MIB modules which
   manage GMPLS networks.

   This MIB module supplements the MIB module in [TCMIB] that defines
   Textual Conventions for Multiprotocol Label Switching (MPLS)
   Management. [TCMIB] may continue to be used without this MIB module
   in networks that support only MPLS.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   Comments should be made directly to the CCAMP mailing list at
   ccamp@ops.ietf.org.

   For an introduction to the concepts of GMPLS, see [GMPLSArch].

2. The SNMP Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].







Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 2]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

3. GMPLS Textual Conventions MIB Definitions

   GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN

   IMPORTS
     MODULE-IDENTITY
       FROM SNMPv2-SMI
     transmission
       FROM SNMPv2-SMI
     TEXTUAL-CONVENTION
       FROM SNMPv2-TC
   ;

   gmplsTCStdMIB MODULE-IDENTITY
     LAST-UPDATED
       "200406010900Z" -- 1 June 2004 9:00:00 GMT"
     ORGANIZATION "Common Control And Management Protocols (CCAMP)
                   Working Group"
     CONTACT-INFO
       "       Thomas D. Nadeau
               Cisco Systems, Inc.
        Email: tnadeau@cisco.com

               Cheenu Srinivasan
               Bloomberg L.P.
        Email: cheenu@bloomberg.net

               Adrian Farrel
               Old Dog Consulting
        Email: adrian@olddog.co.uk

               Ed Harrison
               Data Connection Ltd.
        Email: ed.harrison@dataconnection.com

               Tim Hall
               Data Connection Ltd.
        Email: tim.hall@dataconnection.com

        Comments about this document should be emailed direct to the
        CCAMP working group mailing list at ccamp@ops.ietf.org"
     DESCRIPTION
       "Copyright (C) The Internet Society (2004). This version of this
        MIB module is part of RFCXXX; see the RFC itself for full legal
        notices.

        This MIB module defines Textual Conventions for concepts used in
        Generalized Multiprotocol Label Switching (GMPLS) networks."

   -- Revision history.
     REVISION
       "200406010900Z" -- 1 June 2004 9:00:00 GMT"
     DESCRIPTION
       "Initial version published as part of RFC XXXX."
     -- Please see the IANA Considerations Section.
     -- The requested gmplsStdMIB subId is xx, i.e.
   ::= { gmplsStdMIB xx }

Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 3]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

   gmplsStdMIB OBJECT IDENTIFIER
     -- This object identifier needs to be assigned by IANA.
     -- Since mpls has been assigned an ifType of 166 we recommend
     -- that this OID be 166 as well, i.e.
   ::= { transmission XXX }


   -- Textual Conventions (sorted alphabetically).

   GmplsFreeformLabel ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
       "This value represents a freeform generalized MPLS Label. This
        can be used to represent label types which are not standard
        in the drafts. It may also be used by systems that do not
        wish to represent the labels using the specific label types."
     SYNTAX OCTET STRING (SIZE (0..64))

   GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
       "Determines the interpretation that should be applied to a
        label."
     SYNTAX INTEGER {
       gmplsMplsLabel(1),
       gmplsPortWavelengthLabel(2),
       gmplsFreeformGeneralizedLabel(3),
       gmplsSonetLabel(4),
       gmplsSdhLabel(5),
       gmplsWavebandLabel(6)
     }

   GmplsSegmentDirection ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
       "The direction of data flow on an LSP segment with respect to the
        head of the LSP.

        Where an LSP is signaled using a conventional 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 egress). For unidirectional LSPs, this
        usually matches the direction of flow of data.

        For manually configured unidirectional LSPs the direction of the
        LSP segment matches the direction of flow of data. For manually
        configured bidirecitonal LSPs, an arbitrary decision must be
        made about which LER is the 'head'."
     SYNTAX  INTEGER {
       forward(1),
       reverse(2)
     }

   END




Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 4]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

4. Security Considerations

   This module does not define any management objects. Instead, it
   defines a set of textual conventions which may be used by other GMPLS
   MIB modules to define management objects.

   Meaningful security considerations can only be written in the MIB
   modules that define management objects. Therefore, this document has
   no impact on the security of the Internet.

5. IANA Considerations

   IANA is requested to make a MIB OID assignment under the transmission
   branch, that is, assign the gmplsStdMIB under { transmission 166 }.

   This sub-id is requested because 166 is the ifType for mpls(166) and
   is available under transmission.

   In the future, GMPLS related standards track MIB modules should be
   rooted under the mplsStdMIB (sic) subtree. IANA is requested to
   manage that namespace. New assignments can only be made via a
   Standards Action as specified in [RFC2434].

   This document also requests IANA to assign { gmplsStdMIB xx } to the
   GMPLS-TC-STD-MIB specified in this document. The value 1 is
   suggested.

6. References

6.1. Normative References

   [RFC2119]        Bradner, S., "Key words for use in RFCs to Indicate
                    Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2578]        McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                    Case, J., Rose, M. and S. Waldbusser, "Structure of
                    Management Information Version 2 (SMIv2)", STD 58,
                    RFC 2578, April 1999.

   [RFC2579]        McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                    Case, J., Rose, M. and S. Waldbusser, "Textual
                    Conventions for SMIv2", STD 58, RFC 2579, April
                    1999.

   [RFC2580]        McCloghrie, K., Perkins, D., Schoenwaelder, J.,
                    Case, J., Rose, M. and S. Waldbusser, "Conformance
                    Statements for SMIv2", STD 58, RFC 2580, April 1999.

   [RFC3471]        Berger, L. (Editor), "Generalized Multi-Protocol
                    Label Switching (GMPLS) Signaling Functional
                    Description", RFC 3471, January 2003.







Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 5]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

6.2. Informational References

   [RFC2434]        Narten, T. and H. Alvestrand, "Guidelines for
                    Writing an IANA Considerations Section in RFCs",
                    BCP: 26, RFC 2434, October 1998.

   [RFC3031]        Rosen, E., Viswananthan, A., and R. Callon,
                    Multiprotocol Label Switching Architecture",
                    RFC 3031, January 2001.

   [RFC3209]        Awduche, D., Berger, L., Gan, D., Li, T.,
                    Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to
                    RSVP for LSP Tunnels", RFC 3209, December 2001.

   [RFC3212]        Jamoussi, B., (editor), et. al.  "Constraint-Based
                    LSP Setup using LDP", RFC 3212, January 2002.

   [RFC3410]        Case, J., Mundy, R., Partain, D. and B. Stewart,
                    "Introduction and Applicability Statements for
                    Internet-Standard Management Framework", RFC 3410,
                    December 2002.

   [RFC3472]        Ashwood-Smith, P., Berger, L. (Editors),
                    "Generalized MPLS Signaling - CR-LDP Extensions",
                    RFC 3472, January 2003.

   [RFC3473]        Berger, L. (Editor), "Generalized MPLS Signaling -
                    RSVP-TE Extensions", RFC 3473 January 2003.

   [GMPLSSonetSDH]  Mannie, E., Papadimitriou, D. (Editors),
                    "Generalized Multi-Protocol Label Switching
                    Extensions for SONET and SDH Control", Internet
                    Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
                    February 2003, work in progress.

   [GMPLSLSRMIB]    Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
                    and Harrison, E., "Generalized Multiprotocol Label
                    Switching (GMPLS) Label Switching Router (LSR)
                    Management Information Base", draft-ietf-ccamp-
                    gmpls-lsr-mib-05.txt, June 2004, work in progress.

   [GMPLSTEMIB]     Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
                    and Harrison, E., "Generalized Multiprotocol Label
                    Switching (GMPLS) Traffic Engineering Management
                    Information Base", draft-ietf-ccamp-gmpls-te-mib-
                    05.txt, June 2004, work in progress.

   [TCMIB]          Nadeau, T., Cucchiara, J. (Editors) "Definitions
                    of Textual Conventions for Multiprotocol Label
                    Switching (MPLS) Management", Internet Draft
                    <draft-ietf-mpls-tc-mib-14.txt>, November 2003,
                    work in progress.

   [GMPLSArch]      Mannie, E. (Editor), "Generalized Multiprotocol
                    Label Switching (GMPLS) Architecture", Internet
                    Draft <draft-many-gmpls-architecture-07.txt>, May
                    2003, work in progress.

Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 6]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

7. Acknowledgements

   Special thanks to Joan Cucchiara for her help with compilation
   issues.

8. Authors' Addresses

   Thomas D. Nadeau
   Cisco Systems, Inc.
   300 Apollo Drive
   Chelmsford, MA 01824
   Phone: +1-978-244-3051
   Email: tnadeau@cisco.com

   Cheenu Srinivasan
   Bloomberg L.P.
   499 Park Ave.,
   New York, NY 10022
   Phone: +1-212-893-3682
   Email: cheenu@bloomberg.net

   Adrian Farrel
   Old Dog Consulting
   Phone: +44 1978 860944
   Email: adrian@olddog.co.uk

   Tim Hall
   Data Connection Ltd.
   100 Church Street
   Enfield, Middlesex
   EN2 6BQ, UK
   Phone: +44 20 8366 1177
   Email: tim.hall@dataconnection.com

   Ed Harrison
   Data Connection Ltd.
   100 Church Street
   Enfield, Middlesex
   EN2 6BQ, UK
   Phone: +44 20 8366 1177
   Email: ed.harrison@dataconnection.com

9. Intellectual Property Considerations

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights. Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.






Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 7]


Internet Draft     draft-ietf-ccamp-gmpls-tc-mib-05.txt        June 2004

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard. Please address the information to the IETF at
   ietf-ipr@ietf.org.

9.1. IPR Disclosure Acknowledgement

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance with
   RFC 3668.

10. Full Copyright Statement

   Copyright (C) The Internet Society (2004). This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

























Nadeau, Srinivasan, Farrel, Hall and Harrison                   [Page 8]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/