idnits 2.17.1 draft-ietf-pwe3-cell-transport-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5 on line 197. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 64. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 71. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 77. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2006) is 6402 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) ** Obsolete normative reference: RFC 4447 (ref. '3') (Obsoleted by RFC 8077) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PWE3 Working Group 3 Internet Draft A. Malis 4 draft-ietf-pwe3-cell-transport-06.txt Tellabs 5 Expires: April 2007 L. Martini 6 Cisco Systems 7 J. Brayley 8 ECI Telecom 9 T. Walsh 10 Juniper Networks 11 October 2006 13 PWE3 ATM Transparent Cell Transport Service 15 IPR Statement 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Status of this Memo 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six 30 months and may be updated, replaced, or obsoleted by other 31 documents at any time. It is inappropriate to use Internet-Drafts 32 as reference material or to cite them other than as "work in 33 progress". 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/1id-abstracts.html 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 Abstract 43 The document describes a transparent cell transport service that 44 makes use of the "N-to-one" cell relay mode for PWE3 ATM cell 45 encapsulation. 47 Specification of Requirements 49 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 50 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 51 this document are to be interpreted as described in RFC 2119 [1]. 53 PWE3 ATM Transparent Cell Transport Service October 2006 55 1. Intellectual Property Statement 57 The IETF takes no position regarding the validity or scope of any 58 Intellectual Property Rights or other rights that might be claimed 59 to pertain to the implementation or use of the technology 60 described in this document or the extent to which any license 61 under such rights might or might not be available; nor does it 62 represent that it has made any independent effort to identify any 63 such rights. Information on the procedures with respect to rights 64 in RFC documents can be found in BCP 78 and BCP 79. 66 Copies of IPR disclosures made to the IETF Secretariat and any 67 assurances of licenses to be made available, or the result of an 68 attempt made to obtain a general license or permission for the use 69 of such proprietary rights by implementers or users of this 70 specification can be obtained from the IETF on-line IPR repository 71 at http://www.ietf.org/ipr. 73 The IETF invites any interested party to bring to its attention 74 any copyrights, patents or patent applications, or other 75 proprietary rights that may cover technology that may be required 76 to implement this standard. Please address the information to the 77 IETF at ietf-ipr@ietf.org. 79 2. Introduction 81 This transparent cell transport service allows migration of ATM 82 services to a PSN without having to provision the ATM subscriber or 83 customer edge (CE) devices. The ATM CEs will view the ATM 84 transparent cell transport service as if they were directly connected 85 via a TDM leased line. This service is most likely to be used as an 86 internal function in a ATM service provider's network as a way to 87 connect existing ATM switches via a higher speed PSN, or to provide 88 ATM "backhaul" services for remote access to existing ATM networks. 90 3. Transparent Cell Transport Definition 92 The transparent port service is a natural application of the "N-to- 93 one" VCC cell transport mode for PWE3 ATM encapsulation described in 94 [2], and MUST be used with pseudowires of type 0x0003, "ATM 95 transparent cell transport" [4]. 97 The ATM transparent port service emulates connectivity between two 98 remote ATM ports. This service is useful when one desires to connect 99 two CEs without processing or switching at the VPC or VCC layer. The 100 ingress PE discards any idle/unassigned cells received from the 101 ingress ATM port, and maps all other received cells to a single 102 pseudowire. 104 The egress PE does not change the VPI, VCI, PTI, or CLP bits when it 105 sends these cells on the egress ATM port. Therefore the transparent 107 PWE3 ATM Transparent Cell Transport Service October 2006 109 port service appears to emulate an ATM transmission convergence layer 110 connection between two ports. However, since the ingress PE discards 111 idle/unassigned cells, this service benefits from statistical 112 multiplexing bandwidth savings. 114 In accordance with [2], cell concatenation MAY be used for 115 transparent cell relay transport in order to save the PSN bandwidth. 116 If used, it MUST be agreed between the ingress and egress PEs. In 117 particular, if the Pseudo Wire has been set up using the PWE3 control 118 protocol [3], the ingress PE MUST NOT exceed the value of the 119 "Maximum Number of concatenated ATM cells" Pseudowire Interface 120 Parameter Sub-TLV type (Interface Parameter ID = 0x02 [4]) received 121 in the Label Mapping message for the Pseudo Wire, and MUST NOT use 122 cell concatenation if this parameter has been omitted by the egress 123 PE. 125 ATM OAM cells MUST be transported transparently, and the PEs do not 126 act on them. If the PEs detect a PSN or pseudowire failure between 127 them, they do not generate any OAM cells, but rather bring down the 128 ATM interfaces to the CEs (e.g. generating LOS on the ATM port), 129 just as if it were a transmission layer failure. 131 Similarly, ATM ILMI signaling from the CEs, if any, MUST be 132 transported transparently, and the PEs do not act on it. However, 133 the PEs must act on physical interface failure by either withdrawing 134 the PW labels or by using pseudowire status signaling to indicate the 135 interface failure. The procedures for both alternatives are 136 described in [3]. 138 4. Security Considerations 140 This draft does not introduce any new security considerations beyond 141 those in [2] and [3]. This document defines an application that 142 utilizes the encapsulation specified in [2], and does not specify the 143 protocols used to carry the encapsulated packets across the PSN. Each 144 such protocol may have its own set of security issues, but those 145 issues are not affected by the application specified herein. Note 146 that the security of the transported ATM service will only be as good 147 as the security of the PSN. This level of security might be less 148 rigorous then a native ATM service. 150 5. Congestion Control 152 Since this document discusses an application of the "N-to- 153 one" VCC cell transport mode for PWE3 ATM encapsulation described in 154 [2], the congestion control considerations are identical to those 155 discussed in section 15 of [2]. The PWE3 Working Group is also 156 undertaking additional work on ATM-related congestion issues, and 157 implementers should anticipate that an RFC will be published 158 describing additional congestion techniques that should be applied to 159 ATM emulation over pseudowires. 161 PWE3 ATM Transparent Cell Transport Service October 2006 163 6. IANA Considerations 165 This document does not require any IANA actions. 167 7. Normative References 169 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 170 Levels", BCP 14, RFC 2119, March 1997. 172 [2] Martini, L., et al, "Encapsulation Methods for Transport of ATM 173 Over MPLS Networks", draft-ietf-pwe3-atm-encap-11.txt, May 174 2006, work in progress. 176 [3] Martini, L., et al, "Pseudowire Setup and Maintenance using the 177 Label Distribution Protocol (LDP)", RFC 4447, April 2006. 179 [4] Martini, L. et al, "IANA Allocations for Pseudowire Edge to Edge 180 Emulation (PWE3)", RFC 4446, BCP 116, April 2006. 182 7. Full Copyright Statement 184 Copyright (C) The Internet Society (2006). 186 This document is subject to the rights, licenses and restrictions 187 contained in BCP 78, and except as set forth therein, the authors 188 retain all their rights. 190 This document and the information contained herein are provided on 191 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 192 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 193 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 194 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 195 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 196 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 197 PARTICULAR PURPOSE. 199 8. Acknowledgments 201 The authors would like to thank the members of the PWE3 working group 202 for their assistance on this draft, and Sasha Vainshtein of Axerra in 203 particular for his comments and suggestions. 205 9. Author's Addresses 207 Andrew G. Malis 208 Tellabs 209 90 Rio Robles Drive 210 San Jose, CA 95134 211 Email: Andy.Malis@tellabs.com 213 PWE3 ATM Transparent Cell Transport Service October 2006 215 Luca Martini 216 Cisco Systems, Inc. 217 9155 East Nichols Avenue, Suite 400 218 Englewood, CO, 80112 219 e-mail: lmartini@cisco.com 221 Jeremy Brayley 222 ECI Telecom 223 Omega Corporate Center 224 1300 Omega Drive 225 Pittsburgh, PA 15205 226 Email: jeremy.brayley@ecitele.com 228 Tom Walsh 229 Juniper Networks 230 1194 N Mathilda Ave 231 Sunnyvale, CA 94089 232 Email: twalsh@juniper.net