RFC 4096 on Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.


        RFC 4096

        Title:      Policy-Mandated Labels Such as "Adv:" in Email
                    Subject Headers Considered Ineffective At Best
        Author(s):  C. Malamud
        Status:     Informational
        Date:       May 2005
        Mailbox:    carl@media.org
        Pages:      14
        Characters: 31618
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-draft-malamud-subject-line-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4096.txt


This memo discusses policies that require certain labels to be
inserted in the "Subject:" header of a mail message.  Such policies
are difficult to specify accurately while remaining compliant with
key RFCs and are likely to be ineffective at best.  This memo
discusses an alternate, standards-compliant approach that is
significantly simpler to specify and is somewhat less likely to be
ineffective.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc4096.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux