Re: [spring] 64-bit locators

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 20 December 2019 15:18 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E87CF120098 for <spring@ietfa.amsl.com>; Fri, 20 Dec 2019 07:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 6kaRiduP-KxH for <spring@ietfa.amsl.com>; Fri, 20 Dec 2019 07:18:57 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E22EB12009E for <spring@ietf.org>; Fri, 20 Dec 2019 07:18:56 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBKFIqYI023504; Fri, 20 Dec 2019 16:18:52 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5A725206EAE; Fri, 20 Dec 2019 16:18:52 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 44C36206DCC; Fri, 20 Dec 2019 16:18:52 +0100 (CET)
Received: from [10.11.240.44] ([10.11.240.44]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xBKFIpfW011281; Fri, 20 Dec 2019 16:18:51 +0100
To: Robert Raszuk <robert@raszuk.net>, Gyan Mishra <hayabusagsm@gmail.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, SPRING WG <spring@ietf.org>, "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
References: <BN7PR05MB5699D85CC99CB23B1B573901AE530@BN7PR05MB5699.namprd05.prod.outlook.com> <CAO42Z2yAH4ECeB+PGRS98HgZHXtTq3iX1x6aMSPjKgS6O1GDAQ@mail.gmail.com> <8f5607c9-645a-ea88-e2a7-a4bed8206fc8@gmail.com> <63F5AA66-AEF8-4278-B98C-D3C53AC5A60A@cisco.com> <CAO42Z2x-5NUYHAzjBAR3je7EoPde=-autOXyta5EvqDydbVMWA@mail.gmail.com> <CABNhwV1xZEx6_eZpdgvWAmiopXT-SACR1DM_KSeF_JSDvgSSOQ@mail.gmail.com> <CAOj+MMGSbdL2ZP-_uX_464Tov7MV0vu=cmoKpw71-vL8R4HpRw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <069e6021-537c-422a-37da-f090a6ac334b@gmail.com>
Date: Fri, 20 Dec 2019 16:18:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
MIME-Version: 1.0
In-Reply-To: <CAOj+MMGSbdL2ZP-_uX_464Tov7MV0vu=cmoKpw71-vL8R4HpRw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/mFb86QX3R24nl_NnHhcfURcWEig>
Subject: Re: [spring] 64-bit locators
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2019 15:18:59 -0000


Le 20/12/2019 à 00:07, Robert Raszuk a écrit :
> 
> Fixed length of any field LOC:FUNC:ARGs makes no sense to me. What is 
> optimal for Ron or Mark may not be optimal for me.

I think I can legitimately wonder whether the 'SID' Segment Identfier 
should not be something else than an IP address.

Making a SID an IP address might lead to other well-known confusions 
like in OSPF: there is a Router ID which is an IP address in some 
manufacturer's speak, it works fine, but it does not reply to ping under 
any configuration whatsoever.

That is not a good thing.  The router id looks like an IP address but it 
is not one.  When migrating OSPF to IPv6 all was changed but the Router 
ID stayed like an IPv4 address.  So it is an IPv6 OSPF but has some IPv4 
in it.

The column-hextet notation, or more precisely something like 
"2001:db8::", denotes an IP address.  Not only is it a Documentaiton 
Prefix, but it is an IP address.  There is an RFC for it.  It is somehow 
reserved and it shouldnt be used for something else, otherwise it 
creates confusion.

It could be easy to create a new space for SID, with its distinct 
notation, like 64bit identifiers "ab_cd_ef_gh_01_02__".  Nobody would 
try to ping these because they dont look like IP addresses.

Then, we might wonder whether these SIDs should be fixed or variable length.

Alex

> 
> While we are at that fixed size of 128 bits of IPv6 also makes no sense 
> - but that vessel left the harbour a while ago.
> 
> Cheers,
> R.
> 
> 
> 
> 
> On Thu, Dec 19, 2019 at 10:57 PM Gyan Mishra <hayabusagsm@gmail.com 
> <mailto:hayabusagsm@gmail.com>> wrote:
> 
> 
> 
>     On Thu, Dec 19, 2019 at 4:17 PM Mark Smith <markzzzsmith@gmail.com
>     <mailto:markzzzsmith@gmail.com>> wrote:
> 
> 
> 
>         On Thu, 19 Dec 2019, 22:48 Pablo Camarillo (pcamaril),
>         <pcamaril@cisco.com <mailto:pcamaril@cisco.com>> wrote:
> 
>             Hi,
> 
>             As mentioned in the draft, the choice of the locator length
>             is deployment specific.
>             LINE has deployed SRv6 using a locator different than a /64.
> 
> 
>         This is effectively an appeal to authority.
> 
>         What makes what LINE has done the best and right thing to do?
> 
>         I can already see they're using the IPv4 link-local 169.254/16
>         prefix in a manner that wildly violates how it is specified to
>         be used in RFC3927. See Slides 9, 12, 24.
> 
>         Tying your IPv6 addressing plan to IPv4 addressing could end up
>         imposing IPv4's addressing limitations on IPv6 - defeating the
>         primary purpose of IPv6 - providing many more addresses than IPv4.
> 
>         Slide 32 shows they're violating RFC 4193 (IPv6 ULAs), because
>         they're using ULA-Cs ('fc') rather than ULA-Ls ('fd'), despite
>         there being no central registry.  Their 40 bit Global ID of "17"
>         could be random, although I'm guessing not, as random numbers
>         would usually have far less zeros in them. These sorts of ULA
>         errors are why I presented "Getting IPv6 Addressing Right" at
>         AusNOG this year -
>         https://www.slideshare.net/markzzzsmith/ausnog-2019-getting-ipv6-private-addressing-right .
> 
> 
>         This is an Internet Draft, so this is the best time to make
>         these sorts of changes, as it is much easier now. When things
>         become RFCs it becomes much harder (and much, much harder when
>         they become Internet Standards).
> 
>         If somebody has deployed Internet Draft level technology, they
>         have to accept the risk that what they've deployed might not
>         comply with the eventual RFC.
> 
>         Regards,
>         Mark.
> 
>       [Gyan] For IPv6 addressing you can have any length prefix up to
>     /128.  i am all for flexibility with vlsm even though may not be
>     widely used.
> 
>     SRv6 SID encoding differs in that we had 3 fields
>     {locator;function;arguments} that I think it makes sense to be fixed
>     in the specification as Ron has brought up.
> 
>      From an operator perspective for programmability as SRv6
>     deployments with or without centralized controller, fixed length of
>     the 3 fields makes sense so operators can easily craft ACLs for
>     deployments.
> 
>     I think we could go crazy with the sizing but I think since 64 bit
>     boundary exists today for slaac we could make the locator /64 as
>     well is fine.  We could split the other 2 fields evenly 32 bits each
>     or make the function longer.  I think we’ll defined sizing is
>     important so SID addressing plan is not chaotic.
> 
> 
> 
> 
>             Cheers,
>             Pablo.
> 
>             [1]
>             https://speakerdeck.com/line_developers/line-data-center-networking-with-srv6
> 
>             -----Original Message-----
>             From: spring <spring-bounces@ietf.org
>             <mailto:spring-bounces@ietf.org>> on behalf of Alexandre
>             Petrescu <alexandre.petrescu@gmail.com
>             <mailto:alexandre.petrescu@gmail.com>>
>             Date: Thursday, 19 December 2019 at 09:44
>             To: "spring@ietf.org <mailto:spring@ietf.org>"
>             <spring@ietf.org <mailto:spring@ietf.org>>
>             Subject: Re: [spring] 64-bit locators
> 
> 
> 
>                  Le 19/12/2019 à 00:13, Mark Smith a écrit :
>                  [...]
> 
>                  > VLSM [variable length subnet mask] is fundamentally hard,
> 
>                  We need VLSM in other places too, such as in ULA
>             prefixes fd and fc.
> 
>                  I think it is indeed a difficult to grasp concept, but
>             it is there for
>                  growth.
> 
>                  Alex
> 
>                  >
>                  > Regards,
>                  > Mark.
>                  >
>                  >     __
>                  >
>                  >     In this case, we should probably change the
>             document to reflect
>                  >     implemented behavior.____
>                  >
>                  >     __ __
>                  >
>                  >
>                  >                                                     
>                                  Ron____
>                  >
>                  >     __ __
>                  >
>                  >
>                  >     Juniper Business Use Only
>                  >
>                  >     _______________________________________________
>                  >     spring mailing list
>                  > spring@ietf.org <mailto:spring@ietf.org>
>             <mailto:spring@ietf.org <mailto:spring@ietf.org>>
>                  > https://www.ietf.org/mailman/listinfo/spring
>                  >
>                  >
>                  > _______________________________________________
>                  > spring mailing list
>                  > spring@ietf.org <mailto:spring@ietf.org>
>                  > https://www.ietf.org/mailman/listinfo/spring
>                  >
> 
>                  _______________________________________________
>                  spring mailing list
>             spring@ietf.org <mailto:spring@ietf.org>
>             https://www.ietf.org/mailman/listinfo/spring
> 
> 
>             _______________________________________________
>             spring mailing list
>             spring@ietf.org <mailto:spring@ietf.org>
>             https://www.ietf.org/mailman/listinfo/spring
> 
>         _______________________________________________
>         spring mailing list
>         spring@ietf.org <mailto:spring@ietf.org>
>         https://www.ietf.org/mailman/listinfo/spring
> 
>     -- 
> 
>     Gyan S. Mishra
> 
>     IT Network Engineering & Technology
> 
>     Verizon Communications Inc. (VZ)
> 
>     13101 Columbia Pike FDC1 3rd Floor
> 
>     Silver Spring, MD 20904
> 
>     United States
> 
>     Phone: 301 502-1347
> 
>     Email: gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
> 
>     www.linkedin.com/in/networking-technologies-consultant
>     <http://www.linkedin.com/in/networking-technologies-consultant>
> 
> 
>     _______________________________________________
>     spring mailing list
>     spring@ietf.org <mailto:spring@ietf.org>
>     https://www.ietf.org/mailman/listinfo/spring
>