Re: [spring] FW: New Version Notification for draft-bonica-spring-srv6-plus-05.txt

Mark, I had missed the earlier email suggesting that the SIDs could be 
address specific rather than just node specific.  That is an interesting 
idea.  At first glance, it appears to work, and warrants further thought.

As far as I know, routers tend not to use SLAAC for interface address 
generation, and tend not to be worried about the privacy properties of 
their interface addresses, so at least for most use cases I am having 
trouble following your last paragraph.

Thank you,
Joel

On 8/28/2019 7:39 PM, Mark Smith wrote:
> Hi Ron,
> 
> In an email a while back I think you mentioned that the SID space is
> unique in the context of an address, where as this draft is saying
> that SIDs have node-local significance, which I think means the same
> single SID space across all the addresses of the node.
> 
> The reason I'm wondering is that if the SID space is per-address, then
> I'd think it could be possible to have a single 16 bit SID space,
> rather than two sizes and needing an operator to make a choice (with
> the risk of making an incorrect choice, and the consequences of having
> to migrate a network from one size to another).
> 
> If 16 bits is enough for TCP/UDP etc. ports in most cases then I'd
> guess it would probably be enough for SIDs. Of course, as with running
> out of TCP/UDP port numbers, an operator could give a node or
> interface another IPv6 address to create another 16 bit SID space if
> necessary.
> 
> 
> I also remember from that email you mentioning the idea of unique
> link-local addresses. If IPv6 implementations follow RFC 8064,
> "Recommendation on Stable IPv6 Interface Identifiers", which
> recommends RFC 7217, "A Method for Generating Semantically Opaque
> Interface Identifiers with IPv6 Stateless Address Autoconfiguration
> (SLAAC)", then nodes' link-local addresses (specifically the IID part)
> should not only be network wide unique, but also globally unique.
> 
> Regards,
> Mark.
> 
> On Thu, 29 Aug 2019 at 01:38, Ron Bonica
> <rbonica=40juniper.net@dmarc.ietf.org> wrote:
>>
>> FYI
>>
>>
>> Juniper Public
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
>> Sent: Wednesday, August 28, 2019 11:31 AM
>> To: Ron Bonica <rbonica@juniper.net>; Shraddha Hegde <shraddha@juniper.net>; Andrew Alston <Andrew.Alston@liquidtelecom.com>; Gang Chen <phdgang@gmail.com>; Joel Halpern <joel.halpern@ericsson.com>; Andrew Alston <andrew.alston@liquidtelecom.com>; Daniam Henriques <daniam.henriques@liquidtelecom.com>; Jen Linkova <furry@google.com>; Yuji Kamite <y.kamite@ntt.com>
>> Subject: New Version Notification for draft-bonica-spring-srv6-plus-05.txt
>>
>>
>> A new version of I-D, draft-bonica-spring-srv6-plus-05.txt
>> has been successfully submitted by Ron Bonica and posted to the IETF repository.
>>
>> Name:           draft-bonica-spring-srv6-plus
>> Revision:       05
>> Title:          IPv6 Support for Segment Routing: SRv6+
>> Document date:  2019-08-28
>> Group:          Individual Submission
>> Pages:          23
>>
>>
>> Abstract:
>>     This document describes SRv6+. SRv6+ is a Segment Routing (SR)
>>     solution that leverages IPv6.  It supports a wide variety of use-
>>     cases while remaining in strict compliance with IPv6 specifications.
>>     SRv6+ is optimized for ASIC-based forwarding devices that operate at
>>     high data rates.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 