No, I think it's exactly *not* confused on this point. There's
a distinction between the idealised URI and the produced URI;
in the produced URI, "%25" stands for "%" in the idealised URI.

We have no real choice but to use % since that was chosen years
ago, and that means that the produced URI contains %25.

   Brian


On 2012-03-06 11:15, Carsten Bormann wrote:
> This leaves me thoroughly confused.
> 
> While the text seems to indicate the contrary, the ABNF makes it clear that
> 
> coap://[fe80::a%25en1]/.well-known/core
> 
> is intended to indicate the zone ID of "25en1".
> 
> This is the only place in a URI where a percent is proposed to be used in 
> stand-alone fashion -- everywhere else it occurs as part of pct-encoded.  For 
> a good reason.
> 
> E.g., this works perfectly to talk to localhost in Safari and Chrome:
> http://[%3a%3a1]/
> 
> Any other character but % (or []A-Fa-f0-9:] of course) would be less 
> confusing for indicating zone-ids.  I'd recommend choosing one from 
> sub-delims, such as * or &.
> 
> Grüße, Carsten
> 
> --------------------------------------------------------------------
> 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
--------------------------------------------------------------------

Reply via email to