Re: [v6ops] Agenda scheduling for IETF 79

Tina TSOU <tena@huawei.com> Mon, 04 October 2010 10:05 UTC

Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B26BF3A6F78 for <v6ops@core3.amsl.com>; Mon, 4 Oct 2010 03:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.742
X-Spam-Level:
X-Spam-Status: No, score=-99.742 tagged_above=-999 required=5 tests=[AWL=-0.449, BAYES_50=0.001, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wGxI7m8JvdI for <v6ops@core3.amsl.com>; Mon, 4 Oct 2010 03:05:03 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 54E933A6F4B for <v6ops@ietf.org>; Mon, 4 Oct 2010 03:05:03 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R006J0FS4Z4@szxga05-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 18:00:04 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R007W0FS3PZ@szxga05-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 18:00:04 +0800 (CST)
Received: from [192.168.1.4] ([113.116.36.142]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9R008KAFS2X2@szxml02-in.huawei.com>; Mon, 04 Oct 2010 18:00:03 +0800 (CST)
Date: Mon, 04 Oct 2010 18:00:01 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_Qx2GOIUqi1cwOWLBTbpsQw)"
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Oct 2010 10:05:05 -0000

Thank you for the arrangement. You made the agenda so quickly compared  
to the WG I chair;)

Some comments are below.

1)
"Welcome and introduction from the China Network Operators Group
Dong Yan, CNNOG and CNISP"

What's the implication from the China NOG introduction? In this case,  
do Asia, Europe and Oceania NOG also need to be given the  
introduction? These operators from North America, Europe, and Asia  
consider IETF is a global and original organization for IPv4 to IPv6  
transition.

What's the relationship between IETF WG v6ops and xNOG in v4 to v6  
transition area?

2)
"Problem Statements of IPv6 Transition of ISP
17-Sep-10, <draft-lee-v4v6tran-problem-02.txt>
Framework for IP Version Transition Scenarios
18-Aug-10, <draft-carpenter-v4v6tran-framework-00.txt>"

We have fully discussed the PS I-D and framework I-D in the v4v6tran  
WebEx meeting.
The target is a set of use cases I-Ds and transition guides I-Ds for  
broadband, cable, and mobile scenarios, which are aimed for  
information RFCs.
Do the PS I-D and framework I-D need to be discussed again in WG  
v6ops? Are they also aimed for informational RFCs? I don't have strong  
opinion about this.

3)
"Use Case For IPv6 Transition For a Large-Scale Broadband Service  
Provider
14-Sep-10, <draft-tian-v4v6tran-broadband-sp-usecase-00.txt>"
I don't know whether Can-Can would like to present this. I think it  
has been replaced by draft-huang-v6ops-v4v6tran-bb-usecase.

4)
"IPv6 Transition Guide For A Large ISP Providing Broadband Access
15-Sep-10, <draft-yang-v4v6tran-ipv6-transition-guide-00.txt>
IPv6 Transition Guide For A Large-scale Broadband Network
27-Sep-10, <draft-yang-v6ops-v4v6tran-bb-transition-guide-00.txt>"
I think only latter will be presented in WG v6ops Beijing meeting.
The latter is not China Telecom only any more. It is the initial  
version to invite contribution from all broadband networks. 90% of  
China Telecom's existing access network is PPPoE access network, which  
may be similar to some of the operators. They will focus on this type.  
This I-D leave space for those operators to contribute for existing  
DHCP access network.

Hope it helps.



B. R.
Tina
http://tinatsou.weebly.com




On Oct 4, 2010, at 1:37 PM, Fred Baker wrote:

>
> On Oct 3, 2010, at 5:52 AM, Tina TSOU wrote:
>
>> Hi Fred,
>> Just a minor reminder that you said 0.75 to 1.5 sessions will be  
>> allocated to v4v6tran work.
>> Here is the record.
>> https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=46384302&rKey=10def3e927a116b3
>
> After you look at the posted agenda, please feel free to comment on  
> it.
>
>> B. R.
>> Tina
>> http://tinatsou.weebly.com
>>
>>
>>
>>
>> On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:
>>
>>> On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
>>>> Dear Fred Baker,
>>>>
>>>> The sessions that you have requested have been scheduled.
>>>> Below is the scheduled session information followed by
>>>> the information of sessions that you have requested.
>>>>
>>>> V6OPS Se blockquote>
>>>>> Wednesday, Morning Session I 0900-1130
>>>>> Room Name: Valley Ballroom B
>>>>> ----------------------------------------------
>>>>> V6OPS Session 2 (2.5 hours)
>>>>> Friday, Afternoon Session I 1300-1500
>>>>> Room Name: Valley Ballroom A
>>>>> ----------------------------------------------
>>>>
>>>>
>>>> On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
>>>>> The DRAFT agenda is ready for viewing.  Please note the cutoff  
>>>>> date for
>>>>> requests to reschedule Working Group and BOF meetings is October  
>>>>> 11, 2010
>>>>> 17:00 PT.  The final agenda will be published on October 15, 2010.
>>>>>
>>>> https://datatracker.ietf.org/meeting/79/agenda.html
>>>> https://datatracker.ietf.org/meeting/79/agenda.txt
>>>>
>>>> http://www.ietf.org/meeting/79/index.html
>>>>
>>>>
>>>> Thanks,
>>>> Wanda
>>>>
>>>> Only 36 days until the Beijing IETF!
>>>> Online registration for the IETF meeting is at:
>>>> http://www.ietf.org/meetings/79/
>>>
>>>
>>> Joel, Kurtis, and I are sta F 79 Agenda. What I have at this  
>>> instant is at http://www.ietf.org/proceedings/79/agenda/ 
>>> v6ops.html. I requested two morning (2.5 hours) slots; I got one  
>>> morning slot and "Friday afternoon until we stop talking" -  
>>> nominally two hours, but Wanda tells me she has noted that we will  
>>> likely run over. It looks like we will have a pretty full agenda;  
>>> between the -v4v6tran- and -v6ops- work, we have a total of 18  
>>> drafts.
>>>
>>> Anything I have missed - drop us a note at v6ops-chairs@tools.ietf.org 
>>>  if you would. The chairs have not yet discussed this in detail  
>>> amongst ourselves yet, so I'm not sure which day will get which  
>>> topic, and there are other reorganizations that could happen. If  
>>> folks have strong opinions, that too would be interesting to know.
>>>
>>> This assumes, btw, that the WGLCs that we have been running mean  
>>> that we don't need to discuss those draf ts. Besi nda, our status  
>>> is:
>>>
>>> To complete WGLC before IETF 79
>>> 	draft-arkko-ipv6-transition-guidelines    (waiting new draft)
>>> 	draft-ietf-v6ops-tunnel-security-concerns (waiting document  
>>> writeup)
>>> 	draft-ietf-v6ops-incremental-cgn          (just completed WGLC)
>>> 	draft-ietf-v6ops-tunnel-loops             (in WGLC)
>>> 	draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24)
>>> 	draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)
>>>
>>> In IESG discu ssion:	draft-gundavelli-v6ops-l2-unicast-04	
>>> 	draft-ietf-v6ops-cpe-simple-security-14	
>>> 	draft-ietf-v6ops-ra-guard-08
>>> 	draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)
>>>
>>> RFC Editor Queue		
>>> 	draft-ietf-v6ops-ipv6-cpe-router-07
>>> 	draft-ietf-v6ops-isp-scenarios-00
>>> 	draft-thaler-v6ops-teredo-extensions-08
>>>
>>> Dead?
>>> 	draft-sarikaya-v6ops-prefix-delegation-01		
>>>
>>> Recent RFCs:
>>>
>>> http://www.ietf.org/rfc/rfc5963.txt
>>> 5963 IPv6 Deployment in Internet Exchange Points (IXPs). R.  
>>> Gagliano.
>>>    August 2010. (Format: TXT=22786 bytes) (Status: INFORMATIONAL)
>>>
>>> http://www.ietf.org/rfc/rfc5991.txt
>>> 5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.
>>>    September 2010. (Format: TXT=20847 bytes) (Updates RFC4380)  
>>> (Status:
>>>    PROPOSED STANDARD)
>>>
>>> http://www.ietf.org/rfc/rfc6018.txt
>>> 6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.
>>>    September 2010. (Format: TXT=21541 bytes) (Status: INFORMATIONAL)
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>
>>
>> _______________________________________________
>>
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>