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

Hi Fred,

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Fred Baker
> Sent: Tuesday, November 28, 2017 1:41 PM
> To: v6ops@ietf.org
> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> 
> 
> > On Nov 28, 2017, at 12:37 PM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> > See below for an updated version of this draft. This version addresses comments
> > received on the list regarding more clearly identifying classes of devices that can
> > be considered as ordinary routers.
> 
> I have not gone through the entire list of comments to see if they have been addressed, but I see one quickly that has not. In figure 1,
> and each comparable figure, an assumption is made that the delegation is made by a specific router, referred to as the "delegating
> router", as opposed to "a system in the upstream network". The latter is the common case, implemented using DHCP's relay
> mechanism. From my perspective, if we are describing an architecture for a commonly-implemented service, it should at least
> describe current common implementations of the service.

I didn't add anything about this, because I thought I had already addressed your
question (you didn't respond). What you are asking is already covered in RFC3633,
and the figures in this document are derived from Section 5.1 of RFC3633. The
relay function is also addressed in RFC3633, Section 14.

Proposed resolution is to add the following sentence in the introduction:

  "Delegating/Requesting router relationships and the role of relay agents are
   discussed in [RFC6333] and apply also to this document."

Thanks - Fred

> I would encourage comment on the draft. Lorenzo specifically wanted material added to it to fully describe that architecture, and I'm
> not sure what else others had in mind. Let's get those comments on the table, and then we can decide when and whether to ask for
> adoption.
> 
> > Can we have this version as a wg item?
> >
> > Thanks - Fred
> >
> > -----Original Message-----
> > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> > Sent: Tuesday, November 28, 2017 12:27 PM
> > To: i-d-announce@ietf.org
> > Subject: I-D Action: draft-templin-v6ops-pdhost-16.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >
> >
> >        Title           : IPv6 Prefix Delegation Models
> >        Author          : Fred L. Templin
> > 	Filename        : draft-templin-v6ops-pdhost-16.txt
> > 	Pages           : 12
> > 	Date            : 2017-11-28
> >
> > Abstract:
> >   IPv6 prefixes are typically delegated to requesting routers which
> >   then use them to number their downstream-attached links and networks.
> >   This document considers prefix delegation models according to whether
> >   the requesting router acts as a router on behalf of any downstream
> >   networks, as host on behalf of its local applications or as both.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-templin-v6ops-pdhost/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-templin-v6ops-pdhost-16
> > https://datatracker.ietf.org/doc/html/draft-templin-v6ops-pdhost-16
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-templin-v6ops-pdhost-16
> >
> >
> > 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.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops