Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites to Informational

Fred Baker <fred@cisco.com> Fri, 12 November 2010 22:53 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 028613A6B5A for <v6ops@core3.amsl.com>; Fri, 12 Nov 2010 14:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.095
X-Spam-Level:
X-Spam-Status: No, score=-110.095 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXrnwfM9iAew for <v6ops@core3.amsl.com>; Fri, 12 Nov 2010 14:53:24 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 1BA7A3A6A38 for <v6ops@ietf.org>; Fri, 12 Nov 2010 14:53:24 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABtU3UyrR7Hu/2dsb2JhbACiUXGjOJsuhUoEhFiFf4MM
X-IronPort-AV: E=Sophos;i="4.59,190,1288569600"; d="scan'208";a="285338541"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 12 Nov 2010 22:53:58 +0000
Received: from Freds-Computer.local (tky-vpn-client-230-181.cisco.com [10.70.230.181]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oACMrptT014962; Fri, 12 Nov 2010 22:53:56 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sat, 13 Nov 2010 06:53:57 +0900
X-PGP-Universal: processed; by Freds-Computer.local on Sat, 13 Nov 2010 06:53:57 +0900
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <201011122134.oACLY9Lt015423@cichlid.raleigh.ibm.com>
Date: Sat, 13 Nov 2010 06:53:41 +0800
Message-Id: <7DF14562-C19E-4691-84AE-CF2956ACEAA3@cisco.com>
References: <7DBF181A-1DDB-457E-ACB0-56C16F630EE7@cisco.com> <201011122134.oACLY9Lt015423@cichlid.raleigh.ibm.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Narten <narten@us.ibm.com>, draft-ietf-v6ops-3177bis-end-sites@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites to Informational
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 22:53:25 -0000

Question for the group - if it is not exhausted :-)

When I issued the WGLC for 3177bis, I didn't specify the intended status. When I filed the report with Ron, I stated that it was intended to be Informational. However, the document itself says that it intends to be a BCP.

The argument for BCP is that it replaces a document that was a formal statement from the IESG and IAB, which probably should have been a BCP. For that reason, I notified the IAB of the impending last call a week before opening it, to give them warning and time to respond; in my report, I pointed that fact out and requested that the IESG touch base with the IAB to make sure they were in agreement.

Hmm.

So - question to v6ops. Are you OK with advancing this as BCP?

On Nov 13, 2010, at 5:34 AM, Thomas Narten wrote:

> Fred (& WG):
> 
> I just realized that we don't have clarity as to whether this document
> should be informational or a BCP.
> 
> The document itself (in the headers) says the intendend status is BCP.
> 
> The WGLC didn't actually say one way or the other. It just last-called
> the document. :-)
> 
> Your note to the ADs says advance as Informational.
> 
> Personally, I have a preferance for BCP because that makes it clear
> that this is an IETF statement. If the document is just informational,
> that is less clear. 
> 
> RFC 3177, which it replaces is informational. But it was pretty clear
> that it was an IETF document because the title was:
> 
>     IAB/IESG Recommendations on IPv6 Address Allocations to Sites.
> 
> This document's more modest title is:
> 
>     IPv6 Address Assignment to End Sites
> 
> and has dropped the IESG/IAB part because the document is now just a
> normal IETF/WG document, not something that is an IESG/IAB statement
> per se.
> 
> Is the WG OK with advancing this as a BCP?
> 
> Thomas