Re: [renum] FW: New Version Notification for draft-liu-6renum-gap-analysis-02.txt

["George, Wes" <[e-mail]>]

> From: Brian E Carpenter [mailto:[e-mail]]
> Sent: Friday, November 11, 2011 8:04 PM
> To: George, Wes
> Cc: Leo Liu(bing); [e-mail]
> Subject: Re: [renum] FW: New Version Notification for draft-liu-6renum-
> gap-analysis-02.txt
>
>
> I think there's scope for analysing shim6 in the context of
> renumbering.
> It wasn't really a consideration during the design.
>
[WEG] agree, hadn't really thought about shim6 in that context, which is why I didn't make the connection. As a solution it'd mainly be a question of applicability and benefits vs costs to implement, because while we have running code, wide deployment is another matter entirely.

>
> In all cases, session survivability requires a persistent ID of some
> kind, as far as the transport layer is concerned.
[WEG] and that's critical to include in the discussion regarding its applicability to renumbering

>
> We do need to decide how much of a goal session survivability is. IMHO
> it is a hard goal, and it only affects a very small number of
> applications.
>
[WEG] WG Chair hat on: Since in this WG we're not suggesting solutions to the gaps we identify in most cases, I'm not sure we have to come to a definite decision on that. Session Survivability is a part of any gap discussion on renumbering, and the more articulate we can be on the potential options, where they still have gaps, and where we don't have any solutions will be helpful in determining what follow-on work must be done when passing protocol work to other WGs.

Wes


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.