datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
draft-manral-mpls-rfc3811bis-04

Document type: Active Internet-Draft (mpls WG)
Document stream: IETF
Last updated: 2014-09-10 (latest revision 2014-09-05)
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: Candidate for WG Adoption
Document shepherd: Mach Chen

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Internet Engineering Task Force                                V. Manral
Internet-Draft                                     Hewlett-Packard Corp.
Obsoletes: 3811 (if approved)                                    T. Tsou
Intended status: Standards Track               Huawei Technologies (USA)
Expires: March 9, 2015                                            W. Liu
                                                     Huawei Technologies
                                                             F. Fondelli
                                                                Ericsson
                                                       September 5, 2014

    Definitions of Textual Conventions (TCs) for Multiprotocol Label
                      Switching (MPLS) Management
                    draft-manral-mpls-rfc3811bis-04

Abstract

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

   This document obsoletes RFC3811 as it addresses the need to support
   IPv6 extended TunnelID's by defining a new TC-
   MplsNewExtendedTunnelID which suggests using an IPv4(for dual stack
   network) / IPv6 (for IPv6-only network) address of the ingress or
   egress LSR for the tunnel for dual stack network or an IPv6-only
   network.  This document also fixed the confusing part of MplsLSPID.
   Changes from RFC3811 and the effect of the new TC to other related
   documents are summarized in Section 4 and 5, respectively.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

Manral, et al.            Expires March 9, 2015                 [Page 1]
Internet-Draft                 rfc3811bis                 September 2014

   This Internet-Draft will expire on March 9, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The Internet-Standard Management Framework  . . . . . . . . .   3
   3.  MPLS Textual Conventions MIB Definitions  . . . . . . . . . .   3
   4.  Changes from RFC3811  . . . . . . . . . . . . . . . . . . . .  17
   5.  Effect of the new TC  . . . . . . . . . . . . . . . . . . . .  19
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  19
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  21

[include full document text]