Re: [v6ops] Prep for v6ops IETF 84 agenda

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 10 July 2012 15:58 UTC

Return-Path: <Fred.L.Templin@boeing.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 4E66011E807F for <v6ops@ietfa.amsl.com>; Tue, 10 Jul 2012 08:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 3rS0XQDdC4ZU for <v6ops@ietfa.amsl.com>; Tue, 10 Jul 2012 08:58:40 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 2E67221F85D7 for <v6ops@ietf.org>; Tue, 10 Jul 2012 08:58:40 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q6AFx57n019246 for <v6ops@ietf.org>; Tue, 10 Jul 2012 08:59:06 -0700
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [130.247.228.54]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q6AFx5fY019242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 10 Jul 2012 08:59:05 -0700
Received: from stl-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q6AFx41f031843; Tue, 10 Jul 2012 10:59:04 -0500
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q6AFx39W031749 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 10 Jul 2012 10:59:04 -0500
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-05.nw.nos.boeing.com ([130.247.25.109]) with mapi; Tue, 10 Jul 2012 08:59:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Date: Tue, 10 Jul 2012 08:59:02 -0700
Thread-Topic: [v6ops] Prep for v6ops IETF 84 agenda
Thread-Index: AQHNUnbpWFu7FKUfJEyvobkjy/vWXZcjFqiA//+s4lA=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65D8F24CFF2@XCH-NW-01V.nw.nos.boeing.com>
References: <8D73E1D6-A968-4397-A843-FE073197B7F1@cisco.com> <45F1DB32-74F6-4E4A-88E2-118B76A5F474@cisco.com>
In-Reply-To: <45F1DB32-74F6-4E4A-88E2-118B76A5F474@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] Prep for v6ops IETF 84 agenda
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: Tue, 10 Jul 2012 15:58:41 -0000

Fred,

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
> Fred Baker (fred)
> Sent: Tuesday, July 10, 2012 8:51 AM
> To: v6ops@ietf.org WG
> Cc: Ron Bonica
> Subject: Re: [v6ops] Prep for v6ops IETF 84 agenda
> 
> I have an updated list, as of the -00 cutoff yesterday. I have culled out
> drafts that have not been updated since the last meeting.
> 
> The three "not clear" drafts seem to me on the hairy edge. In Fred's case,
> yes, there has been list discussion. It has mostly been to tell him he's
> wrong in his approach.

That's why we have list discussion - to set things right.
'draft-generic-v6ops-tunmtu' now has things right, and
should have a more solid status than "not clear".

> What little discussion has happened on draft-lopez-
> v6ops-dc-ipv6 seems to mostly point to other documents as already saying
> things. draft-zhang-v6ops-ipv6oa-iwf is just new, and hasn't been
> discussed.
> 
> Your thoughts on this?

This is somewhat better, but now I need to ask why do you
have 'draft-templin-v6ops-isops' as out of charter?

Thanks - Fred
fred.l.templin@boeing.com

> #no expressed interest
> Apr 26 20:07 draft-jiang-v6ops-v4v6mc-proxy-01.txt
> Mar 29 11:27 draft-donley-v6ops-ce-router-design-00.txt
> 
> #out of charter
> May  9 19:44 draft-templin-v6ops-isops-17.txt
> Mar 30 19:33 draft-yang-v6ops-fast6-00.txt
> 
> #in IESG or RFC Editor queues
> May 15 10:12 draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-06.txt
> May 22 05:30 draft-ietf-v6ops-ra-guard-implementation-04.txt
> Jul  3 02:45 draft-ietf-v6ops-ivi-icmp-address-02.txt
> May 29 19:10 draft-ietf-v6ops-wireline-incremental-ipv6-04.txt
> Jun  9 13:41 draft-ietf-v6ops-ipv6-discard-prefix-05.txt
> May 16 19:02 draft-ietf-v6ops-6204bis-09.txt
> 
> #WGLC requested in v6ops, no news from AD on sunset4
> Jul  2 20:42 draft-ietf-v6ops-464xlat-05.txt (WGLC requested by authors)
> 
> #Not clear
> Jun 19 19:33 draft-lopez-v6ops-dc-ipv6-02.txt
> Jul  4 07:42 draft-generic-v6ops-tunmtu-09.txt
> Jun 30 03:02 draft-zhang-v6ops-ipv6oa-iwf-00.txt
> 
> #For agenda
> Jun 29 06:37 draft-matthews-v6ops-design-guidelines-00.txt
> Jun 12 03:26 draft-ietf-v6ops-icp-guidance-01.txt (WGLC requested by
> authors)
> Apr 29 21:58 draft-gundavelli-v6ops-community-wifi-svcs-04.txt
> Jul  4 02:18 draft-chen-v6ops-nat64-experience-02.txt
> 
> On Jun 24, 2012, at 7:04 PM, Fred Baker (fred) wrote:
> 
> > I sat down this morning to assess our agenda. Interested in working
> group comment.
> >
> > # no update
> > Jan 11 16:48 draft-yang-v6ops-fast6-pppoe-02.txt
> > Feb 21 18:10 draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-04.txt
> > Feb 23 07:29 draft-carpenter-v6ops-icp-guidance-03.txt
> > Feb 25 11:37 draft-ietf-v6ops-ivi-icmp-address-01.txt
> > Feb 28 08:49 draft-chkpvc-enterprise-incremental-ipv6-00.txt
> > Mar  5 17:46 draft-ma-v6ops-terminal-test-00.txt
> > Mar  7 07:33 draft-carpenter-v6ops-label-balance-02.txt
> > Mar 12 06:21 draft-vanrein-v6ops-6bed4-01.txt
> > Mar 12 17:52 draft-chen-v6ops-nat64-experience-01.txt
> > Mar 12 21:34 draft-liu-v6ops-ula-usage-analysis-02.txt
> > Mar 13 04:59 draft-sunq-v6ops-contents-transition-03.txt
> > Mar 30 03:27 draft-donley-v6ops-ce-router-design-00.txt
> > Mar 31 11:33 draft-yang-v6ops-fast6-00.txt
> >
> > #no expressed interest
> > Jun 20 11:33 draft-lopez-v6ops-dc-ipv6-02.txt
> > Apr 27 12:07 draft-jiang-v6ops-v4v6mc-proxy-01.txt
> >
> > #out of charter
> > Jun 24 07:59 draft-generic-v6ops-tunmtu-07.txt
> > May 10 11:44 draft-templin-v6ops-isops-17.txt
> >
> > #in IESG queue
> > May 30 11:10 draft-ietf-v6ops-wireline-incremental-ipv6-04.txt
> > May 17 11:02 draft-ietf-v6ops-6204bis-09.txt
> >
> >
> > #WGLC in v6ops or move to sunset4; awaiting AD direction
> > May  8 10:14 draft-ietf-v6ops-464xlat-03.txt
> >
> > #potential for agenda
> > Apr 30 13:58 draft-gundavelli-v6ops-community-wifi-svcs-04.txt
> > May 16 02:12 draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-06.txt
> > May 22 21:30 draft-ietf-v6ops-ra-guard-implementation-04.txt
> >
> > #for agenda, perhaps ready for last call
> > Jun 12 19:26 draft-ietf-v6ops-icp-guidance-01.txt
> >
> >
> >
> > For draft-ietf-v6ops-ivi-icmp-address, the last discussion was in April,
> and we were to expect an update. If that happens, I expect to bring that
> to the agenda.
> >
> > Lee asked about draft-chkpvc-enterprise-incremental-ipv6 on the list,
> but I see no update and I wasn't clear on the list commentary, whether the
> operators want to discuss.
> >
> > There is still, of course, time for folks to post -00 drafts (until 9
> July); if there is list discussion of those drafts, we will include them
> in the agenda.
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops