< draft-ietf-pwe3-cell-transport-05.txt   draft-ietf-pwe3-cell-transport-06.txt >
PWE3 Working Group PWE3 Working Group
Internet Draft A. Malis Internet Draft A. Malis
draft-ietf-pwe3-cell-transport-05.txt Tellabs draft-ietf-pwe3-cell-transport-06.txt Tellabs
Expires: October 2006 L. Martini Expires: April 2007 L. Martini
Cisco Systems Cisco Systems
J. Brayley J. Brayley
Laurel Networks, Inc. ECI Telecom
T. Walsh T. Walsh
Lucent Technologies Juniper Networks
April 2006 October 2006
PWE3 ATM Transparent Cell Transport Service PWE3 ATM Transparent Cell Transport Service
IPR Statement IPR Statement
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
skipping to change at page 2, line 5 skipping to change at page 2, line 5
The document describes a transparent cell transport service that The document describes a transparent cell transport service that
makes use of the "N-to-one" cell relay mode for PWE3 ATM cell makes use of the "N-to-one" cell relay mode for PWE3 ATM cell
encapsulation. encapsulation.
Specification of Requirements Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119 [1]. this document are to be interpreted as described in RFC 2119 [1].
PWE3 ATM Transparent Cell Transport Service October 2006
1. Intellectual Property Statement 1. 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 Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology to pertain to the implementation or use of the technology
described in this document or the extent to which any license described in this document or the extent to which any license
under such rights might or might not be available; nor does it under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any represent that it has made any independent effort to identify any
such rights. Information on the procedures with respect to rights such rights. Information on the procedures with respect to rights
in RFC documents can be found in BCP 78 and BCP 79. in RFC documents can be found in BCP 78 and BCP 79.
skipping to change at page 3, line 4 skipping to change at page 3, line 4
The ATM transparent port service emulates connectivity between two The ATM transparent port service emulates connectivity between two
remote ATM ports. This service is useful when one desires to connect remote ATM ports. This service is useful when one desires to connect
two CEs without processing or switching at the VPC or VCC layer. The two CEs without processing or switching at the VPC or VCC layer. The
ingress PE discards any idle/unassigned cells received from the ingress PE discards any idle/unassigned cells received from the
ingress ATM port, and maps all other received cells to a single ingress ATM port, and maps all other received cells to a single
pseudowire. pseudowire.
The egress PE does not change the VPI, VCI, PTI, or CLP bits when it The egress PE does not change the VPI, VCI, PTI, or CLP bits when it
sends these cells on the egress ATM port. Therefore the transparent sends these cells on the egress ATM port. Therefore the transparent
PWE3 ATM Transparent Cell Transport Service October 2006
port service appears to emulate an ATM transmission convergence layer port service appears to emulate an ATM transmission convergence layer
connection between two ports. However, since the ingress PE discards connection between two ports. However, since the ingress PE discards
idle/unassigned cells, this service benefits from statistical idle/unassigned cells, this service benefits from statistical
multiplexing bandwidth savings. multiplexing bandwidth savings.
In accordance with [2], cell concatenation MAY be used for In accordance with [2], cell concatenation MAY be used for
transparent cell relay transport in order to save the PSN bandwidth. transparent cell relay transport in order to save the PSN bandwidth.
If used, it MUST be agreed between the ingress and egress PEs. In If used, it MUST be agreed between the ingress and egress PEs. In
particular, if the Pseudo Wire has been set up using the PWE3 control particular, if the Pseudo Wire has been set up using the PWE3 control
protocol [3], the ingress PE MUST NOT exceed the value of the protocol [3], the ingress PE MUST NOT exceed the value of the
skipping to change at page 3, line 45 skipping to change at page 3, line 48
This draft does not introduce any new security considerations beyond This draft does not introduce any new security considerations beyond
those in [2] and [3]. This document defines an application that those in [2] and [3]. This document defines an application that
utilizes the encapsulation specified in [2], and does not specify the utilizes the encapsulation specified in [2], and does not specify the
protocols used to carry the encapsulated packets across the PSN. Each protocols used to carry the encapsulated packets across the PSN. Each
such protocol may have its own set of security issues, but those such protocol may have its own set of security issues, but those
issues are not affected by the application specified herein. Note issues are not affected by the application specified herein. Note
that the security of the transported ATM service will only be as good that the security of the transported ATM service will only be as good
as the security of the PSN. This level of security might be less as the security of the PSN. This level of security might be less
rigorous then a native ATM service. rigorous then a native ATM service.
5. IANA Considerations 5. Congestion Control
Since this document discusses an application of the "N-to-
one" VCC cell transport mode for PWE3 ATM encapsulation described in
[2], the congestion control considerations are identical to those
discussed in section 15 of [2]. The PWE3 Working Group is also
undertaking additional work on ATM-related congestion issues, and
implementers should anticipate that an RFC will be published
describing additional congestion techniques that should be applied to
ATM emulation over pseudowires.
PWE3 ATM Transparent Cell Transport Service October 2006
6. IANA Considerations
This document does not require any IANA actions. This document does not require any IANA actions.
6. Normative References 7. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Martini, L., et al, "Encapsulation Methods for Transport of ATM [2] Martini, L., et al, "Encapsulation Methods for Transport of ATM
Over MPLS Networks", draft-ietf-pwe3-atm-encap-10.txt, September Over MPLS Networks", draft-ietf-pwe3-atm-encap-11.txt, May
2005, work in progress. 2006, work in progress.
[3] Martini, L., et al, "Pseudowire Setup and Maintenance using the [3] Martini, L., et al, "Pseudowire Setup and Maintenance using the
Label Distribution Protocol", work in progress, draft-ietf-pwe3- Label Distribution Protocol (LDP)", RFC 4447, April 2006.
control-protocol-17.txt, June 2005, work in progress.
[4] Martini, L. et al, "IANA Allocations for Pseudo Wire Edge to Edge [4] Martini, L. et al, "IANA Allocations for Pseudowire Edge to Edge
Emulation (PWE3)", draft-ietf-pwe3-iana-allocation-15.txt, Emulation (PWE3)", RFC 4446, BCP 116, April 2006.
November 2005, work in progress.
7. Full Copyright Statement 7. Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. PARTICULAR PURPOSE.
Acknowledgments 8. Acknowledgments
The authors would like to thank the members of the PWE3 working group The authors would like to thank the members of the PWE3 working group
for their assistance on this draft, and Sasha Vainshtein of Axerra in for their assistance on this draft, and Sasha Vainshtein of Axerra in
particular for his comments and suggestions. particular for his comments and suggestions.
Author's Addresses 9. Author's Addresses
Andrew G. Malis Andrew G. Malis
Tellabs Tellabs
90 Rio Robles Drive 90 Rio Robles Drive
San Jose, CA 95134 San Jose, CA 95134
Email: Andy.Malis@tellabs.com Email: Andy.Malis@tellabs.com
PWE3 ATM Transparent Cell Transport Service October 2006
Luca Martini Luca Martini
Cisco Systems, Inc. Cisco Systems, Inc.
9155 East Nichols Avenue, Suite 400 9155 East Nichols Avenue, Suite 400
Englewood, CO, 80112 Englewood, CO, 80112
e-mail: lmartini@cisco.com e-mail: lmartini@cisco.com
Jeremy Brayley Jeremy Brayley
ECI Telecom ECI Telecom
Omega Corporate Center Omega Corporate Center
1300 Omega Drive 1300 Omega Drive
Pittsburgh, PA 15205 Pittsburgh, PA 15205
Email: jeremy.brayley@ecitele.com Email: jeremy.brayley@ecitele.com
Tom Walsh Tom Walsh
Lucent Technologies Juniper Networks
1 Robbins Road 1194 N Mathilda Ave
Westford, MA 01886 USA Sunnyvale, CA 94089
Email: tdwalsh@lucent.com Email: twalsh@juniper.net
 End of changes. 15 change blocks. 
16 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/