Re: [v6ops] Prep for v6ops IETF 84 agenda

t.petch <ietfc@btconnect.com> Tue, 26 June 2012 15:33 UTC

Return-Path: <ietfc@btconnect.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 AC06221F8568 for <v6ops@ietfa.amsl.com>; Tue, 26 Jun 2012 08:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level:
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=-0.560, BAYES_00=-2.599, J_CHICKENPOX_13=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 zJAd7OPbJY55 for <v6ops@ietfa.amsl.com>; Tue, 26 Jun 2012 08:33:33 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe004.messaging.microsoft.com [213.199.154.207]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE3721F855E for <v6ops@ietf.org>; Tue, 26 Jun 2012 08:33:32 -0700 (PDT)
Received: from mail3-am1-R.bigfish.com (10.3.201.226) by AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id 14.1.225.23; Tue, 26 Jun 2012 15:31:50 +0000
Received: from mail3-am1 (localhost [127.0.0.1]) by mail3-am1-R.bigfish.com (Postfix) with ESMTP id C5CF3401F8; Tue, 26 Jun 2012 15:31:50 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT012.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zcb8kz9371I542M1432I1418Izz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah304l)
Received: from mail3-am1 (localhost.localdomain [127.0.0.1]) by mail3-am1 (MessageSwitch) id 1340724708147344_14854; Tue, 26 Jun 2012 15:31:48 +0000 (UTC)
Received: from AM1EHSMHS015.bigfish.com (unknown [10.3.201.238]) by mail3-am1.bigfish.com (Postfix) with ESMTP id 219AA20045; Tue, 26 Jun 2012 15:31:48 +0000 (UTC)
Received: from DB3PRD0702HT012.eurprd07.prod.outlook.com (157.55.224.141) by AM1EHSMHS015.bigfish.com (10.3.207.153) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 26 Jun 2012 15:31:47 +0000
Received: from DB3PRD0610HT003.eurprd06.prod.outlook.com (157.56.252.53) by pod51017.outlook.com (10.3.5.132) with Microsoft SMTP Server (TLS) id 14.15.86.1; Tue, 26 Jun 2012 15:33:23 +0000
Message-ID: <00b401cd53b0$88115840$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Masanobu Kawashima <kawashimam@vx.jp.nec.com>
References: <017901cd538a$e9af8980$4001a8c0@gateway.2wire.net> <20120626235550kawashimam@mail.jp.nec.com>
Date: Tue, 26 Jun 2012 16:28:40 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.53]
X-OriginatorOrg: btconnect.com
Cc: v6ops@ietf.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, 26 Jun 2012 15:33:33 -0000

----- Original Message -----
From: "Masanobu Kawashima" <kawashimam@vx.jp.nec.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: <v6ops@ietf.org>; "Fred Baker (fred)" <fred@cisco.com>; "Ron Bonica"
<ron@bonica.org>
Sent: Tuesday, June 26, 2012 3:55 PM
>
> Hi Tom,
>
> Thank you for your comment.
>
> We took your opinion into consideration.
> I think that we did everything we could.
> Could you please comment us your unclear points or suggestion?
> If we should revise the document, we will revise it immediately.

Ah, I haven't read -04 yet:-(

There was a quite a lot of comment on -03 so I was expecting a -04 and
confirmation or otherwise, on the list, that the comments had been
addressed.  Then I saw Fred's note about -03, which I still don't
understand but I realise I have no idea what sunset4 is, which may be
part of the part of the problem but thought that WGLC was premature
until a new version appeared so I drafted a note in response to Fred.

As I was about to hit send, I saw -04 had appeared but still thought
WGLC premature and sent the note anyway.

So I will read -04 and hope that everyone else who had comments will do
likewise, after which, I hope that the chairs will initiate WGLC.

Tom Petch

> Regards,
> Masanobu
>
>
> >I am confused about the legend for
> >draft-ietf-v6ops-464xlat-03.txt
> >
> >There was a lively discussion in May which left a number of issues
> >unclear for me, and I see that, today, a new version has arrived, so
I
> >think that further discussion should ensue, preferrably on the list.
> >
> >Tom Petch
> >
> >----- Original Message -----
> >From: "Fred Baker (fred)" <fred@cisco.com>
> >To: <v6ops@ietf.org>
> >Cc: "Ron Bonica" <ron@bonica.org>
> >Sent: Monday, June 25, 2012 3:04 AM
> >Subject: [v6ops] Prep for v6ops IETF 84 agenda
> >
> >
> >> 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
>
> ========================================
>  NEC AccessTechnica, Ltd.
>  Product Development Department
>  Masanobu Kawashima
>  kawashimam@vx.jp.nec.com
>  http://www.necat.co.jp/
> ========================================
>
>