< draft-ietf-l2tpext-pwe3-ethernet-08.txt   draft-ietf-l2tpext-pwe3-ethernet-09.txt >
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Network Working Group Rahul Aggarwal Network Working Group Rahul Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: February 2007 W. Mark Townsley Expiration Date: February 2007 W. Mark Townsley
Maria A. Dos Santos Maria A. Dos Santos
Cisco Systems Cisco Systems
Editors Editors
August 2006 August 2006
Transport of Ethernet Frames over L2TPv3 Transport of Ethernet Frames over L2TPv3
draft-ietf-l2tpext-pwe3-ethernet-08.txt draft-ietf-l2tpext-pwe3-ethernet-09.txt
Status of this Memo Status of this Memo
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.
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
skipping to change at page 3, line 4 skipping to change at page 3, line 4
2.3 PW Session Monitoring................................. 6 2.3 PW Session Monitoring................................. 6
3. Packet Processing......................................... 8 3. Packet Processing......................................... 8
3.1 Encapsulation......................................... 8 3.1 Encapsulation......................................... 8
3.2 Sequencing............................................ 8 3.2 Sequencing............................................ 8
3.3 MTU Handling.......................................... 8 3.3 MTU Handling.......................................... 8
4. Applicability Statement................................... 9 4. Applicability Statement................................... 9
5. Congestion Control........................................ 11 5. Congestion Control........................................ 11
6. Security Considerations................................... 11 6. Security Considerations................................... 12
7. IANA Considerations....................................... 12 7. IANA Considerations....................................... 12
8. Acknowledgements.......................................... 12 8. Acknowledgements.......................................... 12
9. References................................................ 12 9. References................................................ 12
9.1 Normative References.................................. 12 9.1 Normative References.................................. 12
9.2 Informative References................................ 13 9.2 Informative References................................ 13
10. Author Information....................................... 13 10. Author Information....................................... 13
skipping to change at page 11, line 39 skipping to change at page 11, line 39
Sequencing and detecting that the packet loss is higher than a Sequencing and detecting that the packet loss is higher than a
threshold) the Ethernet or Ethernet VLAN PW SHOULD be halted by threshold) the Ethernet or Ethernet VLAN PW SHOULD be halted by
tearing down the L2TP session via a CDN message. The PW may be tearing down the L2TP session via a CDN message. The PW may be
restarted by manual intervention, or by automatic means after an restarted by manual intervention, or by automatic means after an
appropriate waiting time. Note that the thresholds and time periods appropriate waiting time. Note that the thresholds and time periods
for shutdown and possible automatic recovery need to be carefully for shutdown and possible automatic recovery need to be carefully
configured. This is necessary to avoid loss of service due to configured. This is necessary to avoid loss of service due to
temporary congestion, and to prevent oscillation between the temporary congestion, and to prevent oscillation between the
congested and halted states. congested and halted states.
This specification offers no congestion control and is not TCP
friendly [TFRC]. Future works for PW congestion control (being
studied by the PWE3 Working Group) will provide congestion control
for all PW types including Ethernet and Ethernet VLAN PWs.
6. Security Considerations 6. Security Considerations
Ethernet over L2TPv3 is subject to all of the general security Ethernet over L2TPv3 is subject to all of the general security
considerations outlined in [RFC3931]. considerations outlined in [RFC3931].
7. IANA Considerations 7. IANA Considerations
The signaling mechanisms defined in this document rely upon the The signaling mechanisms defined in this document rely upon the
allocation of following Ethernet Pseudowire Types (see Pseudo Wire allocation of following Ethernet Pseudowire Types (see Pseudo Wire
Capabilities List as defined in 5.4.3 of [RFC3931] and L2TPv3 Capabilities List as defined in 5.4.3 of [RFC3931] and L2TPv3
skipping to change at page 13, line 34 skipping to change at page 13, line 34
networks virtual bridged local area networks", IEEE networks virtual bridged local area networks", IEEE
Std 802.1Q-2005 (Incorporates IEEE Std 802.1Q1998, IEEE Std 802.1Q-2005 (Incorporates IEEE Std 802.1Q1998, IEEE
Std 802.1u-2001, IEEE Std 802.1v-2001, and IEEE Std Std 802.1u-2001, IEEE Std 802.1v-2001, and IEEE Std
802.1s-2002) 802.1s-2002)
[802.1ad] IEEE, "IEEE Std 802.1ad - 2005 IEEE Standard for Local [802.1ad] IEEE, "IEEE Std 802.1ad - 2005 IEEE Standard for Local
and metropolitan area networks - virtual Bridged Local and metropolitan area networks - virtual Bridged Local
Area Networks, Amendment 4: Provider Bridges", IEEE Area Networks, Amendment 4: Provider Bridges", IEEE
Std 802.1ad-2005 (Amendment to IEEE Std 8021Q-2005) Std 802.1ad-2005 (Amendment to IEEE Std 8021Q-2005)
[TFRC] M. Handley, S. Floyd, J. Padhye, J. Widmer, "TCP
Friendly Rate Control (TFRC): Protocol Specification",
RFC3448, January 2003
10. Author Information 10. Author Information
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
1194 North Mathilda Avenue 1194 North Mathilda Avenue
Sunnyvale, CA 94089 Sunnyvale, CA 94089
e-mail: rahul@juniper.net e-mail: rahul@juniper.net
W. Mark Townsley W. Mark Townsley
Cisco Systems Cisco Systems
 End of changes. 4 change blocks. 
2 lines changed or deleted 11 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/