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

<bruno.decraene@orange.com> Mon, 02 September 2019 14:33 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 8160F120019; Mon, 2 Sep 2019 07:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 0wAA_r_0z9SB; Mon, 2 Sep 2019 07:33:26 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C7AF1200E7; Mon, 2 Sep 2019 07:33:26 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 46MXd06dfBz1ybW; Mon, 2 Sep 2019 16:33:24 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 46MXd03NVMz8sY1; Mon, 2 Sep 2019 16:33:24 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBMA4.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Mon, 2 Sep 2019 16:33:24 +0200
From: <bruno.decraene@orange.com>
To: Peter Psenak <ppsenak@cisco.com>, "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-isis-mpls-elc@ietf.org" <draft-ietf-isis-mpls-elc@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>
Thread-Topic: Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using ISIS" - draft-ietf-isis-mpls-elc-07
Thread-Index: AQHVYX4U8SWTPdo8V0iboVd1lmtSkKcYc7Lw
Date: Mon, 2 Sep 2019 14:33:25 +0000
Message-ID: <5410_1567434804_5D6D2834_5410_358_1_53C29892C857584299CBF5D05346208A48BE5894@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <B645A02C-1267-41C8-988F-A9FA4DE565B4@cisco.com> <MN2PR11MB36473898226B71BB5926E5E7C1BE0@MN2PR11MB3647.namprd11.prod.outlook.com> <21833_1567418380_5D6CE80C_21833_195_1_53C29892C857584299CBF5D05346208A48BE4C18@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <ed441ea1-bdab-c26a-747f-6f747bb8cdd1@cisco.com>
In-Reply-To: <ed441ea1-bdab-c26a-747f-6f747bb8cdd1@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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/jtt9FYpL2fDguv6_jNR5bz28cDs>
Subject: Re: [mpls] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using ISIS" - draft-ietf-isis-mpls-elc-07
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 14:33:29 -0000

Hi Peter,

Thanks, looks good.

--Bruno

-----Original Message-----
From: Peter Psenak [mailto:ppsenak@cisco.com] 
Sent: Monday, September 2, 2019 1:04 PM
To: DECRAENE Bruno TGI/OLN; Acee Lindem (acee); lsr@ietf.org; draft-ietf-isis-mpls-elc@ietf.org
Cc: mpls@ietf.org; lsr-ads@ietf.org
Subject: Re: Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using ISIS" - draft-ietf-isis-mpls-elc-07

Hi Bruno,

On 02/09/2019 11:59, bruno.decraene@orange.com wrote:
> 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 EL at different depth.

What about the slightly modified wording:

"This capability, referred to as Entropy Readable Label Depth (ERLD) as
defined in <xref target="I-D.ietf-mpls-spring-entropy-label"/> may be
used by ingress LSRs determine the position of the EL in the stack, and 
whether it's necessary to insert multiple ELs at different position in 
the label stack."

> 
> §7Security 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.

done.

thanks,
Peter
> 
> Regards,
> 
> --Bruno
> 
> *From**:*Lsr [mailto:lsr-bounces@ietf.org] *On Behalf Of * Les Ginsberg 
> (ginsberg)
> *Sent:* Monday, September 2, 2019 6:48 AM
> *To:* Acee Lindem (acee); lsr@ietf.org
> *Cc:* mpls@ietf.org; lsr-ads@ietf.org; draft-ietf-isis-mpls-elc@ietf.org
> *Subject:* Re: [Lsr] Working Group Last Call for "Signaling Entropy 
> Label Capability and Entropy Readable Label-stack Depth Using ISIS" - 
> draft-ietf-isis-mpls-elc-07
> 
> I support moving forward with these drafts.
> 
> There are clearly use cases for this functionality and the solution has 
> been vetted with providers who intend to deploy this.
> 
>     Les
> 
> *From:*Lsr <lsr-bounces@ietf.org>; *On Behalf Of *Acee Lindem (acee)
> *Sent:* Friday, August 30, 2019 12:44 PM
> *To:* lsr@ietf.org
> *Cc:* mpls@ietf.org; lsr-ads@ietf.org; draft-ietf-isis-mpls-elc@ietf.org
> *Subject:* [Lsr] Working Group Last Call for "Signaling Entropy Label 
> Capability and Entropy Readable Label-stack Depth Using ISIS" - 
> draft-ietf-isis-mpls-elc-07
> 
> 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 
> 14^th , 2014. Also, review comments are certainly welcome.
> 
> 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.