idnits 2.17.1 draft-fuxh-pce-boundary-explicit-control-pcep-ext-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 36 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 1, 2010) is 5167 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3036' is defined on line 117, but no explicit reference was found in the text == Unused Reference: 'RFC5036' is defined on line 120, but no explicit reference was found in the text == Unused Reference: 'RFC4447' is defined on line 123, but no explicit reference was found in the text == Unused Reference: 'RFC5493' is defined on line 127, but no explicit reference was found in the text == Unused Reference: 'RFC5654' is defined on line 133, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ccamp-pc-spc-rsvpte-ext' is defined on line 139, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pwe3-ms-pw-arch' is defined on line 146, but no explicit reference was found in the text == Unused Reference: 'I-D.abfb-mpls-tp-control-plane-framework' is defined on line 152, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-tp-framework' is defined on line 159, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) ** Obsolete normative reference: RFC 4447 (Obsoleted by RFC 8077) ** Downref: Normative reference to an Informational RFC: RFC 5493 == Outdated reference: A later version (-12) exists of draft-ietf-mpls-tp-framework-10 Summary: 5 errors (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group X. Fu 3 Internet-Draft X. Lin 4 Intended status: Standards Track G. Xie 5 Expires: September 2, 2010 ZTE Corporation 6 March 1, 2010 8 PCEP Extension for Explicit Control of Region Boundary in PCE-Based 9 Inter-Layer Architecture 10 draft-fuxh-pce-boundary-explicit-control-pcep-ext-00 12 Abstract 14 [draft-fuxh-pce-boundary-explicit-control-framework-00] defines the 15 framework for explicit control of region boundary in PCE-based inter- 16 layer architecture. This document defines the PCEP extension for 17 region boundaries explicit control. 19 Conventions Used In This Document 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on September 2, 2010. 48 Copyright Notice 49 Copyright (c) 2010 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 2. ERBO (Explicit Region Boundary Object) . . . . . . . . . . . . 3 66 3. RSVP-TE Extension . . . . . . . . . . . . . . . . . . . . . . . 3 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 69 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 6.1. Normative References . . . . . . . . . . . . . . . . . . . 3 71 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 74 1. Introduction 76 [draft-fuxh-pce-boundary-explicit-control-framework-00] defines the 77 framework for explicit control of region boundary in PCE-based inter- 78 layer architecture. There is a requirements for PCEP extensions to 79 support explicit control of region boundary. A new object could be 80 introduced in PCEP message. 82 2. ERBO (Explicit Region Boundary Object) 84 The format of ERBO object is the same as an ERO. The ERBO including 85 the region boundaries information can be carried in PCEP message. 87 3. RSVP-TE Extension 89 The PCEP message is extended as followings: 91 ::= 92 93 ::=[] 94 ::= 95 [] 96 [] 97 [] 98 ::=[] 99 ::= [] 100 ::=[] [] [] [] ::=[] 102 4. Security Considerations 104 TBD 106 5. IANA Considerations 108 TBD 110 6. References 112 6.1. Normative References 114 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 115 Requirement Levels", BCP 14, RFC 2119, March 1997. 117 [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and 118 B. Thomas, "LDP Specification", RFC 3036, January 2001. 120 [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP 121 Specification", RFC 5036, October 2007. 123 [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. 124 Heron, "Pseudowire Setup and Maintenance Using the Label 125 Distribution Protocol (LDP)", RFC 4447, April 2006. 127 [RFC5493] Caviglia, D., Bramanti, D., Li, D., and D. McDysan, 128 "Requirements for the Conversion between Permanent 129 Connections and Switched Connections in a Generalized 130 Multiprotocol Label Switching (GMPLS) Network", RFC 5493, 131 April 2009. 133 [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., 134 and S. Ueno, "Requirements of an MPLS Transport Profile", 135 RFC 5654, September 2009. 137 6.2. Informative References 139 [I-D.ietf-ccamp-pc-spc-rsvpte-ext] 140 Caviglia, D., Ceccarelli, D., Li, D., and S. Bardalai, 141 "RSVP-TE Signaling Extension For Management Plane To 142 Control Plane LSP Handover In A GMPLS Enabled Transport 143 Network.", draft-ietf-ccamp-pc-spc-rsvpte-ext-07 (work in 144 progress), February 2010. 146 [I-D.ietf-pwe3-ms-pw-arch] 147 Bocci, M. and S. Bryant, "An Architecture for Multi- 148 Segment Pseudowire Emulation Edge-to-Edge", 149 draft-ietf-pwe3-ms-pw-arch-07 (work in progress), 150 July 2009. 152 [I-D.abfb-mpls-tp-control-plane-framework] 153 Andersson, L., Berger, L., Fang, L., Bitar, N., Takacs, 154 A., Vigoureux, M., and E. Bellagamba, "MPLS-TP Control 155 Plane Framework", 156 draft-abfb-mpls-tp-control-plane-framework-02 (work in 157 progress), February 2010. 159 [I-D.ietf-mpls-tp-framework] 160 Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. 161 Berger, "A Framework for MPLS in Transport Networks", 162 draft-ietf-mpls-tp-framework-10 (work in progress), 163 February 2010. 165 Authors' Addresses 167 Xihua Fu 168 ZTE Corporation 169 West District,ZTE Plaza,No.10,Tangyan South Road,Gaoxin District 170 Xi An 710065 171 P.R.China 173 Phone: +8613798412242 174 Email: fu.xihua@zte.com.cn 175 URI: http://wwwen.zte.com.cn/ 177 Xuefeng Lin 178 ZTE Corporation 179 12F,ZTE Plaza,No.19,Huayuan East Road,Haidian District 180 Beijing 100191 181 P.R.China 183 Phone: +8615901011821 184 Email: lin.xuefeng@zte.com.cn 185 URI: http://www.zte.com.cn/ 187 Gang Xie 188 ZTE Corporation 189 12F,ZTE Plaza,No.19,Huayuan East Road,Haidian District 190 Beijing 100191 191 P.R.China 193 Phone: +8613691280432 194 Email: xie.gang@zte.com.cn