Bug#509935: decide whether Uploaders is parsed per RFC 5322
"Giacomo A. Catenazzi" <cate@debian.org> writes:
> Russ Allbery wrote:
>> We could also standardize a simple escaping mechanism of our own (allow
>> double quotes, for example, but require that, if used, they surround
>> the entire name and are stripped off by the parsing).
>> However we resolve this, we should probably also update the referece in
>> Policy to RFC 822 to refer to RFC 5322 instead, since I doubt we really
>> want to support source-routed e-mail addresses or similar bizarreness
>> in Debian control files.
> Hmm, RFC5322 is not yet a standard (BTW it is not yet cited in STD1),
This is true, but it's essentially meaningless. It's sort of an artifact
of the IETF process, but RFC 822 is for practical purposes obsolete and
RFC 5322 reflects the current state of addressing standards.
> and anyway it still use the old semantic for compatibility (see the
> "obs-" references, e.g. the section 4.4).
True. We should explicitly rule that out.
> IMHO we should specify a subset of RFC 822, because a full 5322 parse is
> IMO too complex (and BTW not so useful) to implement in all the tools.
> Ev. require to use only a subset in the control file, and to recommend a
> full 5322 parsing in the tools.
I'm leaning that way as well. I also don't want to require people to use
RFC 2047 encoding if they have a name that doesn't fit into ASCII.
Anyone have any suggestions on a good subset and description of it that
isn't too complex?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: