draft-akiya-mpls-entropy-lsp-ping-03.txt   draft-akiya-mpls-entropy-lsp-ping-04.txt 
Internet Engineering Task Force N. Akiya Internet Engineering Task Force N. Akiya
Internet-Draft G. Swallow Internet-Draft G. Swallow
Updates: 4379,6424,6790 (if approved) C. Pignataro Updates: 4379,6424,6790 (if approved) C. Pignataro
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: April 25, 2015 A. Malis Expires: May 26, 2015 A. Malis
S. Aldrin S. Aldrin
Huawei Technologies Huawei Technologies
October 22, 2014 November 22, 2014
Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over
MPLS Network using Entropy Labels (EL) MPLS Network using Entropy Labels (EL)
draft-akiya-mpls-entropy-lsp-ping-03 draft-akiya-mpls-entropy-lsp-ping-04
Abstract Abstract
The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)
Ping and Traceroute are used to exercise specific paths of Equal-Cost Ping and Traceroute are used to exercise specific paths of Equal-Cost
Multipath (ECMP). When LSP is signaled to use Entropy Label (EL) Multipath (ECMP). When LSP is signaled to use Entropy Label (EL)
described in RFC6790, the ability for LSP Ping and Traceroute described in RFC6790, the ability for LSP Ping and Traceroute
operation to discover and exercise ECMP paths has been lost in operation to discover and exercise ECMP paths has been lost in
scenarios which LSRs apply deviating load balance techniques. One scenarios which LSRs apply deviating load balance techniques. One
such scenario is when some LSRs apply EL based load balancing while such scenario is when some LSRs apply EL based load balancing while
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 25, 2015. This Internet-Draft will expire on May 26, 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 43 skipping to change at page 2, line 43
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Multipath Type 9 . . . . . . . . . . . . . . . . . . . . . . 7 3. Multipath Type 9 . . . . . . . . . . . . . . . . . . . . . . 7
4. Pseudowire Tracing . . . . . . . . . . . . . . . . . . . . . 7 4. Pseudowire Tracing . . . . . . . . . . . . . . . . . . . . . 7
5. Initiating LSR Procedures . . . . . . . . . . . . . . . . . . 8 5. Initiating LSR Procedures . . . . . . . . . . . . . . . . . . 8
6. Responder LSR Procedures . . . . . . . . . . . . . . . . . . 9 6. Responder LSR Procedures . . . . . . . . . . . . . . . . . . 9
6.1. IP Based Load Balancer & Not Pushing ELI/EL . . . . . . . 9 6.1. IP Based Load Balancer & Not Pushing ELI/EL . . . . . . . 9
6.2. IP Based Load Balancer & Pushes ELI/EL . . . . . . . . . 10 6.2. IP Based Load Balancer & Pushes ELI/EL . . . . . . . . . 10
6.3. Label Based Load Balancer & Not Pushing ELI/EL . . . . . 11 6.3. Label Based Load Balancer & Not Pushing ELI/EL . . . . . 11
6.4. Label Based Load Balancer & Pushes ELI/EL . . . . . . . . 11 6.4. Label Based Load Balancer & Pushes ELI/EL . . . . . . . . 11
6.5. Flow Aware MS-PW Stitching LSR . . . . . . . . . . . . . 12 6.5. Flow Aware MS-PW Stitching LSR . . . . . . . . . . . . . 12
7. Entropy Label FEC . . . . . . . . . . . . . . . . . . . . . . 12 7. Entropy Label FEC . . . . . . . . . . . . . . . . . . . . . . 13
8. DS Flags: L and E . . . . . . . . . . . . . . . . . . . . . . 13 8. DS Flags: L and E . . . . . . . . . . . . . . . . . . . . . . 13
9. New Multipath Information Type: 10 . . . . . . . . . . . . . 14 9. New Multipath Information Type: TBD4 . . . . . . . . . . . . 14
10. Supported and Unsupported Cases . . . . . . . . . . . . . . . 16 10. Supported and Unsupported Cases . . . . . . . . . . . . . . . 16
11. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 18
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
12.1. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 18 12.1. DS Flags . . . . . . . . . . . . . . . . . . . . . . . . 18
12.2. Multpath Type . . . . . . . . . . . . . . . . . . . . . 18 12.2. Multpath Type . . . . . . . . . . . . . . . . . . . . . 18
12.3. Entropy Label FEC . . . . . . . . . . . . . . . . . . . 19 12.3. Entropy Label FEC . . . . . . . . . . . . . . . . . . . 19
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
14. Contributing Authors . . . . . . . . . . . . . . . . . . . . 19 14. Contributing Authors . . . . . . . . . . . . . . . . . . . . 19
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
15.1. Normative References . . . . . . . . . . . . . . . . . . 19 15.1. Normative References . . . . . . . . . . . . . . . . . . 19
skipping to change at page 7, line 32 skipping to change at page 7, line 32
label. These labels may appear anywhere in a label stack. label. These labels may appear anywhere in a label stack.
Multipath type {9} applies to the first label in the label-stack that Multipath type {9} applies to the first label in the label-stack that
corresponds to an EL-FEC. If no such label is found, it applies to corresponds to an EL-FEC. If no such label is found, it applies to
the label at the bottom of the label stack. the label at the bottom of the label stack.
4. Pseudowire Tracing 4. Pseudowire Tracing
This section defines procedures for tracing pseudowires. These This section defines procedures for tracing pseudowires. These
procedures pertain to the use of multipath information type {9} as procedures pertain to the use of multipath information type {9} as
well as type {10}. In all cases below, when a control word is in use well as type {TBD4}. In all cases below, when a control word is in
the N-flag in the DDMAP or DSMAP MUST be set. Note that when a use the N-flag in the DDMAP or DSMAP MUST be set. Note that when a
control word is not in use the returned DDMAPs or DSMAPs may not be control word is not in use the returned DDMAPs or DSMAPs may not be
accurate. accurate.
In order to trace a non Flow-Aware Pseudowire the initiator includes In order to trace a non Flow-Aware Pseudowire the initiator includes
an EL-FEC instead of the appropriate PW-FEC at the bottom of the FEC- an EL-FEC instead of the appropriate PW-FEC at the bottom of the FEC-
Stack. Tracing in this way will cause compliant routers to return Stack. Tracing in this way will cause compliant routers to return
the proper outgoing interface. Note that this procedure only traces the proper outgoing interface. Note that this procedure only traces
to the end of the MPLS LSP that is under test and will not verify the to the end of the MPLS LSP that is under test and will not verify the
PW FEC. To actually verify the PW-FEC or in the case of a MS-PW, to PW FEC. To actually verify the PW-FEC or in the case of a MS-PW, to
determine the next pseudowire label value, the initiator MUST repeat determine the next pseudowire label value, the initiator MUST repeat
skipping to change at page 8, line 37 skipping to change at page 8, line 37
Section 3 and [RFC6424], initiating LSR MUST operate with following Section 3 and [RFC6424], initiating LSR MUST operate with following
procedures. procedures.
o When the initiating LSR pushes ELI/EL, initialize EL_LSP=True. o When the initiating LSR pushes ELI/EL, initialize EL_LSP=True.
Else set EL_LSP=False. Else set EL_LSP=False.
o When the initiating LSR is transmitting non-zero multipath o When the initiating LSR is transmitting non-zero multipath
information type: information type:
* If (EL_LSP), the initiating LSR MUST use multipath information * If (EL_LSP), the initiating LSR MUST use multipath information
type {10} unless same responder LSR cannot handle type {10}. type {TBD4} unless same responder LSR cannot handle type
{TBD4}.
* Else the initiating LSR MAY use multipath information type {2, * Else the initiating LSR MAY use multipath information type {2,
4, 8, 9}. 4, 8, 9}.
o When the initiating LSR is transmitting multipath information type o When the initiating LSR is transmitting multipath information type
{10}, both "IP Multipath Information" and "Label Multipath {TBD4}, both "IP Multipath Information" and "Label Multipath
Information" MUST be included, and "IP Associated Label Multipath Information" MUST be included, and "IP Associated Label Multipath
Information" MUST be omitted (NULL). Information" MUST be omitted (NULL).
o When the initiating LSR receives echo reply with {L=0, E=1} in DS o When the initiating LSR receives echo reply with {L=0, E=1} in DS
flags with valid contents, set EL_LSP=True. flags with valid contents, set EL_LSP=True.
In following conditions, the initiating LSR may have lost the ability In following conditions, the initiating LSR may have lost the ability
to exercise specific ECMP paths. The initiating LSR MAY continue to exercise specific ECMP paths. The initiating LSR MAY continue
with "best effort". with "best effort".
skipping to change at page 9, line 19 skipping to change at page 9, line 23
o Received echo reply contains {L=1, E=<any>} DS flags, but does not o Received echo reply contains {L=1, E=<any>} DS flags, but does not
contain label multipath information. contain label multipath information.
o Received echo reply contains {L=<any>, E=1} DS flags, but does not o Received echo reply contains {L=<any>, E=1} DS flags, but does not
contain associated label multipath information. contain associated label multipath information.
o IP multipath information types {2, 4, 8} sent, and received echo o IP multipath information types {2, 4, 8} sent, and received echo
reply with {L=1, E=0} in DS flags. reply with {L=1, E=0} in DS flags.
o Multipath information type {10} sent, and received echo reply with o Multipath information type {TBD4} sent, and received echo reply
multipath information type other than {10}. with multipath information type other than {TBD4}.
6. Responder LSR Procedures 6. Responder LSR Procedures
Common Procedures: The responder LSR receiving an MPLS echo request Common Procedures: The responder LSR receiving an MPLS echo request
packet with multipath information type {10} MUST validate following packet with multipath information type {TBD4} MUST validate following
contents. Any deviation MUST result in the responder LSR to consider contents. Any deviation MUST result in the responder LSR to consider
the packet as malformed and return code 1 (Malformed echo request the packet as malformed and return code 1 (Malformed echo request
received) in the MPLS echo reply packet. received) in the MPLS echo reply packet.
o IP multipath information MUST be included. o IP multipath information MUST be included.
o Label multipath information MUST be included. o Label multipath information MUST be included.
o IP associated label multipath information MUST be omitted (NULL). o IP associated label multipath information MUST be omitted (NULL).
skipping to change at page 10, line 5 skipping to change at page 10, line 8
6.1. IP Based Load Balancer & Not Pushing ELI/EL 6.1. IP Based Load Balancer & Not Pushing ELI/EL
o The responder MUST set {L=0, E=0} in DS flags. o The responder MUST set {L=0, E=0} in DS flags.
o If multipath information type {2, 4, 8} is received, the responder o If multipath information type {2, 4, 8} is received, the responder
MUST comply with [RFC4379] and [RFC6424]. MUST comply with [RFC4379] and [RFC6424].
o If multipath information type {9} is received, the responder MUST o If multipath information type {9} is received, the responder MUST
reply with multipath type {0}. reply with multipath type {0}.
o If multipath information type {10} is received, following o If multipath information type {TBD4} is received, following
procedures are to be used: procedures are to be used:
* The responder MUST reply with multipath information type {10}. * The responder MUST reply with multipath information type
{TBD4}.
* "Label Multipath Information" and "Associated Label Multipath * "Label Multipath Information" and "Associated Label Multipath
Information" sections MUST be omitted (NULL). Information" sections MUST be omitted (NULL).
* If no matching IP address is found, then "IPMultipathType" * If no matching IP address is found, then "IPMultipathType"
field MUST be set to multipath information type {0} and "IP field MUST be set to multipath information type {0} and "IP
Multipath Information" section MUST also be omitted (NULL). Multipath Information" section MUST also be omitted (NULL).
* If at least one matching IP address is found, then * If at least one matching IP address is found, then
"IPMultipathType" field MUST be set to appropriate multipath "IPMultipathType" field MUST be set to appropriate multipath
information type {2, 4, 8} and "IP Multipath Information" information type {2, 4, 8} and "IP Multipath Information"
section MUST be included. section MUST be included.
6.2. IP Based Load Balancer & Pushes ELI/EL 6.2. IP Based Load Balancer & Pushes ELI/EL
o The responder MUST set {L=0, E=1} in DS flags. o The responder MUST set {L=0, E=1} in DS flags.
o If multipath information type {9} is received, the responder MUST o If multipath information type {9} is received, the responder MUST
reply with multipath type {0}. reply with multipath type {0}.
o If multipath type {2, 4, 8, 10} is received, following procedures o If multipath type {2, 4, 8, TBD4} is received, following
are to be used: procedures are to be used:
* The responder MUST respond with multipath type {10}. See * The responder MUST respond with multipath type {TBD4}. See
Section 9 for details of multipath type {10}. Section 9 for details of multipath type {TBD4}.
* "Label Multipath Information" section MUST be omitted (i.e. is * "Label Multipath Information" section MUST be omitted (i.e. is
it not there). it not there).
* IP address set specified in received IP multipath information * IP address set specified in received IP multipath information
MUST be used to determine the returning IP/Label pairs. MUST be used to determine the returning IP/Label pairs.
* If received multipath information type was {10}, received * If received multipath information type was {TBD4}, received
"Label Multipath Information" sections MUST NOT be used to "Label Multipath Information" sections MUST NOT be used to
determine the associated label portion of returning IP/Label determine the associated label portion of returning IP/Label
pairs. pairs.
* If no matching IP address is found, then "IPMultipathType" * If no matching IP address is found, then "IPMultipathType"
field MUST be set to multipath information type {0} and "IP field MUST be set to multipath information type {0} and "IP
Multipath Information" section MUST be omitted. In addition, Multipath Information" section MUST be omitted. In addition,
"Assoc Label Multipath Length" MUST be set to 0, and "Assoc Label Multipath Length" MUST be set to 0, and
"Associated Label Multipath Information" section MUST also be "Associated Label Multipath Information" section MUST also be
omitted. omitted.
skipping to change at page 11, line 25 skipping to change at page 11, line 28
6.3. Label Based Load Balancer & Not Pushing ELI/EL 6.3. Label Based Load Balancer & Not Pushing ELI/EL
o The responder MUST set {L=1, E=0} in DS flags. o The responder MUST set {L=1, E=0} in DS flags.
o If multipath information type {2, 4, 8} is received, the responder o If multipath information type {2, 4, 8} is received, the responder
MUST reply with multipath type {0}. MUST reply with multipath type {0}.
o If multipath information type {9} is received, the responder MUST o If multipath information type {9} is received, the responder MUST
comply with [RFC4379] and [RFC6424] as updated by Section 3. comply with [RFC4379] and [RFC6424] as updated by Section 3.
o If multipath information type {10} is received, following o If multipath information type {TBD4} is received, following
procedures are to be used: procedures are to be used:
* The responder MUST reply with multipath information type {10}. * The responder MUST reply with multipath information type
{TBD4}.
* "IP Multipath Information" and "Associated Label Multipath * "IP Multipath Information" and "Associated Label Multipath
Information" sections MUST be omitted (NULL). Information" sections MUST be omitted (NULL).
* If no matching label is found, then "LbMultipathType" field * If no matching label is found, then "LbMultipathType" field
MUST be set to multipath information type {0} and "Label MUST be set to multipath information type {0} and "Label
Multipath Information" section MUST also be omitted (NULL). Multipath Information" section MUST also be omitted (NULL).
* If at least one matching label is found, then "LbMultipathType" * If at least one matching label is found, then "LbMultipathType"
field MUST be set to appropriate multipath information type {9} field MUST be set to appropriate multipath information type {9}
and "Label Multipath Information" section MUST be included. and "Label Multipath Information" section MUST be included.
6.4. Label Based Load Balancer & Pushes ELI/EL 6.4. Label Based Load Balancer & Pushes ELI/EL
o The responder MUST set {L=1, E=1} in DS flags. o The responder MUST set {L=1, E=1} in DS flags.
o If multipath information type {2, 4, 8} is received, the responder o If multipath information type {2, 4, 8} is received, the responder
MUST reply with multipath type {0}. MUST reply with multipath type {0}.
o If multipath type {9, 10} is received, following procedures are to o If multipath type {9, TBD4} is received, following procedures are
be used: to be used:
* The responder MUST respond with multipath type {10}. * The responder MUST respond with multipath type {TBD4}.
* "IP Multipath Information" section MUST be omitted. * "IP Multipath Information" section MUST be omitted.
* Label set specified in received label multipath information * Label set specified in received label multipath information
MUST be used to determine the returning Label/Label pairs. MUST be used to determine the returning Label/Label pairs.
* If received multipath information type was {10}, received * If received multipath information type was {TBD4}, received
"Label Multipath Information" sections MUST NOT be used to "Label Multipath Information" sections MUST NOT be used to
determine the associated label portion of returning Label/Label determine the associated label portion of returning Label/Label
pairs. pairs.
* If no matching label is found, then "LbMultipathType" field * If no matching label is found, then "LbMultipathType" field
MUST be set to multipath information type {0} and "Label MUST be set to multipath information type {0} and "Label
Multipath Information" section MUST be omitted. In addition, Multipath Information" section MUST be omitted. In addition,
"Assoc Label Multipath Length" MUST be set to 0, and "Assoc Label Multipath Length" MUST be set to 0, and
"Associated Label Multipath Information" section MUST also be "Associated Label Multipath Information" section MUST also be
omitted. omitted.
skipping to change at page 14, line 5 skipping to change at page 13, line 49
be set in echo reply packets. be set in echo reply packets.
DS Flags DS Flags
-------- --------
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| MBZ |L|E|I|N| | MBZ |L|E|I|N|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
RFC-Editor-Note: Please update above figure to place the flag E in
the bit number TBD2 and the flag L in the bit number TBD3.
Flag Name and Meaning Flag Name and Meaning
---- ---------------- ---- ----------------
L Label based load balance indicator L Label based load balance indicator
This flag MUST be set to zero in the echo request. LSR This flag MUST be set to zero in the echo request. LSR
which performs load balancing on a label MUST set this which performs load balancing on a label MUST set this
flag in the echo reply. LSR which performs load flag in the echo reply. LSR which performs load
balancing on IP MUST NOT set this flag in the echo balancing on IP MUST NOT set this flag in the echo
reply. reply.
E ELI/EL push indicator E ELI/EL push indicator
skipping to change at page 14, line 32 skipping to change at page 14, line 32
o {L=0, E=0} LSR load balances based on IP and does not push ELI/EL. o {L=0, E=0} LSR load balances based on IP and does not push ELI/EL.
o {L=0, E=1} LSR load balances based on IP and pushes ELI/EL. o {L=0, E=1} LSR load balances based on IP and pushes ELI/EL.
o {L=1, E=0} LSR load balances based on label and does not push ELI/ o {L=1, E=0} LSR load balances based on label and does not push ELI/
EL. EL.
o {L=1, E=1} LSR load balances based on label and pushes ELI/EL. o {L=1, E=1} LSR load balances based on label and pushes ELI/EL.
9. New Multipath Information Type: 10 9. New Multipath Information Type: TBD4
One new multipath information type is added to be used in DSMAP/DDMAP One new multipath information type is added to be used in DSMAP/DDMAP
TLVs. New multipath type has value of 10. TLVs. New multipath type has value of TBD4.
Key Type Multipath Information Key Type Multipath Information
--- ---------------- --------------------- --- ---------------- ---------------------
10 IP and label set IP addresses and label prefixes TBD4 IP and label set IP addresses and label prefixes
Multipath type 10 is comprised of three sections. One section to Multipath type TBD4 is comprised of three sections. One section to
describe IP address set. One section to describe label set. One describe IP address set. One section to describe label set. One
section to describe another label set which associates to either IP section to describe another label set which associates to either IP
address set or label set specified in the other section. address set or label set specified in the other section.
Multipath information type 10 has following format: Multipath information type TBD4 has following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IPMultipathType| Reserved(MBZ) | IP Multipath Length | |IPMultipathType| Reserved(MBZ) | IP Multipath Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~ ~ ~
| (IP Multipath Information) | | (IP Multipath Information) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 27 skipping to change at page 15, line 27
| (Label Multipath Information) | | (Label Multipath Information) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved(MBZ) | Assoc Label Multipath Length | | Reserved(MBZ) | Assoc Label Multipath Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~ ~ ~
| (Associated Label Multipath Information) | | (Associated Label Multipath Information) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Multipath Information Type 10 Figure 2: Multipath Information Type TBD4
o IPMultipathType o IPMultipathType
* 0 when "IP Multipath Information" is omitted. Otherwise one of * 0 when "IP Multipath Information" is omitted. Otherwise one of
IP multipath information values: {2, 4, 8}. IP multipath information values: {2, 4, 8}.
o IP Multipath Information o IP Multipath Information
* This section is omitted when "IPMultipathType" is 0. Otherwise * This section is omitted when "IPMultipathType" is 0. Otherwise
this section reuses IP multipath information from [RFC4379]. this section reuses IP multipath information from [RFC4379].
skipping to change at page 18, line 38 skipping to change at page 18, line 38
12. IANA Considerations 12. IANA Considerations
12.1. DS Flags 12.1. DS Flags
The IANA is requested to assign new bit numbers from the "DS flags" The IANA is requested to assign new bit numbers from the "DS flags"
sub-registry from the "Multi-Protocol Label Switching (MPLS) Label sub-registry from the "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters - TLVs" registry Switched Paths (LSPs) Ping Parameters - TLVs" registry
([IANA-MPLS-LSP-PING]). ([IANA-MPLS-LSP-PING]).
Note: the "DS flags" sub-registry is created by Note: the "DS flags" sub-registry is created by
[I-D.decraene-mpls-lsp-ping-registry]. [I-D.ietf-mpls-lsp-ping-registry].
Bit number Name Reference Bit number Name Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
TBD2(5) E: ELI/EL push indicator this document TBD2 E: ELI/EL push indicator this document
TBD3(4) L: Label based load balance indicator this document TBD3 L: Label based load balance indicator this document
This document requests the bit number 5 as TBD2, and the bit number 4
as TBD3.
12.2. Multpath Type 12.2. Multpath Type
The IANA is requested to assign a new value from the "Multipath Type" The IANA is requested to assign a new value from the "Multipath Type"
sub-registry from the "Multi-Protocol Label Switching (MPLS) Label sub-registry from the "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters - TLVs" registry Switched Paths (LSPs) Ping Parameters - TLVs" registry
([IANA-MPLS-LSP-PING]). ([IANA-MPLS-LSP-PING]).
Note: the "Multipath Type" sub-registry is created by Note: the "Multipath Type" sub-registry is created by
[I-D.decraene-mpls-lsp-ping-registry]. [I-D.ietf-mpls-lsp-ping-registry].
Value Meaning Reference Value Meaning Reference
---------- ---------------------------------------- --------- ---------- ---------------------------------------- ---------
TBD4(10) IP and label set this document TBD4 IP and label set this document
This document requests the value 10 as TBD4.
12.3. Entropy Label FEC 12.3. Entropy Label FEC
The IANA is requested to assign a new sub-TLV from the "Sub-TLVs for The IANA is requested to assign a new sub-TLV from the "Sub-TLVs for
TLV Types 1 and 16" section from the "Multi-Protocol Label Switching TLV Types 1 and 16" section from the "Multi-Protocol Label Switching
(MPLS) Label Switched Paths (LSPs) Ping Parameters - TLVs" registry (MPLS) Label Switched Paths (LSPs) Ping Parameters - TLVs" registry
([IANA-MPLS-LSP-PING]). ([IANA-MPLS-LSP-PING]).
Sub-Type Sub-TLV Name Reference Sub-Type Sub-TLV Name Reference
-------- ------------ --------- -------- ------------ ---------
skipping to change at page 19, line 43 skipping to change at page 19, line 39
14. Contributing Authors 14. Contributing Authors
Nagendra Kumar Nagendra Kumar
Cisco Systems Cisco Systems
Email: naikumar@cisco.com Email: naikumar@cisco.com
15. References 15. References
15.1. Normative References 15.1. Normative References
[I-D.ietf-mpls-lsp-ping-registry]
Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and
S. Aldrin, "IANA registries for LSP ping Code Points",
draft-ietf-mpls-lsp-ping-registry-00 (work in progress),
November 2014.
[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.
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
February 2006. February 2006.
[RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and [RFC6790] Kompella, K., Drake, J., Amante, S., Henderickx, W., and
L. Yong, "The Use of Entropy Labels in MPLS Forwarding", L. Yong, "The Use of Entropy Labels in MPLS Forwarding",
RFC 6790, November 2012. RFC 6790, November 2012.
15.2. Informative References 15.2. Informative References
[I-D.decraene-mpls-lsp-ping-registry]
Decraene, B., Akiya, N., Pignataro, C., Andersson, L., and
S. Aldrin, "IANA registries for LSP ping Code Points",
draft-decraene-mpls-lsp-ping-registry-00 (work in
progress), October 2014.
[I-D.ietf-mpls-forwarding] [I-D.ietf-mpls-forwarding]
Villamizar, C., Kompella, K., Amante, S., Malis, A., and Villamizar, C., Kompella, K., Amante, S., Malis, A., and
C. Pignataro, "MPLS Forwarding Compliance and Performance C. Pignataro, "MPLS Forwarding Compliance and Performance
Requirements", draft-ietf-mpls-forwarding-09 (work in Requirements", draft-ietf-mpls-forwarding-09 (work in
progress), March 2014. progress), March 2014.
[I-D.ravisingh-mpls-el-for-seamless-mpls] [I-D.ravisingh-mpls-el-for-seamless-mpls]
Singh, R., Shen, Y., and J. Drake, "Entropy label for Singh, R., Shen, Y., and J. Drake, "Entropy label for
seamless MPLS", draft-ravisingh-mpls-el-for-seamless- seamless MPLS", draft-ravisingh-mpls-el-for-seamless-
mpls-02 (work in progress), July 2014. mpls-04 (work in progress), October 2014.
[IANA-MPLS-LSP-PING] [IANA-MPLS-LSP-PING]
IANA, "Multi-Protocol Label Switching (MPLS) Label IANA, "Multi-Protocol Label Switching (MPLS) Label
Switched Paths (LSPs) Ping Parameters", Switched Paths (LSPs) Ping Parameters",
<http://www.iana.org/assignments/mpls-lsp-ping-parameters/ <http://www.iana.org/assignments/mpls-lsp-ping-parameters/
mpls-lsp-ping-parameters.xhtml>. mpls-lsp-ping-parameters.xhtml>.
[RFC6391] Bryant, S., Filsfils, C., Drafz, U., Kompella, V., Regan, [RFC6391] Bryant, S., Filsfils, C., Drafz, U., Kompella, V., Regan,
J., and S. Amante, "Flow-Aware Transport of Pseudowires J., and S. Amante, "Flow-Aware Transport of Pseudowires
over an MPLS Packet Switched Network", RFC 6391, November over an MPLS Packet Switched Network", RFC 6391, November
 End of changes. 35 change blocks. 
49 lines changed or deleted 50 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/