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

> One is the draft statement that URI producers should
> encode reserved characters (such as the gen-delim '@')

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

so your examples are baffling. The '@' does not need to
be encoded in either place. Both 'segment' and 'query'
are defined in terms of 'pchar' which explicitly includes
'@'.

You've stated your belief about this requirement, but
I can't find it in the draft. Perhaps you could quote
which words have led you to what must be an erroneous
conclusion?

> The subject draft, however, does not list reserved
> characters for the individual URI components, and
> reserves '@' generally, 

but

#  These characters are called
#  "reserved" because they may (or may not) be defined as delimiters by
#  the generic syntax, by each scheme-specific syntax, or by the
#  implementation-specific syntax of a URI's dereferencing algorithm.

Larry

Received on Thursday, 4 November 2004 16:42:44 UTC