Re: [v6ops] Agenda discussion

[Fred Baker <[e-mail]>]

As with all submissions, I'm looking for interest expressed on the mailing list by other operators.

On Mar 12, 2012, at 1:14 PM, Qiong wrote:

> Dear George and all,
> 
> We have submitted an updated version of draft-sunq-v6ops-contents-transition based on our practices of IPv4/IPv6 transition system for data center. Since China Telecom has deployed the transition system for data center, we would like to share our experience.
> 
> Please find it in the following link:
> http://tools.ietf.org/html/draft-sunq-v6ops-contents-transition-03
> 
> We would be appreciated to have your comments and suggestions.
> 
> Best wishes
> 
> Qiong
> 
> 
>  
> 
> On Thu, Mar 8, 2012 at 4:29 AM, George, Wes <[e-mail]> wrote:
> IMO draft-ma-v6ops-terminal-test is not ready for discussion in Paris. I'll provide a few comments separately on that one, but I don't want those to be misconstrued as interest in seeing the draft presented.
> 
> I'm interested in draft-gundavelli, but I think it has an awful lot of placeholders for it to be effectively discussed in Paris. Perhaps next meeting, unless the authors are currently working on a -01 draft to be posted later this week that fills in some of the gaps.
> 
> Regarding draft-lopez, As with previous documents of this type, I think there's a certain burden of proof that we need another cookbook document on "IPv6 deployment in [foo]" and that IETF is the proper venue for it. As other work (like ARMD) in IETF is finding out, "datacenter" is such a nebulous concept that purporting to represent a deployment strategy for a datacenter is probably simplistic and overbroad. It will either be so generic that it won't say anything new, or it will be so specific that it won't be applicable to very many applications, and either way that's not overly helpful.
> While Brian is correct in his observation than ICP != datacenter, many of the same things are suggested/useful, so I do think that there's a lot of overlap. The authors either need to propose solving for a different problem space, or identify a way to eliminate the overlap.
> 
> Thanks,
> 
> Wes George
> 
> 
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf Of Fred
> > Baker
> > Sent: Monday, March 05, 2012 11:59 PM
> > To: v6ops v6ops WG
> > Subject: Re: [v6ops] Agenda discussion
> >
> > Downloading the new drafts, I observe three new ones:
> >
> > -rw-rw-r--  1 fred  fred  10823 Mar  5 17:46 draft-ma-v6ops-terminal-test-
> > 00.txt
> > -rw-rw-r--  1 fred  fred  18058 Mar  6 08:44 draft-gundavelli-v6ops-community-
> > wifi-svcs-00.txt
> > -rw-rw-r--  1 fred  fred  21172 Mar  6 10:08 draft-lopez-v6ops-dc-ipv6-00.txt
> >
> > (the date/time stamp reflects the fact that I'm in Japan and therefore a day
> > ahead)
> >
> > In each case, I will be looking for list traffic related to them as my cue for
> > agenda time. Authors, please provoke list traffic...
> >
> >
> > On Mar 6, 2012, at 1:46 PM, Fred Baker wrote:
> >
> > > Stated in no particular order, we have the following documents that meet
> > these criteria:
> > >  - not in the IESG process somewhere
> > >  - posted or updated since IETF 82
> > >  - have had list discussion since IETF 82 or responds to discussion at IETF
> > 82
> > >
> > > At this point, I take them as our agenda at IETF 83. If I am missing a
> > document (if you have posted it since Sunday, I may well be missing it),
> > please remind me.
> > >
> > >
> > > http://tools.ietf.org/html/draft-carpenter-v6ops-icp-guidance
> > >  "IPv6 Guidance for Internet Content and Application Service Providers",
> > >  Brian Carpenter, Sheng Jiang, 22-Feb-12
> > >
> > > No presentation expected, but the authors would like working group adoption.
> > We need to decide whether we want to do that.
> > >
> > > http://tools.ietf.org/html/draft-carpenter-v6ops-label-balance
> > >  "Using the IPv6 Flow Label for Server Load Balancing", Brian Carpenter,
> > >  Sheng Jiang, Willy Tarreau, 17-Jan-12
> > >
> > > http://tools.ietf.org/html/draft-ietf-v6ops-464xlat
> > >  "464XLAT: Combination of Stateful and Stateless Translation", Masataka
> > >  Mawatari, Masanobu Kawashima, Cameron Byrne, 14-Feb-12
> > >
> > > http://tools.ietf.org/html/draft-ietf-v6ops-6204bis
> > >  "Basic Requirements for IPv6 Customer Edge Routers", Barbara Stark,
> > >  Chris Donley, Hemant Singh, Ole Troan, Wes Beebee, 22-Dec-11
> > >
> > > http://tools.ietf.org/html/draft-ietf-v6ops-ivi-icmp-address
> > >  "Stateless Source Address Mapping for ICMPv6 Packets", Xing Li, Congxiao
> > >  Bao, Dan Wing, Ramji Vaithianathan, Geoff Huston, 24-Feb-12
> > >
> > > http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-implementation
> > >  "Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)",
> > >  Fernando Gont, 3-Mar-12
> > >
> > > http://tools.ietf.org/html/draft-ietf-v6ops-wireline-incremental-ipv6
> > >  "Wireline Incremental IPv6", Victor Kuarsingh, Lee Howard, 1-Feb-12
> > >
> > > In the coming week, I am told to expect one additional -00 draft, and I
> > could imagine other drafts being updated. I will be looking for those drafts
> > to meet the criteria above as well, but please drop the chairs a note.
> > > _______________________________________________
> > > v6ops mailing list
> > > [e-mail]
> > > https://www.ietf.org/mailman/listinfo/v6ops
> >
> > _______________________________________________
> > v6ops mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>