Re: [v6ops] draft-troan-v6ops-extending-network-reqs

Interesting.

Please list ULAs plus NPTv6 *before NAPT66* in the Introduction. It's pretty clearly preferable.

Also there's one option you haven't mentioned, as far as I can see. Since yesterday, it's mentioned at https://www.ietf.org/archive/id/draft-bourbaki-6man-classless-ipv6-09.html#section-5-3

Regards
    Brian Carpenter

On 07-Oct-23 07:01, Ole Troan wrote:
> With draft-ietf-v6ops-dhcp-pd-per-device focusing on network behaviour I just submitted this (very) early draft on how the node extending the network should behave.
> It is intended as a companion draft to pd-per-device, but also trying to cover the use cases where pd-per-device is not enabled on the upstream link, or does not provide enough address space for assigning a /64 on every downstream link.
> 
> Co-authors much desired.
> 
> Best regards,
> Ole
> 
> 
> A new version of Internet-Draft
> draft-troan-v6ops-extending-network-reqs-00.txt has been successfully
> submitted by Ole Troan and posted to the
> IETF repository.
> 
> Name:     draft-troan-v6ops-extending-network-reqs
> Revision: 00
> Title:    Extending the Network - Host Requirements
> Date:     2023-10-05
> Group:    Individual Submission
> Pages:    8
> URL:      https://www.ietf.org/archive/id/draft-troan-v6ops-extending-network-reqs-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-troan-v6ops-extending-network-reqs/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-troan-v6ops-extending-network-reqs
> 
> 
> Abstract:
> 
>     This memo describes the behaviour of a node that when connecting to a
>     network, offers connectivity via itself to other nodes (or entities
>     needing addresses) connected to it.  The focus is on IPv6
>     connectivity, but the same principles could be applied to IPv4.
> 
> 
> 
> The IETF Secretariat
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops