---- Original Message ----- From: "Simon Perreault" <simon.perrea...@viagenie.ca> To: <ipv6@ietf.org> Sent: Friday, May 04, 2012 3:54 PM Subject: Re: Options for draft-ietf-6man-uri-zoneid
> On 2012-05-04 09:44, Juergen Schoenwaelder wrote: > > On Fri, May 04, 2012 at 08:29:11AM -0500, Rajiv Asati (rajiva) wrote: > >> +1 for option 3 with hyphen. > >> > >> I like to be able to read the URI without having to put my glasses on. > > > > Interface names can contain other fancy characters and hence this one > > will simply not work in the general case. > > The character just after the address is "special". We know it is special > because it is just after the address. It can never be confused with the > interface name itself. We could even choose something ridiculous, e.g. > "x", as the special character and there would be no possibility of conflict. > Yes, it is a bit like Microsoft and their use of \ \\ \\\ which, because of the context, can safely be parsed. Ditto some URI such as file:/// file://// Tom Petch > +1 for hyphen > > Simon > -- > DTN made easy, lean, and smart --> http://postellation.viagenie.ca > NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca > STUN/TURN server --> http://numb.viagenie.ca > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
