Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00

But having obviously different prefixes for the class to use to indicate what is ULA and what is "simulated GUA" is still very useful from a teaching perspective.

Owen

On Aug 12, 2013, at 1:30 PM, "George, Wes" <wesley.george@twcable.com> wrote:

>  
> From: Owen DeLong [mailto:owen@delong.com] 
> 
> Because in some cases, the lab is also teaching about ULA+GUA configurations.
>  
> [WEG] I don’t follow your logic. 2001:db8::/32 is not GUA, nor would any such documentation prefix be –quite the contrary, in fact. It just happens to come from 2000::/3 so it *looks* more like GUA, but the network behavior is no different.
>  
> Wes
>  
> On Aug 12, 2013, at 13:05 , "George, Wes" <wesley.george@twcable.com> wrote:
> 
> 
>  
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Carlos Martinez-Cagnazzo
> 
> 
>  
> As far as I understand, Antonio does some training involving 6RD deployments, where each 'team' needs its own /32. There might be other cases though, like for example doing some work involving BGP routing between different teams and for which you expect each one of them to carve a /32.
> [WEG] and that environment can’t use ULA because….?
>  
> Not saying that there aren’t legitimate cases when having more than /32 of documentation space might be useful, just saying that I don’t believe the needs of a lab environment (even in the context of training) is necessarily one of them.
>  
> Wes George
> Anything below this line has been added by my company’s mail server, I have no control over it.
> -----------------
>  
> 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
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops