Skip to main content

Attaching Meaning to Solicitation Class Keywords
RFC 4095

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document proposes a mechanism for finding a URI associated with a solicitation class keyword, which …
Received changes through RFC Editor sync (changed abstract to 'This document proposes a mechanism for finding a URI associated with a solicitation class keyword, which is defined in RFC 3865, the No Soliciting SMTP Service Extension. Solicitation class keywords are simple labels consisting of a domain name that has been reversed, such as "org.example.adv". These solicitation class keywords are inserted in selected header fields or used in the ESMTP service extension, including a new \%"No-Solicit:" header, which can contain one or more solicitation class keywords inserted by the sender.

This document specifies an application based on the Dynamic Delegation Discovery System (DDDS) described in RFC 3401 and related documents. An algorithm is specified to associate a solicitation class keyword with a URI which contains further information about the meaning and usage of that solicitation class keyword. For example, the registrant of the "example.org" domain could use this mechanism to create a URI which contains detailed information about the "org.example.adv" solicitation class keyword. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from carl@media.org to (None)
2005-05-31
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2005-05-31
Amy Vezza [Note]: 'RFC 4095' added by Amy Vezza
2005-05-27
(System) RFC published