Re: [mpls] [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"

"Acee Lindem (acee)" <acee@cisco.com> Fri, 18 November 2016 23:33 UTC

Return-Path: <acee@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1660129490; Fri, 18 Nov 2016 15:33:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.017
X-Spam-Level:
X-Spam-Status: No, score=-16.017 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qD3cVQLAcwJU; Fri, 18 Nov 2016 15:33:00 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0D61126BF7; Fri, 18 Nov 2016 15:32:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=193671; q=dns/txt; s=iport; t=1479511979; x=1480721579; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=AlhpqyDINTST2f5N115mCC/xHYz5tS5EhbuzxN2BIM8=; b=kf4STjCNqvbBArTy5JTDn+18pr9Ze/zMUBQS6HJksdrOe7IPMLeMIY9X PvgpeCD21ghHro+ut7JRB44/+gxe3+M+1p6nShXyveDI7dDe9OeL2SUyk bc8RLU6RMNe195JNLWq6B+m+x7nu+NYqN9kQOd3RIQlUXvFBgCnLUCYlY Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AzAQDFji9Y/49dJa1eGQEBAQEBAQEBAQEBBwEBAQEBgnM2DgEBAQEBH1iBAAeCfIo8lxKUZoIEAx0BDIV3AhqBdT8UAQIBAQEBAQEBYiiEaAEBAQMBAQEBCQIMAQIGCjgJCwULAgEGAhEDAQEBIQEGAwICAiULFAkIAgQBDQUbiEkIDo5YnUWCKYtUAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWKDoEIhBsKAQYBMwgBBw+CToJdBYk5iyqFaAGGP4MPhyOBcIR3gz+EVYEsjVuECgEeN10uHYMoHIFdcgGGBgEOF4EKgQwBAQE
X-IronPort-AV: E=Sophos;i="5.31,660,1473120000"; d="scan'208,217";a="350379548"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Nov 2016 23:32:57 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id uAINWug0016584 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 18 Nov 2016 23:32:57 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 18 Nov 2016 18:32:55 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 18 Nov 2016 18:32:55 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
Thread-Index: AQHSPmUIklF99/iqNkqI5o+7NYJvS6DXyyyAgACUO7eABqFB4IAAWeuA
Date: Fri, 18 Nov 2016 23:32:55 +0000
Message-ID: <D454EA3F.8A24B%acee@cisco.com>
References: <D4438504.8827B%acee@cisco.com> <16761_1478515435_58205AEB_16761_1458_1_53C29892C857584299CBF5D05346208A1EC6CD2A@OPEXCLILM21.corporate.adroot.infra.ftgroup> <D44692FE.88550%acee@cisco.com> <28362_1478603748_5821B3E4_28362_100_6_53C29892C857584299CBF5D05346208A1EC703D3@OPEXCLILM21.corporate.adroot.infra.ftgroup> <0361DDF1-086E-4E94-8EC6-6C38CBA19B76@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB2B73B@NKGEML515-MBX.china.huawei.com> <20678_1478768186_5824363A_20678_143_1_53C29892C857584299CBF5D05346208A1EC72B94@OPEXCLILM21.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB2B97E@NKGEML515-MBX.china.huawei.com> <23297_1478784668_5824769C_23297_3960_1_53C29892C857584299CBF5D05346208A1EC73217@OPEXCLILM21.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB2BF6A@NKGEML515-MBX.china.huawei.com> <D44DC081.88C99%acee@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB3317C@NKGEML515-MBX.china.huawei.com> <17816_1479120670_58299718_17816_688_3_53C29892C857584299CBF5D05346208A1EC772AB@OPEXCLILM21.corporate.adroot.infra.ftgroup> <5082_1479121544_58299A88_5082_3792_4_d485722b-6920-480f-8993-0eb383703f96@OPEXCLILM44.corporate.adroot.infra.ftgroup> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB3568E@NKGEML515-MBX.china.huawei.com> <28959_1479490211_582F3AA3_28959_7751_1_53C29892C857584299CBF5D05346208A1EC95702@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <28959_1479490211_582F3AA3_28959_7751_1_53C29892C857584299CBF5D05346208A1EC95702@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.127.84]
Content-Type: multipart/alternative; boundary="_000_D454EA3F8A24Baceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/rivvmi7RTSFl2RhkjqKM2_VtmLo>
Cc: OSPF WG List <ospf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 23:33:05 -0000

Hi Bruno,

From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Friday, November 18, 2016 at 11:30 AM
To: Xiaohu Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, "mpls@ietf.org<mailto:mpls@ietf.org>" <mpls@ietf.org<mailto:mpls@ietf.org>>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com<mailto:cpignata@cisco.com>>
Subject: Re: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"

Hi Xiaohu,

Please see inline [Bruno]

From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Monday, November 14, 2016 1:00 PM
To: DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Subject: ??: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"


Hi Bruno,



Could you please explain why the defination of the RLDC should be specific to the LB behavior of the transit LSR?

[Bruno] The whole purpose of EL and ELC is to improve load balancing of MPLS packets on transit LSR.

According to §6 of your draft, RLDC is also used to improve load-balancing : “The RLDC is used by ingress LSRs
   to determine whether it's necessary to insert an EL for a given LSP
   tunnel in the case where there has already been at least one EL in
   the label stack. »



What would be the point for the ingress to add an additional EL, within the RLDC of LSR A, if LSR A do not use this EL to improve the load balancing?

cf my example below where a LSR can read 5 labels, yet do not use those 5 labels for the load-balancing hence would not benefit from adding an EL within those 5 labels.

BTW, it would be useful for the discussion if you could reply to the content of my email sent: Monday, November 14, 2016 (also included below). As this was already the second time I send this example on the OSPF mailing list.






If I understand correctly, it seems that the text proposed by you conflict with Acee's take (see blow):


"   1. The standards track IGP drafts should have a precise definition of RLD and so not require a normative reference to the MPLS entropy draft (which is informational). The IGP drafts need not precisely specify how the information is used - this can be specified via a reference to the MPLS draft.
   2. The MPLS draft should precisely specify the initial use case of entropy label insertion at the ingress of the LSP. It should not limit the applicability of RLDC to this use case. "

[Bruno] I’m not seeing any conflict. I agree with both points. In this thread, I’m working on 1, i.e. having a clear definition of RLD.  But I would also like that this RLD advertisement be effective in improving the load-balancing of MPLS packets.

I think Readable Label Depth (RLD) should be independent of EL Capability (ELC). It allows advertisement of the the maximum number of labels an OSPF router will examine in a received MPLS encapsulated packet.

 If an OSPF Router supports ELC, it would imply that it support the EL Capability within RLD labels. think ELC should be defined in RFC 6790 and the SPRING Entropy label draft as opposed to the IGP advertisement drafts.

Thanks,
Acee





Best regards,
Xiaohu





________________________________
发件人:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>]
发送时间: 2016年11月14日 19:05
收件人: DECRAENE Bruno IMT/OLN; Xuxiaohu
抄送: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
主题: RE: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"
I meant:
My concern is that the current definition of the RLDC “the maximum label stack depth that the originating router can read” is not that specific to the load balancing behavior of the transit LSR.

Sorry for the spam

From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
Sent: Monday, November 14, 2016 11:51 AM
To: Xuxiaohu
Cc: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"

Hi Xiaohu,

Thanks for the proposed text.
My understanding is that the RLDC is intended to give information to the ingress node, to help him insert an ELI, EL pair at a given depth (or not)  in order to improve the load-balancing on a transit LSR.

My concern is that the current definition of the RLDC “the maximum label stack depth that the originating router can read” is not that specific to the load balancing capability of the transit LSR.
cf the below example of a load balancing algo on one real world plateform
Label <=3: 2-tuple <source IP(rightmost 30bit), destination IP (rightmost 30bit)>
Label = 4: bottom-of-stack label (rightmost 20bit)
Label>=5: Fifth(rightmost 20bit) label from the top


In this case, even if the LSR can read 5 labels, advertising a RDLC of 5 gives a wrong or incomplete information to the ingress as it could understand that
- it could insert the EL anywhere in the 5 first labels;  which is wrong as the EL would only provide a value if placed at the bottom of the stack
- inserting an EL in the first 5 labels would improve load-balancing; which, is wrong as inserting an (additional EL) could make the IP header not readable anymore hence even degrade the load balancing.

As already expressed, modeling the load-balancing behavior of a MPLS LSR would require more than the advertisement of a single value. However, to keep the change minimal, I would propose the following change
OLD: A new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined to advertise the capability of the router to read the maximum label stack depth....
NEW: This document defines a new TLV, called RLDC TLV, within the body of the OSPF RI LSA. RLDC value advertised is the label stack depth that the LSR will use to load-balance a MPLS packet. If an ELI, EL pair is within the RLDC, and the LSR is capable of recognizing the ELI, the LSR MUST use the entropy of the EL to load-balance the packet.  If an ELI, EL pair is within the RLDC, and the LSR is not capable of recognizing the ELI, the LSR MUST either use the entropy of the whole stack of RLDC labels (hence including the EL label) or load-balance based on the below non-MPLS header (e.g. the IP header).

I’m open to any different text or a different property, but the point is to advertise a _load_balancing_ property of the LSR.

In the above example, with this new definition, the plateform would advertise a RLDC of 0, even though it can read 5 labels.

Thanks
Bruno

From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Sunday, November 13, 2016 1:48 PM
To: Acee Lindem (acee); DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
Subject: ??: [OSPF] ??: WG Last Call for "Signalling ELC using OSPF"


Hi all,



How about making the following two changes:



OLD:



"A new TLV within the body of the OSPF RI LSA, called RLDC TLV is defined to advertise the capability of the router to read the maximum label stack depth....If a router has multiple linecards with different capabilities of reading the maximum label stack deepth, the router MUST advertise the smallest one in the RLDC TLV..."



NEW:



"A new TLV within the body of the OSPF RI LSA, called RLD TLV is defined to advertise the maximum label stack depth that the originating router can read (i.e., how many labels can the router read from the label stack of a given received MPLS packet to the maximum extent). How to use this RLD information is outside the scope of this draft... If a router has multiple line cards and the maximum label stack depths they can read are different, the originating router MUST advertise the smallest one in the RLD TLV..."



OLD:



"6<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6>.  Usage and Applicability

   The ELC is used by ingress LSRs to determine whether an EL could be
   inserted into a given LSP tunnel.  The RLDC is used by ingress LSRs
   to determine whether it's necessary to insert an EL for a given LSP
   tunnel in the case where there has already been at least one EL in
   the label stack.  This document only describes how to signal the ELC
   and RLDC using OSPF.  As for how to apply those capabilities when
   inserting EL(s) into LSP tunnel(s), it's outside the scope of this
  document and accordingly would be described in
   [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]."



NEW:



"6<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#section-6>.  Usage and Applicability

   The ELC is used by ingress LSRs to determine whether an EL could be
   inserted into a given LSP tunnel [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]

   The RLD could be used by ingress LSRs
   to determine whether it's necessary to insert an EL for a given LSP
   tunnel in the case where there has already been at least one EL in
   the label stack [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]."   This document

   only describes how to signal the ELC and RLD using OSPF.  How to apply

   them is outside the scope of this document."



Best regards,

Xiaohu



________________________________
发件人: Acee Lindem (acee) [acee@cisco.com<mailto:acee@cisco.com>]
发送时间: 2016年11月13日 6:08
收件人: Xuxiaohu; bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>
抄送: OSPF WG List; mpls@ietf.org<mailto:mpls@ietf.org>; Carlos Pignataro (cpignata)
主题: Re: [OSPF] 答复: WG Last Call for "Signalling ELC using OSPF"
Hi Tiger, other authors,
So, this is my take on the draft information content based on the comments from Carlos and Bruno.

   1. The standards track IGP drafts should have a precise definition of RLD and so not require a normative reference to the MPLS entropy draft (which is informational). The IGP drafts need not precisely specify how the information is used - this can be specified via a reference to the MPLS draft.
   2. The MPLS draft should precisely specify the initial use case of entropy label insertion at the ingress of the LSP. It should not limit the applicability of RLDC to this use case.

Thanks,
Acee

From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Xiaohu Xu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Date: Friday, November 11, 2016 at 5:10 AM
To: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>, "mpls@ietf.org<mailto:mpls@ietf.org>" <mpls@ietf.org<mailto:mpls@ietf.org>>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com<mailto:cpignata@cisco.com>>
Subject: [OSPF] 答复: WG Last Call for "Signalling ELC using OSPF"

Hi Bruno,

发件人:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:bruno.decraene@orange.com]
发送时间: 2016年11月10日 21:31
收件人: Xuxiaohu
抄送: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
主题: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi Xuxiaohu,

The RLDC specification(s) needs to be clear enough such that:
- transit LSR knows what to advertise

[Xiaohu] LSRs advertise how many labels they could read from the top of the label stack. LSRs can advertise this information no matter whether or not they support EL-based LB.

- ingress LSR knows how to use it in order to achieve/optimize load balancing across the MPLS network.

[Xiaohu] This draft only describes how to advertise the RLDC via IGP. As for how to use this information by ingress LSRs when inserting EL pairs, it’s discussed in Section 4 of draft-ietf-mpls-spring-entropy-label-04.

Best regards,
Xiaohu

So let’s start with the first question: which RLDC value should be advertised by such transit LSR? (cf below) And please quote the text from the RDLC spec which supports the answer.

> From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
> However, it seems that it has nothing to do with the EL-based MPLS load-balancing mechanism.

AFAIK, EL is defined in RFC6790, which defines a new behavior on the egress and ingress. It does not standardize the load-balancing behavior on transit nodes which are mostly free to do any load-balancing behavior. So it looks like hard to define an IGP TLV to advertise this non-standardized behavior, which is largely independent of the EL specification. IOW to re-use your terms, there is no such EL-based MPLS load-balancing specification for transit LSR.
https://tools.ietf.org/html/rfc6790#section-4.3
Now, we (MPLS WG) can try to model the load-balancing behavior of MPLS LSR, so that we (IGP WG) can latter advertise the parameters of this model in the IGP. But from what I can see in existing product, the current RLDC seems insufficient to model the behavior of existing MPLS LSR.
The current RLDC advertisement seems to be able to model a very small subset: a transit LSR which recognizes the ELI, and load balance solely on the following label (the EL).
If so,
- this need to be clear in the RLDC specification, because currently this is not.
- this may be seen as an incremental improvement but I don’t believe that it really solves the problem, nor significantly improve it given the behavior of existing plateform.

I’d rather have a solution which is more generally applicable and provide a significant improvement. i.e. model the load-balancing behavior of most current and future MPLS LSR, and then advertise the parameters in the IGP. (including a model ID such that this can be improved in the future). I agree that this is more complex job.

Thanks,
Best regards,
Bruno


From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Thursday, November 10, 2016 10:58 AM
To: DECRAENE Bruno IMT/OLN
Cc: OSPF WG List; Carlos Pignataro (cpignata); mpls@ietf.org<mailto:mpls@ietf.org>
Subject: ??: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi Bruno,

Thanks for sharing the following information. However, it seems that it has nothing to do with the EL-based MPLS load-balancing mechanism. The ELC and RLDC as described in draft-ietf-ospf-mpls-elc are applicable to the EL-based MPLS load-balancing mechanism.

Best regards,
Xiaohu

发件人:bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> [mailto:bruno.decraene@orange.com]
发送时间: 2016年11月10日 16:56
收件人: Xuxiaohu
抄送: OSPF WG List; Carlos Pignataro (cpignata)
主题: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi all,

(Hopefully) For the benefit of the discussion, I’m sharing a real world MPLS (transit LSR) load balancing algo on one plateform:

Label <=3: 2-tuple <source IP(rightmost 30bit), destination IP (rightmost 30bit)>
Label = 4: bottom-of-stack label (rightmost 20bit)
Label>=5: Fifth(rightmost 20bit) label from the top

This is a more or less random pick, and in general the behaviors are very diverse depending on the plateform (router, line card, os version, MPLS encapsulated traffic).

In general, it’s not clear to me how the RLDC advertisement really helps the ingress to make an informed decision and improve the load balancing of its flow across the MPLS network, as the current advertisement seems a bit simplistic to me.
More specifically, with the current definition of the RLDC, it’s hard for me to guess which RLDC value should be advertised. So I would really expect interop issues and endless discussion about who is right.

Thanks,
Regards,
-- Bruno

From: Xuxiaohu [mailto:xuxiaohu@huawei.com]
Sent: Thursday, November 10, 2016 5:29 AM
To: Carlos Pignataro (cpignata); DECRAENE Bruno IMT/OLN
Cc: OSPF WG List
Subject: ??: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi Carlos,

Thanks for your comments. Please see my response inline.

发件人: OSPF [mailto:ospf-bounces@ietf.org] 代表 Carlos Pignataro (cpignata)
发送时间: 2016年11月8日 23:20
收件人: Bruno Decraene
抄送: OSPF WG List
主题: Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Jumping a bit mid-thread, but with somewhat similar or related comments.

Summary: I am concerned with the lack of precision in the definitions and usage on these set of documents.

Acee, if this document needs to depend on Section 4 of draft-ietf-mpls-spring-entropy-label-04.txt, then the issue is compounded. I believe draft-ietf-mpls-spring-entropy-label-04has its own set of problems (for example, placing EL/ELI independent of whether the underlying Label is for a Node SID or a Segment SID is not optimum).

So the main question is: Is draft-ietf-ospf-mpls-elc-03 to be treated independently form draft-ietf-mpls-spring-entropy-label-04? That is a fundamental question for advancing and reviewing this/these doc(s). We have the advertisement of a capability — what is it used for? Is it the right variable to advertise (based on the application using it)?

[Xiaohu] draft-ietf-ospf-mpls-elc-03 defines an approach of advertising the RLDC of an LSR via OSPF. The definition of the RLDC is described in the following text (i.e., each LSR's capability of reading the maximum label stack depth). As for how to use this capability, it’s not limited by the draft although one use case (i.e., the application as described in Section 4 of draft-ietf-mpls-spring-entropy-label-04.txt) is mentioned in this draft.

Specifically, I think that RLDC is largely underspecified. The doc says:
"
   it would be useful for ingress LSRs to know each LSR's capability of
   reading the maximum label stack deepth.  This capability, referred to
   as Readable Label Deepth Capability (RLDC)
“

That definition simple does not make sense. And it does not explain the applicability (A, b, c, d).

[Xiaohu]Could you speak more specifically? Is the definition of the RLDC (i.e., what is the capability of reading the maximum label stack depth) itself not clear enough? If so, could you please suggestion any more specific text? Or the applicability of the RLDC not clear enough? If so, we co-authors currently only think about one use case of this RLDC that is described in Section 4 of draft-ietf-mpls-spring-entropy-label-04.txt) , please feel free to tell us if you find any other use cases of this RLDC.

Then the doc continues:
“
   Readable Label Deepth Capability (RLDC) can be used by ingress
   LSRs to determine whether it's necessary to insert an EL for a given
   LSP tunnel in the case where there has already been at least one EL
   in the label stack [I-D.ietf-mpls-spring-entropy-label] .
"

So this only is useful when there’s an EL (I assume ELI/EL pair) already?

[Xiaohu] In the EL insertion use case, yes, your understand is correct.

And is “[I-D.ietf-mpls-spring-entropy-label]” normative?

[Xiaohu] Currently yes, if it’s widely believed that this reference should be informational, it can be moved to the informational reference section.

Overall, I think a WGLC is premature, since some basics are not well covered. Is it RLD or RLDC? And what exactly is a “Readable Label Deepth Capability (RLDC)” The capability to do what? Is this a Capability or a scalar?

[Xiaohu] RLDC (Readable Label Deeth Capability) means a given LSR's capability of reading the maximum label stack depth. If it’s widely believed that “RLD” is more suitable than “RLDC” from the expression perspective, it’s fine to make a change.

Another point comment — although I think this needs a thorough review before WGLC.

The doc says:
   Of course,
   even it has been determined that it's neccessary to insert an EL for
   a given LSP tunnel, if the egress LSR of that LSP tunnel has not yet
   indicated that it can process ELs for that tunnel, the ingress LSR
   MUST NOT include an entropy label for that tunnel as well.

This is good and consistent with RFC 6790:
   c.  X MUST NOT include an entropy label for a given tunnel unless the
       egress LSR Y has indicated that it can process entropy labels for
       that tunnel.

So it’s better to point to it instead of re-MUST NOT independently.

[Xiaohu] Good suggestion. Will fix it.

But, what is the egress of a tunnel in this context? Not the final egress, but the SID egress. ?

[Xiaohu] IMHO, the egress of an LSP tunnel is clear enough and easy to understand. In contrast, what’s the mean of SID egress, could you please help point to a reference for this term defincation?

Best regards,
Xiaohu

Thanks,

—
Carlos Pignataro, carlos@cisco.com<mailto:carlos@cisco.com>

“Sometimes I use big words that I do not fully understand, to make myself sound more photosynthesis."

On Nov 8, 2016, at 6:15 AM, bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> wrote:

Hi Acee,

Thanks for your reply. Please see inline [Bruno]

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Tuesday, November 08, 2016 2:27 AM
To: DECRAENE Bruno IMT/OLN; OSPF WG List
Subject: Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi Bruno,

From: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>
Date: Monday, November 7, 2016 at 6:43 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF"

Hi authors, all,

Please find below some comments on the RLDC definition.

1) I’d like to see a more specific definition of RLDC.
e.g. load-balancing hashing could be done based on (hashing):
-a- a (stack of) N  “regular” MPLS labels (i.e. there is no ELI in this stack)
-b- the (IP) header below the stack of N  labels
-c- the EL label in the stack of N labels (i.e. there is one ELI in this stack)

I’d like the specification to be clear on the applicability of the RLDC. Does it apply on these 3 cases, on only a subset?
Personally, I’d like at least a and c be in scope of the RLDC definition, such that an ingress with limited push capability could have enough information to decide that it could avoid pushing an ELI,EL pair if the stack of MPLS labels that it pushes has enough entropy within the first RLDC labels.


I think that the signaling document should reference section 4 of https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt. However, I don’t think -b- is covered there.
[Bruno] The above section 4 has indeed more details, but I’m not certain that the definition is clear enough for everyone to agree on which “a”, “b”, “c” cases are covered by the RLDC advertisement. My reading would be that “a” and “c” are covered, not “b”. Reading your email, I’d say that you have the same understanding. But it bothers me that one of the authors has a different understanding.
Alsodraft-ietf-mpls-spring-entropy-label-04.txt is an informational document, so I’m not sure how much it would qualify to be a normative definition of what draft-ietf-ospf-mpls-elc advertise.

Thanks,
Regards,
-- Bruno


2) Current text seems to limit the use of the RLDC to the insertion of a _second_ EL. Why is the RLD not applicable to the first EL?


§1.  Introduction

“This capability, referred to

   as Readable Label Deepth Capability (RLDC) can be used by ingress

   LSRs to determine whether it's necessary to insert an EL for a given

   LSP tunnel in the case where there has already been at least one EL

   in the label stack [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]”



§6 Usage and Applicability

“The RLDC is used by ingress LSRs

   to determine whether it's necessary to insert an EL for a given LSP

   tunnel in the case where there has already been at least one EL in

   the label stack. »




I think that this is an unnecessary restriction of the RLDC usage. Indeed, an ingress with a limited capability in term of label push, could be forced to push a single EL label. It should be able to use the RLDC info in order to choose the best location for the EL, even if it pushes a single one.
But both sentences seems to restrict RLDC usage for the additional EL push, not the first one.

I would tend to agree.

Thanks,
Acee





Thanks,
Regards,
--Bruno

From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, November 05, 2016 5:46 PM
To: OSPF WG List
Subject: [OSPF] WG Last Call for "Signalling ELC using OSPF"

This begins the WG last call for  "Signalling ELC using OSPF”, https://www.ietf.org/id/draft-ietf-ospf-mpls-elc-03.txt. Please review the document and send comments to this list prior to Nov 27th, 2016. Due to the IETF week, the last call period is going to be 3 weeks rather than usual 2 weeks.

Thanks,
Acee

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
_______________________________________________
OSPF mailing list
OSPF@ietf.org<mailto:OSPF@ietf.org>
https://www.ietf.org/mailman/listinfo/ospf


_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.