Re: [spring] Beyond SRv6.

Robert Raszuk <robert@raszuk.net> Mon, 02 September 2019 11:09 UTC

Return-Path: <robert@raszuk.net>
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 521F2120132 for <spring@ietfa.amsl.com>; Mon, 2 Sep 2019 04:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 gO24CEXmw9D9 for <spring@ietfa.amsl.com>; Mon, 2 Sep 2019 04:09:48 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E0F512006A for <spring@ietf.org>; Mon, 2 Sep 2019 04:09:48 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id q203so2934722qke.1 for <spring@ietf.org>; Mon, 02 Sep 2019 04:09:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+cAiQudtTUjN+mD7l7d6U34Q1jT1BccDwq/m5kfzlO8=; b=WYvgXh2IhnaxS/SPzJBmG9uxMXxB/1G/9WNSHRhTsrG+f9392b/kKs+I78Cym1cjQD wgyN3JnPnxbLKmVmstDe4TsKpiIfdLBEcELfFBjE9vqLG4neoeNn5IWS8A8dyF8pLlCX T/po3ndEXUijtHwJuDxUzBRkSlHakD4HEvqmmA1nVmI4kF7J5r9H8GusE+GHU8Y5SMAv wnnhoADHMHuJUBAXFGLhA3HA7eKAnlS6wU7See8/hOOrkJEz501rtJxePPxxXH9vItj8 /Bm6pjszIa1nB9j5jgaT9729NWP+NyXVes+LJjz1lG8s1ceTOFeE1EpHdCaUhFEJ2AdU 1EVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+cAiQudtTUjN+mD7l7d6U34Q1jT1BccDwq/m5kfzlO8=; b=U8ZNNP8LdRq3O2w/2sJHzQ8FfHcfkrRI9CI4GgHQjTg5Vir5TP2iy02LNS5D+HeLW2 mI8tePnTb2KeNKLKLoY53NsBfJPyNTOX5Yelj+MP7nyepMeph4Sog1Iu2izUxJVQKqGU r5s7fK3MYyELYS0GNvvlROKX/hd/dX6Ny1HjtLRhfYcpR2XL2BOs6A/1TZSNXLEuI8BO OtGo9erUIPWjb3IwfSE6mRp4fNXWCCW3XoXHQmb8hW5Mf1s8wbHdzPsUjbdwS3ugTsrT puI5+XbByLx7PveeDszQdfY4cYzB+KKFWBWawWq0EM2KFo6T2SdPU+afIgfqSL0TSUCj maMA==
X-Gm-Message-State: APjAAAXHO9uaC+XmwUBYPDY6lyK2M3VfBXKsE5M9FVG8uVaXLF2YTRAF E+tTDz64OWb4fmJkbbXrwZeaCWhymZ5u+YKV/pT8+w==
X-Google-Smtp-Source: APXvYqyYTE2iwbpcNVuSca4/dKQ9lJ2f/9ooKO3lFv8gtV7WF2qKiW6LVP9H57zhTiswVz7KkPJpDD2vohnlQqwNQqg=
X-Received: by 2002:a05:620a:1245:: with SMTP id a5mr220726qkl.134.1567422587498; Mon, 02 Sep 2019 04:09:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAHd-QWtA21+2Sm616Fnw0D-eB7SNb_BeG8-A-MCLLFgTwSpOsg@mail.gmail.com> <BYAPR05MB54630831722DE1D3E6C7F872AEBC0@BYAPR05MB5463.namprd05.prod.outlook.com> <abded144-7557-1093-874c-0f9ca708af6a@si6networks.com> <BL0PR05MB5458C00081B05584E77DB19DAEBF0@BL0PR05MB5458.namprd05.prod.outlook.com> <160e947d-790e-67fb-3366-fdc5f1d34f8c@foobar.org> <CAOj+MMGCfpUxu+Rfgpk4Nhbjp2_PeRb-JnHOi7Ru3Ov085WWRA@mail.gmail.com> <CAO42Z2w7yGUQUtE474h5pk0=iz+F5dwRHPHDbAscJqHQiP+WuA@mail.gmail.com> <CAOj+MMH-Vjpbz0=VSDHBMDnDBPDyOCLFzKYFJQO0_7YPPOZcJA@mail.gmail.com> <CAO42Z2zCKQdBydLdOFFAmkZJ3zvtN+mfT4UAtJyrncqCUqpDgg@mail.gmail.com>
In-Reply-To: <CAO42Z2zCKQdBydLdOFFAmkZJ3zvtN+mfT4UAtJyrncqCUqpDgg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 02 Sep 2019 13:09:36 +0200
Message-ID: <CAOj+MMHmLsTCaa_x+GVsLiH5Y+kBu3MBVOTYhE3WpGt8W90c_g@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: Nick Hilliard <nick@foobar.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Rob Shakir <robjs@google.com>, SPRING WG List <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary="0000000000008a86500591900225"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/k1XLhoF01nj5_gESOpSLTNvUwf8>
Subject: Re: [spring] Beyond SRv6.
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: Mon, 02 Sep 2019 11:09:50 -0000

> Are uSID values going to be entirely pseudo-random?

I see no reason why not ...

Networks are managed by some form of NMS. NMS can generate such values and
abstract it with a "node_name_usid" string for any additional processing
and human abstraction.

If that is the only concern I think we are done then. The only issue is
that if you happen to have hierarchical IGP you will not be able to
summarize them - but I don't think that this would be a showstopper to any
deployment.

Best,
R.





On Mon, Sep 2, 2019 at 12:24 PM Mark Smith <markzzzsmith@gmail.com> wrote:

>
>
> On Mon., 2 Sep. 2019, 17:58 Robert Raszuk, <robert@raszuk.net> wrote:
>
>> Hi Mark,
>>
>>
>>> The uSID proposal is taking the position that all the bits after the
>>> high order prefix are available for any purpose. This is not correct, and
>>> would violate a number of standards track RFCs, including the IPv6
>>> Addressing Architecture RFC (RFC 4291) and the ULA RFC (RFC 4193).
>>>
>>> In particular, 40 bits of a ULA prefix, between /8 and /48, the Gobal
>>> ID, must be pseudo random. This is the most critical property of ULA
>>> addresses and prefixes, as it is the solution to the problem ULAs are
>>> designed to solve.
>>>
>>
>> RFC 4193 says about Global_ID allocation:
>>
>>    The local assignments are self-generated and do not need any central
>>    coordination or assignment, but have an extremely high probability of
>>    being unique.
>>
>>
> Are uSID values going to be entirely pseudo-random?
>
> "
>
> 3.2.1 <https://tools.ietf.org/html/rfc4193#section-3.2.1>.  Locally Assigned Global IDs
>
>    Locally assigned Global IDs MUST be generated with a pseudo-random
>    algorithm consistent with [RANDOM <https://tools.ietf.org/html/rfc4193#ref-RANDOM>]."
>
>
>
>> So in some the case operator may choose to make such "local assignment"
>> of Global ID to be per router not per network. And that is all what is
>> needed for uSID. uSID address blocks does not need to be continues.
>>
>> It also does not contradict with any RFC does it ? What breaks if I use
>> more then one self generated Global ID in my network ?
>>
>> Note that the above question goes way beyond any SR related discussion so
>> perhaps deserves a separate 6man thread.
>>
>> Best,
>> R.
>>
>>