Re: New Version Notification for draft-dykim-6man-sid6-00.txt

> I’ve reposted a draft, this time to 6man, which was posted to 6ops about a year ago but fell out of scope there since it involves some changes to NDv6/DAD with added texts.
> 
> I’d like to see whether there should be any interest in this draft within the 6man group, possibly enough to justify the modification of NDv6/DAD as suggested in this draft.
> 
> Your comments are solicited.

From a quick glance it looks like you have re-invented multilink subnet routing.
Which of one flavous is described in https://tools.ietf.org/html/draft-ietf-ipv6-multilink-subnets-00
That particular proposal didn’t go anywhere, for the reasons described in RFC4903.

The basic idea was to share a /64 across multiple IPv6 links.
Steve never wrote down the details, but today, we’d probably do a combination of ND with ARO and an IGP.
Possibly with some modifications. Detecting movement and whenever someone leaves the link is the tricky part.

I would certainly be interested in work in this area.

Cheers,
Ole

>> Begin forwarded message:
>> 
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for draft-dykim-6man-sid6-00.txt
>> Date: 3 September 2018 at 16:46:04 GMT+9
>> To: "DY Kim" <dykim6@gmail.com>
>> 
>> 
>> A new version of I-D, draft-dykim-6man-sid6-00.txt
>> has been successfully submitted by DY Kim and posted to the
>> IETF repository.
>> 
>> Name:		draft-dykim-6man-sid6
>> Revision:	00
>> Title:		Subnet ID Deprecation for IPv6
>> Document date:	2018-09-03
>> Group:		Individual Submission
>> Pages:		17
>> URL:            https://www.ietf.org/internet-drafts/draft-dykim-6man-sid6-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-dykim-6man-sid6/
>> Htmlized:       https://tools.ietf.org/html/draft-dykim-6man-sid6-00
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dykim-6man-sid6
>> 
>> 
>> Abstract:
>>   Deprecation of the subnet ID in IPv6 networking is proposed; the
>>   subnet ID is set to zero so that all nodes in a site carry the same
>>   prefix.  While the procedures for neighbor discovery and duplicate
>>   address detection have to be changed, possible simplification gains
>>   in IPv6 networking including that of intra-site host- and subnet-
>>   mobility might be worth the modification.  Site-external behaviors
>>   don't change through this modification, enabling incremental
>>   deployment of the proposal.  Sites of manageable sizes for which
>>   scalability is not much a critical issue might consider the mode of
>>   operation proposed in this document.
>> 
>> 
>> 
>> 
>> 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
> --------------------------------------------------------------------