MPLS-TP Identifiers Following ITU-T Conventions
draft-ietf-mpls-tp-itu-t-identifiers-02
Network Working Group R. Winter, Ed.
Internet-Draft NEC
Intended status: Standards Track E. Gray, Ed.
Expires: May 3, 2012 Ericsson
H. van Helvoort
Huawei Technologies Co., Ltd.
M. Betts
ZTE
October 31, 2011
MPLS-TP Identifiers Following ITU-T Conventions
draft-ietf-mpls-tp-itu-t-identifiers-02
Abstract
This document specifies an extension to the identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
Identifiers that follow IP/MPLS conventions have already been
defined. This memo augments that set of identifiers for MPLS-TP
management and OAM functions to include identifier information in a
format typically used by the ITU-T.
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."
This Internet-Draft will expire on May 3, 2012.
Copyright Notice
Copyright (c) 2011 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
Winter, et al. Expires May 3, 2012 [Page 1]
Internet-Draft MPLS-TP ITU-T IDs October 2011
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Requirements notation . . . . . . . . . . . . . . . . . . . 4
2. Uniquely Identifying an Operator - the ICC_Operator_ID . . . . 4
3. Use of the ICC_Operator_ID . . . . . . . . . . . . . . . . . . 4
4. ICC_Operator_ID-based MEG Identifiers . . . . . . . . . . . . . 5
5. ICC_Operator_ID-based MEP Identifiers . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Winter, et al. Expires May 3, 2012 [Page 2]
Internet-Draft MPLS-TP ITU-T IDs October 2011
1. Introduction
This document augments the initial set of identifiers to be used in
the Transport Profile of Multiprotocol Label Switching (MPLS-TP)
specified in RFC 6370 [RFC6370].
RFC 6370 [RFC6370] defines a set of MPLS-TP transport and management
entity identifiers to support bidirectional (co-routed and
associated) point-to-point MPLS-TP LSPs, including PWs and Sections
which follow the IP/MPLS conventions.
This document specifies an alternative way to uniquely identify an
operator/service provider based on ITU-T conventions and specifies
how this operator/service provider identifier can be used to make the
existing set of MPLS-TP transport and management entity identifiers,
defined by RFC 6370 [RFC6370], globally unique.
This document solely defines those identifiers. Their use and
possible protocols extensions to carry them is out of scope in this
document.
In this document, we follow the notational convention laid out in RFC
Show full document text