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

<bruno.decraene@orange.com> Fri, 28 September 2018 08:02 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 30646130E04; Fri, 28 Sep 2018 01:02:16 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 tVf_woNpMVw4; Fri, 28 Sep 2018 01:02:12 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C0D130DC9; Fri, 28 Sep 2018 01:02:11 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 42M4013xNWz7tpX; Fri, 28 Sep 2018 10:02:09 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.34]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 42M4011xhwzBrLy; Fri, 28 Sep 2018 10:02:09 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM6F.corporate.adroot.infra.ftgroup ([fe80::bd00:88f8:8552:3349%17]) with mapi id 14.03.0415.000; Fri, 28 Sep 2018 10:02:05 +0200
From: <bruno.decraene@orange.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Alvaro Retana <aretana.ietf@gmail.com>, MEURIC Julien IMT/OLN <julien.meuric@orange.com>
CC: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-isis-segment-routing-msd@ietf.org" <draft-ietf-isis-segment-routing-msd@ietf.org>
Thread-Topic: [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15
Thread-Index: AQHUSRr9UBbi/4/S2U6JtWMOVnItk6T++7dQgAD3yQCAAyVlkIABQdiAgAB9BYD//7bIUIAA3KFw
Date: Fri, 28 Sep 2018 08:02:03 +0000
Message-ID: <4412_1538121729_5BADE001_4412_375_54_f1c05c2e-62d0-437b-af0b-a5a20073f31b@OPEXCLILM6F.corporate.adroot.infra.ftgroup>
References: <cb33dfed-f14a-e079-78a7-83659aac7ffb@orange.com> <da219cdbe1db4edab2afb4dc03aa8656@XCH-ALN-001.cisco.com> <2414700a-0cf2-f663-8ab8-c312c4845ebb@orange.com> <f74187a7c96b40ebae4dccdd26bc29f3@XCH-ALN-001.cisco.com> <af362362-3c0c-6e42-562e-c6f7f16d14ff@orange.com> <CAMMESsy1Wn+O6iuuy_PdFxo6s6nSF0ztc__wyxR3u_WJBXe2CQ@mail.gmail.com> <7a22ba26220d45c8881c5bbf95f4b7e0@XCH-ALN-001.cisco.com>
In-Reply-To: <7a22ba26220d45c8881c5bbf95f4b7e0@XCH-ALN-001.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.6]
Content-Type: multipart/alternative; boundary="_000_f1c05c2e62d0437baf0ba5a20073f31bOPEXCLILM6Fcorporateadr_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/A4Z4ryreWgdAYop8Lw1_KE7h_hE>
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: Fri, 28 Sep 2018 08:02:17 -0000

Les, Alvaro,

Jumping in the conversation, please see comments inlined [Bruno]

From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Les Ginsberg (ginsberg)
Sent: Thursday, September 27, 2018 8:45 PM
To: Alvaro Retana; MEURIC Julien IMT/OLN
Cc: rtg-ads@ietf.org; lsr@ietf.org; rtg-dir@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org
Subject: Re: [Lsr] [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15

Alvaro –

Thanx for helping drive this to closure.
Please see inline.

From: Alvaro Retana <aretana.ietf@gmail.com>
Sent: Thursday, September 27, 2018 10:54 AM
To: Julien Meuric <julien.meuric@orange.com>om>; Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Cc: lsr@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org; rtg-dir@ietf.org; rtg-ads@ietf.org
Subject: Re: [RTG-DIR] RtgDir Review: draft-ietf-isis-segment-routing-msd-15

On September 27, 2018 at 6:26:57 AM, Julien Meuric (julien.meuric@orange.com<mailto:julien.meuric@orange.com>) wrote:

Hi!

It looks like the outstanding item is this one about the terminology used in §5.

tl;dr: I think that the terminology can be slightly improved to be in line with other documents.  See suggestion at the bottom.

>>>> - In section 5, BMI-MSD is defined as "the total number of MPLS
>>>> labels which can be imposed" (which is OK when the incoming packet
>>>> is unlabled). When the incoming packet is labeled (e.g. use of
>>>> segment routing binding SID), if the incoming label is to be
>>>> "replaced" by N outgoing labels, what processing model is assumed
>>>> when advertising the
>> MSD:
>>>> * one swap and one imposition of N-1 labels?
>>>> * one pop and one imposition of N labels?
>>>>
>>> [Les:] What is being defined is the maximum number of SIDs/labels
>>> which
>> can be "imposed". If popping or swapping affects the MSD which can be
>> supported this needs to be accounted for in the advertisement. BMI-MSD
>> is not being used to advertise a value specific to labeled or
>> unlabeled packets nor a value which is "swap specific" or "pop specific".
>>>
>> [JM] We seem to agree on an architecture-agnostic use of BMI-MSD. "If
>> popping or swapping affects the MSD [...] this needs to be accounted
>> for" is a great introduction to the issue and deserves to be included
>> in the I-D. My comment now binds to: in order to have interoperable
>> implementations, I believe the document should be more prescriptive on
>> how we account that for.
>>
> [Les2:] Added text
>
[JM2] Thanks, this is a significant improvement. After talking to Bruno,
we however feel that the proposed wording remains ambiguous, and
especially the phrases "imposed under all conditions" and "be accounted
for". Indeed, section 3.10 of RFC 3031 defines "the operation to perform
on the packet's label stack" and doesn't mention "impose". The closest
concept may be found in:
" replace the label at the top of the label stack with a
specified new label, and then push one or more specified new
labels onto the label stack."
Combining this split to your current text may lead to different
interpretations. Could you clarify the paragraph to be more specific on
the corresponding definitions and fully clear the fuzzy zone?

The document currently (-17) reads:

   Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS

   labels which can be imposed, including all service/transport/special

   labels.  The value advertised MUST indicate what can be imposed under

   all conditions e.g., if label popping/swapping affects the number of

   labels which can be imposed this MUST be accounted for in the value

   which is advertised.

   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.

I think that the term “label imposition” is relatively well understood, as the act of putting labels on the packet (labeling a packet).  However, rfc3031 doesn’t talk about imposition; instead it says that a ""labeled packet" is a packet into which a label has been encoded”, and it talks about pushing labels on the stack.  The SR documents (rfc8402 and draft-ietf-spring-segment-routing-mpls) also don’t talk about imposition, nor do they offer a better alternative.

The text may be interpreted from the point of view of what the LSR can impose, vs what can be imposed on the packet…which can result in confusion.  Note that §7 clarifies which node is expected to do the imposition: "the head-end (the node performing the imposition)”.

rfc4221 does provide a clear precedent of the use of imposition, and a related definition (referring to the LSR MIB / rfc3813): "mplsMaxLabelStackDepth defines the maximum size of a imposed label stack supported at this LSR”.  This definition is akin to what this document already says: “MSD...the number of SIDs supported” (§1.1).  The definition in rfc4221 also presents a subtle difference (from the text in this document): it talks about the “imposed label stack supported” (not “labels which can be imposed”).  I interpret the “imposed label stack” as already taking into consideration any operations that can be performed (rfc3031).

My suggestion is to borrow from rfc4221 and simplify the definition:

NEW>

   Base MPLS Imposition MSD (BMI-MSD) indicates the maximum size of an

   imposed label stack supported by the node.

   If it is not possible to meaningfully advertise

   per link values, then only the Node MSD SHOULD be

   advertised.

[Les:] There are some key elements missing here.

1)Specifying that the value advertised includes “all service/transport/special  labels” is vital. This eliminates ambiguity which might occur if someone is trying to use this value to (for example) determine how many labels can be used for a repair path. It is possible that in the future we might specify other MSD-types advertising what can be imposed for a specific purpose (e.g., for repair only). Such a number would have factored out labels used for other purposes.

2)From the comments Julien has previously provided, clarification as to how popping/swapping “might” impact what a given LSR can do has been requested – and your proposal does not address that.

[Bruno] I agree with Les here.
Trying to rephrase the comment:
- I don’t think the term “imposed” is well defined for the case where the received packet is already labeled. If I’m missing a definition, please point to it.
- To give an example, suppose that I receive a packet with the label stack “12” and forward it with the label stack “14, 15”. Am I doing an imposition of 2 labels (1 POP, 2 PUSH) or an imposition of 1 label (1 SWAP, 1 PUSH)? Any option works for me, but I’d like the definition to be crystal clear in order to avoid interop issues.

IN a recent email I proposed:

“Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS
   labels which can be imposed, including all service/transport/special
   labels.  The value advertised MUST indicate the lowest maximum number of labels which  can be imposed under
   all conditions e.g., if label popping/swapping reduces the maximum number of
   labels which can be imposed this lower number MUST be what is advertised.

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.”

Given you have provided a justification for retaining “imposition”, does the above work??

[Bruno] I think the new proposed text is better (thanks Les), yet, could may be made more obvious by either replacing “labeled imposed” by “labelled added” or “label pushed” or “additional label added”.
May be even better by referring to the size of the label stack, something like “BMI-MSD advertises the ability to increase the depth of the label stack by BMI-MSD labels”. Alternatively, explain the behavior in case of a swap. (e.g. “performing a label swap corresponds to an imposition of zero label”.)

Thanks,
--Bruno

 In line with that suggestion, we could clean up some of the related text:

§1 s/the controller learns the Maximum SID Depth (MSD) that can be imposed at each node/link/the controller learns the Maximum SID Depth (MSD) supported at each node/link
[Les:] “supported” does not cover the same ground as “imposed”. For example, “supported” could be “supported for reading” – which is not what we are specifying in BMI.

   Les


§1 s/not exceed the number of SIDs the node is capable of imposing/not exceed the number of SIDs the node is capable of supporting

§1.1: s/BMI: Base MPLS Imposition…/BMI: Base MPLS Imposition is the size of the imposed label stack supported

Does this work?

Thanks!

Alvaro.

_________________________________________________________________________________________________________________________

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.