Browse Prior Art Database

Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs) (RFC7054)

IP.com Disclosure Number: IPCOM000232489D
Original Publication Date: 2013-Nov-01
Included in the Prior Art Database: 2013-Nov-12
Document File: 22 page(s) / 25K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Farrel: AUTHOR [+5]

Abstract

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 the 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 the forwarding engine.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

Internet Engineering Task Force (IETF)                         A. Farrel Request for Comments: 7054                              Juniper Networks Category: Informational                                          H. Endo ISSN: 2070-1721                                            Hitachi, Ltd.                                                                R. Winter                                                                      NEC                                                                 Y. Koike                                                                      NTT                                                                  M. Paul                                                         Deutsche Telekom                                                            November 2013

          Addressing Requirements and Design Considerations for    Per-Interface Maintenance Entity Group Intermediate Points (MIPs)

Abstract

   The framework for Operations, Administration and Maintenance (OAM)    within the MPLS Transport Profile (MPLS-TP) describes how the    Maintenance Entity Group Intermediate Points (MIPs) may be situated    within network nodes at 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 either incoming or 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 document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it m...