RE: Comments on draft-fielding-uri-rfc2396bis-07

Larry:
> I can't find anything in rfc2396bis section 2.2
> which would lead anyone to believe that 
>   mailto:a@b.com?to=joe@example.com
> should instead be written 
>   mailto:a%40b.com?to=joe%40example.com
> 

Bruce:
>       reserved    = gen-delims / sub-delims
>       gen-delims  = ":" / "/" / "?" / "#" / "[" / "]" / "@"
> 
> [...]
> 
>    URI producing applications should percent-encode data octets that
>    correspond to characters in the reserved set.


You've taken this out of context. The entire preceding paragraphs
describe how reserved characters in gen-delims are used as
delimiters (unencoded). 

To be pedantically accurate, I could imagine
 'should percent-encode' => 'should otherwise percent-encode'

but I'm not convinced it is necessary, since a reading that
ALL reserved characters should be encoded no matter what
would lead you to encode every delimiter everywhere -- which
would be nonsensical.

Larry