Re: [mpls] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08

<bruno.decraene@orange.com> Mon, 02 September 2019 10:14 UTC

Return-Path: <bruno.decraene@orange.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 C7DF5120073; Mon, 2 Sep 2019 03:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 59m0Z1LTELGt; Mon, 2 Sep 2019 03:14:41 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1D7C120123; Mon, 2 Sep 2019 03:14:40 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 46MQtQ5fHLz8tfW; Mon, 2 Sep 2019 12:14:38 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.89]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 46MQtQ4GMszCqkS; Mon, 2 Sep 2019 12:14:38 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM44.corporate.adroot.infra.ftgroup ([fe80::e8a4:8bb:d7c2:f4e2%21]) with mapi id 14.03.0468.000; Mon, 2 Sep 2019 12:14:39 +0200
From: <bruno.decraene@orange.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-ietf-ospf-mpls-elc@ietf.org" <draft-ietf-ospf-mpls-elc@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
Thread-Index: AQHVX2sAQulbgKOGJkm1XSoIFYiCBKcYK6vw
Date: Mon, 2 Sep 2019 10:14:39 +0000
Message-ID: <18922_1567419278_5D6CEB8E_18922_350_1_53C29892C857584299CBF5D05346208A48BE4D9F@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <3378034A-5DF1-41BE-8BEF-A6B153B6B1DE@cisco.com>
In-Reply-To: <3378034A-5DF1-41BE-8BEF-A6B153B6B1DE@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A48BE4D9FOPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/XZ8cMudwp8BJvQbhDIZVw1RF4E8>
Subject: Re: [mpls] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 02 Sep 2019 10:14:43 -0000

Support.
This is needed for using MPLS Entropy Label in SR-MPLS.

Please find below some proposed comments. Please feel free to silently discard.

§1 Introduction
OLD:

“This capability, referred to as Entropy

   Readable Label Depth (ERLD) as defined in

   [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-07#ref-I-D.ietf-mpls-spring-entropy-label>;] may be used by ingress LSRs to

   determine whether it's necessary to insert an EL for a given LSP 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-isis-mpls-elc-07#ref-I-D.ietf-mpls-spring-entropy-label>].”

NEW:

This capability, referred to as Entropy

   Readable Label Depth (ERLD) as defined in

   [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-07#ref-I-D.ietf-mpls-spring-entropy-label>;] may be used by ingress LSRs to

   determine the position of the EL label in the stack, and whether it's necessary to insert multiple ELs at different depth.



§7 Security Considerations



“This document does not introduce any new security risks.”



Incorrectly setting the E flag (ELC capable) (during origination, propagation, redistribution) may lead to black-holing the traffic on the egress node. I believe this risk should be mentioned.



§3.x

“0x04 - E-Flag (ELC Flag): Set by the advertising router to indicate that the prefix originator is capable of processing ELs”



I’m not that familiar with OSPF so I may be wrong. But it seems like one could understand “prefix originator” as the router advertising the prefix in the OSPF message. In which case this would be wrong in the case of inter-AS (and possibly inter area) as this OSPF originator would not be the egress of the MPLS LSP. RFC 6790 refers to “Egress LSR” for such node.

I would propose :s/prefix originator/Egress of the MPLS LSP for this prefix


Thanks
Regards,
--Bruno


From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Friday, August 30, 2019 9:42 PM
To: lsr@ietf.org
Cc: mpls@ietf.org; lsr-ads@ietf.org; draft-ietf-ospf-mpls-elc@ietf.org
Subject: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08

We’ve gone through a number of iterations with these ELC drafts and I believe they are ready and meets all the use case requirements. Note that “Entropy Label for Spring tunnels” – draft-ietf-mpls-spring-entropy-label-12 is on the RFC editor’s queue.
This begins a two week last call for the subject draft. Please indicate your support or objection on this list prior to 12:00 AM UTC on Sept 14th, 2014.
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.