[prev in list] [next in list] [prev in thread] [next in thread]
List: ms-ospf
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
From: <bruno.decraene () orange ! com>
Date: 2018-08-30 9:25:59
Message-ID: 3748_1535621161_5B87B829_3748_490_1_a94dc0e2-c35e-4806-915c-d0d17f9a78ac () OPEXCLILM32 ! corporate ! adroot ! infra ! ftgroup
[Download RAW message or body]
[Attachment #2 (text/plain)]
Commenting on myself [Bruno]
From: DECRAENE Bruno IMT/OLN
Sent: Monday, August 27, 2018 4:57 PM
Hi Acee,
Thanks for the suggestion.
Contrary to MSD, ELC does not require the knowledge of the path topology. Hence I \
don't think this is helpful to refer to LSP path topology.
[Bruno] Sorry, I meant :s/MSD/ERLD (Entropy Readable Label Depth)
Tiger's proposal could work for me, but I personally think it would be fair and \
clearer to clearly state that the proposal does not provide a solution for inter-AS \
and inter-protocol deployments. e.g. "The advertisement of ELC in Inter-AS and \
inter-protocol scenarios is not supported."
[Bruno] To clarify my position:
- I believe that draft-ietf-isis-mpls-elc should support the use/advertisement of EL \
in SR-MPLS inter-area/AS/protocol deployments, in order to avoid regressions compared \
to LDP.
- In the meantime, I think the document should explicitly state that it does not \
support it (in its current version), in order to raise awareness of this limit
Thanks,
Regards,
--Bruno
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Wednesday, August 15, 2018 5:28 PM
To: ???(??); Lsr; LITKOWSKI Stephane OBS/OINIS; Van De Velde, Gunter (Nokia - \
BE/Antwerp)
Cc: lsr@ietf.org; draft-ietf-isis-mpls-elc@ietf.org
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Hi Tiger, Bruno,
Or would this be better?
"The advertisement and discovery of the complete LSP path topology in inter-AS \
and inter-protocol scenarios is outside the scope of this document."
Thanks,
Acee
From: Lsr <lsr-bounces@ietf.org> on behalf of "Xiaohu (Tiger) Xu" \
<xiaohu.xxh@alibaba-inc.com>
Reply-To: "Xiaohu (Tiger) Xu" <xiaohu.xxh@alibaba-inc.com>
Date: Friday, August 10, 2018 at 2:20 AM
To: Lsr <lsr-bounces@ietf.org>, Stephane Litkowski <stephane.litkowski@orange.com>, \
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-isis-mpls-elc@ietf.org" \
<draft-ietf-isis-mpls-elc@ietf.org>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Bruno,
OK. I will add the text as follows: "How to apply the ELC advertisement in the \
inter-AS and inter-protocol scenarios is outside the scope of this document".
Best regards,
Xiaohu
------------------------------------------------------------------
From:bruno.decraene <bruno.decraene@orange.com>
Send Time:2018年8月9日(星期四) 17:32
To:徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>; Lsr <lsr-bounces@ietf.org>; \
LITKOWSKI Stephane OBS/OINIS <stephane.litkowski@orange.com>; "Van De Velde, Gunter \
(Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com> Cc:lsr@ietf.org <lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org <draft-ietf-isis-mpls-elc@ietf.org> Subject:Re: \
[Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Xiaohu,
Please see inline [Bruno]
From:徐小虎(义先) [mailto:xiaohu.xxh@alibaba-inc.com]
Sent: Thursday, August 09, 2018 4:40 AM
I agree with Les's points.
To clarify the usage of the ELC in the inter-area scenario, I would like to add the \
following text to draft-ietf-isis|ospf-mpls-elc:
"When the ELC advertisement originated by a router in one area is propagated to \
another area in the inter-area scenario, those routers in the latter area need to \
find the routable IP addresses of the router originating that ELC advertisement \
before inserting the Entropy Label (EL) for packets going to the Label Switch Path \
(LSP) tunnel towards one of the above routable IP addresses. How to find the \
correlation between the Router-ID and the routable IP address of a given router is \
outside the scope of this document. Note that how to find the correlation between the \
Router-ID and the routable IP address of a given router in an ISIS domain is \
described in [RFC7794]. "
Any comments and suggestions are welcome.
[Bruno] Please also clarify the usage of ELC in the inter-protocol/AS case. At \
minimum acknowledging that this solution does not work in this case.
Best regards,
------------------------------------------------------------------
From:Les Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org>
Send Time:2018年8月9日(星期四) 07:54
To:stephane.litkowski@orange.com <stephane.litkowski@orange.com>; "Van De Velde, \
Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com> Cc:lsr@ietf.org <lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org <draft-ietf-isis-mpls-elc@ietf.org>; \
徐小虎(义先) <xiaohu.xxh@alibaba-inc.com> Subject:Re: [Lsr] I-D Action: \
draft-ietf-isis-mpls-elc-05.txt
Stephane –
There are some issues you raise that I think are easily resolved/agreed upon – some \
others that may require more discussion. Responses inline.
From: stephane.litkowski@orange.com <stephane.litkowski@orange.com>
Sent: Monday, August 06, 2018 2:58 AM
To: Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com>; Les \
Ginsberg (ginsberg) <ginsberg@cisco.com>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com>
Cc: lsr@ietf.org; draft-ietf-isis-mpls-elc@ietf.org; 徐小虎(义先) \
<xiaohu.xxh@alibaba-inc.com>
Subject: RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Hi Gunter,
IMO, there are multiple cases to distinguish.
The basic case (Adj-SIDs & Prefix-SIDs, single area, single domain, single protocol):
- ELC as a node property is a good thing. I personally do not see a use case \
to get some segments to be ELC and some others not to be ELCs.
[Les:] Good – I think there is general agreement on this point.
Multiarea case:
- When prefixes are leaked from one area to the other, we are losing the per \
node properties (like the ERLD). If we want to get benefit of EL, the ingress node in \
one area should get the ELC status of nodes in the other areas.
- One solution would be to propagate the ELC as part of the prefix \
advertisement (when the prefix is leaked). We are still losing the ERLD which may \
impact the loadbalancing (EL/ELI placement not efficient).
- Another solution could be for the ingress node to retrieve the ERLD from \
another source of information like BGP-LS but that's not trivial as the ingress must \
know the best route to the tail from the ABR point of view.
[Les:] There is no issue with multiarea. Repeating some points made earlier in the \
thread:
Both IGPs have the ability to leak router capabilities/info between areas. Which \
means the node based attributes ELC and ERLD can be available domain-wide. We also \
have the ability to leak source router-id with the leaked prefixes (OSPF has a gap \
here but we have a commitment to address that with a modest extension to the protocol \
– which needs to be done for multiple reasons.) So all the information necessary is \
available in all areas.
Multiprotocol case:
- It's not really different than the multiarea case.
[Les:] Multiprotocol is quite different than multiarea.
In the case of multiprotocol we do not have the ability to know/advertise the \
original source router-id nor the node capabilities in the destination protocol. It \
is not even guaranteed that reachability to the router-id of the source protocol is \
available in the area of the destination protocol. This is where a controller based \
solution is most advantageous as it has the ability to learn all of that information \
from all of the protocols enabled in the domain.
SRMS and SR-LDP stitching:
• SR to LDP: the LDP tail-end may be ELC, if an SR ingress node wants to \
use an ELI/EL on top of the prefix SID associated to the LDP FEC, we need to \
propagate the ELC known from LDP (attached to the FEC) to the SR advertisement. The \
SR-LDP stitching node is not a tail-end node, it will do a label swap, not a pop then \
push. So an entropy label pushed by the SR ingress node will be carried to the \
tail-end LDP node. Am I wrong ?
• LDP to SR: the stitching node knows if the tail-end SR node is ELC \
(through the IGP advertisement). It may propagate the ELC into LDP. All the prefixes \
of the tail-end SR node which are LDP FECs can get the ELC set if the SR tail-end \
node is ELC. I do not see any strict prescription requirement for the LSP here.
[Les:] Here there is more room for differences of opinion.
One viewpoint is that SR-LDP interworking is a transition strategy. Any solution \
which attempts to exchange ELC/ELRD information between the SR<->LDP portions of the \
network will be "messy" and perhaps not worth the trouble as we hope that the \
transition will be "short-lived".
Another viewpoint could be that if the transition period is long enough it may be \
useful to have such support.
But as any solution (even if we were to advertise ELC per prefix) would be \
non-trivial, I think there needs to be a strong case for taking this on. Do you \
believe we have a strong case here?
Binding SID:
- Binding SID associated to an SRTE LSP: if an ingress node wants to put an \
ELI/EL next to a binding SID, it needs to ensure that the tail-end of the binding SID \
is ELC. In addition, the expansion of the binding SID may introduce new ELI/ELs as \
part of the new added label stack.
- Binding SID associated to an RSVP-TE LSP: this case was removed from the \
SR extensions, but if it is revived in future, the ELC status of the RSVP-TE LSP may \
need to be propagated to the SR domain as part of the binding SID advertisement if we \
want the ingress to be able to push an ELI/ELI next to the BSID.
[Les:] I don't appreciate the problem here.
I think you are talking about two possible EL use cases.
1)An ingress node which imposes the binding-SID may wish to utilize entropy on the \
path to the owner of the Binding-SID. As the node sid (or possibly an adj-sid \
advertised by the owner of the binding sid) will be needed in the label stack, the \
ingress node still knows – independent of the binding-sid, whether the owner is \
ELC.
2)When the packet arrives at the node which owns the binding SID, that node may wish \
to include EL in the label stack which it imposes to implement the policy defined by \
the binding SID. But as the ELC of the LSP tail end is known this should not be a \
problem. And I do not see why the ingress node that imposed the binding-sid needs to \
know whether the owner of the binding-sid will/will not impose EL.
Les
Brgds,
Stephane
From: Van De Velde, Gunter (Nokia - BE/Antwerp) \
[mailto:gunter.van_de_velde@nokia.com]
Sent: Monday, August 06, 2018 10:47
To: LITKOWSKI Stephane OBS/OINIS; Les Ginsberg (ginsberg); DECRAENE Bruno IMT/OLN
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>; \
徐小虎(义先)
Subject: RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
"
The other case to handle is the binding SID. The binding SID needs to reflect the ELC \
of the associated LSP. The SRMS case is also interesting if we want to enable entropy \
when doing SR-LDP interworking. "
Does this not assume that a LSP is strictly defined hop-by-hop? If LSP is a loose \
LSP, then it is very well possible that depending on the state of network, sometimes \
the LSP is ELC capable and another time it is not capable or the ERLD changes.
I'm not convinced or have clear understanding on the value of ELC/ERLD for a \
particular LSP without making some strict prescriptions on LSP.
To me, having ERLD (and maybe of less importance) ELC has value only for a controller \
to make more educated decisions upon packet flows. Having such information per LSP \
seems complex and of lesser value as per node in the network.
G/
From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of \
stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>
Sent: Monday, August 6, 2018 10:26
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>; DECRAENE \
Bruno IMT/OLN \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>; \
徐小虎(义先) \
<xiaohu.xxh@alibaba-inc.com<mailto:xiaohu.xxh@alibaba-inc.com>>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Hi,
Hi Les, Bruno,
[Bruno] I also raised the case of redistribution of IP prefix/SID between IGP \
domains. Possibly one using OSPF and one using IS-IS. This case needs to be also \
covered.
[Les:] If a prefix is leaked between protocols then you lose the identification of \
the source. Which means you have other considerations which are not met e.g., what is \
the value for ERLD (which also is clearly not a per prefix value). To know this you \
need to know the source and have the Node Capabilities.
[SLI] I agree with Les that we are losing the ERLD information. But I think it is \
worth allowing the propagation of the ELC even if we are losing the ERLD info. We \
make this propagation optional. Moreover it will be still optional for the ingress \
node to use it. I agree that we must not leak the node infos.
The other case to handle is the binding SID. The binding SID needs to reflect the ELC \
of the associated LSP. The SRMS case is also interesting if we want to enable entropy \
when doing SR-LDP interworking.
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Friday, August 03, 2018 23:27
To: DECRAENE Bruno IMT/OLN
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>; \
徐小虎(义先)
Subject: RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Bruno –
Inline.
From:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> \
<bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Sent: Friday, August 03, 2018 10:01 AM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>; \
徐小虎(义先) \
<xiaohu.xxh@alibaba-inc.com<mailto:xiaohu.xxh@alibaba-inc.com>>
Subject: RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Les,
Please see inline [Bruno]
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Friday, August 03, 2018 6:32 PM
To: DECRAENE Bruno IMT/OLN; 徐小虎(义先)
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>
Subject: RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Bruno –
I appreciate why you suggest per-prefix signaling for ELC, but I would prefer that we \
not employ that model. [Bruno] Thanks for the feedback. That's part of the discussion \
that I was calling for.
ELC is clearly a node capability
[Bruno] It's a node capability of the egress of the LSP. Hence it could also be seen \
as a property of the LSP ;-) RFC 6790 says "one may choose to associate ELs with \
MPLS tunnels (LSPs) or with MPLS applications […] We take the former approach"
– signaling it in per node scope is therefore most appropriate. And it aligns with \
the SR model where we do not need to depend on hop-by-hop signaling as in the LDP \
case. [Bruno] I would argue that advertising ELC per prefix is not a hop-by-hop \
signaling as in the LDP case. That's one single advertisement per area/level.
[Les:] I probably expressed this poorly.
As LDP does hop-by-hop signaling the "natural" way to signal this in LDP is in the \
neighbor label exchanges. However, SR signaling is scoped by the area/domain and \
therefore we have the ability to advertise capability in a way that matches how the \
support is actually enabled. There is no basis for a node to advertise ELC support \
for local Prefix A but not for Local Prefix B. So advertising this per prefix is \
redundant (though I agree is still possible).
As regards the interarea issues you raise:
Both Router Capability TLV (IS-IS) and Router Information LSA (OSPF) support \
domain-wide flooding scope. This is not a new capability [Bruno] Agreed.
– though I do agree with you that the ELC drafts should explicitly mention the \
flooding scope requirement. [Bruno] May be the scalability impact may need to be \
discussed. I would assume an impact on the size of the LSDB (but a priori no impact \
on the churn). This is also a new behavior which may surprise operational teams. \
[Les:] The significant issue as regards scale is the leaking of the prefixes – not \
the leaking of per-Node information. So I am not greatly concerned about leaking Node \
Capability info.
[Bruno] I also raised the case of redistribution of IP prefix/SID between IGP \
domains. Possibly one using OSPF and one using IS-IS. This case needs to be also \
covered.
[Les:] If a prefix is leaked between protocols then you lose the identification of \
the source. Which means you have other considerations which are not met e.g., what is \
the value for ERLD (which also is clearly not a per prefix value). To know this you \
need to know the source and have the Node Capabilities.
Les
Thanks,
Regards,
--Bruno
As regards identifying the source of a prefix advertisement domain-wide, IS-IS has a \
complete solution for this as defined in RFC 7794. OSPF is lacking support for \
advertising the source Router-ID, but this can be easily remedied by defining an \
extension using Extended Prefix LSA (as has been mentioned by Peter in another \
thread). And this functionality is needed for other reasons e.g., to know when PHP \
should/should not be done. So it is probably past time when this should be defined.
So I think it is better if we use the per-node ELC scope proposed in the ELC drafts.
As an aside, I would prefer that we utilize the existing TE Node Capability \
Descriptor registry defined in RFC 5073 rather than invent a new codepoint/registry \
(the proposed Non-IGP Functional Capabilities registry) – but that is a minor \
point.
Les
From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of \
bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Sent: Friday, August 03, 2018 12:46 AM
To: 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com<mailto:xiaohu.xxh@alibaba-inc.com>>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>; \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Hi Xiaohu,
Thanks for the reply.
You seem to assume/require that (router) capability advertisement be propagated \
across IGP areas/domains. If so,
- this is a new requirement for existing multi-area networks that need to be \
indicated in the draft
- I find this debatable. This point should be explicitly discussed. I'd rather \
advertise the ELC capability on a per Segment basis. This would also be better \
aligned with RFC 6790 hence safer if EL extensions are defined. The (Segment Routing) \
Prefix-SID sub-TLV has 2 flags remaining. This may be a good candidate as this \
information seems SR specific. Alternatively, RFC7794 may be used.
Thanks
Best regards,
--Bruno
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of ???(??)
Sent: Friday, August 03, 2018 4:13 AM
To: Lsr; draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>
Cc: lsr@ietf.org<mailto:lsr@ietf.org>
Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
Hi Bruno,
Thanks for raising this important issue.
In fact, the Routable IP Address TLVs/sub-TLVs as described in \
(https://tools.ietf.org/html/draft-ietf-ospf-routable-ip-address-02) and \
(https://tools.ietf.org/html/draft-xu-isis-routable-ip-address-01) respectively were \
intended to address the problem that you had mentioned (i.e., it is required for OSPF \
routers in one area to find correlations between routable IP addresses and \
capabilities of OSPF routers in another area).
The following text is quoted from
" There are several situations where it is required for OSPF routers in
one area to find correlations between routable IP addresses and
capabilities of OSPF routers in another area. One example is the
Entropy Label Capability (ELC) advertisement \
[I-D.xu-ospf-mpls-elc<https://tools.ietf.org/html/draft-ietf-ospf-routable-ip-address-02#ref-I-D.xu-ospf-mpls-elc>]
across the OSPF domain. In this example, assume the ELC TLV
originated by a router in one area is propagated to another area.
Those routers in the latter area need to find routable IP addresses
of the router originating that ELC TLV before inserting the Entropy
Label (EL) for packets going to the Label Switch Path (LSP) tunnel
towards one of the above routable IP addresses..."
Later, such correlation requirement in the ISIS domain was addressed by introducing \
the source IPv4/IPv6 router ID sub-TLVs into the Extended Reachability TLVs (see \
https://tools.ietf.org/html/rfc7794). I forget whether the same extension to OSPF as \
RFC7794 has been done.
Best regards,
Xiaohu
------------------------------------------------------------------
From:bruno.decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Send Time:2018年8月3日(星期五) 04:50
To:draft-ietf-isis-mpls-elc@ietf.org \
<draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org>> \
Cc:lsr@ietf.org <lsr@ietf.org<mailto:lsr@ietf.org>> Subject:Re: [Lsr] I-D Action: \
draft-ietf-isis-mpls-elc-05.txt
Hi authors,
"4. Advertising ELC Using IS-IS
One bit of the Non-IGP Functional Capability Bits (Bit 0 is desired)
is to be assigned by the IANA for the ELC [RFC6790]."
RFC6790 defines ELC capability on a per FEC/LSP egress basis.
Please defines what you mean exactly with this per node capability. If this is \
expected to advertise ELC capability in spring networks, it's not crystal clear to me \
how it works in multi-area/domain network with IP prefix/SID redistribution. Possibly \
the ELC flag would need to be advertised on a per prefix basis.
Thanks,
Regards,
--Bruno
> -----Original Message-----
> From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of \
bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> > Sent: Thursday, August \
02, 2018 10:24 PM > To: \
draft-ietf-isis-mpls-elc@ietf.org<mailto:draft-ietf-isis-mpls-elc@ietf.org> > Cc: \
lsr@ietf.org<mailto:lsr@ietf.org> > Subject: Re: [Lsr] I-D Action: \
draft-ietf-isis-mpls-elc-05.txt >
> Hi authors,
>
> Please find below some minor comments:
>
> 1) Abstract:
> " In addition, this document introduces the Non-IGP Functional
> Capabilities Sub-TLV for advertising IS-IS router's actual non-IGP
> functional capabilities. ELC is one of such non-IGP functional
> capabilities."
>
> It's a matter of opinion but reducing the number of occurrences of " non-IGP \
functional > capabilities" may improve the S/N ration.
>
> 2)
> The format of the Router Non-IGP Functional Capabilities Sub-TLV is as \
follows: >
> 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=TBD1 | Length=4 |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> The sub-TLV is not hard coded/defined with a length of 4, hence this value should \
not be part of > the definition.
>
> 3)
> "Length: Indicates the length of the value portion in octets and will be a \
multiple of 4 octets" >
> Possibly :s/will/MUST
> Please specify the error handling. (e.g. disregards the whole sub-TLV, disregards \
the last 1 to 3 > octets, accept the whole sub-TLV...)
>
>
> 4)
> "One bit of the Non-IGP Functional Capability Bits (Bit 0 is desired) is to be \
assigned by the > IANA for the ELC [RFC6790]."
>
> Since this document defines the new sub-TLV, it can freely do any allocation \
itself. >
> 5)
> "The registration procedure is "Expert Review" as defined in [RFC8126]."
>
> You may want to read RFC 8126 https://tools.ietf.org/html/rfc8126#section-4.5
> Which, In particular, states:
> " The registry's
> definition needs to make clear to registrants what information is
> necessary.
>
> [...]
>
> The required documentation and review criteria, giving clear guidance
> to the designated expert, should be provided when defining the
> registry. It is particularly important to lay out what should be
> considered when performing an evaluation and reasons for rejecting a
> request. It is also a good idea to include, when possible, a sense
> of whether many registrations are expected over time, or if the
> registry is expected to be updated infrequently or in exceptional
> circumstances only. "
>
> 6)
> "This capability, referred to as Entropy Readable Label Depth (ERLD) as defined \
in [I-D.ietf- > mpls-spring-entropy-label] "
>
> This probably calls for this document to be a normative reference.
>
>
> " A new MSD-type of the Node MSD b-TLV
> [I-D.ietf-isis-segment-routing-msd], called ERLD is defined to
> advertise the ERLD of a given router."
>
> May be adding the reference to the document defining the ERLD:
> OLD: advertise the ERLD
> NEW: advertise the ERLD [I-D.ietf-mpls-spring-entropy-label]
>
> 7)
> "If a router has
> multiple line cards, the router MUST NOT announce the ELC [RFC6790]
> unless all of its linecards are capable of processing ELs."
>
> May be you mean
> OLD: all of its linecards
> OLD: all of the linecards of the links advertised as IS-IS adjacencies.
>
> Regards,
> --Bruno
>
> > -----Original Message-----
> > From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of \
internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> > > Sent: Tuesday, July \
31, 2018 4:07 PM > > To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> > Cc: lsr@ietf.org<mailto:lsr@ietf.org>
> > Subject: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Link State Routing WG of the IETF.
> >
> > Title : Signaling Entropy Label Capability and Entropy \
Readable Label Depth Using > > IS-IS
> > Authors : Xiaohu Xu
> > Sriganesh Kini
> > Siva Sivabalan
> > Clarence Filsfils
> > Stephane Litkowski
> > Filename : draft-ietf-isis-mpls-elc-05.txt
> > Pages : 7
> > Date : 2018-07-29
> >
> > Abstract:
> > Multiprotocol Label Switching (MPLS) has defined a mechanism to load
> > balance traffic flows using Entropy Labels (EL). An ingress Label
> > Switching Router (LSR) cannot insert ELs for packets going into a
> > given tunnel unless an egress LSR has indicated via signaling that it
> > has the capability of processing ELs, referred to as Entropy Label
> > Capability (ELC), on that tunnel. In addition, it would be useful
> > for ingress LSRs to know each LSR's capability of reading the maximum
> > label stack depth and performing EL-based load-balancing, referred to
> > as Entropy Readable Label Depth (ERLD), in the cases where stacked
> > LSPs are used for whatever reasons. This document defines mechanisms
> > to signal these two capabilities using IS-IS. These mechanisms are
> > useful when the label advertisement is also done via IS-IS. In
> > addition, this document introduces the Non-IGP Functional
> > Capabilities Sub-TLV for advertising IS-IS router's actual non-IGP
> > functional capabilities. ELC is one of such non-IGP functional
> > capabilities.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-05
> > https://datatracker.ietf.org/doc/html/draft-ietf-isis-mpls-elc-05
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-mpls-elc-05
> >
> >
> > Please note that it may take a couple of minutes from the time of submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > Lsr mailing list
> > Lsr@ietf.org<mailto:Lsr@ietf.org>
> > https://www.ietf.org/mailman/listinfo/lsr
>
> __________________________________________________________________________
> _______________________________________________
>
> 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.
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org<mailto:Lsr@ietf.org>
> https://www.ietf.org/mailman/listinfo/lsr
_________________________________________________________________________________________________________________________
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.
_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr
_________________________________________________________________________________________________________________________
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.
_________________________________________________________________________________________________________________________
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:x="urn:schemas-microsoft-com:office:excel" \
xmlns:p="urn:schemas-microsoft-com:office:powerpoint" \
xmlns:a="urn:schemas-microsoft-com:office:access" \
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" \
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" \
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" \
xmlns:b="urn:schemas-microsoft-com:office:publisher" \
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" \
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" \
xmlns:odc="urn:schemas-microsoft-com:office:odc" \
xmlns:oa="urn:schemas-microsoft-com:office:activation" \
xmlns:html="http://www.w3.org/TR/REC-html40" \
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" \
xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" \
xmlns:Repl="http://schemas.microsoft.com/repl/" \
xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" \
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" \
xmlns:ppda="http://www.passport.com/NameSpace.xsd" \
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" \
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" \
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" \
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" \
xmlns:udc="http://schemas.microsoft.com/data/udc" \
xmlns:xsd="http://www.w3.org/2001/XMLSchema" \
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" \
xmlns:ec="http://www.w3.org/2001/04/xmlenc#" \
xmlns:sp="http://schemas.microsoft.com/sharepoint/" \
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" \
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \
xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" \
xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" \
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" \
xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" \
xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" \
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" \
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" \
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" \
xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" \
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" \
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" \
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" \
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" \
xmlns:Z="urn:schemas-microsoft-com:" \
xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" \
xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" \
xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" \
xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" \
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:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
@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:"MS UI Gothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@MS UI Gothic";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@MingLiU";
panose-1:2 2 5 9 0 0 0 0 0 0;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* 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;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.prformathtml, li.prformathtml, div.prformathtml
{mso-style-name:prformathtml;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
{mso-style-name:"HTML Preformatted";
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.prformathtmlcar0
{mso-style-name:prformathtmlcar;
mso-style-priority:99;
font-family:Consolas;
mso-fareast-language:FR;}
span.htmlpreformattedchar0
{mso-style-name:htmlpreformattedchar;
mso-style-priority:99;
font-family:Consolas;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle37
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.8pt 70.8pt 70.8pt 70.8pt;}
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 \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Commenting \
on myself [Bruno]<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><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""> \
DECRAENE Bruno IMT/OLN <br>
<b>Sent:</b> Monday, August 27, 2018 4:57 PM<br>
<br>
<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi \
Acee,<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks \
for the suggestion.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Contrary \
to MSD, ELC does not require the knowledge of the path topology. Hence I don't think \
this is helpful to refer to LSP path topology.<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
Sorry, I meant :s/MSD/ERLD (Entropy Readable Label Depth)<o:p></o:p></span></p> <p \
class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Tiger's \
proposal could work for me, but I personally think it would be fair and clearer to \
clearly state that the proposal does not provide a solution for inter-AS and \
inter-protocol deployments.<o:p></o:p></span></p> <p class="MsoNormal"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">e.g. \
"The advertisement of ELC in Inter-AS and inter-protocol scenarios is not \
supported."<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
To clarify my position:<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- \
I believe that draft-ietf-isis-mpls-elc should support the use/advertisement of EL in \
SR-MPLS inter-area/AS/protocol deployments, in order to avoid regressions compared \
to LDP.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- \
In the meantime, I think the document should explicitly state that it does not \
support it (in its current version), in order to raise awareness of this \
limit<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">--Bruno<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><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""> Lsr \
[mailto:lsr-bounces@ietf.org] <b>On Behalf Of </b>Acee Lindem (acee)<br>
<b>Sent:</b> Wednesday, August 15, 2018 5:28 PM<br>
<b>To:</b> ???(??); Lsr; LITKOWSKI Stephane OBS/OINIS; Van De Velde, Gunter (Nokia - \
BE/Antwerp)<br> <b>Cc:</b> lsr@ietf.org; draft-ietf-isis-mpls-elc@ietf.org<br>
<b>Subject:</b> Re: [Lsr] I-D Action: \
draft-ietf-isis-mpls-elc-05.txt<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-family:"Calibri","sans-serif"">Hi Tiger, Bruno, \
<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif"">Or would this be \
better? <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif""> \
"The advertisement and discovery of the complete LSP path topology in inter-AS and \
inter-protocol scenarios is outside the scope of this document." \
<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif"">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif"">Acee<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" \
style="font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="color:black">From: </span></b><span lang="EN-US" style="color:black">Lsr \
<lsr-bounces@ietf.org> on behalf of "Xiaohu (Tiger) Xu" \
<xiaohu.xxh@alibaba-inc.com><br> <b>Reply-To: </b>"Xiaohu (Tiger) Xu" \
<xiaohu.xxh@alibaba-inc.com><br> <b>Date: </b>Friday, August 10, 2018 at 2:20 \
AM<br> <b>To: </b>Lsr <lsr-bounces@ietf.org>, Stephane Litkowski \
<stephane.litkowski@orange.com>, Gunter Van de Velde \
<gunter.van_de_velde@nokia.com><br> <b>Cc: </b>"lsr@ietf.org" \
<lsr@ietf.org>, "draft-ietf-isis-mpls-elc@ietf.org" \
<draft-ietf-isis-mpls-elc@ietf.org><br> <b>Subject: </b>Re: [Lsr] I-D Action: \
draft-ietf-isis-mpls-elc-05.txt<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.0pt"><o:p> </o:p></span></p> </div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><a name="_MailOriginalBody"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Bruno,</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">OK. \
I will add the text as follows: "How to apply the ELC advertisement in the \
inter-AS and inter-protocol scenarios is outside the scope of this \
document".<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Best \
regards,<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Xiaohu<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:bl \
ack">------------------------------------------------------------------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">From:bruno.decraene \
<bruno.decraene@orange.com><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Send \
Time:2018</span><span style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">年</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">8</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">月</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">9</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">日</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">星期四</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
17:32<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">To:</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.5pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
<xiaohu.xxh@alibaba-inc.com>; Lsr <lsr-bounces@ietf.org>; LITKOWSKI \
Stephane OBS/OINIS <stephane.litkowski@orange.com>; "Van De Velde, Gunter \
(Nokia - BE/Antwerp)" \
<gunter.van_de_velde@nokia.com><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Cc:lsr@ietf.org \
<lsr@ietf.org>; draft-ietf-isis-mpls-elc@ietf.org \
<draft-ietf-isis-mpls-elc@ietf.org><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Subject:Re: \
[Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Xiaohu,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Please \
see inline [Bruno]</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span \
style="font-size:10.0pt;font-family:"MS UI \
Gothic","sans-serif";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.0pt;font-family:"PMingLiU","serif";color:black">义先</span><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">)
[mailto:xiaohu.xxh@alibaba-inc.com] <br>
<b>Sent:</b> Thursday, August 09, 2018 4:40 AM</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">I \
agree with Les's points.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">To \
clarify the usage of the ELC in the inter-area scenario, I would like to \
add the following text to draft-ietf-isis|ospf-mpls-elc:</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black;border:none \
windowtext 1.0pt;padding:0cm">"When the ELC advertisement originated by a router \
in one area is propagated to another area in the inter-area scenario, those routers \
in the latter area need to find the routable IP addresses of the router originating \
that ELC advertisement before inserting the Entropy Label (EL) for packets going to \
the Label Switch Path (LSP) tunnel towards one of the above routable IP addresses. \
How to find the correlation between the Router-ID and the routable IP address of a \
given router is outside the scope of this document. Note that h<span \
style="background:white">ow to find the correlation between the Router-ID and the \
routable IP address of a given router in an ISIS domain is described in \
[RFC7794]. </span>"</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black;border:none \
windowtext 1.0pt;padding:0cm">Any comments and suggestions are welcome.</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
Please also clarify the usage of ELC in the inter-protocol/AS case. At minimum \
acknowledging that this solution does not work in this case.</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black;border:none \
windowtext 1.0pt;padding:0cm">Best regards,</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:bl \
ack">------------------------------------------------------------------</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">From:Les \
Ginsberg (ginsberg) <ginsberg=40cisco.com@dmarc.ietf.org></span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Send \
Time:2018</span><span style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">年</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">8</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">月</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">9</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">日</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">星期四</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
07:54</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">To:stephane.litkowski@orange.com \
<stephane.litkowski@orange.com>; "Van De Velde, Gunter (Nokia - \
BE/Antwerp)" <gunter.van_de_velde@nokia.com>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com></span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Cc:lsr@ietf.org \
<lsr@ietf.org>; draft-ietf-isis-mpls-elc@ietf.org \
<draft-ietf-isis-mpls-elc@ietf.org>; </span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.5pt;font-family:MingLiU;color:black">义先</span><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
<xiaohu.xxh@alibaba-inc.com></span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Subject:Re: \
[Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Stephane \
–</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">There \
are some issues you raise that I think are easily resolved/agreed upon – some \
others that may require more discussion.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Responses \
inline.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #E1E1E1 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> \
stephane.litkowski@orange.com <stephane.litkowski@orange.com> <br>
<b>Sent:</b> Monday, August 06, 2018 2:58 AM<br>
<b>To:</b> Van De Velde, Gunter (Nokia - BE/Antwerp) \
<gunter.van_de_velde@nokia.com>; Les Ginsberg (ginsberg) \
<ginsberg@cisco.com>; DECRAENE Bruno IMT/OLN \
<bruno.decraene@orange.com><br> <b>Cc:</b> lsr@ietf.org; \
draft-ietf-isis-mpls-elc@ietf.org; </span><span \
style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">(</span><span \
style="font-size:11.5pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">)
<xiaohu.xxh@alibaba-inc.com><br>
<b>Subject:</b> RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi \
Gunter,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">IMO, \
there are multiple cases to distinguish.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
basic case (Adj-SIDs & Prefix-SIDs, single area, single domain, single \
protocol):</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">ELC \
as a node property is a good thing. I personally do not see a use case to get some \
segments to be ELC and some others not to be ELCs.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
Good – I think there is general agreement on this point.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Multiarea \
case:</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">When \
prefixes are leaked from one area to the other, we are losing the per node properties \
(like the ERLD). If we want to get benefit of EL, the ingress node in one area \
should get the ELC status of nodes in the other areas.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoListParagraph" \
style="margin-left:72.0pt;text-indent:-14.25pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">One \
solution would be to propagate the ELC as part of the prefix advertisement (when the \
prefix is leaked). We are still losing the ERLD which may impact the loadbalancing \
(EL/ELI placement not efficient).</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoListParagraph" \
style="margin-left:72.0pt;text-indent:-14.25pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Another \
solution could be for the ingress node to retrieve the ERLD from another source of \
information like BGP-LS but that's not trivial as the ingress must know the best \
route to the tail from the ABR point of view.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
There is no issue with multiarea. Repeating some points made earlier in the \
thread:</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> \
<p class="MsoNormal" style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Both \
IGPs have the ability to leak router capabilities/info between areas. Which means the \
node based attributes ELC and ERLD can be available domain-wide.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">We \
also have the ability to leak source router-id with the leaked prefixes (OSPF has a \
gap here but we have a commitment to address that with a modest extension to the \
protocol – which needs to be done for multiple reasons.)</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">So \
all the information necessary is available in all areas.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Multiprotocol \
case:</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoListParagraph" style="margin-left:93.75pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">It's \
not really different than the multiarea case.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
Multiprotocol is quite different than multiarea.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">In \
the case of multiprotocol we do not have the ability to know/advertise the original \
source router-id nor the node capabilities in the destination protocol. It is not \
even guaranteed that reachability to the router-id of the source protocol is \
available in the area of the destination protocol.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">This \
is where a controller based solution is most advantageous as it has the ability to \
learn all of that information from all of the protocols enabled in the \
domain.</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> \
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">SRMS \
and SR-LDP stitching:</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoListParagraph" \
style="margin-left:72.0pt;text-indent:-14.25pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:Symbol;color:#1F497D"> </span><span lang="EN-US" \
style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">SR \
to LDP: the LDP tail-end may be ELC, if an SR ingress node wants to use an ELI/EL on \
top of the prefix SID associated to the LDP FEC, we need to propagate the ELC known \
from LDP (attached to the FEC) to the SR advertisement. The SR-LDP stitching node is \
not a tail-end node, it will do a label swap, not a pop then push. So an entropy \
label pushed by the SR ingress node will be carried to the tail-end LDP node. Am I \
wrong ?</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:Symbol;color:#1F497D"> </span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">LDP \
to SR: the stitching node knows if the tail-end SR node is ELC (through the IGP \
advertisement). It may propagate the ELC into LDP. All the prefixes of the tail-end \
SR node which are LDP FECs can get the ELC set if the SR tail-end node is \
ELC.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:50.25pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">I \
do not see any strict prescription requirement for the LSP here.</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
Here there is more room for differences of opinion.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">One \
viewpoint is that SR-LDP interworking is a transition strategy. Any solution which \
attempts to exchange ELC/ELRD information between the SR<->LDP portions of the \
network will be "messy" and perhaps not worth the trouble as we hope that the \
transition will be "short-lived".</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Another \
viewpoint could be that if the transition period is long enough it may be useful to \
have such support.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">But \
as any solution (even if we were to advertise ELC per prefix) would be non-trivial, I \
think there needs to be a strong case for taking this on.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Do \
you believe we have a strong case here? </span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Binding \
SID:</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoListParagraph" style="margin-left:93.75pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Binding \
SID associated to an SRTE LSP: if an ingress node wants to put an ELI/EL next to a \
binding SID, it needs to ensure that the tail-end of the binding SID is ELC. In \
<p class="MsoListParagraph" style="margin-left:93.75pt;text-indent:-14.25pt"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">-</span><span \
lang="EN-US" style="font-size:7.0pt;color:#1F497D">
</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Binding \
SID associated to an RSVP-TE LSP: this case was removed from the SR extensions, but \
if it is revived in future, the ELC status of the RSVP-TE LSP may need to be \
propagated to the SR domain as part of the binding SID advertisement if we want the \
ingress to be able to push an ELI/ELI next to the BSID.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
I don't appreciate the problem here. </span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">I \
think you are talking about two possible EL use cases.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">1)An \
ingress node which imposes the binding-SID may wish to utilize entropy on the path to \
the owner of the Binding-SID. As the node sid (or possibly an adj-sid advertised by \
the owner of the binding sid) will be needed in the label stack, the ingress node \
still knows – independent of the binding-sid, whether the owner is \
ELC.</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">2)When \
the packet arrives at the node which owns the binding SID, that node may wish to \
include EL in the label stack which it imposes to implement the policy defined by \
the binding SID. But as the ELC of the LSP tail end is known this should not be a \
problem. And I do not see why the ingress node that imposed the binding-sid needs to \
know whether the owner of the binding-sid will/will not impose \
EL.</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> \
Les</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Brgds,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Stephane</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> \
Van De Velde, Gunter (Nokia - BE/Antwerp) [</span><a \
href="mailto:gunter.van_de_velde@nokia.com" target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:gunter.van_de_velde@nokia.com</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<br>
<b>Sent:</b> Monday, August 06, 2018 10:47<br>
<b>To:</b> LITKOWSKI Stephane OBS/OINIS; Les Ginsberg (ginsberg); DECRAENE Bruno \
IMT/OLN<br> <b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">;
</span><span style="font-size:10.0pt;font-family:"MS UI \
Gothic","sans-serif";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.0pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:10.0pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">)<br>
<b>Subject:</b> RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">"</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
other case to handle is the binding SID. The binding SID needs to reflect the ELC of \
the associated LSP.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
SRMS case is also interesting if we want to enable entropy when doing SR-LDP \
interworking.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">"</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">Does \
this not assume that a LSP is strictly defined hop-by-hop? If LSP is a loose LSP, \
then it is very well possible that </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">depending \
on the state of network, sometimes the LSP is ELC capable and another time it is not \
capable or the ERLD changes. </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">I'm \
not convinced or have clear understanding on the value of ELC/ERLD for a particular \
LSP without making some strict prescriptions on LSP.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">To \
me, having ERLD (and maybe of less importance) ELC has value only for a controller to \
make more educated decisions upon packet flows. </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">Having \
such information per LSP seems complex and of lesser value as per node in the \
network. </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">G/</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-top:solid #E1E1E1 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> \
Lsr <</span><a href="mailto:lsr-bounces@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">lsr-bounces@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">>
<b>On Behalf Of </b></span><a href="mailto:stephane.litkowski@orange.com" \
target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">stephane.litkowski@orange.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Sent:</b> Monday, August 6, 2018 10:26<br>
<b>To:</b> Les Ginsberg (ginsberg) <</span><a href="mailto:ginsberg@cisco.com" \
target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">ginsberg@cisco.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">>;
DECRAENE Bruno IMT/OLN <</span><a href="mailto:bruno.decraene@orange.com" \
target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">;
</span><span style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">(</span><span \
style="font-size:11.5pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">)
<</span><a href="mailto:xiaohu.xxh@alibaba-inc.com" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">xiaohu.xxh@alibaba-inc.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Subject:</b> Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi \
Les, Bruno,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
I also raised the case of redistribution of IP prefix/SID between IGP domains. \
Possibly one using OSPF and one using IS-IS. This case needs to be also \
covered.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
If a prefix is leaked between protocols then you lose the identification of the \
source. Which means you have other considerations which are not met e.g., what is \
the value for ERLD (which also is clearly not a per prefix value). To know this you \
need to know the source and have the Node Capabilities.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[SLI] \
I agree with Les that we are losing the ERLD information. But I think it is worth \
allowing the propagation of the ELC even if we are losing the ERLD info. We make \
this propagation optional. Moreover it will be still optional for the ingress node to \
use it.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">I \
agree that we must not leak the node infos.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
other case to handle is the binding SID. The binding SID needs to reflect the ELC of \
the associated LSP.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">The \
SRMS case is also interesting if we want to enable entropy when doing SR-LDP \
interworking.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> \
Les Ginsberg (ginsberg) [</span><a href="mailto:ginsberg@cisco.com" \
target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:ginsberg@cisco.com</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<br>
<b>Sent:</b> Friday, August 03, 2018 23:27<br>
<b>To:</b> DECRAENE Bruno IMT/OLN<br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">;
</span><span style="font-size:10.0pt;font-family:"MS UI \
Gothic","sans-serif";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.0pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:10.0pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">)<br>
<b>Subject:</b> RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Bruno \
–</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Inline.</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #E1E1E1 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><a \
href="mailto:bruno.decraene@orange.com" target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">
<</span><a href="mailto:bruno.decraene@orange.com" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">>
<br>
<b>Sent:</b> Friday, August 03, 2018 10:01 AM<br>
<b>To:</b> Les Ginsberg (ginsberg) <</span><a href="mailto:ginsberg@cisco.com" \
target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">ginsberg@cisco.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">;
</span><span style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">(</span><span \
style="font-size:11.5pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">)
<</span><a href="mailto:xiaohu.xxh@alibaba-inc.com" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">xiaohu.xxh@alibaba-inc.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Subject:</b> RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Les,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Please \
see inline [Bruno]</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> \
Les Ginsberg (ginsberg) [</span><a href="mailto:ginsberg@cisco.com" \
target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:ginsberg@cisco.com</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<br>
<b>Sent:</b> Friday, August 03, 2018 6:32 PM<br>
<b>To:</b> DECRAENE Bruno IMT/OLN; </span><span \
style="font-size:10.0pt;font-family:"MS UI \
Gothic","sans-serif";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.0pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:10.0pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">)<br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Subject:</b> RE: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Bruno \
–</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">I \
appreciate why you suggest per-prefix signaling for ELC, but I would prefer that we \
not employ that model.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
Thanks for the feedback. That's part of the discussion that I was calling \
for.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">ELC \
is clearly a node capability</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
It's a node capability of the egress of the LSP. Hence it could also be seen as a \
property of the LSP ;-) RFC 6790 says "</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black">one may \
choose to associate ELs with MPLS tunnels (LSPs) or</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black"> \
with MPLS applications […] We take the former approach"</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">– \
signaling it in per node scope is therefore most appropriate. And it aligns with the \
SR model where we do not need to depend on hop-by-hop signaling as in the LDP \
case.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
I would argue that advertising ELC per prefix is not a hop-by-hop signaling as in the \
LDP case. That's one single advertisement per area/level.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
I probably expressed this poorly.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">As \
LDP does hop-by-hop signaling the "natural" way to signal this in LDP is in the \
neighbor label exchanges.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">However, \
SR signaling is scoped by the area/domain and therefore we have the ability to \
advertise capability in a way that matches how the support is actually enabled. \
There is no basis for a node to advertise ELC support for local Prefix A but not for \
Local Prefix B. So advertising this per prefix is redundant (though I agree is still \
possible).</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">As \
regards the interarea issues you raise:</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Both \
Router Capability TLV (IS-IS) and Router Information LSA (OSPF) support domain-wide \
flooding scope. This is not a new capability</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
Agreed.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">– \
though I do agree with you that the ELC drafts should explicitly mention the flooding \
scope requirement.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
May be the scalability impact may need to be discussed. I would assume an impact on \
the size of the LSDB (but a priori no impact on the churn). This is also a new \
behavior which may surprise operational teams.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
The significant issue as regards scale is the leaking of the prefixes – not the \
leaking of per-Node information. So I am not greatly concerned about leaking Node \
Capability info.</span></i></b><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">[Bruno] \
I also raised the case of redistribution of IP prefix/SID between IGP domains. \
Possibly one using OSPF and one using IS-IS. This case needs to be also \
covered.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">[Les:] \
If a prefix is leaked between protocols then you lose the identification of the \
source. Which means you have other considerations which are not met e.g., what is \
the value for ERLD (which also is clearly not a per prefix value). To know this you \
need to know the source and have the Node Capabilities.</span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></i></b><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><b><i><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> \
Les</span></i></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Regards,</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">--Bruno</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">As \
regards identifying the source of a prefix advertisement domain-wide, IS-IS has a \
complete solution for this as defined in RFC 7794.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">OSPF \
is lacking support for advertising the source Router-ID, but this can be easily \
remedied by defining an extension using Extended Prefix LSA (as has been mentioned \
by Peter in another thread). And this functionality is needed for other reasons e.g., \
to know when PHP should/should not be done. So it is probably past time when this \
should be defined.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">So \
I think it is better if we use the per-node ELC scope proposed in the ELC \
drafts.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D">As \
an aside, I would prefer that we utilize the existing TE Node Capability Descriptor \
registry defined in RFC 5073 rather than invent a new codepoint/registry (the \
proposed Non-IGP Functional Capabilities registry) – but that is a minor \
point.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> \
Les</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #E1E1E1 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"> \
Lsr <</span><a href="mailto:lsr-bounces@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">lsr-bounces@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">>
<b>On Behalf Of </b></span><a href="mailto:bruno.decraene@orange.com" \
target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Sent:</b> Friday, August 03, 2018 12:46 AM<br>
<b>To:</b> </span><span style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">徐小虎</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">(</span><span \
style="font-size:11.5pt;font-family:MingLiU;color:black">义</span><span \
style="font-size:11.5pt;font-family:"MS \
Gothic";color:black">先</span><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">)
<</span><a href="mailto:xiaohu.xxh@alibaba-inc.com" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">xiaohu.xxh@alibaba-inc.com</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">><br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:11.5pt;font-family:"Calibri","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black">;
</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<b>Subject:</b> Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hi \
Xiaohu,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks \
for the reply.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">You \
seem to assume/require that (router) capability advertisement be propagated across \
IGP areas/domains. If so,</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- \
this is a new requirement for existing multi-area networks that need to be indicated \
in the draft</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- \
I find this debatable. This point should be explicitly discussed. I'd rather \
advertise the ELC capability on a per Segment basis. This would also be better \
aligned with RFC 6790 hence safer if EL extensions are defined. The (Segment Routing) \
Prefix-SID sub-TLV has 2 flags remaining. This may be a good candidate as this \
information seems SR specific. Alternatively, RFC7794 may be used.</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Best \
regards,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">--Bruno</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div \
style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div \
style="border:none;border-top:solid #B5C4DF 1.0pt;padding:0cm 0cm 0cm 0cm"> <p \
class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> \
Lsr [</span><a href="mailto:lsr-bounces@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:lsr-bounces@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">]
<b>On Behalf Of </b>???(??)<br>
<b>Sent:</b> Friday, August 03, 2018 4:13 AM<br>
<b>To:</b> Lsr; </span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" \
target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Cc:</b> </span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
<b>Subject:</b> Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></p> <div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Hi \
Bruno,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Thanks \
for raising this important issue.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">In \
fact, the Routable IP Address TLVs/sub-TLVs as described in (</span><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-routable-ip-address-02" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://tools.ietf.org/html/draft-ietf-ospf-routable-ip-address-02</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
and (</span><a href="https://tools.ietf.org/html/draft-xu-isis-routable-ip-address-01" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://tools.ietf.org/html/draft-xu-isis-routable-ip-address-01</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">) respectively
were intended to address the problem that you had mentioned (i.e., it is \
required for OSPF routers in one area to find correlations between routable IP \
addresses and capabilities of OSPF routers in another area). </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">The \
following text is quoted from </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">" \
</span><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">There \
are several situations where it is required for OSPF routers in</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <pre \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black"> \
one area to find correlations between routable IP addresses and</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black"> \
capabilities of OSPF routers in another area. One example is the</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black"> \
Entropy Label Capability (ELC) advertisement [</span><a \
href="https://tools.ietf.org/html/draft-ietf-ospf-routable-ip-address-02#ref-I-D.xu-ospf-mpls-elc" \
target="_blank" title=""Signaling Entropy Label Capability Using \
OSPF""><span lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New"">I-D.xu-ospf-mpls-elc</span></a><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black">]</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> across the OSPF domain. In this example, \
assume the ELC TLV</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> originated by a router in one area is propagated \
to another area.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> Those routers in the latter area need to find \
routable IP addresses</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> of the router originating that ELC TLV before \
inserting the Entropy</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> Label (EL) for packets going to the Label Switch \
Path (LSP) tunnel</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> towards one of the above routable IP \
addresses..."</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Later, \
such correlation requirement in the ISIS domain was addressed by introducing \
the source IPv4/IPv6 router ID sub-TLVs into the Extended Reachability \
TLVs (see </span><a href="https://tools.ietf.org/html/rfc7794" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://tools.ietf.org/html/rfc7794</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">).
I forget whether the same extension to OSPF as RFC7794 has been \
done. </span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> \
</div> <div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Best \
regards,</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Xiaohu</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:bl \
ack">------------------------------------------------------------------</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">From:bruno.decraene \
<</span><a href="mailto:bruno.decraene@orange.com" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">></span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Send \
Time:2018</span><span style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">年</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">8</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">月</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">3</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">日</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">(</span><span \
style="font-size:10.5pt;font-family:"MS \
Gothic";color:black">星期五</span><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">)
04:50</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">To:draft-ietf-isis-mpls-elc@ietf.org \
<</span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">></span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Cc:lsr@ietf.org \
<</span><a href="mailto:lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">></span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Subject:Re: \
[Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">Hi authors,<br>
<br>
"4. Advertising ELC Using IS-IS<br>
<br>
One bit of the Non-IGP Functional Capability Bits (Bit 0 is desired)<br>
is to be assigned by the IANA for the ELC [RFC6790]."<br>
<br>
RFC6790 defines ELC capability on a per FEC/LSP egress basis.<br>
Please defines what you mean exactly with this&nbs \
p;per node capability. If this is expected to \
advertise ELC capability in spring networks, it's n \
ot crystal clear to me how it works in mu \
lti-area/domain network with IP prefix/SID redistribution.<br>
Possibly the ELC flag would need to be advertised on a per prefix basis.<br>
<br>
Thanks,<br>
Regards,<br>
--Bruno<br>
<br>
<br>
> -----Original Message-----<br>
> From: Lsr [</span><a href="mailto:lsr-bounces@ietf.org" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">mailto:lsr-bounces@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">] On Behalf Of </span><a \
href="mailto:bruno.decraene@orange.com" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">bruno.decraene@orange.com</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> Sent: Thursday, August 02, 2018 10:24 PM<br>
> To: </span><a href="mailto:draft-ietf-isis-mpls-elc@ietf.org" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">draft-ietf-isis-mpls-elc@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> Cc: </span><a href="mailto:lsr@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> Subject: Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt<br>
> <br>
> Hi authors,<br>
> <br>
> Please find below some minor comments:<br>
> <br>
> 1) Abstract:<br>
> " In addition, this document introduces the Non-IGP Functional<br>
> Capabilities Sub-TLV for advertising IS-IS router's actual non-IGP<br>
> functional capabilities. ELC is one of such non-IGP functional<br>
> capabilities."<br>
> <br>
> It's a matter of opinion but reducing&nb \
sp;the number of occurrences of " non-IGP functional<br>
> capabilities" may improve the S/N ration.<br>
> <br>
> 2)<br>
> The format of the Router No \
n-IGP Functional Capabilities Sub-TLV is as follows:<br>
> <br>
> 0 &nb \
sp;   \
; 1 \
2 3<br>
> 0 1 2 \
3 4 5 6 7 8 9 0 1 2 3 4 5& \
nbsp;6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<br>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
> | Type=TBD1 | Length=4 |<br>
> +-+-+-+- \
3;-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \
-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
> <br>
> <br>
> The sub-TLV is not hard coded/defined wi \
th a length of 4, hence this value should not be part of<br>
> the definition.<br>
> <br>
> 3)<br>
> "Length: Indicates the length of the&nbs \
p;value portion in octets and will be a multiple of 4 octets"<br>
> <br>
> Possibly :s/will/MUST<br>
> Please specify the error handling. (e.g.  \
;disregards the whole sub-TLV, disregards the last 1 to 3<br>
> octets, accept the whole sub-TLV...)<br>
> <br>
> <br>
> 4)<br>
> "One bit of the Non-IGP Functional \
Capability Bits (Bit 0 is desired) is to be assigned by the<br>
> IANA for the ELC [RFC6790]."<br>
> <br>
> Since this document defines the new sub- \
TLV, it can freely do any allocation itself.<br> \
> <br> > 5)<br>
> "The registration procedure is "Expert&n \
bsp;Review" as defined in [RFC8126]."<br> \
> <br> \
> You may want to read RFC 8126 </span><a \
href="https://tools.ietf.org/html/rfc8126#section-4.5" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://tools.ietf.org/html/rfc8126#section-4.5</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> Which, In particular, states:<br>
> " The registry's<br>
> definition needs to make clear to registrants what information is<br>
> necessary.<br>
> <br>
> [...]<br>
> <br>
> The required documentation and review criteria, giving clear guidance<br>
> to the designated expert, should be provided when defining the<br>
> registry. It is particularly important to lay out what should be<br>
> considered when performing an evaluation and reasons for rejecting a<br>
> request. It is also a&nbs \
p;good idea to include, when possible, a sense<br> \
> of whether many registrations are expected over time, or if the<br>
> registry is expected to be updated infrequently or in exceptional<br>
> circumstances only. "<br>
> <br>
> 6)<br>
> "This capability, referred to as Entropy \
Readable Label Depth (ERLD) as defined in [I-D.ietf-<br>
> mpls-spring-entropy-label] "<br>
> <br>
> This probably calls for this document to be a normative reference.<br>
> <br>
> <br>
> " A new MSD-type of the Node MSD b-TLV<br>
> [I-D.ietf-isis-segment-routing-msd], called ERLD is defined to<br>
> advertise the ERLD of a given router."<br>
> <br>
> May be adding the reference to the document defining the ERLD:<br>
> OLD: advertise the ERLD<br>
> NEW: advertise the ERLD [I-D.ietf-mpls-spring-entropy-label]<br>
> <br>
> 7)<br>
> "If a router has<br>
> multiple line cards, the router MUST NOT announce the ELC [RFC6790]<br>
> unless all of its linecards are capable of processing ELs."<br>
> <br>
> May be you mean<br>
> OLD: all of its linecards<br>
> OLD: all of the linecards of the links advertised as IS-IS adjacencies.<br>
> <br>
> Regards,<br>
> --Bruno<br>
> <br>
> > -----Original Message-----<br>
> > From: Lsr [</span><a \
href="mailto:lsr-bounces@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">mailto:lsr-bounces@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black">] On Behalf Of </span><a \
href="mailto:internet-drafts@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">internet-drafts@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> > Sent: Tuesday, July 31, 2018 4:07 PM<br>
> > To: </span><a \
href="mailto:i-d-announce@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">i-d-announce@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> > Cc: </span><a href="mailto:lsr@ietf.org" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> > Subject: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-05.txt<br>
> ><br>
> ><br>
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.<br>
> > This draft is a work item&nb \
sp;of the Link State Routing WG of the IETF.<br>
> ><br>
> > Title& \
nbsp; : Signaling  \
;Entropy Label Capability and Entropy Readable Label Depth Using<br>
> > IS-IS<br>
> > Authors : Xiaohu Xu<br>
> >   \
; Sriganesh Kini<br>
> >   \
; Siva Sivabalan<br>
> >   \
; Clarence Filsfils<br>
> >   \
; Stephane Litkowski<br>
> > Filename : draft-ietf-isis-mpls-elc-05.txt<br>
> > Pages : 7<br>
> > Date : 2018-07-29<br>
> ><br>
> > Abstract:<br>
> > Multiprotocol Label Switch \
ing (MPLS) has defined a mechanism to load<br> \
> > balance traffic flows  \
;using Entropy Labels (EL). An ingress Label<br> \
> > Switching Router (LSR)&nbs \
p;cannot insert ELs for packets going into a<br> \
> > given tunnel unless a \
n egress LSR has indicated via signaling that it<br>
> > has the capability o \
f processing ELs, referred to as Entropy Label<br> \
> > Capability (ELC), on \
that tunnel. In addition, it would be useful<br>
> > for ingress LSRs to& \
nbsp;know each LSR's capability of reading the maximum<br>
> > label stack depth and performing EL-based load-balancing, referred to<br>
> > as Entropy Readable \
Label Depth (ERLD), in the cases where stacked<br> \
> > LSPs are used for&nbs \
p;whatever reasons. This document defines mechanisms<br>
> > to signal these two& \
nbsp;capabilities using IS-IS. These mechanisms are<br>
> > useful when the labe \
l advertisement is also done via IS-IS. In<br>
> > addition, this document introduces the Non-IGP Functional<br>
> > Capabilities Sub-TLV for advertising IS-IS router's actual non-IGP<br>
> > functional capabilities. ELC is one of such non-IGP functional<br>
> > capabilities.<br>
> ><br>
> ><br>
> > The IETF datatracker status page for this draft is:<br>
> > </span><a \
href="https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> ><br>
> > There are also htmlized versions available at:<br>
> > </span><a \
href="https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-05" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-05</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> > </span><a \
href="https://datatracker.ietf.org/doc/html/draft-ietf-isis-mpls-elc-05" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://datatracker.ietf.org/doc/html/draft-ietf-isis-mpls-elc-05</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> ><br>
> > A diff from the previous version is available at:<br>
> > </span><a \
href="https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-mpls-elc-05" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-mpls-elc-05</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> ><br>
> ><br>
> > Please note that it may take& \
nbsp;a couple of minutes from the time of submission<br>
> > until the htmlized version and diff are available at tools.ietf.org.<br>
> ><br>
> > Internet-Drafts are also available by anonymous FTP at:<br>
> > </span><a href="ftp://ftp.ietf.org/internet-drafts/" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">ftp://ftp.ietf.org/internet-drafts/</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> ><br>
> > _______________________________________________<br>
> > Lsr mailing list<br>
> > </span><a href="mailto:Lsr@ietf.org" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">Lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> > </span><a \
href="https://www.ietf.org/mailman/listinfo/lsr" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://www.ietf.org/mailman/listinfo/lsr</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> <br>
> __________________________________________________________________________<br>
> _______________________________________________<br>
> <br>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou<br>
> privilegiees et ne doivent donc<br>
> pas etre diffuses, exploites ou copies s \
ans autorisation. Si vous avez recu ce message par<br>
> erreur, veuillez le signaler<br>
> a l'expediteur et le detruire ainsi que& \
nbsp;les pieces jointes. Les messages electroniques etant<br>
> susceptibles d'alteration,<br>
> Orange decline toute responsabilite si ce&nbs \
p;message a ete altere, deforme ou falsifie. Merci.<br>
> <br>
> This message and its attachments may con \
tain confidential or privileged information that may<br>
> be protected by law;<br>
> they should not be distributed, used or copied without authorisation.<br>
> If you have received this email in  \
;error, please notify the sender and delete this message and<br>
> its attachments.<br>
> As emails may be altered, Orange is  \
;not liable for messages that have been modified, changed<br>
> or falsified.<br>
> Thank you.<br>
> <br>
> _______________________________________________<br>
> Lsr mailing list<br>
> </span><a href="mailto:Lsr@ietf.org" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">Lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
> </span><a href="https://www.ietf.org/mailman/listinfo/lsr" \
target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://www.ietf.org/mailman/listinfo/lsr</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
<br>
_________________________________________________________________________________________________________________________<br>
<br>
Ce message et ses pieces jointes peuvent contenir&n \
bsp;des informations confidentielles ou privilegiees et ne doivent donc<br>
pas etre diffuses, exploites ou copies sans autori \
sation. Si vous avez recu ce message par erreur, veuillez le signaler<br>
a l'expediteur et le detruire ainsi que les p \
ieces jointes. Les messages electroniques etant susceptibles d'alteration,<br>
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<br>
<br>
This message and its attachments may contain confid \
ential or privileged information that may be protected by law;<br>
they should not be distributed, used or copied without authorisation.<br>
If you have received this email in error, ple \
ase notify the sender and delete this message and its attachments.<br>
As emails may be altered, Orange is not liabl \
e for messages that have been modified, changed or falsified.<br>
Thank you.<br>
<br>
_______________________________________________<br>
Lsr mailing list<br>
</span><a href="mailto:Lsr@ietf.org" target="_blank"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">Lsr@ietf.org</span></a><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><br>
</span><a href="https://www.ietf.org/mailman/listinfo/lsr" target="_blank"><span \
lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma","sans-serif"">https://www.ietf.org/mailman/listinfo/lsr</span></a><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> <div>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:15.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
</div>
</div>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black">_________________________________________________________________________________________________________________________</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier \
New";color:black"> </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">Ce message et ses pieces jointes peuvent contenir des \
informations confidentielles ou privilegiees et ne doivent donc</span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black">pas etre \
diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par \
erreur, veuillez le signaler</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">a l'expediteur et le detruire ainsi que les pieces jointes. \
Les messages electroniques etant susceptibles d'alteration,</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">Orange decline toute responsabilite si ce message a ete \
altere, deforme ou falsifie. Merci.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black"> </span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">This message and its attachments may contain confidential or \
privileged information that may be protected by law;</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">they should not be distributed, used or copied without \
authorisation.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></pre> \
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="font-size:10.0pt;font-family:"Courier New";color:black">If you have \
received this email in error, please notify the sender and delete this message and \
its attachments.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">As emails may be altered, Orange is not liable for messages \
that have been modified, changed or falsified.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="font-size:10.0pt;font-family:"Courier \
New";color:black">Thank you.</span><span lang="EN-US" \
style="color:black"><o:p></o:p></span></pre> </div>
</div>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Ce message et ses \
pieces jointes peuvent contenir des informations confidentielles ou privilegiees et \
ne doivent donc<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Orange decline \
toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">they should not be distributed, used or copied \
without authorisation.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Thank \
you.<o:p></o:p></span></pre> </div>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Ce message et ses \
pieces jointes peuvent contenir des informations confidentielles ou privilegiees et \
ne doivent donc<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Orange decline \
toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">they should not be distributed, used or copied \
without authorisation.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Thank \
you.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Ce message et ses \
pieces jointes peuvent contenir des informations confidentielles ou privilegiees et \
ne doivent donc<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Orange decline \
toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"> <o:p></o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">they should not be distributed, used or copied \
without authorisation.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Thank \
you.<o:p></o:p></span></pre> </div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:15.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"> </span><span \
lang="EN-US" style="color:black"><o:p></o:p></span></p> </div>
</div>
</div>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"><o:p> </o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Ce message et ses \
pieces jointes peuvent contenir des informations confidentielles ou privilegiees et \
ne doivent donc<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Orange decline \
toute responsabilite si ce message a ete altere, deforme ou falsifie. \
Merci.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span lang="EN-US" \
style="color:black"><o:p> </o:p></span></pre> <pre \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">This message and \
its attachments may contain confidential or privileged information that may be \
protected by law;<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">they should not be distributed, used or copied \
without authorisation.<o:p></o:p></span></pre> <pre style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 style="margin-left:36.0pt"><span \
lang="EN-US" style="color:black">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 \
style="margin-left:36.0pt"><span lang="EN-US" style="color:black">Thank \
you.<o:p></o:p></span></pre> </blockquote>
<div>
<p class="MsoNormal" style="margin-left:36.0pt;line-height:15.0pt"><span lang="EN-US" \
style="font-size:10.5pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</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>
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
--===============0820462235799657321==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic