Per-Interface MIP Addressing Requirements and Design Considerations
draft-ietf-mpls-tp-mip-mep-map-07
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (mpls WG)
|
|
Last updated |
|
2013-06-03
(latest revision 2013-04-22)
|
|
Replaces |
|
draft-farrel-mpls-tp-mip-mep-map
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
None
|
|
Shepherd write-up |
|
Show
(last changed 2013-04-22)
|
IESG |
IESG state |
|
AD Evaluation::Revised I-D Needed
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Stewart Bryant
|
|
IESG note |
|
Assigned to Stewart as Adrian is a co-author
|
|
Send notices to |
|
mpls-chairs@tools.ietf.org, draft-ietf-mpls-tp-mip-mep-map@tools.ietf.org
|
Network Working Group A. Farrel
Internet-Draft Juniper Networks
Intended status: Informational H. Endo
Expires: October 24, 2013 Hitachi, Ltd.
R. Winter
NEC
Y. Koike
NTT
M. Paul
Deutsche Telekom
April 22, 2013
Per-Interface MIP Addressing Requirements and Design Considerations
draft-ietf-mpls-tp-mip-mep-map-07
Abstract
The Framework for Operations, Administration and Maintenance (OAM)
within the MPLS Transport Profile (MPLS-TP) describes how Maintenance
Entity Group Intermediate Points (MIPs) may be situated within
network nodes at the incoming and outgoing interfaces.
This document elaborates on important considerations for internal MIP
addressing. More precisely it describes important restrictions for
any mechanism that specifies a way of forming OAM messages so that
they can be targeted at MIPs on incoming or MIPs on outgoing
interfaces and forwarded correctly through the forwarding engine.
Furthermore, the document includes considerations for node
implementations where there is no distinction between the incoming
and outgoing MIP.
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 October 24, 2013.
Farrel, et al. Expires October 24, 2013 [Page 1]
Internet-Draft Internal MIP Considerations April 2013
Copyright Notice
Copyright (c) 2013 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Summary of the Problem Statement . . . . . . . . . . . . . . . 4
5. Requirements and Design Considerations for Internal-MIP
Adressing . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Farrel, et al. Expires October 24, 2013 [Page 2]
Internet-Draft Internal MIP Considerations April 2013
1. Introduction
The Framework for Operations, Administration and Maintenance (OAM)
within the MPLS Transport Profile (MPLS-TP)(the MPLS-TP OAM
Framework, [RFC6371]) distinguishes two configurations for
Maintenance Entity Group Intermediate Points (MIPs) on a node. It
defines per-node MIPs and per-interface MIPs, where a per-node MIP is
a single MIP per node in an unspecified location within the node and
per-interface MIPs are two (or more) MIPs per node on each side of
Show full document text