draft-ietf-mpls-in-udp-07.txt   draft-ietf-mpls-in-udp-08.txt 
Network Working Group X. Xu Network Working Group X. Xu
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track N. Sheth Intended status: Standards Track N. Sheth
Expires: April 27, 2015 Juniper Networks Expires: June 13, 2015 Juniper Networks
L. Yong L. Yong
Huawei USA Huawei USA
C. Pignataro
Cisco Systems
Y. Fan
China Telecom
R. Callon R. Callon
Juniper Networks Juniper Networks
D. Black D. Black
EMC Corporation EMC Corporation
October 24, 2014 December 10, 2014
Encapsulating MPLS in UDP Encapsulating MPLS in UDP
draft-ietf-mpls-in-udp-07 draft-ietf-mpls-in-udp-08
Abstract Abstract
This document specifies an IP-based encapsulation for MPLS, called This document specifies an IP-based encapsulation for MPLS, called
MPLS-in-UDP (User Datagram Protocol). The MPLS-in-UDP encapsulation MPLS-in-UDP (User Datagram Protocol). The MPLS-in-UDP encapsulation
technology MUST only be deployed within a service provider network or technology MUST only be deployed within a service provider network or
networks of an adjacent set of co-operating service providers where networks of an adjacent set of co-operating service providers where
congestion control is not a concern. congestion control is not a concern.
Status of This Memo Status of This Memo
skipping to change at page 1, line 45 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 27, 2015. This Internet-Draft will expire on June 13, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 21
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Existing Encapsulations . . . . . . . . . . . . . . . . . 3 1.1. Existing Encapsulations . . . . . . . . . . . . . . . . . 3
1.2. Motivations for MPLS-in-UDP Encapsulation . . . . . . . . 3 1.2. Motivations for MPLS-in-UDP Encapsulation . . . . . . . . 3
1.3. Application Statements . . . . . . . . . . . . . . . . . 4 1.3. Application Statements . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Encapsulation in UDP . . . . . . . . . . . . . . . . . . . . 4 3. Encapsulation in UDP . . . . . . . . . . . . . . . . . . . . 4
3.1. UDP Checksum Usage with IPv6 . . . . . . . . . . . . . . 6 3.1. UDP Checksum Usage with IPv6 . . . . . . . . . . . . . . 6
3.2. Middlebox Considerations for IPv6 UDP Zero Checksums . . 9 3.2. Middlebox Considerations for IPv6 UDP Zero Checksums . . 8
4. Processing Procedures . . . . . . . . . . . . . . . . . . . . 9 4. Processing Procedures . . . . . . . . . . . . . . . . . . . . 9
5. Congestion Considerations . . . . . . . . . . . . . . . . . . 9 5. Congestion Considerations . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
This document specifies an IP-based encapsulation for MPLS, i.e. This document specifies an IP-based encapsulation for MPLS, i.e.
MPLS-in-UDP (User Datagram Protocol), which is applicable in some MPLS-in-UDP (User Datagram Protocol), which is applicable in some
circumstances where IP-based encapsulation for MPLS is required and circumstances where IP-based encapsulation for MPLS is required and
further fine-grained load balancing of MPLS packets over IP networks further fine-grained load balancing of MPLS packets over IP networks
over Equal Cost Multi-Path (ECMP) and/or Link Aggregation Groups over Equal Cost Multi-Path (ECMP) and/or Link Aggregation Groups
skipping to change at page 8, line 41 skipping to change at page 8, line 39
The remaining requirements specified in Section 5 of [RFC6936] are The remaining requirements specified in Section 5 of [RFC6936] are
inapplicable to MPLS-in-UDP. Requirements 6 and 7 do not apply inapplicable to MPLS-in-UDP. Requirements 6 and 7 do not apply
because MPLS does not have an MPLS-generic control feedback because MPLS does not have an MPLS-generic control feedback
mechanism. Requirements 8-10 are middlebox requirements that do not mechanism. Requirements 8-10 are middlebox requirements that do not
apply to MPLS-in-UDP tunnel endpoints, but see Section 3.2 for apply to MPLS-in-UDP tunnel endpoints, but see Section 3.2 for
further middlebox discussion. further middlebox discussion.
In summary, UDP zero-checksum mode for IPv6 is allowed to be used In summary, UDP zero-checksum mode for IPv6 is allowed to be used
with MPLS-in-UDP when one of the two exceptions specified above with MPLS-in-UDP when one of the two exceptions specified above
applies, provided that the five additional requirements (six for applies, provided that the additional requirements specified above
middlebox implementations) stated above are complied with. Otherwise are complied with. Otherwise the UDP checksum MUST be used for IPv6
the UDP checksum MUST be used for IPv6 as specified in [RFC0768] and as specified in [RFC0768] and [RFC2460].
[RFC2460].
This entire section and its requirements apply only to use of UDP This entire section and its requirements apply only to use of UDP
zero-checksum mode for IPv6; they can be avoided by using the UDP zero-checksum mode for IPv6; they can be avoided by using the UDP
checksum as specified in [RFC0768] and [RFC2460]. checksum as specified in [RFC0768] and [RFC2460].
3.2. Middlebox Considerations for IPv6 UDP Zero Checksums 3.2. Middlebox Considerations for IPv6 UDP Zero Checksums
IPv6 datagrams with a zero UDP checksum will not be passed by any IPv6 datagrams with a zero UDP checksum will not be passed by any
middlebox that validates the checksum based on [RFC2460] or that middlebox that validates the checksum based on [RFC2460] or that
updates the UDP checksum field, such as NATs or firewalls. Changing updates the UDP checksum field, such as NATs or firewalls. Changing
skipping to change at page 13, line 45 skipping to change at page 13, line 35
Description: Encapsulate MPLS packets in UDP tunnels with DTLS. Description: Encapsulate MPLS packets in UDP tunnels with DTLS.
Reference: This document -- draft-ietf-mpls-in-udp (MPLS WG Reference: This document -- draft-ietf-mpls-in-udp (MPLS WG
document). document).
Port Number: TBD2 -- To be assigned by IANA. Port Number: TBD2 -- To be assigned by IANA.
8. Contributors 8. Contributors
Zhenbin Li Note that contributors are listed in alphabetical order according to
their last names.
Huawei Technologies, Yongbing Fan
Beijing, China China Telecom
Email: fanyb@gsta.com
Adrian Farrel
Juniper Networks
Email: adrian@olddog.co.uk
Zhenbin Li
Huawei Technologies
Email: lizhenbin@huawei.com Email: lizhenbin@huawei.com
Carlos Pignataro
Cisco Systems
Email: cpignata@cisco.com
Curtis Villamizar Curtis Villamizar
Outer Cape Cod Network Consulting, LLC Outer Cape Cod Network Consulting, LLC
Email: curtis@occnc.com Email: curtis@occnc.com
9. Acknowledgements 9. Acknowledgements
Thanks to Shane Amante, Dino Farinacci, Keshava A K, Ivan Pepelnjak, Thanks to Shane Amante, Dino Farinacci, Keshava A K, Ivan Pepelnjak,
Eric Rosen, Andrew G. Malis, Kireeti Kompella, Marshall Eubanks, Eric Rosen, Andrew G. Malis, Kireeti Kompella, Marshall Eubanks,
George Swallow, Loa Andersson, Vivek Kumar, Stewart Bryant, Wen George Swallow, Loa Andersson, Vivek Kumar, Stewart Bryant, Wen
Zhang, Joel M. Halpern, Noel Chiappa, Scott Brim, Alia Atlas, Zhang, Joel M. Halpern, Noel Chiappa, Scott Brim, Alia Atlas,
Alexander Vainshtein, Joel Jaeggli, Edward Crabbe, Mark Tinka, Lars Alexander Vainshtein, Joel Jaeggli, Edward Crabbe, Mark Tinka, Lars
Eggert, Joe Touch, Lloyd Wood, Weiguo Hao, Mark Szczesniak, Zhenxiao Eggert, Joe Touch, Lloyd Wood, Gorry Fairhurst, Weiguo Hao, Mark
Liu and Xing Tong for their valuable comments and suggestions on this Szczesniak, Zhenxiao Liu and Xing Tong for their valuable comments
document. and suggestions on this document.
Special thanks to Adrian Farrel for his conscientious AD review and Special thanks to Alia Atlas for her insightful suggestion of adding
insightful suggestion of using DTLS for securing the MPLS-in-UDP an applicability statement.
tunnels. Special thanks to Alia Atlas for her insightful suggestion
of adding an applicability statement.
Thanks to Daniel King, Gregory Mirsky and Eric Osborne for their Thanks to Daniel King, Gregory Mirsky and Eric Osborne for their
valuable MPLS-RT reviews on this document. Thanks to Charlie Kaufman valuable MPLS-RT reviews on this document. Thanks to Charlie Kaufman
for his SecDir review of this document. Thanks to Nevil Brownlee for for his SecDir review of this document. Thanks to Nevil Brownlee for
the OPSDir review of this document. Thanks to Roni Even for the Gen- the OPSDir review of this document. Thanks to Roni Even for the Gen-
ART review of this document. Thanks to Pearl Liang for the IANA ART review of this document. Thanks to Pearl Liang for the IANA
review of this documents. review of this documents.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
skipping to change at page 16, line 31 skipping to change at page 17, line 4
Email: nsheth@juniper.net Email: nsheth@juniper.net
Lucy Yong Lucy Yong
Huawei USA Huawei USA
5340 Legacy Dr 5340 Legacy Dr
Plano, TX 75025 Plano, TX 75025
USA USA
Email: Lucy.yong@huawei.com Email: Lucy.yong@huawei.com
Carlos Pignataro
Cisco Systems
7200-12 Kit Creek Road
Research Triangle Park, NC 27709
USA
Email: cpignata@cisco.com
Yongbing Fan
China Telecom
Guangzhou
CHINA
Email: fanyb@gsta.com
Ross Callon Ross Callon
Juniper Networks Juniper Networks
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA USA
Email: rcallon@juniper.net Email: rcallon@juniper.net
David Black David Black
EMC Corporation EMC Corporation
 End of changes. 17 change blocks. 
41 lines changed or deleted 37 lines changed or added

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