Re: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions
<bruno.decraene@orange.com> Fri, 28 February 2020 14:24 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 0CF863A18BD; Fri, 28 Feb 2020 06:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 ZzeJ-kdoxhiZ; Fri, 28 Feb 2020 06:23:59 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A080D3A18B3; Fri, 28 Feb 2020 06:23:58 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 48TWxT0NLtz5w7b; Fri, 28 Feb 2020 15:23:57 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1582899837; bh=CxczCk81n8MvmpsQlFL1gzoXb8xwU6OWBCi6/VukLDI=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=r49pk3cbF4Ahd37IjWz2cjwT8RTVYVdSLtwbRFUAGWb3lINst+MleJxiAirpNqrwf HzguHbvKpGO/3lLXdW+OH2iFlPmTXX2bBJFTjFahOVQJH93P+n17oFoxr/x1D1HzfM G9OGqQfrbs8n5R2HwfIUqEbPky1nO16hthJ/DcwzJk4Ba6kO0w4OS5AOTYwoyKWBhm 87d/2fUhiuzUu4n5QxKQhhRTjAl+MBvQPyEvHkPiX179I0Ocy41moL3pzR7e43vVpk P7Hyme7TLD9HR6pEYQHOEWHdA1nz6kJ3foQXGS4yfchpokP1iG5s+FH81FenzXoXeR b/YYaPIJBkVGQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 48TWxS6DdhzDq8D; Fri, 28 Feb 2020 15:23:56 +0100 (CET)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM5F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0487.000; Fri, 28 Feb 2020 15:23:56 +0100
From: bruno.decraene@orange.com
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, Chris Bowers <chrisbowers.ietf@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, SPRING WG List <spring@ietf.org>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>
Thread-Topic: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions
Thread-Index: AQHV7ZILnZjIpKq3N0WdLR4BCssnCqgwFDqggAA7KhCAABElwIAASL5A
Date: Fri, 28 Feb 2020 14:23:56 +0000
Message-ID: <7453_1582899837_5E59227C_7453_80_1_53C29892C857584299CBF5D05346208A48DD14BA@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <CAHzoHbtmJGB8QY==A5EMzzSwh+8bQjhbVgPBjA3kHJGxpCD_zA@mail.gmail.com> <c8828557-85a4-d002-cc8f-a8cd8da0aeaa@cisco.com> <CAHzoHbsU-+fUDdr5knmUE87DudCswwF2qGi11SVSSypT2UXKaQ@mail.gmail.com> <MW3PR11MB45703130D6A8527ED0C4C9CDC1E80@MW3PR11MB4570.namprd11.prod.outlook.com> <12659_1582880639_5E58D77F_12659_66_1_53C29892C857584299CBF5D05346208A48DCA80D@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <MW3PR11MB4570EDAE9E6AF17C9CCC9899C1E80@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570EDAE9E6AF17C9CCC9899C1E80@MW3PR11MB4570.namprd11.prod.outlook.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_53C29892C857584299CBF5D05346208A48DD14BAOPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/0wZ0ZjoyQutqaLXJDb84dESIMOQ>
Subject: Re: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions
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 Feb 2020 14:24:01 -0000
Hi Ketan, Thanks fort the follow up. Clarification inline [Bruno] From: Ketan Talaulikar (ketant) [mailto:ketant@cisco.com] Sent: Friday, February 28, 2020 11:11 AM To: DECRAENE Bruno TGI/OLN; Ketan Talaulikar (ketant); Chris Bowers Cc: lsr@ietf.org; SPRING WG List; draft-ietf-spring-srv6-network-programming; Peter Psenak (ppsenak) Subject: RE: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions Hi Bruno, I believe the description and usage of Locator is very well described and covered in the net-pgm draft as also the corresponding IGP extensions. Is the question is more about the “block” part of it (what is not in the block part is in the node part as per the text in the net-pgm draft)? The “block” is again not a new thing. Please check the following: Under https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-26#section-5 … look for “block” https://tools.ietf.org/html/rfc8402#section-2 … look under SRGB for SRv6 [Bruno] To clarify, my question was not specific to “block” but related to the usage, by the receiver, of the following piece of information: LB Length: SRv6 SID Locator Block length LN Length: SRv6 SID Locator Node length Fun. Length: SRv6 SID Function length Arg. Length: SRv6 SID Arguments length So perhaps I don’t get Chris’s point and would wait for him to clarify. [Bruno] I’ll leave this to Chris. Thanks, Ketan From: Lsr <lsr-bounces@ietf.org> On Behalf Of bruno.decraene@orange.com Sent: 28 February 2020 14:34 To: Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org>; Chris Bowers <chrisbowers.ietf@gmail.com> Cc: lsr@ietf.org; SPRING WG List <spring@ietf.org>; draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>; Peter Psenak (ppsenak) <ppsenak@cisco.com> Subject: Re: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions Hi Ketan, From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Ketan Talaulikar (ketant) Sent: Friday, February 28, 2020 6:30 AM Hi Chris, I agree with Peter and I would suggest to drop LSR since this is not a protocol specific thing. I believe the text in draft-ietf-spring-srv6-network-programming clears says what locator block and locator node are. What more details do you think are required? [Bruno] Speaking as an individual, the draft could possibly clarify the usage of these information/fields by the receiver. Possibly using the same name/term (e.g. SRv6 SID Locator Block length) to ease the references between both drafts. Thanks, --Bruno Thanks, Ketan From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of Chris Bowers Sent: 27 February 2020 22:46 To: lsr@ietf.org<mailto:lsr@ietf.org>; SPRING WG List <spring@ietf.org<mailto:spring@ietf.org>> Cc: Peter Psenak (ppsenak) <ppsenak@cisco.com<mailto:ppsenak@cisco.com>> Subject: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions SPRING and LSR WGs, I think that we need a much more detailed description of the locator block and locator node in either draft-ietf-spring-srv6-network-programming or draft-ietf-lsr-isis-srv6-extensions. See original email below. Thanks, Chris On Thu, Feb 27, 2020 at 11:08 AM Peter Psenak <ppsenak@cisco.com<mailto:ppsenak@cisco.com>> wrote: Hi Chris, On 27/02/2020 17:54, Chris Bowers wrote: > LSR WG, > > Section 9 of draft-ietf-lsr-isis-srv6-extensions-05 defines the SRv6 > SID Structure Sub-Sub-TLV. In particular, it defines encoding for the > locator block length and the locator node length. The text refers to > [I-D.ietf-spring-srv6-network-programming] for the definition of these > concepts. > > As far as I can tell, the only reference to locator block and locator > node in draft-ietf-spring-srv6-network-programming-10 is section 3.1 > which has the following text: > > A locator may be represented as B:N where B is the SRv6 SID block > (IPv6 subnet allocated for SRv6 SIDs by the operator) and N is the > identifier of the parent node instantiating the SID.. > > I think that we need a much more detailed description of the locator > block and locator node. sure, but that would be in the draft-ietf-spring-srv6-network-programming-10, not in draft-ietf-lsr-isis-srv6-extensions, as these are not a protocol specific constructs. thanks, Peter > > Thanks, > > Chris > _________________________________________________________________________________________________________________________ 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.
- [Lsr] clarification of locator block and locator … Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Peter Psenak
- [Lsr] clarification of locator block and locator … Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Ketan Talaulikar (ketant)
- Re: [Lsr] clarification of locator block and loca… bruno.decraene
- Re: [Lsr] clarification of locator block and loca… Ketan Talaulikar (ketant)
- Re: [Lsr] clarification of locator block and loca… bruno.decraene
- Re: [Lsr] clarification of locator block and loca… Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Ketan Talaulikar (ketant)
- Re: [Lsr] clarification of locator block and loca… Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Ketan Talaulikar (ketant)
- Re: [Lsr] [spring] clarification of locator block… Christian Hopps
- Re: [Lsr] [spring] clarification of locator block… Ketan Talaulikar (ketant)
- Re: [Lsr] clarification of locator block and loca… Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Ketan Talaulikar (ketant)
- Re: [Lsr] clarification of locator block and loca… Peter Psenak
- Re: [Lsr] [spring] clarification of locator block… Peter Psenak
- Re: [Lsr] clarification of locator block and loca… Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Peter Psenak
- Re: [Lsr] clarification of locator block and loca… Chris Bowers
- Re: [Lsr] clarification of locator block and loca… Peter Psenak
- Re: [Lsr] [spring] clarification of locator block… Gengxuesong (Geng Xuesong)
- Re: [Lsr] clarification of locator block and loca… Derek Yeung
- Re: [Lsr] [spring] clarification of locator block… Weiqiang Cheng
- Re: [Lsr] clarification of locator block and loca… Acee Lindem (acee)