Re: [Lsr] [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15

<bruno.decraene@orange.com> Wed, 03 October 2018 14:07 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 856031312AC; Wed, 3 Oct 2018 07:07:20 -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_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 cF9nYCW_ABMR; Wed, 3 Oct 2018 07:07:18 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76D613129A; Wed, 3 Oct 2018 07:07:17 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 42QHs011V0z8tbT; Wed, 3 Oct 2018 16:07:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.69]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 42QHrz5zl7z5vNC; Wed, 3 Oct 2018 16:07:15 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0415.000; Wed, 3 Oct 2018 16:07:13 +0200
From: <bruno.decraene@orange.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-isis-segment-routing-msd@ietf.org" <draft-ietf-isis-segment-routing-msd@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>, Alvaro Retana <aretana.ietf@gmail.com>, "lsr@ietf.org" <lsr@ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, MEURIC Julien IMT/OLN <julien.meuric@orange.com>
Thread-Topic: [Lsr] [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15
Thread-Index: AQHUWw46HJBMIr9LnUmVD4nnvDM3nKUNjWFg
Date: Wed, 3 Oct 2018 14:07:13 +0000
Message-ID: <20010_1538575635_5BB4CD13_20010_244_10_71d2bce7-864e-4292-a6fa-94313fb56b0e@OPEXCLILMA2.corporate.adroot.infra.ftgroup>
References: <F4955ED6-1FC9-4BD9-A3AE-CEAE3C474586@cisco.com>
In-Reply-To: <F4955ED6-1FC9-4BD9-A3AE-CEAE3C474586@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_71d2bce7864e4292a6fa94313fb56b0eOPEXCLILMA2corporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/1UfLL17KncUghrt-Tp6-1TquNIk>
Subject: Re: [Lsr] [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 14:07:21 -0000

Hi Acee,


From: Acee Lindem (acee) [mailto:acee@cisco.com]


Hey Bruno, Jeff, Les,

Have we agreed on the precise definition of “label imposition”?
Thanks for asking.
Not so far.
We don’t necessarily need to agree on a precision definition of “label imposition”. In my latest email (a few hours ago), I proposed to reuse the phrasing from RFC 3031, which does not use that term. If we are fine with using RFC 3031 terms, that would be fine for me.

Thanks,
--Bruno


Thanks,
Acee

From: Lsr <lsr-bounces@ietf.org>; on behalf of Bruno Decraene <bruno.decraene@orange.com>;
Date: Wednesday, October 3, 2018 at 4:37 AM
To: Jeff Tantsura <jefftant.ietf@gmail.com>;
Cc: Routing Directorate <rtg-dir@ietf.org>;, "draft-ietf-isis-segment-routing-msd@ietf.org"; <draft-ietf-isis-segment-routing-msd@ietf.org>;, "rtg-ads@ietf.org"; <rtg-ads@ietf.org>;, Alvaro Retana <aretana.ietf@gmail.com>;, "lsr@ietf.org"; <lsr@ietf.org>;, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>;, MEURIC Julien IMT/OLN <julien.meuric@orange.com>;
Subject: Re: [Lsr] [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15

Jeff,

From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Tuesday, October 02, 2018 8:28 PM
To: DECRAENE Bruno IMT/OLN; Alvaro Retana; MEURIC Julien IMT/OLN; Les Ginsberg (ginsberg)
Cc: rtg-ads@ietf.org; lsr@ietf.org; rtg-dir@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org
Subject: RE: [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15

Gents,

I’m 100% with Les here, going into platform/asic specifics within this document would inevitably create ambiguity.
Absolutely.
And nobody is asking for this.

Cheers
--Bruno



Cheers,
Jeff
On Oct 2, 2018, 11:20 AM -0700, Les Ginsberg (ginsberg) <ginsberg@cisco.com>;, wrote:

Bruno –

Trimming the thread…

[Les2:] Label imposition is meant to cover both the SWAP operation and the PUSH operation. In the example you provided above where a label stack of “12” is replaced by a label stack of “14,15” the number of labels “imposed” is 2.
[Bruno2] In that case, I definitely think that the discussion was useful and that this point needs to be clarified in the document.
Whether you choose to call that (1 POP, 2 PUSH) or (1 SWAP, 1 PUSH)  or simply a SWAP isn’t relevant here (though it might matter to folks like the RFC 3031 authors).

With that ibn mind, here is proposed text:

“Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS
   labels which can be imposed, including all service/transport/special
   labels.  Imposition includes swap and/or push operations.

If the advertising router performs label imposition in the context of
   the ingress interface, it is not possible to meaningfully advertise
   per link values.  In such a case only the Node MSD SHOULD be
   advertised.”

[Bruno2] Given that the term “imposition” does not seem to be defined within the IETF, I would still favor a formal definition not using it. e.g. “BMI-MSD advertises the ability to increase the depth of the label stack by BMI-MSD labels”.
Alternatively, I’d propose the following rewording which seems clearer to me:
OLD: Imposition includes swap and/or push operations.
NEW: A swap operation counts as an imposition of one label; just like one push operation.

[Les3:] This gets into implementation specific issues that I would really like to avoid.
For example, some implementations perform one and only one  “operation”. Conceptually that may involve a swap and a push – but from the internal implementation POV it is simply one operation. And this may be true regardless of how many labels are involved. Other implementations might perform this in several discrete steps. The language we use here should not imply anything about how many labels are associated with a specific operation.

The term “increase” isn’t accurate because in the case of a swap there is no increase, yet the label which is replaced is counted.

https://tools.ietf.org/html/rfc3031#section-3.10 is relevant here.

The term “imposition” is generic – and as Alvaro has pointed out is used in RFC 4221. And the language proposed above does define the relationship between “swap and push” and “imposition”.

I appreciate your desire for clarity – and I am still open to new language – but at this point I still think what I proposed is  the most accurate.

   Les



Thanks,
--Bruno


_________________________________________________________________________________________________________________________



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.