[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: narten-ipv6-3177bis-48boundary: updating an IAB document
- To: Thomas Narten <narten@us.ibm.com>
- Subject: Re: narten-ipv6-3177bis-48boundary: updating an IAB document
- From: Brian E Carpenter <brian.e.carpenter@gmail.com>
- Date: Wed, 30 Jul 2008 19:22:31 +1200
- Cc: v6ops@ops.ietf.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=i/2e8okzJri9Qdyv23SwDs0aWTHkXwUFwuODBgNhOzz/UzFO2atlVr+reDlKgQbU1r Z5oJJrEWS1/haWlstfUM8GWcXVhZBnny1Blz1R4H75Dk8zIS7JG/Kd4HW3wimWOOAq3R vj7dxK24SfRPvsy59OBp4lQwkKSVu5W3XRRuU=
- In-reply-to: <200807252015.m6PKFuRu011888@cichlid.raleigh.ibm.com>
- Organization: University of Auckland
- References: <200807252015.m6PKFuRu011888@cichlid.raleigh.ibm.com>
- User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
On 2008-07-26 08:15, Thomas Narten wrote:
> There were some comments in earlier mail and at the Philly session
> saying essentially: 3177 is an IAB document (actually it was a joint
> IAB/IESG document) and therefore the IAB needs to change it and the WG
> shouldn't (or can't) be the one to do this.
>
> I've had some informal conversations with I* members about this and
> the impression I got was they'd actually prefer this be a WG
> document. If it is a regular IETF document, both the IESG/IAB will
> have a chance to review and have input. But there is no need for those
> organizations to initiate the document or be the primary drivers for
> it.
>
> If the IAB ends up wanting its name on the document or have some other
> text included (i.e, to somehow give it the weight needed to updated
> 3177), we can have that discussion later. But I think first and
> foremost, this document should be an IETF document, since it is
> intended to be an IETF recommendation. That means having it come up
> through a WG is just fine.
>
> Having said all that, I will raise the issue again to see if anything
> has changed in how best to process this document.
>
Note that 3177 actually says:
"3. Address Delegation Recommendations
The IESG and the IAB recommend ..."
However, as we've now got more clarity on the various RFC streams,
and probably a clearer relationship with IANA than in 2001,
I don't think there's much doubt that this should be handled
as a regular IETF document.
The draft doesn't list an intended status. Are you thinking
of anything stronger than Informational?
Brian