Re: [v6ops] Prep for v6ops IETF 84 agenda

On Jun 26, 2012, at 11:28 PM, t.petch wrote:

> ----- 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 came out a few minutes before I got the announcement of -04 :-)

> 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.

http://datatracker.ietf.org/wg/sunset4/charter/ isn't all that helpful; the IESG isn't done with the charter. But in essence, it is a working group for documents that address issues in IPv4 during the IPv6 turn-up. As originally written, it sounded like they couldn't mention IPv6 at all, which is silly. Current discussion among the chairs and the relevant ADs stops it short of being a "transition mechanism working group", but permits discussion of transition mechanisms. At this point, the discussion has come down to cases: does document X fit? does document Y? How do we adjust the proposed charter so that the point, yea or nay, is clear?

Wes and Marc can probably comment more thoroughly, but that's where the discussion stands as I understand it.

> 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/
>> ========================================
>> 
>> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops