RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt

[Skip Montanaro <skip@xxxxxxxxxxxxxx>]

Please forgive me for barging into this discussion in the middle and
probably missing the point.  I'm on the ietf-calendar list.  I don't believe
we were all privy to the ietf-asid discussion that went on before
ietf-calendar was added to the CC: of this thread.  At least it seemed that
way to me.

Would 

   Common-Name; Language=en:  Burgerman
   Common-Name; Language=en:  Burgerdude

have the same semantics as

   Common-Name; Language=en: { Burgerman, Burgerdude }

or

   Common-Name: { Language=en; Burgerman, Language=en; Burgerdude }

The thing that made this pop into my head is the Netscape Cookie: header.  I
know the Apache folks had some problems and had to special-case Cookie:
different than other HTTP headers.  Deciding whether or not it was
beneficial to have multiple occurrences of Common-Name.  Mixing my RFC
metaphors a bit, I could see where you might legitimately have multiple
Received: headers (mix in a little RFC-822) while allowing only a single
Cookie: header (toss in a a little HTTP), but that it could be multi-valued
(in the sense of lists or associative arrays) using one of the second or
third forms above.

Skip Montanaro     |   Musi-Cal: http://concerts.calendar.com/
skip@calendar.com  |   Conference Calendar: http://conferences.calendar.com/
(518)372-5583      |   Python: http://www.python.org/