Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?

Hi Gunter,

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp)
> Sent: Wednesday, November 15, 2017 6:31 PM
> To: Fred Baker <fredbaker.ietf@gmail.com>; v6ops@ietf.org
> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> Does this mean that the document desires to include all the dynamics of address assignment subscriber management when PD is
> used? (i.e. subscriber vs address correlation state, identification of the subscriber/host, etc...)?

This draft is about what a host can do internally when it gets a prefix delegation
through whatever means. It lists DHCPv6 PD as an example PD service, but does
not impose any special requirements on the delegating router in the operator's
network. The host is required to participate in the client-side prefix delegation
control messaging specified by the prefix delegation service, however.

Thanks - Fred

> If that is a yes, then this is something I think that this easily will result in a too wide scope and boiling the ocean. I think before deciding
> to adopt or not, it would be great to understand the exact scope intended. (I know for a fact that configuration guide of vendors
> regarding subscriber management tend to be huge and lengthy (+1000 pages) documents). I want to make sure that v6ops progresses
> with a pragmatic document of value to operators and not a pure academic exercise.
> 
> G/
> 
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Fred Baker
> Sent: Thursday, November 16, 2017 10:20
> To: v6ops@ietf.org
> Subject: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> At IETF 100, we discussed this document. The “hum” regarding adoption was slightly in favor, but not clear. However, we had one
> comment that IF it were adopted, it needs to be expanded to be an architectural document describing /64-to-the-host deployments.
> 
> Shall we adopt it as a working group draft?
> 
> Sent using a machine that autocorrects in interesting ways...
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops