Re: [v6ops] new draft: draft-troan-v6ops-6to4-update

Keith Moore <moore@network-heretics.com> Thu, 11 August 2011 17:10 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7515921F8BCB for <v6ops@ietfa.amsl.com>; Thu, 11 Aug 2011 10:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.828
X-Spam-Level:
X-Spam-Status: No, score=-2.828 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGgVIMQDFQm9 for <v6ops@ietfa.amsl.com>; Thu, 11 Aug 2011 10:10:47 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id DA1F321F8BB8 for <v6ops@ietf.org>; Thu, 11 Aug 2011 10:10:47 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id A2D5520E9B; Thu, 11 Aug 2011 13:11:22 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 11 Aug 2011 13:11:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=pIEop0fWHmwr9NxxQyVywLwJutA=; b=d2 5pT1uUus4hK9qMVSIq49bvpHlM4CQbvPcDpJY8vgmOOyHhIsy/XwqVth+PGTfL9z hJcbmn55yhwG5DDMuQWg5IzK294g55F7FE9/hfFy3ssyh9xLM+Qc9XivWzN9z0To EUGRXTlb7LzylwViXf4MO4Wyeb7Y4oclNnCfDkUZo=
X-Sasl-enc: PUSGpFuy85lhwICcg52v7xE9bI0Wr6vKMxXJPkbhKtJ0 1313082681
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E7DE45CC4E; Thu, 11 Aug 2011 13:11:21 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAD6AjGR71CT-M3ZvSSeBuKZWUz=Svc6X=XgLO0NQZBasHsh-cw@mail.gmail.com>
Date: Thu, 11 Aug 2011 13:11:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0C51C1B-D1F2-4FAF-801E-22BBFA65CD2C@network-heretics.com>
References: <201108111355.p7BDt1G05082@ftpeng-update.cisco.com> <CAD6AjGR71CT-M3ZvSSeBuKZWUz=Svc6X=XgLO0NQZBasHsh-cw@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@ietf.org, draft-troan-v6ops-6to4-update@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-troan-v6ops-6to4-update
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 11 Aug 2011 17:10:48 -0000

On Aug 11, 2011, at 12:12 PM, Cameron Byrne wrote:

> Is there a need for this to be standards track or even a working group document?
> 
> I strongly feel the IETF has spent too much time on this and any more
> time is waste of effort.
> 
> RFC6343 is good enough.

Several people have expressed a strong desire for a document that "updates" RFCs 3056 and 3068.  From a process point-of-view, it's not clear (to me) that such an update has to be a standards-track document.  But having it be standards-track would make it clear to the public that the statement represents (rough) IETF consensus.

From a process POV, this doesn't have to be a v6ops WG document.  It could be treated as an individual submission and given a 4-week community-wide Last Call.    That decision is up to the WG chairs and AD.     But even if it were treated as an individual submission, IESG would certainly ask v6ops participants to comment on it.   

For those who wish to minimize the amount of discussion on the v6ops list, comments to the authors (without cc'ing the v6ops list) are certainly welcome.

Keith