[v6ops] Discussions Thursday

"Fred Baker (fred)" <fred@cisco.com> Mon, 05 November 2012 14:58 UTC

Return-Path: <fred@cisco.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 9E9EA21F867E for <v6ops@ietfa.amsl.com>; Mon, 5 Nov 2012 06:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t31ZqHgI-yK5 for <v6ops@ietfa.amsl.com>; Mon, 5 Nov 2012 06:58:42 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1C83821F8681 for <v6ops@ietf.org>; Mon, 5 Nov 2012 06:58:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1337; q=dns/txt; s=iport; t=1352127522; x=1353337122; h=from:to:subject:date:message-id:mime-version; bh=84GIR5jSyI5qX6k3StTDvhqAuur/7y7oe6QvWttb2nE=; b=G/a3ElxHYk0I5RGttBu90aVpoVTQqC9RkxihXPGW09aw/EwS+MdHsNrV Cpmv0iAcqBSYbkHq6Bw+43mRpU8pP4LFekl90wO+TkKUfhdKJPFwar4a3 udFhxNCaKXnTo34e9WQnIqTDEUA2zc1hvPONCp/H3PkmDpiptRxeLz+Mx U=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAHHTl1CtJV2Z/2dsb2JhbABEhVC9aoEIgiABBBIBeAEqVicEGwYUh2gLmTiBK59hBJFcYQOOe4EhlDiBa4Jvghk
X-IronPort-AV: E=Sophos; i="4.80,715,1344211200"; d="asc'?scan'208"; a="138900468"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 05 Nov 2012 14:58:41 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id qA5Ewfix017297 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <v6ops@ietf.org>; Mon, 5 Nov 2012 14:58:41 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 08:58:41 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: Discussions Thursday
Thread-Index: AQHNu2YKaiFTjkTlaEuM0x9Gv5aqow==
Date: Mon, 05 Nov 2012 14:58:40 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B1963FA@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.249.91]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--24.256100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/signed; boundary="Apple-Mail=_306BBFBC-C3E0-4AA0-8B22-C81233D45864"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Subject: [v6ops] Discussions Thursday
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: Mon, 05 Nov 2012 14:58:42 -0000

https://datatracker.ietf.org/meeting/85/agenda/v6ops/

We have 11 drafts to discuss on Thursday, and of course it is best if we are all familiar with their contents before we get there. I expect some of them will want to be adopted as working group drafts, some will be dead ends, and some will need more work before they achieve working group support.

Specifically, however, if you have no time to read anything else, please be familiar with the first four drafts on the agenda. I expect we will start the process of finalizing the two working group drafts, and that we will have a robust discussion about the future of RFC 3316.