draft-ietf-mpls-oam-requirements-05.txt   draft-ietf-mpls-oam-requirements-06.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Monique Morrow Internet Draft Monique Morrow
Expires: May 2005 George Swallow Expires: July 2005 George Swallow
Cisco Systems, Inc. Cisco Systems, Inc.
David Allan David Allan
Nortel Networks Nortel Networks
Satoru Matsushima Satoru Matsushima
Japan Telecom Japan Telecom
December 2004 January 2006
OAM Requirements for MPLS Networks OAM Requirements for MPLS Networks
draft-ietf-mpls-oam-requirements-05.txt draft-ietf-mpls-oam-requirements-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, we certify that any applicable By submitting this Internet-Draft, each author represents that
patent or other IPR claims of which we are aware have been disclosed, any applicable patent or other IPR claims of which he or she is
or will be disclosed, and any of which we become aware will be aware have been or will be disclosed, and any of which he or she
disclosed, in accordance with RFC 3668. becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
This document is an Internet-Draft and is subject to all
provisions of section 3 of RFC 3667. By submitting this
Internet-Draft, each author represents that any applicable patent
or other IPR claims of which he or she is aware have been or will
be disclosed, and any of which he or she become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as groups may also distribute working documents as Internet-Drafts.
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use time. It is inappropriate to use Internet-Drafts as reference
Internet-Drafts as reference material or to cite them other than material or to cite them other than as "work in progress."
as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
As transport of diverse traffic types such as voice, frame As transport of diverse traffic types such as voice, frame
relay, and ATM over MPLS become more common, the ability to detect, relay, and ATM over MPLS become more common, the ability to detect,
handle and diagnose control and data plane defects becomes handle and diagnose control and data plane defects becomes
critical. critical.
skipping to change at page 2, line 28 skipping to change at page 2, line 22
MPLS networks, similarly some of these MPLS networks, similarly some of these
requirements have appeared in other documents. This draft specifies requirements have appeared in other documents. This draft specifies
Operations and Management requirements for Multi-Protocol Label Operations and Management requirements for Multi-Protocol Label
Switching, as well as for applications of Multi-Protocol Label Switching, as well as for applications of Multi-Protocol Label
Switching such as pseudowire voice and virtual private network Switching such as pseudowire voice and virtual private network
services. Those interested in specific issues relating to services. Those interested in specific issues relating to
instrumenting MPLS for Operations instrumenting MPLS for Operations
and Management purposes are directed to the Multi-Protocol Label and Management purposes are directed to the Multi-Protocol Label
Switching Architecture specification. Switching Architecture specification.
Abstract......................................................1
1 Introduction..................................................2
2 Document Conventions..........................................2
2.1 Terminology..................................................2
2.2 Acronyms.....................................................2
3. Motivations..................................................2
4. Requirements..................................................2
5 Security Considerations......................................26
6 IANA considerations..........................................27
7 References..................................................27
7.1 Normative references........................................27
7.2 Informative references......................................29
8 Author's Addresses..........................................29
9 Intellectual Property Notice................................30
10 Full Copyright Statement...................................29
1. Introduction 1. Introduction
This document describes requirements for user and data This document describes requirements for user and data
plane operations and management (OAM) for Multi-Protocol plane operations and management (OAM) for Multi-Protocol
Label Switching (MPLS). These requirements have been gathered Label Switching (MPLS). These requirements have been gathered
from network operators who have extensive experience deploying from network operators who have extensive experience deploying
MPLS networks. This draft specifies OAM requirements MPLS networks. This draft specifies OAM requirements
for MPLS, as well as for applications of MPLS. for MPLS, as well as for applications of MPLS.
No specific mechanisms are proposed to address these No specific mechanisms are proposed to address these
skipping to change at page 13, line 39 skipping to change at page 14, line 25
Voice: 1-613-763-6362 Voice: 1-613-763-6362
Email: dallan@nortelnetworks.com Email: dallan@nortelnetworks.com
Satoru Matsushima Satoru Matsushima
Japan Telecom Japan Telecom
4-7-1, Hatchobori, Chuo-ku 4-7-1, Hatchobori, Chuo-ku
Tokyo, 104-8508 Japan Tokyo, 104-8508 Japan
Phone: +81-3-5540-8214 Phone: +81-3-5540-8214
Email: satoru@ft.solteria.net Email: satoru@ft.solteria.net
9. Copyright Notice 9. Intellectual Property Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
10. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at ietf-
ietf-ipr@ietf.org. ipr@ietf.org.
11. Disclaimer of Validity 10. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their
rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
12. Copyright Statement 11. IANA Considerations
Copyright (C) The Internet Society (2004). This document is subject This document has no IANA actions.
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
13. Acknowledgment 12. Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
The authors wish to acknowledge and thank the following The authors wish to acknowledge and thank the following
individuals for their valuable comments to this document: individuals for their valuable comments to this document:
Adrian Smith, British Telecom; Chou Lan Pok, SBC; Mr. Adrian Smith, British Telecom; Chou Lan Pok, SBC; Mr.
Ikejiri, NTT Communications and Mr.Kumaki of KDDI. Ikejiri, NTT Communications and Mr.Kumaki of KDDI.
Hari Rakotoranto, Miya Khono, Cisco Systems; Luyuan Fang, AT&T; Hari Rakotoranto, Miya Khono, Cisco Systems; Luyuan Fang, AT&T;
Danny McPherson, TCB; Dr.Ken Nagami, Ikuo Nakagawa, Intec Netcore, Danny McPherson, TCB; Dr.Ken Nagami, Ikuo Nakagawa, Intec Netcore,
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/