[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: Re: [mpls] [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
From: <bruno.decraene () orange ! com>
Date: 2016-11-29 13:39:46
Message-ID: 15517_1480426787_583D8523_15517_45_1_53C29892C857584299CBF5D05346208A1ECA1851 () OPEXCLILM21 ! corporate ! adroot ! infra ! ftgroup
[Download RAW message or body]
[Attachment #2 (text/plain)]
Hi Xiaohu,
Thanks for proposing text.
Please see inline [Bruno5]
In summary, I think we have converged on this OSPF document defining the OSPF \
encoding and I-D.ietf-mpls-spring-entropy-label defining the meaning and usage of \
RLD. This is clearly one way to avoid inconsistency between both documents.
Thanks,
--Bruno
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Tuesday, November 29, 2016 11:06 AM
To: DECRAENE Bruno IMT/OLN; Acee Lindem (acee)
Cc: OSPF WG List; mpls@ietf.org; Carlos Pignataro (cpignata)
Subject: ??: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
Thanks for your further comments and suggestions. Please see my response inline with \
[Xiaohu2]
发件人: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
[mailto:bruno.decraene@orange.com] 发送时间: 2016年11月29日 0:24
收件人: Xuxiaohu; Acee Lindem (acee)
抄送: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro \
(cpignata) 主题: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Xiaohu,
Please see inline [Bruno4]
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Saturday, November 26, 2016 2:05 AM
To: DECRAENE Bruno IMT/OLN; Acee Lindem (acee)
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 Bruno,
发件人: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
[mailto:bruno.decraene@orange.com] 发送时间: 2016年11月25日 22:46
收件人: Xuxiaohu; Acee Lindem (acee)
抄送: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro \
(cpignata) 主题: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Xiaohu,
Please see inline [Bruno3]
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Friday, November 25, 2016 3:20 AM
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 Acee and Bruno,
发件人: Acee Lindem (acee) [mailto:acee@cisco.com]
发送时间: 2016年11月25日 1:21
收件人: bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
抄送: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro \
(cpignata); Xuxiaohu 主题: Re: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"
Hi Bruno,
See inline (I've neglected migrating to Outlook 2016 since it won't do proper reply \
formatting).
From: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Thursday, November 24, 2016 at 4:57 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.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>>, Xiaohu Xu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Subject: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Acee
Please see inline [Bruno3]
From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Monday, November 21, 2016 6:41 PM
To: DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata); \
Xuxiaohu
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 21, 2016 at 12:21 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.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>>, Xiaohu Xu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Subject: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Acee,
From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Monday, November 21, 2016 6:02 PM
To: DECRAENE Bruno IMT/OLN; Xuxiaohu
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
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 21, 2016 at 9:43 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Xiaohu Xu \
<xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.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: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Acee,
From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Saturday, November 19, 2016 12:33 AM
To: DECRAENE Bruno IMT/OLN; Xuxiaohu
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
Subject: Re: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Bruno,
From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Bruno \
Decraene \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Friday, November 18, 2016 at 11:30 AM
To: Xiaohu Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.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: Re: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Hi Xiaohu,
Please see inline [Bruno]
From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Monday, November 14, 2016 1:00 PM
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,
Could you please explain why the defination of the RLDC should be specific to the LB \
behavior of the transit LSR?
[Bruno] The whole purpose of EL and ELC is to improve load balancing of MPLS packets \
on transit LSR.
According to 6 of your draft, RLDC is also used to improve load-balancing : "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.
What would be the point for the ingress to add an additional EL, within the RLDC of \
LSR A, if LSR A do not use this EL to improve the load balancing?
cf my example below where a LSR can read 5 labels, yet do not use those 5 labels for \
the load-balancing hence would not benefit from adding an EL within those 5 labels.
BTW, it would be useful for the discussion if you could reply to the content of my \
email sent: Monday, November 14, 2016 (also included below). As this was already the \
second time I send this example on the OSPF mailing list.
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. "
[Bruno] I'm not seeing any conflict. I agree with both points. In this thread, I'm \
working on 1, i.e. having a clear definition of RLD. But I would also like that this \
RLD advertisement be effective in improving the load-balancing of MPLS packets.
I think Readable Label Depth (RLD) should be independent of EL Capability (ELC). It \
allows advertisement of the the maximum number of labels an OSPF router will examine \
in a received MPLS encapsulated packet. If an OSPF Router supports ELC, it would \
imply that it support the EL Capability within RLD labels. [Bruno] Would work for me, \
assuming that this is stated in the document, and :s/support the EL Capability within \
RLD labels/for load-balancing purpose, use the EL within RLD labels. I would propose \
the following text: "RLDC is the maximum number of labels, from the top of the stack, \
where the MPLS transit LSR searches for the ELI,EL pair and load-balance based on the \
EL if present."
I would completely decouple the two capabilities. Here is the text I would recommend.
The Readable Label Depth (RLD) is the maximum number of labels, starting with top or \
first label in the stack, that an LSR can examine in a received MPLS packet. The \
supported RLD can be important when searching for an entropy label for purpose of \
load-balancing as the <ELI, EL> pair must be included in the first RLD labels in the \
stack.
[Bruno] What would you use this RLD information for?
Current OSPF draft proposes to use it to make a decision on whether/where adding an \
additional ELI, EL pairs in the stack of labels. But if we don't know whether that \
additional EL, within the RLD, will be used for load-balancing purpose, the ingress \
can't know whether adding this ELI, EL is useful or not. Since we are in a context \
where the number of labels that can be pushed is limited, we may be wasting 2 label \
push for zero benefit.
As the name would imply, Entropy Label Capability (ELC) would be used to determine if \
the LSR supports load-balancing. The RLD capability, also as as the name would imply, \
would be used solely to determine the number of labels an LSR will read. [Bruno3] \
"read" is one thing but it does not say much about the result/behavior. That's why \
I'm calling for "read and use" or "use" for short.
If you want to restrict the capability to the entropy label usage then an appropriate \
moniker would be the ELRD (Entropy Label Readable Depth). However, I see no reason to \
restrict it or attempt to tie load balancing to the depth an LSR can read (other than \
the former is constrained by the latter). The Entropy Label behavior can be fully \
defined by the Entropy Label Capability (ELC). Please view this in terms of \
capability modularity without allowing the details of two capabilities to be mix.
[Xiaohu] Concur.
[Bruno3] you concur on "I see no reason to [..] attempt to tie load balancing to the \
depth an LSR can read"? The draft seems to say otherwise:
- 1 "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 "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.
[Xiaohu1] Is the following updated text OK to you?
5. Advertising RLDC Using OSPF
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. As showed in Figure 2, it is formatted as
described in Section 2.3 of [RFC7770] with a Type code to be assigned
by IANA and a Length of one. The Value field is set to the maximum
readable label stack depth in the range between 1 to 255. The scope
of the advertisement depends on the application but it is RECOMMENDED
that it SHOULD be domain-wide. 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.
This TLV is applicable to both OSPFv2 and OSPFv3.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RLD |
+-+-+-+-+-+-+-+-+
Figure 2: RLDC TLV Format
[Bruno4] I'm fine with this, with the addition of the reference to \
draft-ietf-mpls-spring-entropy-label at the end of the first sentence, in order for \
the reader to know where RLD is defined and how it is used.
[Xiaohu2] In fact, it has been said in the introduction section that
"…In addition, in the cases where stacked LSPs are used for
whatever reasons (e.g., SPRING-MPLS
[I-D.ietf-spring-segment-routing-mpls]), it would be useful for
ingress LSRs to know each LSR's capability of reading the maximum
label stack depth. This capability, referred to as Readable Label
Xu, et al. Expires June 2, 2017 [Page 2]
Internet-Draft Signalling ELC using OSPF November 2016
Depth Capability (RLDC) may be used by ingress LSRs to determine
whether it's necessary to insert an EL for a given LSP of the stacked
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].
…"
As a result, it seems no need to add the reference to \
draft-ietf-mpls-spring-entropy-label in Section 5, IMO. No? [Bruno5] ok. works for \
me. In section 10, I think [I-D.ietf-mpls-spring-entropy-label]. should be moved to \
normative reference, as it's the reference to the RLD meaning and usage.
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 may 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. 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
Xu, et al. Expires April 21, 2017 [Page 4]
Internet-Draft Signalling ELC using OSPF October 2016
document and accordingly would be described in
[I-D.ietf-mpls-spring-entropy-label].
[Bruno4] I'm not seeing the benefit of this section and would rather remove it.
[Xiaohu2] OK, I will remove it.
[Bruno5] ok ,thanks.
Best regards,
Xiaohu
--Bruno
Best regards,
Xiaohu
If this is not what you mean, please update the draft to reflect this. Also note that \
changing this would significantly impact \
[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>] \
because they use the same term RLD to mean something different. And they use it \
specifically to influence the load-balancing behavior.
Am I the only one who thinks this is obvious?
think ELC should be defined in RFC 6790 and the SPRING Entropy label draft as opposed \
to the IGP advertisement drafts. [Bruno] I tend to agree that the definition of RLD, \
or the load-balancing behavior of a transit LSR supporting EL, would be better \
specified by the MPLS WG. Then the value advertised by control plane \
protocols/signaling. https://tools.ietf.org/html/rfc7325#section-2.4.5 talks about \
this, but the document is informational, and the text is a bit too large/ open to \
have the LSR behavior advertised in the IGP using a single integer. But this option \
may delay a lot the IGP draft, unless it is splitted in 2 parts (as ELC is ready). \
Alternatively, I'm ok with your above proposition.
Why can't we simply use the definition of entropy processing included in RFC 6790 \
section 4? [Bruno] Basically, section 4.3 says that the LSR can load-balance based on \
whatever it wants, and not necessarily based on the EL label. If it does not use the \
EL label, there is no point in the ingress trying to add additional ELI,EL labels \
within the RLD of this LSR.
I'd say that a router supporting ELC recognizes the <ELI, EL> label in the first RLD \
labels and MAY load-balance as described in RFC 6790. An OSPF document should not \
update the MPLS data plane behavior. [Bruno3] I agree that an OSPF document should \
not update the MPLS data plane behavior. ELC is defined in RFC 6790 as the capability \
of the egress (of the LSP/segment). It does not advertise any transit capability. \
(Now we could argue that a sensible implementation would implement both features at \
the same time, but I would not a priori bet on this for all implementation, \
especially since those are two different forwarding plane capabilities and some \
hardware could be able to do one and not the other)
I get it that you want an LSR capability that indicates that it MUST load-balance \
based on an entropy label within the first RLD labels. However, shouldn't this \
forwarding plane behavior be defined in MPLS rather than the IGPs? If the MPLS WG \
won't engage in this definition, perhaps this should be defined in \
https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt – I believe you \
have some leverage here ;^) and it certainly isn't within the charter of the OSPF or \
ISIS WGs.
[Xiaohu] Agree. As per RFC6790, the ingress of a given LSP doesn't know whether or \
not intermediate LSRs along that LSP could perform EL-based load-balancing when \
inserting EL/ELI under that LSP. The ingress just "assumes" that all or partial \
intermediate LSRs could perform EL-based LB.
[Bruno3] No. RFC 6790 makes no assumption on transit LSR behavior. e.g. "Transit LSRs \
MAY operate with no change in forwarding behavior."
And there is no issue with RFC 6790. The issue is related to the RLD usage made by \
[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>]
--Bruno
When you look the stacked LSP tunnel in the MPLS SR case as a stack of LSPs that \
share the same ingress, things become much simpler. The principles used in RFC6790 \
should be applicable to the MPLS-SR case as well. That's to say, the ingress of a \
given tier LSP (i.e., a node segment) within the stacked LSP tunnel just needs to \
assume that all or partial intermediate LSRs could perform EL-based LB as well. More \
specially, there is no need for the ingress to "know" whether intermediate LSRs are \
capable of performing EL-based LB. Even assume that the ingress of a given LSP knows \
that some intermediate LSRs of that LSP don't support EL-based LB, should it insert \
EL/ELI or not?
Best regards,
Xiaohu
Which is the purpose of advertising the RLD (AFAIK).
It is one usage of RLD – however, the maximum number of labels an LSR can examine \
must not be inextricably tied to the Entropy Label processing. [Bruno3] It's \
currently the only usage, so I'd rather have the RLD useful for this usage. If there \
are more usages, we may take them into account. But there is not free lunch: if we \
want to advertise 2 (slightly) different thing, we'll need to advertise two \
capabilities)
Why doesn't this work?
1. The RLD defines the maximum number of labels that an MPLS LSR is able to read.
2. The ELC defines an MPLS LSR's Entropy Label load-balancing and entropy label \
popping capabilities with the constraint that the LSR will only look at the first RLD \
labels.
Happy Thanksgiving,
Acee
Thanks,
--Bruno
Thanks,
Acee
Thanks
--Bruno
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.
_________________________________________________________________________________________________________________________
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.
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
p.prformathtml, li.prformathtml, div.prformathtml
{mso-style-name:prformathtml;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.textedebulles, li.textedebulles, div.textedebulles
{mso-style-name:textedebulles;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
p.HTML, li.HTML, div.HTML
{mso-style-name:"HTML 预设 式";
mso-style-link:"HTML 预设 式 Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLChar
{mso-style-name:"HTML 预设 式 Char";
mso-style-priority:99;
mso-style-link:"HTML 预设 式";
font-family:"Courier New";}
p.a, li.a, div.a
{mso-style-name:批注框文本;
mso-style-link:"批注框文本 Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Char
{mso-style-name:"批注框文本 Char";
mso-style-priority:99;
mso-style-link:批注框文本;
font-family:SimSun;}
span.prformathtmlcar0
{mso-style-name:prformathtmlcar;
font-family:Consolas;}
span.textedebullescar0
{mso-style-name:textedebullescar;
font-family:"Tahoma","sans-serif";}
span.htmlchar0
{mso-style-name:htmlchar;
font-family:"Courier New";}
span.char0
{mso-style-name:char;
font-family:SimSun;}
span.prformathtmlcar00
{mso-style-name:prformathtmlcar0;
font-family:"Courier New";}
span.textedebullescar00
{mso-style-name:textedebullescar0;
font-family:"Tahoma","sans-serif";}
span.emailstyle25
{mso-style-name:emailstyle25;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle26
{mso-style-name:emailstyle26;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle27
{mso-style-name:emailstyle27;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle28
{mso-style-name:emailstyle28;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle29
{mso-style-name:emailstyle29;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle30
{mso-style-name:emailstyle30;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle31
{mso-style-name:emailstyle31;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle37
{mso-style-name:emailstyle37;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle38
{mso-style-name:emailstyle38;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.h2
{mso-style-name:h2;}
span.EmailStyle45
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle46
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle47
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle48
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle49
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle50
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle51
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle53
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle54
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
</span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Xiaohu,</span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Thanks \
for proposing text.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Please \
see inline [Bruno5]<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">In \
summary, I think we have converged on this OSPF document defining the OSPF encoding \
and I-D.ietf-mpls-spring-entropy-label defining the meaning and usage of RLD. This \
is clearly one way to avoid inconsistency between both \
documents.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">--Bruno<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> \
Xuxiaohu [mailto:xuxiaohu@huawei.com] <br>
<b>Sent:</b> Tuesday, November 29, 2016 11:06 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Acee Lindem (acee)<br>
<b>Cc:</b> OSPF WG List; mpls@ietf.org; Carlos Pignataro (cpignata)<br>
<b>Subject:</b> ??: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Bruno,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Thanks \
for your further comments and suggestions. Please see my response inline with \
[Xiaohu2]<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a> [<a \
href="mailto:bruno.decraene@orange.com">mailto:bruno.decraene@orange.com</a>] <br>
</span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发送时间</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
2016</span><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">年</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">11</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">月</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">29</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">日</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
0:24<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">收件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
Xuxiaohu; Acee Lindem (acee)<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">抄送</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos Pignataro \
(cpignata)<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">主题</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
RE: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US" \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Xiaohu,</span><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Please \
see inline [Bruno4]</span><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:ZH-CN"> \
Xuxiaohu [<a href="mailto:xuxiaohu@huawei.com">mailto:xuxiaohu@huawei.com</a>] <br>
<b>Sent:</b> Saturday, November 26, 2016 2:05 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Acee Lindem (acee)<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos \
Pignataro (cpignata)<br> <b>Subject:</b> ??: [OSPF] ??: WG Last Call for \
"Signalling ELC using OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Bruno,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a> [<a \
href="mailto:bruno.decraene@orange.com">mailto:bruno.decraene@orange.com</a>] <br>
</span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发送时间</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
2016</span><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">年</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">11</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">月</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">25</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">日</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
22:46<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">收件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
Xuxiaohu; Acee Lindem (acee)<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">抄送</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos Pignataro \
(cpignata)<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">主题</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
RE: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US" \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Xiaohu,</span><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Please \
see inline [Bruno3]</span><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:ZH-CN"> \
Xuxiaohu [<a href="mailto:xuxiaohu@huawei.com">mailto:xuxiaohu@huawei.com</a>] <br>
<b>Sent:</b> Friday, November 25, 2016 3:20 AM<br>
<b>To:</b> Acee Lindem (acee); DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos \
Pignataro (cpignata)<br> <b>Subject:</b> ??: [OSPF] ??: WG Last Call for \
"Signalling ELC using OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Acee and Bruno,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
Acee Lindem (acee) [<a href="mailto:acee@cisco.com">mailto:acee@cisco.com</a>] <br> \
</span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">发送时间</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
2016</span><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">年</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">11</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">月</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">25</span><span \
lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">日</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
1:21<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">收件人</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a><br> \
</span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">抄送</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos Pignataro \
(cpignata); Xuxiaohu<br> </span><b><span lang="ZH-CN" \
style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">主题</span></b><b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
Re: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span lang="EN-US" \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></p> <div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Hi \
Bruno, <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">See \
inline (I've neglected migrating to Outlook 2016 since it won't do proper reply \
formatting). <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">From:
</span></b><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>><br>
<b>Date: </b>Thursday, November 24, 2016 at 4:57 AM<br>
<b>To: </b>Acee Lindem <<a href="mailto:acee@cisco.com">acee@cisco.com</a>><br>
<b>Cc: </b>OSPF WG List <<a href="mailto:ospf@ietf.org">ospf@ietf.org</a>>, \
"<a href="mailto:mpls@ietf.org">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>>, "Carlos Pignataro \
(cpignata)" <<a href="mailto:cpignata@cisco.com">cpignata@cisco.com</a>>, \
Xiaohu Xu <<a href="mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>><br> \
<b>Subject: </b>RE: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Acee</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Please \
see inline </span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3]</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
Acee Lindem (acee) [<a href="mailto:acee@cisco.com">mailto:acee@cisco.com</a>] <br>
<b>Sent:</b> Monday, November 21, 2016 6:41 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos \
Pignataro (cpignata); Xuxiaohu<br> <b>Subject:</b> Re: [OSPF] ??: WG Last Call for \
"Signalling ELC using OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></p> <div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Hi \
Bruno, </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>><br>
<b>Date: </b>Monday, November 21, 2016 at 12:21 PM<br>
<b>To: </b>Acee Lindem <<a href="mailto:acee@cisco.com">acee@cisco.com</a>><br>
<b>Cc: </b>OSPF WG List <<a href="mailto:ospf@ietf.org">ospf@ietf.org</a>>, \
"<a href="mailto:mpls@ietf.org">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>>, "Carlos Pignataro \
(cpignata)" <<a href="mailto:cpignata@cisco.com">cpignata@cisco.com</a>>, \
Xiaohu Xu <<a href="mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>><br> \
<b>Subject: </b>RE: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Acee,</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
Acee Lindem (acee) [<a href="mailto:acee@cisco.com">mailto:acee@cisco.com</a>] <br>
<b>Sent:</b> Monday, November 21, 2016 6:02 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Xuxiaohu<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos \
Pignataro (cpignata)<br> <b>Subject:</b> Re: [OSPF] ??: WG Last Call for \
"Signalling ELC using OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></p> <div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Hi \
Bruno, </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Bruno \
Decraene <<a href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>><br>
<b>Date: </b>Monday, November 21, 2016 at 9:43 AM<br>
<b>To: </b>Acee Lindem <<a href="mailto:acee@cisco.com">acee@cisco.com</a>>, \
Xiaohu Xu <<a href="mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>><br> \
<b>Cc: </b>OSPF WG List <<a href="mailto:ospf@ietf.org">ospf@ietf.org</a>>, \
"<a href="mailto:mpls@ietf.org">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>>, "Carlos Pignataro \
(cpignata)" <<a \
href="mailto:cpignata@cisco.com">cpignata@cisco.com</a>><br> <b>Subject: </b>RE: \
[OSPF] ??: WG Last Call for "Signalling ELC using OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Acee,</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
Acee Lindem (acee) [<a href="mailto:acee@cisco.com">mailto:acee@cisco.com</a>] <br>
<b>Sent:</b> Saturday, November 19, 2016 12:33 AM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; Xuxiaohu<br>
<b>Cc:</b> OSPF WG List; <a href="mailto:mpls@ietf.org">mpls@ietf.org</a>; Carlos \
Pignataro (cpignata)<br> <b>Subject:</b> Re: [OSPF] ??: WG Last Call for \
"Signalling ELC using OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></p> <div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Hi \
Bruno, </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">OSPF \
<<a href="mailto:ospf-bounces@ietf.org">ospf-bounces@ietf.org</a>> on behalf of \
Bruno Decraene <<a \
href="mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>><br> \
<b>Date: </b>Friday, November 18, 2016 at 11:30 AM<br> <b>To: </b>Xiaohu Xu <<a \
href="mailto:xuxiaohu@huawei.com">xuxiaohu@huawei.com</a>><br> <b>Cc: </b>OSPF WG \
List <<a href="mailto:ospf@ietf.org">ospf@ietf.org</a>>, "<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>" <<a \
href="mailto:mpls@ietf.org">mpls@ietf.org</a>>, "Carlos Pignataro \
(cpignata)" <<a \
href="mailto:cpignata@cisco.com">cpignata@cisco.com</a>><br> <b>Subject: </b>Re: \
[OSPF] ??: WG Last Call for "Signalling ELC using OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Hi \
Xiaohu,</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Please \
see inline [Bruno]</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
Xuxiaohu [<a href="mailto:xuxiaohu@huawei.com">mailto:xuxiaohu@huawei.com</a>] <br>
<b>Sent:</b> Monday, November 14, 2016 1:00 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> OSPF WG List; Carlos Pignataro (cpignata); <a href="mailto:mpls@ietf.org">
mpls@ietf.org</a><br>
<b>Subject:</b> ??: [OSPF] ??: WG Last Call for "Signalling ELC using \
OSPF"</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><span \
style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></p> <div>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">Hi \
Bruno,</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">Could \
you please explain why the defination of the RLDC should be specific to the LB \
behavior of the transit LSR?</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
The whole purpose of EL and ELC is to improve load balancing of MPLS packets on \
transit LSR.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <pre><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">According \
to 6 of your draft, RLDC is also used to improve load-balancing : "</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black;mso-fareast-language:ZH-CN">The RLDC is used by ingress \
LSRs</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></pre>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black;mso-fareast-language:ZH-CN"> to determine whether \
it's necessary to insert an EL for a given LSP</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black;mso-fareast-language:ZH-CN"> tunnel in the case \
where there has already been at least one EL in</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="font-size:10.0pt;font-family:"Courier \
New";color:black;mso-fareast-language:ZH-CN">the label stack. \
</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> \
<p><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">What \
would be the point for the ingress to add an additional EL, within the RLDC of LSR A, \
if LSR A do not use this EL to improve the load balancing?</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">cf \
my example below where a LSR can read 5 labels, yet do not use those 5 labels for the \
load-balancing hence would not benefit from adding an EL within those 5 \
labels.</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p style="margin-bottom:12.0pt"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">BTW, \
it would be useful for the discussion if you could reply to the content of my email \
sent: Monday, November 14, 2016 (also included below). As this was already the \
second time I send this example on the OSPF mailing list.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN">If \
I understand correctly, it seems that the text proposed by you conflict with Acee's \
take (see blow):</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <div>
<p class="MsoNormal"><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN">" 1. The standards \
t</span><span style="color:black;mso-fareast-language:ZH-CN">rack 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. <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"> 2. The MPLS draft should \
precisely specify the initial use case of entropy label insertion at the ingress of \
the LSP. </span><span style="color:black;mso-fareast-language:ZH-CN">It should not \
limit the applicability of RLDC to this use case. "<o:p></o:p></span></p> \
<p class="MsoNormal"><span \
style="color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
I'm not seeing any conflict. I agree with both points. In this thread, I'm working on \
1, i.e. having a clear definition of RLD. But I would also like that this RLD \
advertisement be effective in improving the load-balancing of MPLS \
packets.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">I \
think Readable Label Depth (RLD) should be independent of EL Capability (ELC). It \
allows advertisement of the the maximum number of labels an OSPF router will examine \
in a received MPLS encapsulated packet. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> If \
an OSPF Router supports ELC, it would imply that it support the EL Capability within \
RLD labels.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
Would work for me, assuming that this is stated in the document, and :s/support the \
EL Capability within RLD labels/for load-balancing purpose, use the EL within RLD \
labels.</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">I \
would propose the following text: "RLDC is the maximum number of labels, from the top \
of the stack, where the MPLS transit LSR searches for the ELI,EL pair and \
load-balance based on the EL if present."</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">I \
would completely decouple the two capabilities. Here is the text I would \
recommend. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">The \
Readable Label Depth (RLD) is the maximum number of labels, starting with top or \
first label in the stack, that an LSR can examine in a received MPLS packet. \
The supported RLD can be important when searching for an entropy label for \
purpose of load-balancing as the <ELI, EL> pair must be included in the first \
RLD labels in the stack. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
What would you use this RLD information for?</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Current \
OSPF draft proposes to use it to make a decision on whether/where adding an \
additional ELI, EL pairs in the stack of labels. But if we don't know whether that \
additional EL, within the RLD, will be used for load-balancing purpose, the ingress \
can't know whether adding this ELI, EL is useful or not. Since we are in a context \
where the number of labels that can be pushed is limited, we may be wasting 2 label \
push for zero benefit.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">As \
the name would imply, Entropy Label Capability (ELC) would be used to determine if \
the LSR supports load-balancing. The RLD capability, also as as the name would \
imply, would be used solely to determine the number of labels an LSR will \
read.</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3] \
"read" is one thing but it does not say much about the result/behavior. That's why \
I'm calling for "read and use" or "use" for short.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">If \
you want to restrict the capability to the entropy label usage then an appropriate \
moniker would be the ELRD (Entropy Label Readable Depth). However, I see no reason \
to restrict it or attempt to tie load balancing to the depth an LSR can read (other \
than the former is constrained by the latter). The Entropy Label behavior can be \
fully defined by the Entropy Label Capability (ELC). Please view this in terms of \
capability modularity without allowing the details of two capabilities to be \
mix. <o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Xiaohu] \
Concur.<o:p></o:p></span></p> <pre><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3] \
you concur on "I see no reason to [..] attempt to tie load balancing to the depth an \
LSR can read"? The draft seems to say otherwise:<o:p></o:p></span></pre> <pre><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">- \
1 "</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">This capability, referred \
to<o:p></o:p></span></pre> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> as Readable Label Deepth \
Capability (RLDC) can be used by ingress<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> LSRs to determine whether it's \
necessary to insert an EL for a given<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> LSP tunnel in the case where there \
has already been at least one EL<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> in the label stack [</span><span \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label"><span \
lang="EN-US">I-D.ietf-mpls-spring-entropy-label</span></a></span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">] </span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">"<o:p></o:p></span></p>
</div>
<div>
<pre><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> \
6 "</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">The RLDC is used by ingress \
LSRs<o:p></o:p></span></pre> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> to determine whether it's \
necessary to insert an EL for a given LSP<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> tunnel in the case where there has \
already been at least one EL in<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"> </span><span \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">the label stack. <o:p></o:p></span></p> \
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Xiaohu1] \
Is the following updated text OK to you?<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">5. \
Advertising RLDC Using OSPF<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> A \
new TLV within the body of the OSPF RI LSA, called RLDC TLV is<o:p></o:p></span></p> \
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
defined to advertise the capability of the router to read the \
maximum<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
label stack depth. As showed in Figure 2, it is formatted \
as<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
described in Section 2.3 of [RFC7770] with a Type code to be \
assigned<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
by IANA and a Length of one. The Value field is set to the \
maximum<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
readable label stack depth in the range between 1 to 255. The \
scope<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
of the advertisement depends on the application but it is \
RECOMMENDED<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
that it SHOULD be domain-wide. If a router has multiple \
linecards<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
with different capabilities of reading the maximum label stack<o:p></o:p></span></p> \
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
deepth, the router MUST advertise the smallest one in the RLDC \
TLV.<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
This TLV is applicable to both OSPFv2 and OSPFv3.<o:p></o:p></span></p> <p \
class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
0 \
1 \
2 \
3<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<o:p></o:p></span></p> \
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-&# \
43;-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
| \
Type=TBD2 \
| \
Length \
|<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-&# \
43;-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
| RLD \
|<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
+-+-+-+-+-+-+-+-+<o:p></o:p></span></p> <p \
class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> &nb \
sp; \
Figure 2: RLDC TLV Format<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno4] \
I'm fine with this, with the addition of the reference to \
draft-ietf-mpls-spring-entropy-label at the end of the first sentence, in order for \
the reader to know where RLD is defined and how it is used.<o:p></o:p></span></p> <p \
class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Xiaohu2] \
In fact, it has been said in the introduction section that <o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> "…</span><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">In
addition, in the cases where stacked LSPs are used for<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
whatever reasons (e.g., SPRING-MPLS<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
[I-D.ietf-spring-segment-routing-mpls]), it would be useful for<o:p></o:p></span></p> \
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
ingress LSRs to know each LSR's capability of reading the \
maximum<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
label stack depth. This capability, referred to as Readable \
Label<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">Xu, et \
al. \
Expires June 2, 2017 \
[Page 2]<o:p></o:p></span></p> <span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><br \
clear="all" style="page-break-before:always"> </span>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">Internet-Draft \
Signalling ELC using OSPF \
November 2016<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
Depth Capability (RLDC) may be used by ingress LSRs to \
determine<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
whether it's necessary to insert an EL for a given LSP of the \
stacked<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
LSP tunnel in the case where there has already been at least one \
EL<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
in the label stack [I-D.ietf-mpls-spring-entropy-label].<o:p></o:p></span></p> <p \
class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">…"<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">As \
a result, it seems no need to add the reference to \
draft-ietf-mpls-spring-entropy-label in Section 5, IMO. No?<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno5] \
ok. works for me. In section 10, I think </span><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">[I-D.ietf-mpls-spring-entropy-label].
</span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">should \
be moved to normative reference, as it's the reference to the RLD meaning and \
usage.</span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">6. Usage \
and Applicability<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
The ELC is used by ingress LSRs to determine whether an EL could \
be<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
inserted into a given LSP tunnel. The RLDC may be used by ingress \
LSRs<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
to determine whether it's necessary to insert an EL for a given \
LSP<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
tunnel in the case where there has already been at least one EL \
in<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
the label stack. This document only describes how to signal the \
ELC<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
and RLDC using OSPF. As for how to apply those capabilities \
when<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
inserting EL(s) into LSP tunnel(s), it's outside the scope of \
this<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">Xu, et \
al. \
Expires April 21, 2017 \
[Page 4]<o:p></o:p></span></p> <span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><br \
clear="all" style="page-break-before:always"> </span>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN">Internet-Draft \
Signalling ELC using OSPF \
October 2016<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
document and accordingly would be described in<o:p></o:p></span></p> <p \
class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"> \
[I-D.ietf-mpls-spring-entropy-label].<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno4] \
I'm not seeing the benefit of this section and would rather remove it. \
<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Xiaohu2] \
OK, I will remove it.<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno5] \
ok ,thanks.<o:p></o:p></span></p> <p class="MsoNormal" \
style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Best \
regards,<o:p></o:p></span></p> <p class="MsoNormal" style="text-autospace:none"><span \
lang="EN-US" style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Xiaohu<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">--Bruno<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Best \
regards,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Xiaohu<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">If \
this is not what you mean, please update the draft to reflect this. Also note that \
changing this would significantly impact </span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">[</span><span \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label"><span \
lang="EN-US">I-D.ietf-mpls-spring-entropy-label</span></a></span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">] </span><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">because \
they use the same term RLD to mean something different. And they use it specifically \
to influence the load-balancing behavior.</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> \
</div> <div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
lang="EN-US" style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> \
</div> <div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Am \
I the only one who thinks this is obvious? </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">think \
ELC should be defined in RFC 6790 and the SPRING Entropy label draft as opposed to \
the IGP advertisement drafts. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
I tend to agree that the definition of RLD, or the load-balancing behavior of a \
transit LSR supporting EL, would be better specified by the MPLS WG. Then the value \
advertised by control plane protocols/signaling.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><a \
href="https://tools.ietf.org/html/rfc7325#section-2.4.5">https://tools.ietf.org/html/rfc7325#section-2.4.5</a> \
talks about this, but the document is informational, and the text is a bit too \
large/ open to have the LSR behavior advertised in the IGP using a single \
integer.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">But \
this option may delay a lot the IGP draft, unless it is splitted in 2 parts (as ELC \
is ready). Alternatively, I'm ok with your above proposition.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Why \
can't we simply use the definition of entropy processing included in RFC 6790 section \
4? </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno] \
Basically, section 4.3 says that the LSR can load-balance based on whatever it wants, \
and not necessarily based on the EL label. If it does not use the EL label, there is \
no point in the ingress trying to add additional ELI,EL labels within the RLD of this \
LSR. </span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">I'd \
say that a router supporting ELC recognizes the <ELI, EL> label in the first \
RLD labels and MAY load-balance as described in RFC 6790. An OSPF document should \
not update the MPLS data plane behavior. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3] \
I agree that an OSPF document should not update the MPLS data plane behavior. ELC is \
defined in RFC 6790 as the capability of the egress (of the LSP/segment). It does \
not advertise any transit capability.</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">(Now \
we could argue that a sensible implementation would implement both features at the \
same time, but I would not a priori bet on this for all implementation, especially \
since those are two different forwarding plane capabilities and some hardware could \
be able to do one and not the other)</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">I \
get it that you want an LSR capability that indicates that it MUST load-balance based \
on an entropy label within the first RLD labels. However, shouldn't this forwarding \
plane behavior be defined in MPLS rather than the IGPs? If the MPLS WG won't engage \
in this definition, perhaps this should be defined in <a \
href="https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt">https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt</a> –
I believe you have some leverage here ;^) and it certainly isn't within the \
charter of the OSPF or ISIS WGs.<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Xiaohu] \
Agree. As per RFC6790, the ingress of a given LSP doesn't know whether or not \
intermediate LSRs along that LSP could perform EL-based load-balancing when \
inserting EL/ELI under that LSP. The ingress just "assumes" that all or partial \
intermediate LSRs could perform EL-based LB.<o:p></o:p></span></p> <pre><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3] \
No. RFC 6790 makes no assumption on transit LSR behavior. e.g. "</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">Transit LSRs MAY operate with no change in \
forwarding behavior."<o:p></o:p></span></pre> <pre><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">And \
there is no issue with RFC 6790. The issue is related to the RLD usage made by \
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">[</span><span \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN"><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label"><span \
lang="EN-US">I-D.ietf-mpls-spring-entropy-label</span></a></span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";mso-fareast-language:ZH-CN">]<o:p></o:p></span></pre> <pre><span \
lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">--Bruno<o:p></o:p></span></pre>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">When \
you look the stacked LSP tunnel in the MPLS SR case as a stack of LSPs that share the \
same ingress, things become much simpler. The principles used in RFC6790 should be \
applicable to the MPLS-SR case as well. That's to say, the ingress of a given tier \
LSP (i.e., a node segment) within the stacked LSP tunnel just needs to assume that \
all or partial intermediate LSRs could perform EL-based LB as well. More specially, \
there is no need for the ingress to "know" whether intermediate LSRs are capable of \
performing EL-based LB. Even assume that the ingress of a given LSP knows that some \
intermediate LSRs of that LSP don't support EL-based LB, should it insert EL/ELI or \
not? <o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Best \
regards,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:16.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Xiaohu<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Which \
is the purpose of advertising the RLD (AFAIK).</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">It \
is one usage of RLD – however, the maximum number of labels an LSR can examine must \
not be inextricably tied to the Entropy Label processing. </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">[Bruno3] \
It's currently the only usage, so I'd rather have the RLD useful for this usage. If \
there are more usages, we may take them into account. But there is not free lunch: \
if we want to advertise 2 (slightly) different thing, we'll need to advertise two \
capabilities)</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Why \
doesn't this work?<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
1. The RLD defines the maximum number of labels that an MPLS LSR is able to \
read.<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> \
2. The ELC defines an MPLS LSR's Entropy Label load-balancing and entropy label \
popping capabilities with the constraint that the LSR will only look at the first \
RLD labels. <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Happy \
Thanksgiving, <o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Acee <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Thanks,</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">--Bruno</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Thanks,</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Acee </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">Thanks</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:ZH-CN">--Bruno
</span><span style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Thanks,</span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN">Acee </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></p> </div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm \
4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt" \
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"> <div>
<div>
<pre><span lang="EN-US" \
style="color:black;mso-fareast-language:ZH-CN"> </span><span \
style="color:black;mso-fareast-language:ZH-CN"><o:p></o:p></span></pre> </div>
</div>
</blockquote>
</div>
<pre><span style="color:black;mso-fareast-language:ZH-CN">____________________________ \
_____________________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN">Ce message et ses pieces \
jointes peuvent contenir des informations confidentielles ou privilegiees et ne \
doivent donc<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">pas etre diffuses, exploites ou copies \
sans autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">a l'expediteur et le detruire ainsi \
que les pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">Orange decline toute responsabilite si \
ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre> \
<pre><span style="color:black;mso-fareast-language:ZH-CN"> <o:p></o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN">This message and its \
attachments may contain confidential or privileged information that may be protected \
by law;<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">they should not be distributed, used \
or copied without authorisation.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">If you have received this email in \
error, please notify the sender and delete this message and its \
attachments.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">As emails may be altered, Orange is \
not liable for messages that have been modified, changed or \
falsified.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">Thank you.<o:p></o:p></span></pre> \
</div> </div>
</blockquote>
</div>
<pre><span style="color:black;mso-fareast-language:ZH-CN">____________________________ \
_____________________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN">Ce message et ses pieces \
jointes peuvent contenir des informations confidentielles ou privilegiees et ne \
doivent donc<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">pas etre diffuses, exploites ou copies \
sans autorisation. Si vous avez recu ce message par erreur, veuillez le \
signaler<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">a l'expediteur et le detruire ainsi \
que les pieces jointes. Les messages electroniques etant susceptibles \
d'alteration,<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">Orange decline toute responsabilite si \
ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre> \
<pre><span style="color:black;mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre>
<pre><span style="color:black;mso-fareast-language:ZH-CN">This message and its \
attachments may contain confidential or privileged information that may be protected \
by law;<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">they should not be distributed, used \
or copied without authorisation.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">If you have received this email in \
error, please notify the sender and delete this message and its \
attachments.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">As emails may be altered, Orange is \
not liable for messages that have been modified, changed or \
falsified.<o:p></o:p></span></pre> <pre><span \
style="color:black;mso-fareast-language:ZH-CN">Thank you.<o:p></o:p></span></pre> \
</div> </div>
</blockquote>
</div>
</div>
<pre><span style="mso-fareast-language:ZH-CN">________________________________________ \
_________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre>
<pre><span style="mso-fareast-language:ZH-CN">Ce message et ses pieces jointes \
peuvent contenir des informations confidentielles ou privilegiees et ne doivent \
donc<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">pas etre \
diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par \
erreur, veuillez le signaler<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">a l'expediteur et le detruire ainsi que les pieces \
jointes. Les messages electroniques etant susceptibles \
d'alteration,<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">Orange decline toute responsabilite si ce message \
a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">This message and its attachments may contain \
confidential or privileged information that may be protected by \
law;<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">they \
should not be distributed, used or copied without \
authorisation.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">If you have received this email in error, please \
notify the sender and delete this message and its \
attachments.<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">As \
emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">Thank you.<o:p></o:p></span></pre> </div>
</div>
<pre><span style="mso-fareast-language:ZH-CN">________________________________________ \
_________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre>
<pre><span style="mso-fareast-language:ZH-CN">Ce message et ses pieces jointes \
peuvent contenir des informations confidentielles ou privilegiees et ne doivent \
donc<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">pas etre \
diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par \
erreur, veuillez le signaler<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">a l'expediteur et le detruire ainsi que les pieces \
jointes. Les messages electroniques etant susceptibles \
d'alteration,<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">Orange decline toute responsabilite si ce message \
a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN"><o:p> </o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">This message and its attachments may contain \
confidential or privileged information that may be protected by \
law;<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">they \
should not be distributed, used or copied without \
authorisation.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">If you have received this email in error, please \
notify the sender and delete this message and its \
attachments.<o:p></o:p></span></pre> <pre><span style="mso-fareast-language:ZH-CN">As \
emails may be altered, Orange is not liable for messages that have been modified, \
changed or falsified.<o:p></o:p></span></pre> <pre><span \
style="mso-fareast-language:ZH-CN">Thank you.<o:p></o:p></span></pre> </div>
</div>
</div>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--===============8465482996949977410==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic