[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: [mpls] =?gb2312?b?tPC4tDogIFtPU1BGXSAgILTwuLQ6ICA/PzogIFdHIExh?= =?gb2312?b?c3QgQ2FsbCBmb3IgIlNpZ25h
From: Xuxiaohu <xuxiaohu () huawei ! com>
Date: 2016-11-17 8:27:55
Message-ID: 1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB376D6 () NKGEML515-MBX ! china ! huawei ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Hi Jeff,
________________________________
·¢¼þÈË: Jeff Tantsura [jefftant.ietf@gmail.com]
·¢ËÍʱ¼ä: 2016Äê11Ô 17ÈÕ 16:20
ÊÕ¼þÈË: stephane.litkowski@orange.com; Xuxiaohu; Acee Lindem (acee)
³ËÍ: John E Drake; Shraddha Hegde; DECRAENE Bruno IMT/OLN; OSPF WG List; \
mpls@ietf.org Ö÷Ìâ: Re: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC \
using OSPF"
There¡¯s some confusion going on :)
In MPLS Entropy labels (RFC6790) only egress pops the ELI/EL, multiple ELI/EL pairs \
can only be present in hierarchical tunnels.
ELC work has been done keeping in mind SR and draft-ietf-mpls-spring-entropy-label \
where label stack depth decreases as packet traverses the network and hence transport \
node would have to pop ELI/EL with popping its own SID as in no case can ELI/EL be at \
the top of the stack since ELI is a reserved label (PHP and explicit cases are \
described in 6790).
[Xiaohu] please don't say that transport node would have to pop ELI/EI. It's the \
egress of the each LSP of the stacked LSP tunnel that pops ELI/EI immediately under \
that LSP.
Best regards,
Xiaohu
Cheers,
Jeff
From: <stephane.litkowski@orange.com>
Date: Thursday, November 17, 2016 at 00:03
To: Xuxiaohu <xuxiaohu@huawei.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, "Acee \
Lindem (acee)" <acee@cisco.com>
Cc: John Drake <jdrake@juniper.net>, Shraddha Hegde <shraddha@juniper.net>, DECRAENE \
Bruno IMT/OLN <bruno.decraene@orange.com>, "ospf@ietf.org" <ospf@ietf.org>, \
"mpls@ietf.org" <mpls@ietf.org>
Subject: RE: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
Right in case of LDP or RSVP because you have a single tunnel end to end but with SR, \
we have multiple small nested tunnels so some LSR in transit (from an end to end \
point of view) may be egress for one of the nested tunnel, so we need to care of \
ELI/EL here.
Let¡¯s consider this small topology:
I1 ¨C R1 ¨C R2 ¨CR3 - R4 - R5 ¨C R6 ¨C E1
All routers are ELC except R3.
If the optimal label stack that fits LSP constraint is for I1 to push \
{Adj_R6-E1,Node_R6,Node_R3,Node_R2} , I1 cannot insert an ELI/EL between Node_R6 and \
Node_R3 because R3 will not be able to process it.
After checking the draft, this point is mentioned in the example of pseudocode but \
not really in the text. We may need to enhance the text with a reminder even if this \
comes directly from RFC6790.
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Thursday, November 17, 2016 16:47
To: LITKOWSKI Stephane OBS/OINIS; Jeff Tantsura; Acee Lindem (acee)
Cc: John E Drake; Shraddha Hegde; DECRAENE Bruno IMT/OLN; OSPF WG List; mpls@ietf.org
Subject: ´ð¸´: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
If I understand the ELC concept as described in RFC6790 correctly, the ELC is only \
used to indicate that the advertising router acting as the egress of a given LSP is \
capable of removing the ELI/EL pair. It has nothing to do with whether or not transit \
routers are capable of performing EL-based LB.
Best regards,
Xiaohu
________________________________
·¢¼þÈË: stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> \
[stephane.litkowski@orange.com] ·¢ËÍʱ¼ä: 2016Äê11Ô 17ÈÕ 15:18
ÊÕ¼þÈË: Jeff Tantsura; Acee Lindem (acee)
³ËÍ: John E Drake; Shraddha Hegde; Xuxiaohu; DECRAENE Bruno IMT/OLN; OSPF WG List; \
mpls@ietf.org<mailto:mpls@ietf.org> Ö÷Ìâ: RE: [mpls] [OSPF] ´ð¸´: ??: WG Last Call \
for "Signalling ELC using OSPF" +1
But this makes me think that in the mpls entropy label draft, a router should not \
insert an ELI/EL at a position so the transit LSR is not ELC and will not be able to \
process it. I need to check if we are clear on this or not in the text.
From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Thursday, November 17, 2016 14:28
To: Acee Lindem (acee)
Cc: John E Drake; Shraddha Hegde; LITKOWSKI Stephane OBS/OINIS; Xuxiaohu; DECRAENE \
Bruno IMT/OLN; OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
+1
Regards,
Jeff
On Nov 17, 2016, at 14:18, Acee Lindem (acee) <acee@cisco.com<mailto:acee@cisco.com>> \
wrote: Thanks John!
I think we should use this reference and not try and come up with a more granular \
definition of what it means to support entropy labels.
Acee
From: John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>>
Date: Wednesday, November 16, 2016 at 6:56 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Shraddha Hegde \
<shraddha@juniper.net<mailto:shraddha@juniper.net>>, Stephane Litkowski \
<stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, Xiaohu Xu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>, Bruno Decraene \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, \
"mpls@ietf.org<mailto:mpls@ietf.org>" \
<mpls@ietf.org<mailto:mpls@ietf.org>>
Subject: RE: [OSPF] [mpls] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
Hi,
If a node supports Entropy Label it can push or pop the ELI/EL pair \
(https://tools.ietf.org/html/rfc6790#section-4).
Yours Irrespectively,
John
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Wednesday, November 16, 2016 4:10 PM
To: Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>; \
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>; Xuxiaohu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>; \
mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [OSPF] [mpls] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
Hi Shraddha,
From: Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>
Date: Wednesday, November 16, 2016 at 9:14 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Stephane Litkowski \
<stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>, Xiaohu Xu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>, Bruno Decraene \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, \
"mpls@ietf.org<mailto:mpls@ietf.org>" \
<mpls@ietf.org<mailto:mpls@ietf.org>>
Subject: RE: [OSPF] [mpls] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
Hi Acee,Stephane,Tiger Bruno
I see a lot of good discussion on the RLDC, and the capability of router to be able \
to load balance. One important point that is missing is the capability of a router to \
be able to remove <ELI, EL> as appropriate.This is very important for SR since the \
labels keep getting popped off at intermediate nodes and there is a possibility of \
top label being <ELI, EL> . If this <ELI, EL> gets exposed to a router which does not \
understand these labels then it can potentially cause problems.
In my opinion, the router must also indicate it¡¯s capability to be able to remove \
the <ELI, EL> From top of the stack if the ingress has inserted the <ELI, EL> at a \
position that exposes <ELI, EL> at the top of the Stack when the packet reaches this \
node. It is very much possible that a router is capable of load balancing And can \
read a certain label stack depth but cannot understand <ELI, EL> and is not capable \
of removing those labels from label stack.
Good point. I¡¯d thought that forwarding ASICs that are able to load-balance based on \
EL would also be able to remove <ELI, EL> if is it on the top of the label stack and \
we could include this in the EL capability. However, I would like hear from \
especially MPLS WG participants to verify this. In any case, this needs to be \
documented.
Thanks,
Acee
Rgds
Shraddha
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Wednesday, November 16, 2016 8:22 PM
To: stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>; Xuxiaohu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>; \
mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [OSPF] [mpls] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
Hi Stephane, Tiger, Bruno,
This is the way I interpret the capabilities.
- The Entropy Label (EL) Non-OSPF Functional Capability indicates whether or not \
the advertising OSPF router can load balance based on MPLS Entropy Labels (i.e., an \
>Entropy Label Indicator, Entropy Label>).
- The Readable Label Depth Capability (RLDC) indicates the maximum label depth \
(i.e., number of labels including the top of the label stack) the advertising OSPF \
router can examine in a received packet with an MPLS header. It is a generic \
capability and not restricted to Entropy Label processing. To process an entropy \
label, the <ELI, EL> tuple must be included in the the RLD for the \
receiving router.
- Whether or not an advertising OSPF Router can insert the <ELI, EL> tuple into \
a received packet is not currently specified. Segment routing will be the first \
application of RLDC as described above.
Thanks,
Acee
From: mpls <mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>> on behalf of \
Stephane Litkowski <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Monday, November 14, 2016 at 3:27 PM
To: Xiaohu Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>, Bruno Decraene \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, \
"mpls@ietf.org<mailto:mpls@ietf.org>" \
<mpls@ietf.org<mailto:mpls@ietf.org>>
Subject: Re: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
I think Bruno¡¯s point is to tell that if a router advertises that it can read up to \
x labels, it does not mean that it will take into account all labels between position \
1 and x when doing loadbalancing. This is implementation dependent. And even RFC6790 \
tells that looking for ELI is optional by using a ¡°MAY¡±. In addition, loadbalancing \
hash keys may be tuned on a node and not reflected in RLDC. A user may prefer to ask \
router to look at payload rather than hashing one or more MPLS labels.
Regards,
Stephane
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Xuxiaohu
Sent: Monday, November 14, 2016 21:16
To: DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>
Subject: [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using OSPF"
by the way, the RLD is just used to advertise how many labels can be read to the \
maximum extent. It's not used to indicate whether or not the EL-based LB capability \
is supported. In the EL-based LB approach, it doesn't require all LSRs along a given \
LSP to recoginize the ELI. In a word, the ingress of a given LSP tries to insert \
ELI/EL within the RLD of all LSRs along the LSP. If all LSRs are capable of \
performing EL-based BL, that's great. If some or even all LSRs are not capable of \
performing EL-based BL, that's fine.
Best regards,
Xiaohu
________________________________
·¢¼þÈË: mpls [mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] ´ú±í Xuxiaohu \
[xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>] ·¢ËÍʱ¼ä: 2016Äê11Ô 14ÈÕ 20:00
ÊÕ¼þÈË:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
³ËÍ: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>
Ö÷Ìâ: [mpls] ´ð¸´: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
Could you please explain why the defination of the RLDC should be specific to the LB \
behavior of the transit LSR?
If I understand correctly, it seems that the text proposed by you conflict with \
Acee's take (see blow):
" 1. The standards track IGP drafts should have a precise definition of RLD and so \
not require a normative reference to the MPLS entropy draft (which is informational). \
The IGP drafts need not precisely specify how the information is used - this can be \
specified via a reference to the MPLS draft. 2. The MPLS draft should precisely \
specify the initial use case of entropy label insertion at the ingress of the LSP. It \
should not limit the applicability of RLDC to this use case. "
Best regards,
Xiaohu
________________________________
·¢¼þÈË:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
[bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>] ·¢ËÍʱ¼ä: 2016Äê11Ô \
14ÈÕ 19:05 ÊÕ¼þÈË: DECRAENE Bruno IMT/OLN; Xuxiaohu
³ËÍ: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Ö÷Ìâ: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
I meant:
My concern is that the current definition of the RLDC ¡°the maximum label stack depth \
that the originating router can read¡± is not that specific to the load balancing \
behavior of the transit LSR.
Sorry for the spam
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of \
bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Sent: Monday, November 14, 2016 11:51 AM
To: Xuxiaohu
Cc: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Xiaohu,
Thanks for the proposed text.
My understanding is that the RLDC is intended to give information to the ingress \
node, to help him insert an ELI, EL pair at a given depth (or not) in order to \
improve the load-balancing on a transit LSR.
My concern is that the current definition of the RLDC ¡°the maximum label stack depth \
that the originating router can read¡± is not that specific to the load balancing \
capability of the transit LSR. cf the below example of a load balancing algo on one \
real world plateform Label <=3: 2-tuple <source IP(rightmost 30bit), destination IP \
(rightmost 30bit)> Label = 4: bottom-of-stack label (rightmost 20bit)
Label>=5: Fifth(rightmost 20bit) label from the top
In this case, even if the LSR can read 5 labels, advertising a RDLC of 5 gives a \
wrong or incomplete information to the ingress as it could understand \
that
- it could insert the EL anywhere in the 5 first labels; which is wrong as the EL \
would only provide a value if placed at the bottom of the stack
- inserting an EL in the first 5 labels would improve load-balancing; which, is wrong \
as inserting an (additional EL) could make the IP header not readable anymore hence \
even degrade the load balancing.
As already expressed, modeling the load-balancing behavior of a MPLS LSR would \
require more than the advertisement of a single value. However, to keep the change \
minimal, I would propose the following change
OLD: A new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined to \
advertise the capability of the router to read the maximum label \
stack depth....
NEW: This document defines a new TLV, called RLDC TLV, within the body of the OSPF RI \
LSA. RLDC value advertised is the label stack depth that the LSR will use to \
load-balance a MPLS packet. If an ELI, EL pair is within the RLDC, and the LSR is \
capable of recognizing the ELI, the LSR MUST use the entropy of the EL to \
load-balance the packet. If an ELI, EL pair is within the RLDC, and the LSR is not \
capable of recognizing the ELI, the LSR MUST either use the entropy of the whole \
stack of RLDC labels (hence including the EL label) or load-balance based on the \
below non-MPLS header (e.g. the IP header).
I¡¯m open to any different text or a different property, but the point is to \
advertise a _load_balancing_ property of the LSR.
In the above example, with this new definition, the plateform would advertise a RLDC \
of 0, even though it can read 5 labels.
Thanks
Bruno
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Sunday, November 13, 2016 1:48 PM
To: Acee Lindem (acee); DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
Subject: ??: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi all,
How about making the following two changes:
OLD:
"A new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined to \
advertise the capability of the router to read the maximum label stack depth....If a \
router has multiple linecards with different capabilities of reading the maximum \
label stack deepth, the router MUST advertise the smallest one in the RLDC TLV..."
NEW:
"A new TLV within the body of the OSPF RI LSA, called RLD TLV is defined to advertise \
the maximum label stack depth that the originating router can read (i.e., how many \
labels can the router read from the label stack of a given received MPLS packet to \
the maximum extent). How to use this RLD information is outside the scope of this \
draft... If a router has multiple line cards and the maximum label stack depths they \
can read are different, the originating router MUST advertise the smallest one in the \
RLD TLV..."
OLD:
"6<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6>. Usage and \
Applicability
The ELC is used by ingress LSRs to determine whether an EL could be
inserted into a given LSP tunnel. The RLDC is used by ingress LSRs
to determine whether it's necessary to insert an EL for a given LSP
tunnel in the case where there has already been at least one EL in
the label stack. This document only describes how to signal the ELC
and RLDC using OSPF. As for how to apply those capabilities when
inserting EL(s) into LSP tunnel(s), it's outside the scope of this
document and accordingly would be described in
[I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]."
NEW:
"6<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6>. Usage and \
Applicability
The ELC is used by ingress LSRs to determine whether an EL could be
inserted into a given LSP tunnel \
[I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>].
The RLD could be used by ingress LSRs
to determine whether it's necessary to insert an EL for a given LSP
tunnel in the case where there has already been at least one EL in
the label stack [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]." \
This document
only describes how to signal the ELC and RLD using OSPF. How to apply
them is outside the scope of this document."
Best regards,
Xiaohu
________________________________
·¢¼þÈË: Acee Lindem (acee) [acee@cisco.com<mailto:acee@cisco.com>]
·¢ËÍʱ¼ä: 2016Äê11Ô 13ÈÕ 6:08
ÊÕ¼þÈË: Xuxiaohu; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
³ËÍ: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
Ö÷Ìâ: Re: [OSPF] ´ð¸´: WG Last Call for "Signalling ELC using OSPF"
Hi Tiger, other authors,
So, this is my take on the draft information content based on the comments from \
Carlos and Bruno.
1. The standards track IGP drafts should have a precise definition of RLD and so \
not require a normative reference to the MPLS entropy draft (which is informational). \
The IGP drafts need not precisely specify how the information is used - this can be \
specified via a reference to the MPLS draft. 2. The MPLS draft should precisely \
specify the initial use case of entropy label insertion at the ingress of the LSP. It \
should not limit the applicability of RLDC to this use case.
Thanks,
Acee
From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Xiaohu \
Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Date: Friday, November 11, 2016 at 5:10 AM
To: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, \
"mpls@ietf.org<mailto:mpls@ietf.org>" <mpls@ietf.org<mailto:mpls@ietf.org>>, "Carlos \
Pignataro (cpignata)" <cpignata@cisco.com<mailto:cpignata@cisco.com>>
Subject: [OSPF] ´ð¸´: WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
·¢¼þÈË:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
[mailto:bruno.decraene@orange.com] ·¢ËÍʱ¼ä: 2016Äê11Ô 10ÈÕ 21:31
ÊÕ¼þÈË: Xuxiaohu
³ËÍ: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Ö÷Ìâ: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi Xuxiaohu,
The RLDC specification(s) needs to be clear enough such that:
- transit LSR knows what to advertise
[Xiaohu] LSRs advertise how many labels they could read from the top of the label \
stack. LSRs can advertise this information no matter whether or not they support \
EL-based LB.
- ingress LSR knows how to use it in order to achieve/optimize load balancing across \
the MPLS network.
[Xiaohu] This draft only describes how to advertise the RLDC via IGP. As for how to \
use this information by ingress LSRs when inserting EL pairs, it¡¯s discussed in \
Section 4 of draft-ietf-mpls-spring-entropy-label-04.
Best regards,
Xiaohu
So let¡¯s start with the first question: which RLDC value should be advertised by \
such transit LSR? (cf below) And please quote the text from the RDLC spec which \
supports the answer.
> From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
> However, it seems that it has nothing to do with the EL-based MPLS load-balancing \
> mechanism.
AFAIK, EL is defined in RFC6790, which defines a new behavior on the egress and \
ingress. It does not standardize the load-balancing behavior on transit nodes which \
are mostly free to do any load-balancing behavior. So it looks like hard to define an \
IGP TLV to advertise this non-standardized behavior, which is largely independent of \
the EL specification. IOW to re-use your terms, there is no such EL-based MPLS \
load-balancing specification for transit LSR. \
https://tools.ietf.org/html/rfc6790#section-4.3 Now, we (MPLS WG) can try to model \
the load-balancing behavior of MPLS LSR, so that we (IGP WG) can latter advertise the \
parameters of this model in the IGP. But from what I can see in existing product, the \
current RLDC seems insufficient to model the behavior of existing MPLS LSR. The \
current RLDC advertisement seems to be able to model a very small subset: a transit \
LSR which recognizes the ELI, and load balance solely on the following label (the \
EL). If so,
- this need to be clear in the RLDC specification, because currently this is not.
- this may be seen as an incremental improvement but I don¡¯t believe that it really \
solves the problem, nor significantly improve it given the behavior of existing \
plateform.
I¡¯d rather have a solution which is more generally applicable and provide a \
significant improvement. i.e. model the load-balancing behavior of most current and \
future MPLS LSR, and then advertise the parameters in the IGP. (including a model ID \
such that this can be improved in the future). I agree that this is more complex job.
Thanks,
Best regards,
Bruno
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Thursday, November 10, 2016 10:58 AM
To: DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Subject: ??: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
Thanks for sharing the following information. However, it seems that it has nothing \
to do with the EL-based MPLS load-balancing mechanism. The ELC and RLDC as described \
in draft-ietf-ospf-mpls-elc are applicable to the EL-based MPLS load-balancing \
mechanism.
Best regards,
Xiaohu
·¢¼þÈË:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
[mailto:bruno.decraene@orange.com] ·¢ËÍʱ¼ä: 2016Äê11Ô 10ÈÕ 16:56
ÊÕ¼þÈË: Xuxiaohu
³ËÍ: OSPF WG List; Carlos Pignataro (cpignata)
Ö÷Ìâ: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi all,
(Hopefully) For the benefit of the discussion, I¡¯m sharing a real world MPLS \
(transit LSR) load balancing algo on one plateform:
Label <=3: 2-tuple <source IP(rightmost 30bit), destination IP (rightmost 30bit)>
Label = 4: bottom-of-stack label (rightmost 20bit)
Label>=5: Fifth(rightmost 20bit) label from the top
This is a more or less random pick, and in general the behaviors are very diverse \
depending on the plateform (router, line card, os version, MPLS encapsulated \
traffic).
In general, it¡¯s not clear to me how the RLDC advertisement really helps the ingress \
to make an informed decision and improve the load balancing of its flow across the \
MPLS network, as the current advertisement seems a bit simplistic to me. More \
specifically, with the current definition of the RLDC, it¡¯s hard for me to guess \
which RLDC value should be advertised. So I would really expect interop issues and \
endless discussion about who is right.
Thanks,
Regards,
-- Bruno
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Thursday, November 10, 2016 5:29 AM
To: Carlos Pignataro (cpignata); DECRAENE Bruno IMT/OLN
Cc: OSPF WG List
Subject: ??: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi Carlos,
Thanks for your comments. Please see my response inline.
·¢¼þÈË: OSPF [mailto:ospf-bounces@ietf.org] ´ú±í Carlos Pignataro (cpignata)
·¢ËÍʱ¼ä: 2016Äê11Ô 8ÈÕ 23:20
ÊÕ¼þÈË: Bruno Decraene
³ËÍ: OSPF WG List
Ö÷Ìâ: Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Jumping a bit mid-thread, but with somewhat similar or related comments.
Summary: I am concerned with the lack of precision in the definitions and usage on \
these set of documents.
Acee, if this document needs to depend on Section 4 of \
draft-ietf-mpls-spring-entropy-label-04.txt, then the issue is compounded. I believe \
draft-ietf-mpls-spring-entropy-label-04has its own set of problems (for example, \
placing EL/ELI independent of whether the underlying Label is for a Node SID or a \
Segment SID is not optimum).
So the main question is: Is draft-ietf-ospf-mpls-elc-03 to be treated independently \
form draft-ietf-mpls-spring-entropy-label-04? That is a fundamental question for \
advancing and reviewing this/these doc(s). We have the advertisement of a capability \
¡ª what is it used for? Is it the right variable to advertise (based on the \
application using it)?
[Xiaohu] draft-ietf-ospf-mpls-elc-03 defines an approach of advertising the RLDC of \
an LSR via OSPF. The definition of the RLDC is described in the following text (i.e., \
each LSR's capability of reading the maximum label stack depth). As for how to use \
this capability, it¡¯s not limited by the draft although one use case (i.e., the \
application as described in Section 4 of draft-ietf-mpls-spring-entropy-label-04.txt) \
is mentioned in this draft.
Specifically, I think that RLDC is largely underspecified. The doc says:
"
it would be useful for ingress LSRs to know each LSR's capability of
reading the maximum label stack deepth. This capability, referred to
as Readable Label Deepth Capability (RLDC)
¡°
That definition simple does not make sense. And it does not explain the applicability \
(A, b, c, d).
[Xiaohu]Could you speak more specifically? Is the definition of the RLDC (i.e., what \
is the capability of reading the maximum label stack depth) itself not clear enough? \
If so, could you please suggestion any more specific text? Or the applicability of \
the RLDC not clear enough? If so, we co-authors currently only think about one use \
case of this RLDC that is described in Section 4 of \
draft-ietf-mpls-spring-entropy-label-04.txt) , please feel free to tell us if you \
find any other use cases of this RLDC.
Then the doc continues:
¡°
Readable Label Deepth Capability (RLDC) can be used by ingress
LSRs to determine whether it's necessary to insert an EL for a given
LSP tunnel in the case where there has already been at least one EL
in the label stack [I-D.ietf-mpls-spring-entropy-label] .
"
So this only is useful when there¡¯s an EL (I assume ELI/EL pair) already?
[Xiaohu] In the EL insertion use case, yes, your understand is correct.
And is ¡°[I-D.ietf-mpls-spring-entropy-label]¡± normative?
[Xiaohu] Currently yes, if it¡¯s widely believed that this reference should be \
informational, it can be moved to the informational reference section.
Overall, I think a WGLC is premature, since some basics are not well covered. Is it \
RLD or RLDC? And what exactly is a ¡°Readable Label Deepth Capability (RLDC)¡± The \
capability to do what? Is this a Capability or a scalar?
[Xiaohu] RLDC (Readable Label Deeth Capability) means a given LSR's capability of \
reading the maximum label stack depth. If it¡¯s widely believed that ¡°RLD¡± is more \
suitable than ¡°RLDC¡± from the expression perspective, it¡¯s fine to make a change.
Another point comment ¡ª although I think this needs a thorough review before WGLC.
The doc says:
Of course,
even it has been determined that it's neccessary to insert an EL for
a given LSP tunnel, if the egress LSR of that LSP tunnel has not yet
indicated that it can process ELs for that tunnel, the ingress LSR
MUST NOT include an entropy label for that tunnel as well.
This is good and consistent with RFC 6790:
c. X MUST NOT include an entropy label for a given tunnel unless the
egress LSR Y has indicated that it can process entropy labels for
that tunnel.
So it¡¯s better to point to it instead of re-MUST NOT independently.
[Xiaohu] Good suggestion. Will fix it.
But, what is the egress of a tunnel in this context? Not the final egress, but the \
SID egress. ?
[Xiaohu] IMHO, the egress of an LSP tunnel is clear enough and easy to understand. In \
contrast, what¡¯s the mean of SID egress, could you please help point to a reference \
for this term defincation?
Best regards,
Xiaohu
Thanks,
¡ª
Carlos Pignataro, carlos@cisco.com<mailto:carlos@cisco.com>
¡°Sometimes I use big words that I do not fully understand, to make myself sound more \
photosynthesis."
On Nov 8, 2016, at 6:15 AM, \
bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> wrote:
Hi Acee,
Thanks for your reply. Please see inline [Bruno]
From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Tuesday, November 08, 2016 2:27 AM
To: DECRAENE Bruno IMT/OLN; OSPF WG List
Subject: Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
From: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Monday, November 7, 2016 at 6:43 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, OSPF WG List \
<ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Hi authors, all,
Please find below some comments on the RLDC definition.
1) I¡¯d like to see a more specific definition of RLDC.
e.g. load-balancing hashing could be done based on (hashing):
-a- a (stack of) N ¡°regular¡± MPLS labels (i.e. there is no ELI in this stack)
-b- the (IP) header below the stack of N labels
-c- the EL label in the stack of N labels (i.e. there is one ELI in this stack)
I¡¯d like the specification to be clear on the applicability of the RLDC. Does it \
apply on these 3 cases, on only a subset? Personally, I¡¯d like at least a and c be \
in scope of the RLDC definition, such that an ingress with limited push capability \
could have enough information to decide that it could avoid pushing an ELI,EL pair if \
the stack of MPLS labels that it pushes has enough entropy within the first RLDC \
labels.
I think that the signaling document should reference section 4 of \
https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt. However, I \
don¡¯t think -b- is covered there. [Bruno] The above section 4 has indeed more \
details, but I¡¯m not certain that the definition is clear enough for everyone to \
agree on which ¡°a¡±, ¡°b¡±, ¡°c¡± cases are covered by the RLDC advertisement. My \
reading would be that ¡°a¡± and ¡°c¡± are covered, not ¡°b¡±. Reading your email, \
I¡¯d say that you have the same understanding. But it bothers me that one of the \
authors has a different understanding. \
Alsodraft-ietf-mpls-spring-entropy-label-04.txt is an informational document, so I¡¯m \
not sure how much it would qualify to be a normative definition of what \
draft-ietf-ospf-mpls-elc advertise.
Thanks,
Regards,
-- Bruno
2) Current text seems to limit the use of the RLDC to the insertion of a _second_ EL. \
Why is the RLD not applicable to the first EL?
¡ì1. Introduction
¡°This capability, referred to
as Readable Label Deepth Capability (RLDC) can be used by ingress
LSRs to determine whether it's necessary to insert an EL for a given
LSP tunnel in the case where there has already been at least one EL
in the label stack \
[I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]¡±
¡ì6 Usage and Applicability
¡°The RLDC is used by ingress LSRs
to determine whether it's necessary to insert an EL for a given LSP
tunnel in the case where there has already been at least one EL in
the label stack. >
I think that this is an unnecessary restriction of the RLDC usage. Indeed, an ingress \
with a limited capability in term of label push, could be forced to push a single EL \
label. It should be able to use the RLDC info in order to choose the best location \
for the EL, even if it pushes a single one. But both sentences seems to restrict RLDC \
usage for the additional EL push, not the first one.
I would tend to agree.
Thanks,
Acee
Thanks,
Regards,
--Bruno
From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, November 05, 2016 5:46 PM
To: OSPF WG List
Subject: [OSPF] WG Last Call for "Signalling ELC using OSPF"
This begins the WG last call for "Signalling ELC using OSPF¡±, \
https://www.ietf.org/id/draft-ietf-ospf-mpls-elc-03.txt. Please review the document \
and send comments to this list prior to Nov 27th, 2016. Due to the IETF week, the \
last call period is going to be 3 weeks rather than usual 2 weeks.
Thanks,
Acee
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_______________________________________________
OSPF mailing list
OSPF@ietf.org<mailto:OSPF@ietf.org>
https://www.ietf.org/mailman/listinfo/ospf
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou \
privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce \
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages \
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.
This message and its attachments may contain confidential or privileged information \
that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this \
message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.
Thank you.
[Attachment #3 (text/html)]
<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style>@font-face {
font-family: Courier New;
}
@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Consolas;
}
@font-face {
font-family: MS Mincho;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: SimSun;
}
@font-face {
font-family: PMingLiU;
}
@font-face {
font-family: MS Gothic;
}
@font-face {
font-family: MS UI Gothic;
}
@page WordSection1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.MsoNormal {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
A:link {
TEXT-DECORATION: underline; COLOR: blue
}
SPAN.MsoHyperlink {
TEXT-DECORATION: underline; COLOR: blue
}
A:visited {
TEXT-DECORATION: underline; COLOR: purple
}
SPAN.MsoHyperlinkFollowed {
TEXT-DECORATION: underline; COLOR: purple
}
PRE {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
P.MsoAcetate {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.MsoAcetate {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.MsoAcetate {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: Consolas
}
SPAN.BalloonTextChar {
FONT-FAMILY: Tahoma
}
P.msonormal0 {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.msonormal0 {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.msonormal0 {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
P.prformathtml {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.prformathtml {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.prformathtml {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
P.textedebulles {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.textedebulles {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.textedebulles {
FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
P.msochpdefault {
FONT-SIZE: 10pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
LI.msochpdefault {
FONT-SIZE: 10pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
DIV.msochpdefault {
FONT-SIZE: 10pt; FONT-FAMILY: "Times New Roman","serif"; MARGIN: 0in 0in 0pt
}
SPAN.htmlpreformattedchar0 {
FONT-FAMILY: Consolas
}
SPAN.balloontextchar0 {
FONT-FAMILY: Tahoma
}
SPAN.prformathtmlcar {
FONT-FAMILY: Consolas
}
SPAN.textedebullescar {
FONT-FAMILY: Tahoma
}
SPAN.htmlchar {
FONT-FAMILY: "Courier New"
}
SPAN.char {
FONT-FAMILY: SimSun
}
SPAN.prformathtmlcar0 {
FONT-FAMILY: "Courier New"
}
SPAN.textedebullescar0 {
FONT-FAMILY: Tahoma
}
SPAN.emailstyle25 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle26 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle27 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle28 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle29 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle30 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle31 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle37 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle38 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle42 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle43 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle44 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.emailstyle45 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.EmailStyle48 {
FONT-FAMILY: Calibri; COLOR: #1f497d
}
SPAN.EmailStyle49 {
FONT-FAMILY: Calibri; COLOR: windowtext
}
SPAN.msoIns {
TEXT-DECORATION: underline; COLOR: teal
}
.msochpdefault {
FONT-SIZE: 10pt
}
</style><style id="owaParaStyle">P {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
</style>
</head>
<body lang="EN-US" link="blue" bgcolor="white" vlink="purple" fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Hi Jeff,</p>
<p> </p>
<div style="FONT-SIZE: 16px; FONT-FAMILY: Times New Roman; COLOR: #000000">
<hr tabindex="-1">
<div id="divRpF475390" style="DIRECTION: ltr"><font color="#000000" size="2" \
face="Tahoma"><b>·¢¼þÈË:</b> Jeff Tantsura [jefftant.ietf@gmail.com]<br> \
<b>·¢ËÍʱ¼ä:</b> 2016Äê11Ô 17ÈÕ 16:20<br> <b>ÊÕ¼þÈË:</b> \
stephane.litkowski@orange.com; Xuxiaohu; Acee Lindem (acee)<br> <b>³ËÍ:</b> John E \
Drake; Shraddha Hegde; DECRAENE Bruno IMT/OLN; OSPF WG List; mpls@ietf.org<br> \
<b>Ö÷Ìâ:</b> Re: [mpls] [OSPF] ´ð¸´: ??: WG Last Call for "Signalling ELC using \
OSPF"<br> </font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">There¡¯s \
some confusion going on </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Wingdings">J</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri"></span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri">In MPLS Entropy labels (RFC6790) only egress pops the ELI/EL, \
multiple ELI/EL pairs can only be present in hierarchical tunnels.</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri">ELC work has been done keeping in mind SR and \
draft-ietf-mpls-spring-entropy-label where label stack depth decreases as packet \
traverses the network and hence transport node would have to pop ELI/EL with popping \
its own SID as in no case can ELI/EL be at the top of the stack since ELI is a \
reserved label (PHP and explicit cases are described in 6790).</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri">[Xiaohu] please don't say that transport node would have to pop \
ELI/EI. It's the egress of the each LSP of the stacked LSP tunnel that pops ELI/EI \
immediately under that LSP. </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri">Best regards,</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">Xiaohu</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri"></span><span \
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: black"></span> </p> <div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Cheers,</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; \
FONT-FAMILY: Calibri; COLOR: black">Jeff</span></p> </div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri"></span> </p> <div style="BORDER-TOP: #b5c4df 1pt solid; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in"> \
<p class="MsoNormal"><b><span style="FONT-FAMILY: Calibri; COLOR: black">From: \
</span> </b><span style="FONT-FAMILY: Calibri; COLOR: \
black"><stephane.litkowski@orange.com><br> <b>Date: </b>Thursday, November 17, \
2016 at 00:03<br> <b>To: </b>Xuxiaohu <xuxiaohu@huawei.com>, Jeff Tantsura \
<jefftant.ietf@gmail.com>, "Acee Lindem (acee)" \
<acee@cisco.com><br> <b>Cc: </b>John Drake <jdrake@juniper.net>, Shraddha \
Hegde <shraddha@juniper.net>, DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com>, "ospf@ietf.org" <ospf@ietf.org>, \
"mpls@ietf.org" <mpls@ietf.org><br> <b>Subject: </b>RE: [mpls] [OSPF] \
</span><span style="FONT-FAMILY: "MS Mincho"; COLOR: \
black">´ð¸´</span><span style="FONT-FAMILY: Calibri; COLOR: black">: ??: WG Last Call \
for "Signalling ELC using OSPF"</span></p> </div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Right in case of LDP or RSVP because you have a single tunnel end to end but \
with SR, we have multiple small nested tunnels so some LSR in transit (from an end to \
end point of view) may be egress for one of the nested tunnel, so we need to care of \
ELI/EL here.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d"></span> </p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Let¡¯s consider this \
small topology:</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">I1 ¨C R1 ¨C R2 ¨CR3 - R4 - R5 ¨C R6 ¨C \
E1</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d"></span> </p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">All routers are ELC \
except R3.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">If the optimal label stack that fits LSP constraint is for \
I1 to push {Adj_R6-E1,Node_R6,Node_R3,Node_R2} , I1 cannot insert an ELI/EL between \
Node_R6 and Node_R3 because R3 will not be able to process it.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">After checking the draft, this point is \
mentioned in the example of pseudocode but not really in the text. We may need to \
enhance the text with a reminder even if this comes directly from \
RFC6790.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d"></span> </p> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma">From:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma"> Xuxiaohu [mailto:xuxiaohu@huawei.com] <br>
<b>Sent:</b> Thursday, November 17, 2016 16:47<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; Jeff Tantsura; Acee Lindem (acee)<br>
<b>Cc:</b> John E Drake; Shraddha Hegde; DECRAENE Bruno IMT/OLN; OSPF WG List; \
mpls@ietf.org<br> <b>Subject:</b> </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
"MS UI Gothic"">´ð¸´</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma">: [mpls] [OSPF] </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"">´ð¸´</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">: ??: WG \
Last Call for "Signalling ELC using OSPF"</span></p> </div>
</div>
<p class="MsoNormal"> </p>
<div>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">If I understand \
the ELC concept as described in RFC6790 correctly, the ELC is only used to indicate \
that the advertising router acting as the egress of a given LSP is capable of \
removing the ELI/EL pair. It has nothing to do with whether or not transit routers \
are capable of performing EL-based LB. </span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"></span> </p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">Best \
regards,</span></p> <p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">Xiaohu</span></p> <div>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span style="COLOR: \
black"> <hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF478738">
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: PMingLiU; COLOR: black">·¢¼þÈË</span></b><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black"> <a href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a> [stephane.litkowski@orange.com]<br> \
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: \
black">·¢ËÍʱ¼ä</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black"> 2016</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">Äê</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">11</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">Ô </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">17</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">ÈÕ</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> 15:18<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> \
Jeff Tantsura; Acee Lindem (acee)<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">³ËÍ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> \
John E Drake; Shraddha Hegde; Xuxiaohu; DECRAENE Bruno IMT/OLN; OSPF WG List; <a \
href="mailto:mpls@ietf.org" target="_blank"> mpls@ietf.org</a><br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">Ö÷</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: \
black">Ìâ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> \
RE: [mpls] [OSPF] </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">+1</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">But this makes me think that in the mpls \
entropy label draft, a router should not insert an ELI/EL at a position so the \
transit LSR is not ELC and will not be able to process it. I need to check if we are \
clear on this or not in the text.</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black"> Jeff Tantsura [<a \
href="mailto:jefftant.ietf@gmail.com" \
target="_blank">mailto:jefftant.ietf@gmail.com</a>] <br>
<b>Sent:</b> Thursday, November 17, 2016 14:28<br>
<b>To:</b> Acee Lindem (acee)<br>
<b>Cc:</b> John E Drake; Shraddha Hegde; LITKOWSKI Stephane OBS/OINIS; Xuxiaohu; \
DECRAENE Bruno IMT/OLN; OSPF WG List; <a href="mailto:mpls@ietf.org" \
target="_blank">mpls@ietf.org</a><br> <b>Subject:</b> Re: [mpls] [OSPF] </span><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">´ð¸´</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">: \
??: WG Last Call for "Signalling ELC using OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p class="MsoNormal"><span style="COLOR: black">+1<br>
<br>
Regards,</span></p>
<div>
<p class="MsoNormal"><span style="COLOR: black">Jeff</span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><span style="COLOR: black"><br>
On Nov 17, 2016, at 14:18, Acee Lindem (acee) <<a href="mailto:acee@cisco.com" \
target="_blank">acee@cisco.com</a>> wrote:</span></p> </div>
<blockquote style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Thanks John!</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> I think we should use this \
reference and not try and come up with a more granular definition of what it means to \
support entropy labels. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Acee </span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">From: </span></b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">John E Drake <<a \
href="mailto:jdrake@juniper.net" target="_blank">jdrake@juniper.net</a>><br> \
<b>Date: </b>Wednesday, November 16, 2016 at 6:56 PM<br> <b>To: </b>Acee Lindem \
<<a href="mailto:acee@cisco.com" target="_blank">acee@cisco.com</a>>, Shraddha \
Hegde <<a href="mailto:shraddha@juniper.net" \
target="_blank">shraddha@juniper.net</a>>, Stephane Litkowski <<a \
href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a>>, Xiaohu Xu <<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">xuxiaohu@huawei.com</a>>, Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc: </b>OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>, "<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>><br> <b>Subject: \
</b>RE: [OSPF] [mpls] </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: "MS \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">If a node supports Entropy Label it can push or \
pop the ELI/EL pair (<a href="https://tools.ietf.org/html/rfc6790#section-4" \
target="_blank">https://tools.ietf.org/html/rfc6790#section-4</a>).</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Yours Irrespectively,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">John</span></p> </div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium \
none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue \
1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">From:</span></b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
<b>On Behalf Of </b>Acee Lindem (acee)<br> <b>Sent:</b> Wednesday, November 16, 2016 \
4:10 PM<br> <b>To:</b> Shraddha Hegde <<a href="mailto:shraddha@juniper.net" \
target="_blank">shraddha@juniper.net</a>>; <a \
href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a>; Xuxiaohu <<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">xuxiaohu@huawei.com</a>>; \
DECRAENE Bruno IMT/OLN <<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc:</b> OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>; <a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br> <b>Subject:</b> Re: \
[OSPF] [mpls] </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: "MS \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Hi Shraddha,</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">From: </span></b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">Shraddha Hegde <<a \
href="mailto:shraddha@juniper.net" target="_blank">shraddha@juniper.net</a>><br> \
<b>Date: </b>Wednesday, November 16, 2016 at 9:14 AM<br> <b>To: </b>Acee Lindem \
<<a href="mailto:acee@cisco.com" target="_blank">acee@cisco.com</a>>, Stephane \
Litkowski <<a href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a>>, Xiaohu Xu <<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">xuxiaohu@huawei.com</a>>, Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc: </b>OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>, "<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>><br> <b>Subject: \
</b>RE: [OSPF] [mpls] </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: "MS \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Acee,Stephane,Tiger Bruno</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">I see a lot of good discussion on the \
RLDC, and the capability of router to be able to load balance.</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">One important point that is missing is the capability of a router to be able \
to remove <ELI, EL></span></p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">as appropriate.This is very important for \
SR since the labels keep getting popped off at intermediate nodes</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">and there is a possibility of top label being <ELI, EL> . If this \
<ELI, EL> gets exposed to a router</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">which does not \
understand these labels then it can potentially cause problems.</span></p> </div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">In my opinion, the router must also indicate it¡¯s capability to be \
able to remove the <ELI, EL></span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">From top of the stack \
if the ingress has inserted the <ELI, EL> at a position that exposes <ELI, \
EL> at the top of the</span></p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Stack when the packet reaches this node. \
It is very much possible that a router is capable of load balancing</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">And can read a certain label stack depth but cannot understand <ELI, \
EL> and is not capable of removing those labels from label stack.</span></p> \
</div> </div>
</blockquote>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Good point. I¡¯d thought that forwarding ASICs that are able to load-balance \
based on EL would also be able to remove <ELI, EL> if is it on the top of the \
label stack and we could include this in the EL capability. However, I would like \
hear from especially MPLS WG participants to verify this. In any case, this needs to \
be documented. </span></p> </div>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Thanks,</span></p> </div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Acee </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Rgds</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Shraddha</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div>
<div style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">From:</span></b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
<b>On Behalf Of </b>Acee Lindem (acee)<br> <b>Sent:</b> Wednesday, November 16, 2016 \
8:22 PM<br> <b>To:</b> <a href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a>; Xuxiaohu <<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">xuxiaohu@huawei.com</a>>; \
DECRAENE Bruno IMT/OLN <<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc:</b> OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>; <a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br> <b>Subject:</b> Re: \
[OSPF] [mpls] </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: "MS \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Hi Stephane, Tiger, Bruno, </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">This is the way I interpret the capabilities. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black"> - The Entropy Label (EL) Non-OSPF Functional Capability \
indicates whether or not the advertising OSPF router can load balance based on MPLS \
Entropy Labels (i.e., an >Entropy Label Indicator, Entropy \
Label>). </span></p> </div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black"> - The Readable Label Depth Capability (RLDC) indicates the \
maximum label depth (i.e., number of labels including the top of the label stack) the \
advertising OSPF router can examine in a received packet with an MPLS header. It is \
a generic capability and not restricted to Entropy Label processing. To process an \
entropy label, the <ELI, EL> tuple must be included in the the RLD for the \
receiving router. </span></p> </div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black"> - Whether or not an advertising OSPF Router can insert the \
<ELI, EL> tuple into a received packet is not currently specified. \
Segment routing will be the first application of RLDC as described \
above. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Thanks, </span></p> </div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">Acee</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">From: </span></b><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: black">mpls <<a \
href="mailto:mpls-bounces@ietf.org" target="_blank">mpls-bounces@ietf.org</a>> on \
behalf of Stephane Litkowski <<a href="mailto:stephane.litkowski@orange.com" \
target="_blank">stephane.litkowski@orange.com</a>><br> <b>Date: </b>Monday, \
November 14, 2016 at 3:27 PM<br> <b>To: </b>Xiaohu Xu <<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">xuxiaohu@huawei.com</a>>, Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc: </b>OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>, "<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>><br> <b>Subject: \
</b>Re: [mpls] [OSPF] </span><span style="FONT-SIZE: 11pt; FONT-FAMILY: "MS \
Gothic"; COLOR: black">´ð¸´</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: black">: ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">I think Bruno¡¯s point is to tell that if a router advertises that it can \
read up to x labels, it does not mean that it will take into account all labels \
between position 1 and x when doing loadbalancing. This is implementation dependent. \
And even RFC6790 tells that looking for ELI is optional by using a \
¡°MAY¡±.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">In addition, loadbalancing hash keys may be tuned on a node \
and not reflected in RLDC. A user may prefer to ask router to look at payload rather \
than hashing one or more MPLS labels.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Regards,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Stephane</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
<b>On Behalf Of </b>Xuxiaohu<br> <b>Sent:</b> Monday, November 14, 2016 21:16<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org" \
target="_blank">mpls@ietf.org</a><br> <b>Subject:</b> [OSPF] </span><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">´ð¸´</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">: \
??: WG Last Call for "Signalling ELC using OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">by the \
way, the RLD is just used to advertise how many labels can be read to the maximum \
extent. It's not used to indicate whether or not the EL-based LB capability is \
supported. In the EL-based LB approach, it doesn't require all LSRs along a given \
LSP to recoginize the ELI. In a word, the ingress of a given LSP tries to \
insert ELI/EL within the RLD of all LSRs along the LSP. If all LSRs are capable \
of performing EL-based BL, that's great. If some or even all LSRs are not capable of \
performing EL-based BL, that's fine.</span></p> <p><span style="COLOR: \
black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">Best regards,</span></p> <p><span lang="FR" style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">Xiaohu</span></p> <p><span style="COLOR: \
black"></span> </p> <div>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span lang="FR" \
style="COLOR: black"> <hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF23556">
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: PMingLiU; COLOR: black">·¢¼þÈË</span></b><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> mpls [<a \
href="mailto:mpls-bounces@ietf.org" target="_blank">mpls-bounces@ietf.org</a>] \
</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">´ú±í</span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black"> Xuxiaohu [<a href="mailto:xuxiaohu@huawei.com" \
target="_blank">xuxiaohu@huawei.com</a>]<br> </span><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: PMingLiU; COLOR: black">·¢ËÍʱ¼ä</span></b><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> \
2016</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; \
COLOR: black">Äê</span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">11</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">Ô </span><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black">14</span><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "MS UI Gothic"; COLOR: black">ÈÕ</span><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> 20:00<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black"><a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a><br> </span><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: black">³ËÍ</span></b><b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black"> OSPF WG List; <a href="mailto:mpls@ietf.org" \
target="_blank">mpls@ietf.org</a><br> </span><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "MS UI Gothic"; COLOR: black">Ö÷</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: black">Ìâ</span></b><b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black"> [mpls] </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">´ð¸´</span><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black">: [OSPF] ??: WG Last Call for "Signalling ELC \
using OSPF"</span></p> </div>
<div>
<div>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">Hi \
Bruno,</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">Could \
you please explain why the defination of the RLDC should be specific to the LB \
behavior of the transit LSR?</span></p> <p><span style="COLOR: \
black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">If I understand correctly, it seems that the text proposed by \
you conflict with Acee's take (see blow):</span></p> <p><span style="COLOR: \
black"></span> </p> <div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black">" 1. The \
standards track IGP drafts should have a precise definition of RLD and so not require \
a normative reference to the MPLS entropy draft (which is informational). The IGP \
drafts need not precisely specify how the information is used - this can be \
specified via a reference to the MPLS draft. </span></p> </div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black"> 2. The MPLS \
draft should precisely specify the initial use case of entropy label insertion at the \
ingress of the LSP. It should not limit the applicability of RLDC to this use \
case. "</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span lang="FR" style="COLOR: \
black">Best regards,</span></p> <p class="MsoNormal"><span lang="FR" style="COLOR: \
black">Xiaohu</span></p> </div>
<p><span style="COLOR: black"></span> </p>
<p><span style="COLOR: black"></span> </p>
<div>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span lang="FR" \
style="COLOR: black"> <hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF501063">
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: PMingLiU; COLOR: black">·¢¼þÈË</span></b><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"><a \
href="mailto:bruno.decraene@orange.com" target="_blank">bruno.decraene@orange.com</a> \
[<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>]<br> </span><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: PMingLiU; COLOR: black">·¢ËÍʱ¼ä</span></b><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> \
2016</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; \
COLOR: black">Äê</span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">11</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI \
Gothic"; COLOR: black">Ô </span><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black">14</span><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "MS UI Gothic"; COLOR: black">ÈÕ</span><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> 19:05<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black"> DECRAENE Bruno IMT/OLN; Xuxiaohu<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">³ËÍ</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> OSPF WG List; Carlos Pignataro (cpignata); <a \
href="mailto:mpls@ietf.org" target="_blank"> mpls@ietf.org</a><br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">Ö÷</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: \
black">Ìâ</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> RE: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">I meant:</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">My concern is that the current definition of \
the RLDC ¡°</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">the maximum label stack depth that the originating router can read¡± \
</span><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">is not \
that specific to the load balancing behavior of the transit LSR.</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Sorry for the spam</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
<b>On Behalf Of </b><a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a><br> <b>Sent:</b> Monday, November 14, \
2016 11:51 AM<br> <b>To:</b> Xuxiaohu<br>
<b>Cc:</b> OSPF WG List; Carlos Pignataro (cpignata); <a href="mailto:mpls@ietf.org" \
target="_blank"> mpls@ietf.org</a><br>
<b>Subject:</b> Re: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Xiaohu,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks for the proposed text.</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">My understanding is that the RLDC is intended to give information to the \
ingress node, to help him insert an ELI, EL pair at a given depth (or not) in \
order to improve the load-balancing on a transit LSR.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">My concern is that the current definition of the RLDC ¡°</span><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">the maximum label \
stack depth that the originating router can read¡± </span><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">is not that specific to the load \
balancing capability of the transit LSR.</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">cf the below example of \
a load balancing algo on one real world plateform</span></p> <p class="MsoNormal" \
style="MARGIN-LEFT: 35.4pt"><span style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier \
New"; COLOR: black">Label <=3: 2-tuple <source IP(rightmost 30bit), \
destination IP (rightmost 30bit)></span></p> <p class="MsoNormal" \
style="MARGIN-LEFT: 35.4pt"><span style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier \
New"; COLOR: black">Label = 4: bottom-of-stack label (rightmost \
20bit)</span></p> <p class="MsoNormal" style="MARGIN-LEFT: 35.4pt"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier New"; COLOR: \
black">Label>=5: Fifth(rightmost 20bit) label from the top</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">In this case, even if the LSR can read 5 labels, advertising a RDLC of 5 \
gives a wrong or incomplete information to the ingress as it could understand \
that</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">- it could insert the EL anywhere in the 5 first labels; \
which is wrong as the EL would only provide a value if placed at the bottom of \
the stack</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">- inserting an EL in the first 5 labels would improve \
load-balancing; which, is wrong as inserting an (additional EL) could make the IP \
header not readable anymore hence even degrade the load balancing.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">As already expressed, modeling the load-balancing behavior of a MPLS LSR \
would require more than the advertisement of a single value. However, to keep the \
change minimal, I would propose the following change</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">OLD: </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">A new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined \
to advertise the capability of the router to read the maximum label stack \
depth....</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">NEW:</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> This document defines a new TLV, called RLDC TLV, within the \
body of the OSPF RI LSA. RLDC value advertised is the label stack depth that the LSR \
will use to load-balance a MPLS packet. If an ELI, EL pair is within the RLDC, and \
the LSR is capable of recognizing the ELI, the LSR MUST use the entropy of the EL to \
load-balance the packet. If an ELI, EL pair is within the RLDC, and the LSR is \
not capable of recognizing the ELI, the LSR MUST either use the entropy of the whole \
stack of RLDC labels (hence including the EL label) or load-balance based on the \
below non-MPLS header (e.g. the IP header).</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">I¡¯m open to any different text or a \
different property, but the point is to advertise a _<i>load_balancing</i>_ property \
of the LSR.</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">In the above example, with this new definition, \
the plateform would advertise a RLDC of 0, even though it can read 5 \
labels.</span></p> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Thanks</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Bruno</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <div style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: \
0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black"> Xuxiaohu [<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">mailto:xuxiaohu@huawei.com</a>] \
<br> <b>Sent:</b> Sunday, November 13, 2016 1:48 PM<br>
<b>To:</b> Acee Lindem (acee); DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org" \
target="_blank">mpls@ietf.org</a>; Carlos Pignataro (cpignata)<br> <b>Subject:</b> \
??: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"</span></p> \
</div> </div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">Hi \
all,</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">How \
about making the following two changes:</span></p> <p><span style="COLOR: \
black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">OLD:</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">"A \
new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined to \
advertise the capability of the router to read the maximum label stack \
depth....If a router has multiple linecards with different capabilities of \
reading the maximum label stack deepth, the router MUST advertise the smallest \
one in the RLDC TLV..."</span></p> <p><span style="COLOR: \
black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">NEW:</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">"A \
new TLV within the body of the OSPF RI LSA, called RLD TLV is defined to \
advertise the maximum label stack depth that the originating router can read \
(i.e., how many labels can the router read from the label stack of a given received \
MPLS packet to the maximum extent). How to use this RLD information is \
outside the scope of this draft... If a router has multiple line \
cards and the maximum label stack depths they can read are different, \
the originating router MUST advertise the smallest one in the RLD \
TLV..."</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">OLD:</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">"<span class="h2"><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6" \
target="_blank"><span style="COLOR: black">6</span></a>. Usage and \
Applicability</span><br> <br>
The ELC is used by ingress LSRs to determine whether an EL could be<br>
inserted into a given LSP tunnel. The RLDC is used by ingress \
LSRs<br> to determine whether it's necessary to insert an EL for a given \
LSP<br> tunnel in the case where there has already been at least one EL \
in<br> the label stack. This document only describes how to signal \
the ELC<br> and RLDC using OSPF. As for how to apply those \
capabilities when<br> inserting EL(s) into LSP tunnel(s), it's outside \
the scope of this<br> document and accordingly would be described in<br>
[<a href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label" \
target="_blank"><span style="COLOR: \
#0066cc">I-D.ietf-mpls-spring-entropy-label</span></a>]."</span></p> <p><span \
style="COLOR: black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black">NEW:</span></p> <p><span style="COLOR: \
black"></span> </p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">"<a name="section-6"></a><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6" \
target="_blank"><span style="COLOR: black">6</span></a><span class="h2">. Usage \
and Applicability</span><br> <br>
The ELC is used by ingress LSRs to determine whether an EL could be<br>
inserted into a given LSP tunnel [<a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label" \
target="_blank"><span style="COLOR: \
#0066cc">I-D.ietf-mpls-spring-entropy-label</span></a>]. </span></p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black"> The RLD could be used by ingress LSRs<br> \
to determine whether it's necessary to insert an EL for a given LSP<br> \
tunnel in the case where there has already been at least one EL in<br> \
the label stack [<a href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label" \
target="_blank"><span style="COLOR: \
#0066cc">I-D.ietf-mpls-spring-entropy-label</span></a>]." This \
document </span></p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black"> only describes how to signal the ELC and RLD using OSPF. \
How to apply</span></p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> them is outside the scope of \
this document."</span></p> <p><span style="COLOR: black"></span> </p>
<p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">Best \
regards,</span></p> <p><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">Xiaohu</span></p> <p><span style="COLOR: black"></span> </p>
<div>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span lang="FR" \
style="COLOR: black"> <hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF768477">
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: PMingLiU; COLOR: black">·¢¼þÈË</span></b><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> Acee Lindem \
(acee) [<a href="mailto:acee@cisco.com" target="_blank">acee@cisco.com</a>]<br> \
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: \
black">·¢ËÍʱ¼ä</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black"> 2016</span><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "MS UI Gothic"; COLOR: black">Äê</span><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">11</span><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: black">Ô \
</span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">13</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; \
COLOR: black">ÈÕ</span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black"> 6:08<br>
</span><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: Tahoma; COLOR: black"> Xuxiaohu; <a \
href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a><br> </span><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: black">³ËÍ</span></b><b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black"> OSPF WG List; <a href="mailto:mpls@ietf.org" \
target="_blank">mpls@ietf.org</a>; Carlos Pignataro (cpignata)<br> </span><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "MS UI Gothic"; COLOR: \
black">Ö÷</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: PMingLiU; COLOR: \
black">Ìâ</span></b><b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; \
COLOR: black">:</span></b><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma; COLOR: black"> Re: [OSPF] </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
"MS UI Gothic"; COLOR: black">´ð¸´</span><span lang="FR" style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">: WG Last Call for "Signalling ELC \
using OSPF"</span></p> </div>
<div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black">Hi Tiger, other \
authors, </span></p> </div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black">So, this is my take on the \
draft information content based on the comments from Carlos and \
Bruno. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black"> 1. The \
standards track IGP drafts should have a precise definition of RLD and so not require \
a normative reference to the MPLS entropy draft (which is informational). The IGP \
drafts need not precisely specify how the information is used - this can be \
specified via a reference to the MPLS draft. </span></p> </div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black"> 2. The MPLS \
draft should precisely specify the initial use case of entropy label insertion at the \
ingress of the LSP. It should not limit the applicability of RLDC to this use \
case. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black">Thanks,</span></p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="COLOR: black">Acee</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: black">From: </span></b><span \
lang="FR" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: black">OSPF <<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">ospf-bounces@ietf.org</a>> on \
behalf of Xiaohu Xu <<a href="mailto:xuxiaohu@huawei.com" \
target="_blank">xuxiaohu@huawei.com</a>><br> <b>Date: </b>Friday, November 11, \
2016 at 5:10 AM<br> <b>To: </b>Bruno Decraene <<a \
href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Cc: </b>OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>>, "<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>>, "Carlos \
Pignataro (cpignata)" <<a href="mailto:cpignata@cisco.com" \
target="_blank">cpignata@cisco.com</a>><br> <b>Subject: </b>[OSPF] </span><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: "MS Gothic"; COLOR: \
black">´ð¸´</span><span lang="FR" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; \
COLOR: black">: WG Last Call for "Signalling ELC using OSPF"</span></p> \
</div> <div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Bruno,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="ZH-CN" \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">·¢¼þÈË</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">:</span></b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"><a \
href="mailto:bruno.decraene@orange.com" target="_blank">bruno.decraene@orange.com</a> \
[<a href="mailto:bruno.decraene@orange.com" \
target="_blank">mailto:bruno.decraene@orange.com</a>] <br>
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">·¢ËÍʱ¼ä</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black"> 2016</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">Äê</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">11</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">Ô </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">10</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">ÈÕ</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black"> 21:31<br>
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> \
Xuxiaohu<br> </span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: \
SimSun; COLOR: black">³ËÍ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
SimSun; COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black"> OSPF WG List; Carlos Pignataro (cpignata); <a \
href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br> </span><b><span \
lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">Ö÷Ìâ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> \
RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"</span></p>
</div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Xuxiaohu,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">The RLDC specification(s) needs to be clear \
enough such that:</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">- transit LSR knows what to \
advertise</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 16pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">[Xiaohu] LSRs advertise how many labels they \
could read from the top of the label stack. LSRs can advertise this information no \
matter whether or not they support EL-based LB.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">- ingress LSR knows how to use it in order to achieve/optimize load \
balancing across the MPLS network.</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
16pt; FONT-FAMILY: Calibri; COLOR: #1f497d">[Xiaohu] This draft only describes how to \
advertise the RLDC via IGP. As for how to use this information by ingress LSRs when \
inserting EL pairs, it¡¯s discussed in Section 4 of \
draft-ietf-mpls-spring-entropy-label-04.</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
16pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Best regards,</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Xiaohu</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">So let¡¯s start with the first question: which \
RLDC value should be advertised by such transit LSR? (cf below) And please quote the \
text from the RDLC spec which supports the answer.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black">> From:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: \
black"> Xuxiaohu [<a href="mailto:xuxiaohu@huawei.com" \
target="_blank">mailto:xuxiaohu@huawei.com</a>]</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">> However, it seems \
that it has nothing to do with the EL-based MPLS load-balancing mechanism.</span></p> \
<p class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">AFAIK, EL is defined in RFC6790, which defines a new behavior on the egress \
and ingress. It does not standardize the load-balancing behavior on transit nodes \
which are mostly free to do any load-balancing behavior. So it looks like hard to \
define an IGP TLV to advertise this non-standardized behavior, which is largely \
independent of the EL specification. IOW to re-use your terms, there is no such \
EL-based MPLS load-balancing specification for transit LSR.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d"><a href="https://tools.ietf.org/html/rfc6790#section-4.3" \
target="_blank">https://tools.ietf.org/html/rfc6790#section-4.3</a></span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Now, we (MPLS WG) can try to model the load-balancing behavior of MPLS LSR, \
so that we (IGP WG) can latter advertise the parameters of this model in the IGP. But \
from what I can see in existing product, the current RLDC seems insufficient to \
model the behavior of existing MPLS LSR.</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">The current RLDC \
advertisement seems to be able to model a very small subset: a transit LSR which \
recognizes the ELI, and load balance solely on the following label (the \
EL).</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">If so,</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">- this need to be clear \
in the RLDC specification, because currently this is not.</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">- this may be seen as an incremental improvement but I don¡¯t believe that \
it really solves the problem, nor significantly improve it given the behavior of \
existing plateform.</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">I¡¯d rather have a solution which is more \
generally applicable and provide a significant improvement. i.e. model the \
load-balancing behavior of most current and future MPLS LSR, and then advertise the \
parameters in the IGP. (including a model ID such that this can be improved in the \
future). I agree that this is more complex job.</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks,</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Best regards,</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Bruno</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> Xuxiaohu [<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">mailto:xuxiaohu@huawei.com</a>] \
<br> <b>Sent:</b> Thursday, November 10, 2016 10:58 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; Carlos Pignataro (cpignata); <a href="mailto:mpls@ietf.org" \
target="_blank"> mpls@ietf.org</a><br>
<b>Subject:</b> ??: [OSPF] WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Bruno,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 16pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks for sharing the following information. \
However, it seems that it has nothing to do with the EL-based MPLS load-balancing \
mechanism. The ELC and RLDC as described in draft-ietf-ospf-mpls-elc are applicable \
to the EL-based MPLS load-balancing mechanism.</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
16pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Best regards,</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Xiaohu</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="ZH-CN" \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">·¢¼þÈË</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">:</span></b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"><a \
href="mailto:bruno.decraene@orange.com" target="_blank">bruno.decraene@orange.com</a> \
[<a href="mailto:bruno.decraene@orange.com" \
target="_blank">mailto:bruno.decraene@orange.com</a>] <br>
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">·¢ËÍʱ¼ä</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black"> 2016</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">Äê</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">11</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">Ô </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">10</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">ÈÕ</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black"> 16:56<br>
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">ÊÕ¼þÈË</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> \
Xuxiaohu<br> </span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: \
SimSun; COLOR: black">³ËÍ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
SimSun; COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black"> OSPF WG List; Carlos Pignataro (cpignata)<br>
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">Ö÷Ìâ</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> \
RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"</span></p>
</div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; \
COLOR: #1f497d">Hi all,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">(Hopefully) For the benefit of the discussion, \
I¡¯m sharing a real world MPLS (transit LSR) load balancing algo on one \
plateform:</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal" style="MARGIN-LEFT: 35.4pt"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier New"; COLOR: black">Label \
<=3: 2-tuple <source IP(rightmost 30bit), destination IP (rightmost \
30bit)></span></p> <p class="MsoNormal" style="MARGIN-LEFT: 35.4pt"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier New"; COLOR: black">Label = \
4: bottom-of-stack label (rightmost 20bit)</span></p> <p class="MsoNormal" \
style="MARGIN-LEFT: 35.4pt"><span style="FONT-SIZE: 11pt; FONT-FAMILY: "Courier \
New"; COLOR: black">Label>=5: Fifth(rightmost 20bit) label from the \
top</span></p> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">This is a more or less random pick, and in general the behaviors are very \
diverse depending on the plateform (router, line card, os version, MPLS encapsulated \
traffic).</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">In general, it¡¯s not clear to me how the RLDC \
advertisement really helps the ingress to make an informed decision and improve the \
load balancing of its flow across the MPLS network, as the current advertisement \
seems a bit simplistic to me.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">More specifically, with the current \
definition of the RLDC, it¡¯s hard for me to guess which RLDC value should be \
advertised. So I would really expect interop issues and endless discussion about who \
is right. </span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks,</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">Regards,</span></p> <p \
class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">-- Bruno</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> Xuxiaohu [<a \
href="mailto:xuxiaohu@huawei.com" target="_blank">mailto:xuxiaohu@huawei.com</a>] \
<br> <b>Sent:</b> Thursday, November 10, 2016 5:29 AM<br>
<b>To:</b> Carlos Pignataro (cpignata); DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List<br>
<b>Subject:</b> ??: [OSPF] WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Carlos,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 16pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks for your comments. Please see my \
response inline.</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <div style="BORDER-TOP: medium none; BORDER-RIGHT: medium \
none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; \
PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="ZH-CN" \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">·¢¼þÈË</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">:</span></b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
</span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">´ú±í </span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">Carlos Pignataro (cpignata)<br> </span><b><span lang="ZH-CN" style="FONT-SIZE: \
10pt; FONT-FAMILY: SimSun; COLOR: black">·¢ËÍʱ¼ä</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">:</span></b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> 2016</span><span \
lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">Äê</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">11</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">Ô </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">8</span><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black">ÈÕ</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> \
23:20<br> </span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">ÊÕ¼þÈË</span></b><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; \
COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: \
black"> Bruno Decraene<br> </span><b><span lang="ZH-CN" style="FONT-SIZE: 10pt; \
FONT-FAMILY: SimSun; COLOR: black">³ËÍ</span></b><b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: SimSun; COLOR: black">:</span></b><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: SimSun; COLOR: black"> OSPF WG List<br> </span><b><span lang="ZH-CN" \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">Ö÷Ìâ</span></b><b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black">:</span></b><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: SimSun; COLOR: black"> Re: [OSPF] WG Last Call \
for "Signalling ELC using OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="COLOR: black">Jumping a bit mid-thread, but with \
somewhat similar or related comments. </span></p>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Summary: I am concerned with the lack \
of precision in the definitions and usage on these set of documents. </span></p> \
<div> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Acee, if this document needs to \
depend on Section 4 of draft-ietf-mpls-spring-entropy-label-04.txt, then the issue is \
compounded. I believe draft-ietf-mpls-spring-entropy-label-04has its own set of \
problems (for example, placing EL/ELI independent of whether the underlying Label is \
for a Node SID or a Segment SID is not optimum).</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">So the main question is: Is \
draft-ietf-ospf-mpls-elc-03 to be treated independently form \
draft-ietf-mpls-spring-entropy-label-04? That is a fundamental question for advancing \
and reviewing this/these doc(s). We have the advertisement of a capability ¡ª what \
is it used for? Is it the right variable to advertise (based on the application using \
it)?</span></p> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">[Xiaohu] draft-ietf-ospf-mpls-elc-03 defines an approach of advertising the \
RLDC of an LSR via OSPF. The definition of the RLDC is described in the following \
text (i.e., each LSR's capability of reading the maximum label stack depth). As for \
how to use this capability, it¡¯s not limited by the draft although one use case \
(i.e., the application as described in Section 4 of \
draft-ietf-mpls-spring-entropy-label-04.txt) is mentioned in this draft.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Specifically, I think that RLDC is \
largely underspecified. The doc says:</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black">"</span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> it would be useful for \
ingress LSRs to know each LSR's capability of</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> reading the maximum \
label stack deepth. This capability, referred to</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> as Readable Label Deepth \
Capability (RLDC) </span></p> </div>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">¡°</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">That definition simple does not make \
sense. And it does not explain the applicability (A, b, c, d).</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">[Xiaohu]Could you speak more specifically? Is the definition of the RLDC \
(i.e., what is the capability of reading the maximum label stack depth) itself not \
clear enough? If so, could you please suggestion any more specific text? Or the \
applicability of the RLDC not clear enough? If so, we co-authors currently only think \
about one use case of this RLDC that is described in Section 4 of \
draft-ietf-mpls-spring-entropy-label-04.txt) , please feel free to tell us if you \
find any other use cases of this RLDC.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Then the doc continues:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">¡°</span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> Readable Label Deepth \
Capability (RLDC) can be used by ingress</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> LSRs to determine \
whether it's necessary to insert an EL for a given</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> LSP tunnel in the case \
where there has already been at least one EL</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> in the label stack \
[I-D.ietf-mpls-spring-entropy-label] .</span></p> </div>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">"</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">So this only is useful when there¡¯s \
an EL (I assume ELI/EL pair) already? </span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
16pt; FONT-FAMILY: Calibri; COLOR: #1f497d">[Xiaohu] In the EL insertion use case, \
yes, your understand is correct.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">And is \
¡°[I-D.ietf-mpls-spring-entropy-label]¡± normative?</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">[Xiaohu] Currently yes, if it¡¯s widely believed that this reference should \
be informational, it can be moved to the informational reference section. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Overall, I think a WGLC is premature, \
since some basics are not well covered. Is it RLD or RLDC? And what exactly is a \
¡°Readable Label Deepth Capability (RLDC)¡± The capability to do what? Is this a \
Capability or a scalar?</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">[Xiaohu] RLDC (Readable Label Deeth Capability) means a given LSR's \
capability of reading the maximum label stack depth. If it¡¯s widely believed that \
¡°RLD¡± is more suitable than ¡°RLDC¡± from the expression perspective, it¡¯s fine \
to make a change.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Another point comment ¡ª although I \
think this needs a thorough review before WGLC.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">The doc says:</span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> Of course,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> even it has been \
determined that it's neccessary to insert an EL for</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> a given LSP tunnel, if \
the egress LSR of that LSP tunnel has not yet</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> indicated that it can \
process ELs for that tunnel, the ingress LSR</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> MUST NOT include an \
entropy label for that tunnel as well.</span></p> </div>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">This is good and consistent with RFC \
6790:</span></p> </div>
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> c. X MUST NOT \
include an entropy label for a given tunnel unless the</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> egress LSR \
Y has indicated that it can process entropy labels for</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"> that \
tunnel.</span></p> </div>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">So it¡¯s better to point to it \
instead of re-MUST NOT independently.</span></p> <p class="MsoNormal"><span \
style="COLOR: black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: \
16pt; FONT-FAMILY: Calibri; COLOR: #1f497d">[Xiaohu] Good suggestion. Will fix \
it.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">But, what is the egress of a tunnel \
in this context? Not the final egress, but the SID egress. ?</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <p \
class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">[Xiaohu] IMHO, the egress of an LSP tunnel is clear enough and easy to \
understand. In contrast, what¡¯s the mean of SID egress, could you please help point \
to a reference for this term defincation?</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 16pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Best regards,</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 16pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Xiaohu</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Thanks,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="COLOR: black">¡ª</span></p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black">Carlos Pignataro, <a \
href="mailto:carlos@cisco.com" target="_blank">carlos@cisco.com</a><br> <br>
<i>¡°Sometimes I use big words that I do not fully understand, to make myself sound \
more photosynthesis."</i></span></p> </div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<blockquote style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<div>
<p class="MsoNormal"><span style="COLOR: black">On Nov 8, 2016, at 6:15 AM, <a \
href="mailto:bruno.decraene@orange.com" target="_blank"> \
bruno.decraene@orange.com</a> wrote:</span></p> </div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi Acee,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Thanks for your reply. Please see inline \
[Bruno]</span></p> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium \
none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue \
1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma; COLOR: black"> Acee Lindem \
(acee) [<a href="mailto:acee@cisco.com" target="_blank">mailto:acee@cisco.com</a>] \
<br> <b>Sent:</b> Tuesday, November 08, 2016 2:27 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; OSPF WG List<br>
<b>Subject:</b> Re: [OSPF] WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">Hi Bruno, </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span lang="FR" \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: black">From: </span></b><span \
lang="FR" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: black">Bruno Decraene \
<<a href="mailto:bruno.decraene@orange.com" \
target="_blank">bruno.decraene@orange.com</a>><br> <b>Date: </b>Monday, November \
7, 2016 at 6:43 AM<br> <b>To: </b>Acee Lindem <<a href="mailto:acee@cisco.com" \
target="_blank">acee@cisco.com</a>>, OSPF WG List <<a \
href="mailto:ospf@ietf.org" target="_blank">ospf@ietf.org</a>><br> <b>Subject: \
</b>RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"</span></p> \
</div> <div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Hi authors, all,</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Please find below some comments on the RLDC \
definition.</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">1) I¡¯d like to see a more specific definition \
of RLDC.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">e.g. load-balancing hashing could be done based on \
(hashing):</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">-a- a (stack of) N ¡°regular¡± MPLS labels (i.e. there \
is no ELI in this stack)</span></p> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">-b- the (IP) header below the stack of N \
labels</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">-c- the EL label in the stack of N labels (i.e. \
there is one ELI in this stack)</span></p> <p class="MsoNormal"><span style="COLOR: \
black"></span> </p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">I¡¯d like the specification to be clear on the \
applicability of the RLDC. Does it apply on these 3 cases, on only a \
subset?</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: \
Calibri; COLOR: #1f497d">Personally, I¡¯d like at least a and c be in scope of the \
RLDC definition, such that an ingress with limited push capability could have enough \
information to decide that it could avoid pushing an ELI,EL pair if the stack of \
MPLS labels that it pushes has enough entropy within the first RLDC \
labels.</span></p> <p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black">I think that the signaling document should reference section 4 \
of </span><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: \
black"><a href="https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt" \
target="_blank"><span \
lang="EN-US">https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt</span></a></span><span \
style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: black">. </span><span \
lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; COLOR: black">However, I \
don¡¯t think -b- is covered there. </span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">[Bruno] The above \
section 4 has indeed more details, but I¡¯m not certain that the definition is clear \
enough for everyone to agree on which ¡°a¡±, ¡°b¡±, ¡°c¡± cases are covered by the \
RLDC advertisement. My reading would be that ¡°a¡± and ¡°c¡± are covered, not ¡°b¡±. \
Reading your email, I¡¯d say that you have the same understanding. But it bothers me \
that one of the authors has a different understanding. </span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Alsodraft-ietf-mpls-spring-entropy-label-04.txt is an informational \
document, so I¡¯m not sure how much it would qualify to be a normative definition of \
what draft-ietf-ospf-mpls-elc advertise.</span></p>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Thanks,</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Regards,</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">-- Bruno</span></p> \
</div> <div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">2) Current text seems to limit the use of the RLDC to the insertion of a \
_<i>second</i>_ EL. Why is the RLD not applicable to the first EL?</span></p> </div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">¡ì1. Introduction</span></p> <pre><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black">¡°This capability, referred \
to</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier \
New"; COLOR: black"> as Readable Label Deepth Capability (RLDC) can \
be used by ingress</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black"> LSRs to determine whether it's \
necessary to insert an EL for a given</span></pre> <pre><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black"> LSP tunnel in the \
case where there has already been at least one EL</span></pre> <pre><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black"> in the label stack [</span><span lang="FR" style="FONT-SIZE: \
10pt; FONT-FAMILY: "Courier New"; COLOR: black"><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label" \
target="_blank"><span \
lang="EN-US">I-D.ietf-mpls-spring-entropy-label</span></a></span><span \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black">]¡±</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier \
New"; COLOR: black"> </span></pre> <pre><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black">¡ì6 Usage and \
Applicability</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">¡°The RLDC is used by ingress \
LSRs</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier \
New"; COLOR: black"> to determine whether it's necessary to insert \
an EL for a given LSP</span></pre> <pre><span style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black"> tunnel in the case where there \
has already been at least one EL in</span></pre> <pre><span style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black"> </span><span \
lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black">the label stack. »</span></pre> <pre><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black"> </span></pre> <pre><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; \
COLOR: #1f497d"> </span></pre> <p class="MsoNormal"><span style="FONT-SIZE: \
11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">I think that this is an unnecessary \
restriction of the RLDC usage. Indeed, an ingress with a limited capability in term \
of label push, could be forced to push a single EL label. It should be able to use \
the RLDC info in order to choose the best location for the EL, even if it pushes a \
single one.</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">But both sentences seems to restrict RLDC usage \
for the additional EL push, not the first one.</span></p> </div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">I would tend to agree.</span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">Thanks,</span></p> </div>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">Acee </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-TOP: medium none; \
BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; \
PADDING-TOP: 0in; PADDING-LEFT: 4pt; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: #b5c4df \
4.5pt solid; PADDING-RIGHT: 0in"> <div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: \
#1f497d">Thanks,</span></p> <p class="MsoNormal"><span style="FONT-SIZE: 11pt; \
FONT-FAMILY: Calibri; COLOR: #1f497d">Regards,</span></p> <p class="MsoNormal"><span \
style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; COLOR: #1f497d">--Bruno</span></p> <p \
class="MsoNormal"><span style="COLOR: black"></span> </p> <div \
style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium \
none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue \
1.5pt solid; PADDING-RIGHT: 0in"> <div>
<div style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: \
medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: \
medium none; PADDING-RIGHT: 0in"> <p class="MsoNormal"><b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black">From:</span></b><span style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma; COLOR: black"> OSPF [<a \
href="mailto:ospf-bounces@ietf.org" target="_blank">mailto:ospf-bounces@ietf.org</a>] \
<b>On Behalf Of </b>Acee Lindem (acee)<br> <b>Sent:</b> Saturday, November 05, 2016 \
5:46 PM<br> <b>To:</b> OSPF WG List<br>
<b>Subject:</b> [OSPF] WG Last Call for "Signalling ELC using \
OSPF"</span></p> </div>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">This begins the WG last call for "Signalling ELC using \
OSPF¡±, <a href="https://www.ietf.org/id/draft-ietf-ospf-mpls-elc-03.txt" \
target="_blank">https://www.ietf.org/id/draft-ietf-ospf-mpls-elc-03.txt</a>. Please \
review the document and send comments to this list prior to Nov 27th, 2016. Due to \
the IETF week, the last call period is going to be 3 weeks rather than usual 2 \
weeks. </span></p> </div>
<div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">Thanks,</span></p> </div>
<div>
<p class="MsoNormal"><span lang="FR" style="FONT-SIZE: 10.5pt; FONT-FAMILY: Calibri; \
COLOR: black">Acee </span></p> </div>
</div>
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black"> </span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black">Ce message et ses pieces jointes \
peuvent contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">pas etre diffuses, exploites ou copies sans \
autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">a l'expediteur et le detruire ainsi que les \
pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">Orange decline toute responsabilite si ce \
message a ete altere, deforme ou falsifie. Merci.</span></pre> <pre><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black"> </span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">This message and its attachments may contain \
confidential or privileged information that may be protected by law;</span></pre> \
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">they should not be distributed, used or copied without \
authorisation.</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">If you have received this email in error, \
please notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">As emails may be altered, Orange is not liable for messages that have \
been modified, changed or falsified.</span></pre> <pre><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: black">Thank \
you.</span></pre> </div>
</div>
</blockquote>
</div>
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black"> </span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; \
FONT-FAMILY: "Courier New"; COLOR: black">Ce message et ses pieces jointes \
peuvent contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">pas etre diffuses, exploites ou copies sans \
autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">a l'expediteur et le detruire ainsi que les \
pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">Orange decline toute responsabilite si ce \
message a ete altere, deforme ou falsifie. Merci.</span></pre> <pre><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: \
black"> </span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">This message and its attachments may contain \
confidential or privileged information that may be protected by law;</span></pre> \
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">they should not be distributed, used or copied without \
authorisation.</span></pre> <pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: \
"Courier New"; COLOR: black">If you have received this email in error, \
please notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; \
COLOR: black">As emails may be altered, Orange is not liable for messages that have \
been modified, changed or falsified.</span></pre> <pre><span lang="FR" \
style="FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"; COLOR: black">Thank \
you.</span></pre> </div>
<p class="MsoNormal"><span style="FONT-FAMILY: SimSun; COLOR: \
black">_______________________________________________<br> OSPF mailing list<br>
<a href="mailto:OSPF@ietf.org" target="_blank">OSPF@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/ospf" \
target="_blank">https://www.ietf.org/mailman/listinfo/ospf</a></span></p> </div>
</blockquote>
</div>
<p class="MsoNormal"><span style="COLOR: black"></span> </p>
</div>
</div>
</div>
</div>
<pre><span lang="FR" style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="COLOR: black"> </span></pre>
<pre><span lang="FR" style="COLOR: black">Ce message et ses pieces jointes peuvent \
contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="COLOR: black">pas etre diffuses, \
exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, \
veuillez le signaler</span></pre> <pre><span lang="FR" style="COLOR: black">a \
l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques \
etant susceptibles d'alteration,</span></pre> <pre><span lang="FR" style="COLOR: \
black">Orange decline toute responsabilite si ce message a ete altere, deforme ou \
falsifie. Merci.</span></pre> <pre><span lang="FR" style="COLOR: \
black"> </span></pre> <pre><span lang="FR" style="COLOR: black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;</span></pre> <pre><span lang="FR" style="COLOR: black">they should \
not be distributed, used or copied without authorisation.</span></pre> <pre><span \
lang="FR" style="COLOR: black">If you have received this email in error, please \
notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="COLOR: black">As emails may be altered, Orange is not \
liable for messages that have been modified, changed or falsified.</span></pre> \
<pre><span lang="FR" style="COLOR: black">Thank you.</span></pre> </div>
</div>
<pre><span lang="FR" style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="COLOR: black"> </span></pre>
<pre><span lang="FR" style="COLOR: black">Ce message et ses pieces jointes peuvent \
contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="COLOR: black">pas etre diffuses, \
exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, \
veuillez le signaler</span></pre> <pre><span lang="FR" style="COLOR: black">a \
l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques \
etant susceptibles d'alteration,</span></pre> <pre><span lang="FR" style="COLOR: \
black">Orange decline toute responsabilite si ce message a ete altere, deforme ou \
falsifie. Merci.</span></pre> <pre><span lang="FR" style="COLOR: \
black"> </span></pre> <pre><span lang="FR" style="COLOR: black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;</span></pre> <pre><span lang="FR" style="COLOR: black">they should \
not be distributed, used or copied without authorisation.</span></pre> <pre><span \
lang="FR" style="COLOR: black">If you have received this email in error, please \
notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="COLOR: black">As emails may be altered, Orange is not \
liable for messages that have been modified, changed or falsified.</span></pre> \
<pre><span lang="FR" style="COLOR: black">Thank you.</span></pre> </div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
<pre><span lang="FR" style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="COLOR: black"> </span></pre>
<pre><span lang="FR" style="COLOR: black">Ce message et ses pieces jointes peuvent \
contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="COLOR: black">pas etre diffuses, \
exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, \
veuillez le signaler</span></pre> <pre><span lang="FR" style="COLOR: black">a \
l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques \
etant susceptibles d'alteration,</span></pre> <pre><span lang="FR" style="COLOR: \
black">Orange decline toute responsabilite si ce message a ete altere, deforme ou \
falsifie. Merci.</span></pre> <pre><span lang="FR" style="COLOR: \
black"> </span></pre> <pre><span lang="FR" style="COLOR: black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;</span></pre> <pre><span lang="FR" style="COLOR: black">they should \
not be distributed, used or copied without authorisation.</span></pre> <pre><span \
lang="FR" style="COLOR: black">If you have received this email in error, please \
notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="COLOR: black">As emails may be altered, Orange is not \
liable for messages that have been modified, changed or falsified.</span></pre> \
<pre><span lang="FR" style="COLOR: black">Thank you.</span></pre> </div>
</div>
<pre><span lang="FR" style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span lang="FR" style="COLOR: black"> </span></pre>
<pre><span lang="FR" style="COLOR: black">Ce message et ses pieces jointes peuvent \
contenir des informations confidentielles ou privilegiees et ne doivent \
donc</span></pre> <pre><span lang="FR" style="COLOR: black">pas etre diffuses, \
exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, \
veuillez le signaler</span></pre> <pre><span lang="FR" style="COLOR: black">a \
l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques \
etant susceptibles d'alteration,</span></pre> <pre><span lang="FR" style="COLOR: \
black">Orange decline toute responsabilite si ce message a ete altere, deforme ou \
falsifie. Merci.</span></pre> <pre><span lang="FR" style="COLOR: \
black"> </span></pre> <pre><span lang="FR" style="COLOR: black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;</span></pre> <pre><span lang="FR" style="COLOR: black">they should \
not be distributed, used or copied without authorisation.</span></pre> <pre><span \
lang="FR" style="COLOR: black">If you have received this email in error, please \
notify the sender and delete this message and its attachments.</span></pre> \
<pre><span lang="FR" style="COLOR: black">As emails may be altered, Orange is not \
liable for messages that have been modified, changed or falsified.</span></pre> \
<pre><span lang="FR" style="COLOR: black">Thank you.</span></pre> </div>
</div>
</div>
</div>
</div>
</div>
<pre><span style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span style="COLOR: black"> </span></pre>
<pre><span style="COLOR: black">Ce message et ses pieces jointes peuvent contenir des \
informations confidentielles ou privilegiees et ne doivent donc</span></pre> \
<pre><span style="COLOR: black">pas etre diffuses, exploites ou copies sans \
autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler</span></pre> <pre><span style="COLOR: black">a l'expediteur et le detruire \
ainsi que les pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,</span></pre> <pre><span style="COLOR: black">Orange decline toute \
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</span></pre> \
<pre><span style="COLOR: black"> </span></pre> <pre><span style="COLOR: \
black">This message and its attachments may contain confidential or privileged \
information that may be protected by law;</span></pre> <pre><span style="COLOR: \
black">they should not be distributed, used or copied without \
authorisation.</span></pre> <pre><span style="COLOR: black">If you have received this \
email in error, please notify the sender and delete this message and its \
attachments.</span></pre> <pre><span style="COLOR: black">As emails may be altered, \
Orange is not liable for messages that have been modified, changed or \
falsified.</span></pre> <pre><span style="COLOR: black">Thank you.</span></pre>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<div>
<p class="MsoNormal"><span style="COLOR: \
black">_______________________________________________<br> mpls mailing list<br>
<a href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/mpls" \
target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a></span></p> </div>
</blockquote>
</div>
<pre><span style="COLOR: \
black">_________________________________________________________________________________________________________________________</span></pre>
<pre><span style="COLOR: black"> </span></pre>
<pre><span style="COLOR: black">Ce message et ses pieces jointes peuvent contenir des \
informations confidentielles ou privilegiees et ne doivent donc</span></pre> \
<pre><span style="COLOR: black">pas etre diffuses, exploites ou copies sans \
autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler</span></pre> <pre><span style="COLOR: black">a l'expediteur et le detruire \
ainsi que les pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,</span></pre> <pre><span style="COLOR: black">Orange decline toute \
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</span></pre> \
<pre><span style="COLOR: black"> </span></pre> <pre><span style="COLOR: \
black">This message and its attachments may contain confidential or privileged \
information that may be protected by law;</span></pre> <pre><span style="COLOR: \
black">they should not be distributed, used or copied without \
authorisation.</span></pre> <pre><span style="COLOR: black">If you have received this \
email in error, please notify the sender and delete this message and its \
attachments.</span></pre> <pre><span style="COLOR: black">As emails may be altered, \
Orange is not liable for messages that have been modified, changed or \
falsified.</span></pre> <pre><span style="COLOR: black">Thank you.</span></pre>
</div>
</div>
</div>
<pre>_________________________________________________________________________________________________________________________</pre>
<pre> </pre>
<pre>Ce message et ses pieces jointes peuvent contenir des informations \
confidentielles ou privilegiees et ne doivent donc</pre> <pre>pas etre diffuses, \
exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, \
veuillez le signaler</pre> <pre>a l'expediteur et le detruire ainsi que les pieces \
jointes. Les messages electroniques etant susceptibles d'alteration,</pre> \
<pre>Orange decline toute responsabilite si ce message a ete altere, deforme ou \
falsifie. Merci.</pre> <pre> </pre>
<pre>This message and its attachments may contain confidential or privileged \
information that may be protected by law;</pre> <pre>they should not be distributed, \
used or copied without authorisation.</pre> <pre>If you have received this email in \
error, please notify the sender and delete this message and its attachments.</pre> \
<pre>As emails may be altered, Orange is not liable for messages that have been \
modified, changed or falsified.</pre> <pre>Thank you.</pre>
</div>
</div>
</div>
</div>
</body>
</html>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--===============5447260202453061497==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic