[mpls] Document Action: 'Per-Interface MIP Addressing Requirements and Design Considerations' to Informational RFC (draft-ietf-mpls-tp-mip-mep-map-09.txt)

The IESG <iesg-secretary@ietf.org> Tue, 17 September 2013 00:30 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130917003037.15602.6841.idtracker@ietfa.amsl.com>
Date: Mon, 16 Sep 2013 17:30:37 -0700
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [mpls] Document Action: 'Per-Interface MIP Addressing Requirements and Design Considerations' to Informational RFC (draft-ietf-mpls-tp-mip-mep-map-09.txt)

The IESG has approved the following document:
- 'Per-Interface MIP Addressing Requirements and Design Considerations'
(draft-ietf-mpls-tp-mip-mep-map-09.txt) as Informational RFC

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/

Technical Summary

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.

Working Group Summary

This document has support in the working group and has been well
reviewed.

There has been a comparatively long discussion that in the end
converged on a widely accepted definition of pre-interface MIPs
and MEPs.

Document Quality

This an informational document, it discusses deployment of per-
interface MIPs and MEPs.

The document have had the review that is needed.

No need for third party expert reviews.

Personnel

Loa Andersson is the document shepherd.

Stewart Bryant is the responsible AD.

RFC Editor Note
OLD
Deployments are strongly advised to use such mechanisms.
NEW
Deployments are therefore strongly advised to follow the security advice provided in RFC6371 and RFC6941.
END

[mpls] Document Action: 'Per-Interface MIP Addres… The IESG