[v6ops] draft-byrne-v6ops-clatip WGLC

Fred Baker <fred@cisco.com> Sun, 04 May 2014 18:00 UTC

Return-Path: <fred@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B728A1A00E2 for <v6ops@ietfa.amsl.com>; Sun, 4 May 2014 11:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.152
X-Spam-Level:
X-Spam-Status: No, score=-115.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZ6lH7Da3uoj for <v6ops@ietfa.amsl.com>; Sun, 4 May 2014 11:00:30 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9651A00DE for <v6ops@ietf.org>; Sun, 4 May 2014 11:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1297; q=dns/txt; s=iport; t=1399226427; x=1400436027; h=date:from:message-id:to:subject:cc; bh=bv/H6wMVCZAfNSTtObQ53UuWcjWWl6BJJYCUlZaALo8=; b=mnJOCGDuCRu8XyW97sP5mViGQkTAGTu05Rz+brfCnJQLM327cM3R5JbG y4QoHsf4ra1q6SlsVzPjIVT9lgZIB8qRq5kLPeZ0EREURaL65G7mwDBjm wtSqlekzZjk7EiKDBjoZAQKDKo7cdxEcvpgXnDJD34rxeRwAqzUJxA21V A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao0KAPp/ZlOrRDoI/2dsb2JhbABSBoMGT64YAZcmgQ8WdIMlPDSJIQ7JexeOD0MdhCkEigeQaZE4g1Q
X-IronPort-AV: E=Sophos;i="4.97,983,1389744000"; d="scan'208";a="108592627"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 04 May 2014 18:00:26 +0000
Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s44I0NBm008363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 May 2014 18:00:25 GMT
Received: from irp-view13.cisco.com (localhost [127.0.0.1]) by irp-view13.cisco.com (8.14.4+Sun/8.13.8) with ESMTP id s44I0NIs002030; Sun, 4 May 2014 11:00:23 -0700 (PDT)
Received: (from fred@localhost) by irp-view13.cisco.com (8.14.4+Sun/8.14.4/Submit) id s44I0Mvh002013; Sun, 4 May 2014 11:00:22 -0700 (PDT)
Date: Sun, 04 May 2014 11:00:22 -0700
From: Fred Baker <fred@cisco.com>
Message-Id: <201405041800.s44I0Mvh002013@irp-view13.cisco.com>
To: v6ops@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/PmqdKNuWCLdb82lDLUaKn6yK1LE
Subject: [v6ops] draft-byrne-v6ops-clatip WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 04 May 2014 18:00:32 -0000

This is to initiate a two week working group last call of
http://tools.ietf.org/html/draft-byrne-v6ops-clatip.  

This is unusual. Please bear with me here. We have discussed it several
times. In March, the working group decided to offer it to softwire,
whose chairs told me they wanted to take it on themselves and pursue
it.  However, it is HOL blocked by MAP, which they want to complete
first. With their concurrence, noting that the working group has said
in the past couple of weeks that it wants to finish it, we need to
finish it here.

My game plan is to collect comments on the existing draft, including
any idnits issues, and have Cameron post an update named
draft-ietf-v6ops-clatip - a working group draft. If that passes the
smell test, we'll send it to Joel.

Please read it now. If you find nits (spelling errors, minor suggested
wording changes, etc), comment to the authors; if you find greater
issues, such as disagreeing with a statement or finding additional
issues that need to be addressed, please post your comments to the
list.

We are looking specifically for comments on the importance of the
document as well as its content. If you have read the document and
believe it to be of operational utility, that is also an important
comment to make.