I read this draft and support the publication as an informational RFC.
I believe the document is needed since it explains why it is not
beneficial to standardize two solutions for the same purpose. The
document also makes clear some of the aspects I was not aware of.
It is obvious that two solutions would cause a lot of unnecessary effort
and costs. There are many examples which show that competing standards
are contra-productive for the goals of each party.
I fully agree with one of the statements I read on this list.
"I think it would be irresponsible of the IETF not to document this
On Behalf Of ext The IESG
Sent: Monday, September 26, 2011 9:43 PM
Subject: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>
(TheReasons for Selecting a Single Solution for MPLS-TP OAM)
The IESG has received a request from an individual submitter to
the following document:
- 'The Reasons for Selecting a Single Solution for MPLS-TP OAM'
<draft-sprecher-mpls-tp-oam-considerations-01.txt> as an
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2011-10-24. Exceptionally, comments
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
for use in transport network deployments. That is, MPLS-TP is a set
of functions and features selected from the wider MPLS toolset and
applied in a consistent way to meet the needs and requirements of
operators of packet transport networks.
During the process of development of the profile, additions to the
MPLS toolset have been made to ensure that the tools available met
the requirements. These additions were motivated by MPLS-TP, but
part of the wider MPLS toolset such that any of them could be used
any MPLS deployment.
One major set of additions provides enhanced support for
Administration, and Maintenance (OAM). This enables fault
and performance monitoring to the level needed in a transport
network. Many solutions and protocol extensions have been proposed
address these OAM requirements, and this document sets out the
reasons for selecting a single, coherent set of solutions for
The file can be obtained via
IESG discussion can be tracked via
No IPR declarations have been submitted directly on this I-D.
IETF-Announce mailing list
Ietf mailing list