Re: [v6ops] new draft: draft-townsley-v6ops-6rd-sunsetting

[Fred Baker <[e-mail]>]

Well, we have had 182 messages on the topic since IETF 82. It fits that criterion.

I have a problem in that Monday's agenda is pretty full. Let's discuss Monday during the agenda bash, and we may move a discussion to Thursday. I'll be looking for a volunteer; with my luck, I'll move someone that has a dead short conflict if I pick at random.

On Mar 24, 2012, at 12:04 AM, Mark Townsley wrote:

> 
> On Mar 17, 2012, at 2:55 PM, <[e-mail]> <[e-mail]> wrote:
> 
>> 
>> A new draft has been posted, at http://tools.ietf.org/html/draft-townsley-v6ops-6rd-sunsetting. Please take a look at it and comment.
> 
> 
> It's actually not a new draft, it's an "old" one, posted during the IETF meeting in Taipei last November. After our admittedly tardy posting, the Chairs asked me to pull together a presentation on it, which I was happy to do though the time was quite rushed if I recall. I think the meeting-based conversation on this one started but did not finish.
> 
> In any case, since then Ole and I worked out a draft that incorporates the 6rd sunsetting issue together with the related (yet "inverted") issue that ds-lite has. This is described in draft-townsley-troan-ipv6-ce-transitioning-02.
> 
> As mentioned in my other mail, 6204-bis is skirting this issue in what I continue to assert will end up as dangerous to both technologies should 6204-bis become the reference for inclusion of 6rd or ds-lite into retail CPE hardware.
> 
> Chairs: Alexandre from Free *may* be available Monday (and only Monday) for presentation or Q&A on 6rd-sunsetting if you can squeeze it in as the last presentation (I only know this as CIsco is trying to arrange our "host lunch presentation" on Monday to include him and others to discuss the upcoming v6world launch, so he would have to be here at noon for that anyway - perhaps we can talk him into coming at 11). As the largest 6rd (and IPv6) operator in the world, it might be worth making time for… In particular as generally he and his team does not have time to contribute directly to IETF activities, even if they are certainly contributing to IETF running code. 
> 
> Thanks,
> 
> - Mark
> 
> 
> 
>