Encapsulating MPLS in UDP
draft-ietf-mpls-in-udp-01
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (mpls WG)
|
|
Last updated |
|
2013-04-01
|
|
Replaces |
|
draft-xu-mpls-in-udp
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network working group X. Xu
Internet Draft Huawei
Category: Standard Track N. Sheth
Juniper
L. Yong
Huawei
C. Pignataro
Cisco
Y. Fan
China Telecom
Expires: September 2013 March 30, 2013
Encapsulating MPLS in UDP
draft-ietf-mpls-in-udp-01
Abstract
Existing technologies to encapsulate Multi-Protocol Label Switching
(MPLS) over IP are not adequate for efficient load balancing of MPLS
application traffic, such as MPLS-based Layer2 Virtual Private
Network (L2VPN) or Layer3 Virtual Private Network (L3VPN) traffic
across IP networks. This document specifies additional IP-based
encapsulation technology, referred to as MPLS-in-User Datagram
Protocol (UDP), which can facilitate the load balancing of MPLS
application traffic across IP networks.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 30, 2013.
Xu, et al. Expires September 30, 2013 [Page 1]
Internet-Draft Encapsulating MPLS in UDP March 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents
1. Introduction ................................................ 3
1.1. Existing Technologies .................................. 3
1.2. Motivations for MPLS-in-UDP Encapsulation .............. 4
2. Terminology ................................................. 4
3. Encapsulation in UDP......................................... 4
4. Processing Procedures ....................................... 5
5. Applicability ............................................... 6
6. Security Considerations ..................................... 6
7. IANA Considerations ......................................... 6
8. Acknowledgements ............................................ 6
9. References .................................................. 7
9.1. Normative References ................................... 7
9.2. Informative References ................................. 7
Authors' Addresses ............................................. 8
Xu, et al. Expires September 30, 2013 [Page 2]
Internet-Draft Encapsulating MPLS in UDP March 2013
1. Introduction
To fully utilize the bandwidth available in IP networks and/or
facilitate recovery from a link or node failure, load balancing of
Show full document text