![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I am in favor of the proposed Originator_Info header, but the Devil is
in the details. Specifically, I question the wisdom of prohibiting use
of the attributes in filters, and I strongly disagree with the
specification of character set.
While it is true that the header can be trivially forged, that does
not not provide adequate grounds for a MUST NOT. If I choose to use
the contents of this header for purposes of authorization, no harm to
the net occurs, although I may cause harm to myself. Even a SHOULD NOT
is questionable.
Given the current direction of internationalization, I don't see why
any choice of character encoding other than UTF-8 makes sense. Use of
MIME means that attributes will be unreadable by those not possessing
the appropriate character sets, even if they have all of the glyphs.
The only advantage that I can see for MIME is in distinguishing the
oriental languages that have been "unified" in Unicode.
-----------------------------------------------------
-- End of forwarded message
-----------------------------------------------------
-----------------------------------------------------------
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2
Team OS/2
Team PL/I
-----------------------------------------------------------
The US Senate thinks you need your junk email. Now the House of Reps.
is considering the issue. Let them know how
you feel about junk email! Info available at
http://www.ybecker.net/pink/ page of the Forum for Responsible and
Ethical Email.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.