Internet DRAFT - draft-chen-mpls-tp-nm-discovery-req
draft-chen-mpls-tp-nm-discovery-req
MPLS Working Group Q.G. Chen
Internet-Draft J. Yang
Intended status: Informational ZTE Corporation
Expires: April 22, 2010 October 19, 2009
Multiprotocol Label Switching Transport NM Auto discovery requirement
draft-chen-mpls-tp-nm-discovery-req-00
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 22, 2010.
Copyright Notice
Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
Layer network topology display on NMS (Network Management System),
and can refresh quickly on any change happen on managed network, this
function is very useful and important in current and future TMN
Q.G. Chen & Yang Expires April 22, 2010 [Page 1]
Internet-Draft MPLS-TP NM Auto discovery requirement October 2009
(Telecom Management Network). It implies equipment should provide
some mechanism to support, such as auto discovery. These also apply
to TMN of MPLS-TP network.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . . 3
3. Information for LSP layer to be discovered . . . . . . . . . . 3
4. Information for PW layer to be discovered . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Q.G. Chen & Yang Expires April 22, 2010 [Page 2]
Internet-Draft MPLS-TP NM Auto discovery requirement October 2009
1. Introduction
Layer network topology display on NMS, and can refresh quickly on any
change happen on managed network, this function is very useful and
important in current and future TMN. It implies equipment should
provide some mechanism to support, such as auto discovery. These
also apply to TMN of MPLS-TP network. Assuming server layer is exist
and in working status. From NMS point of view, the following MPLS-TP
specific information are expected to retrieve from network element.
And any change on these information, are expected to report to NMS
immediately, in spite of whether control plane is exist or not. .
2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Information for LSP layer to be discovered
From NMS point of view, the following MPLS-TP specific information
are expected to retrieve from network element.
- Local NE identifier
- Local NE address
- Local node(LSR) identifier
- Local node(LSR) address
- Corresponding sever layer connection point identifier
- Adjacent NE identifier
- Adjacnet NE address
- Adjacent node(LSR) ID
- Adjacent node(LSR) address
Q.G. Chen & Yang Expires April 22, 2010 [Page 3]
Internet-Draft MPLS-TP NM Auto discovery requirement October 2009
- Adjacent corresponding sever layer connection point identifier
If connection is exist the following information on per-connection
are also needed:
- LSP identifiers
- Local LSR identifier
- Adjacent LSR identifier
- Label
If protection is involve, the following information on per-
protection-group are also needed:
- Protection group identifier
- Working LSP identifier
- Protecting LSP identifier
- Adjacent LSR identifiers in protection group
- Protection type
- Current protection status
4. Information for PW layer to be discovered
From NMS point of view, the following MPLS-TP specific information
are expected to retrieve from network element.
- Local NE identifier
- Local NE address
- Local node(PE) ID
- Local node(PE) address
- Corresponding sever layer connection point identifier
- Adjacent NE identifier
Q.G. Chen & Yang Expires April 22, 2010 [Page 4]
Internet-Draft MPLS-TP NM Auto discovery requirement October 2009
- Adjacnet NE address
- Adjacent node(PE) ID
- Adjacent node(PE) address
- Adjacent corresponding sever layer connection point identifier
If connection is exist the following information are also needed:
- PW identifiers
- Local node(PE) identifier
- Adjacent node(PE) identifier
5. Security Considerations
TBD.
6. IANA Considerations
TBD.
7. Acknowledgments
TBD.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4090] Pan, P., Swallow, G., and A. Atlas, "Fast Reroute
Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
May 2005.
8.2. Informative References
[ITUT-G.7714]
ITU-T, "ITU-T Recommendation G.7714 Generalized Automatic
Q.G. Chen & Yang Expires April 22, 2010 [Page 5]
Internet-Draft MPLS-TP NM Auto discovery requirement October 2009
Discovery Techniques", Dec 2008.
Authors' Addresses
Qiaogang chen
ZTE Corporation
3F,R&D Building 3,ZTE Industrial Park,XiLi LiuXian Road
Nanshan District,Shenzhen 518055
P.R.China
Phone: +86 755 26773840
Email: chen.qiaogang@zte.com.cn
Jian Yang
ZTE Corporation
5F,R&D Building 3, ZTE Industrial Park, XiLi LiuXian Road
Nanshan District,Shenzhen 518055
P.R.China
Phone: +86 755 26773731
Email: yang_jian@zte.com.cn
Q.G. Chen & Yang Expires April 22, 2010 [Page 6]
