Attaching Meaning to Solicitation Class Keywords

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 11
Abstract: 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]
Publication Date: 2005-05-01
Status Note: Proposed Standard
DOI: 10.17487/RFC4095
Link: https://doi.org/10.17487/RFC4095
Author(s): Carl Malamud
Keyword(s): URI, Uniform Resource Identifier, No Soliciting, ESMTP, DDDS

Latest version of IETF RFC 4095

Document Versions — IETF RFC 4095

▶ IETF RFC 4095 (2005-05-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 2660 [Active*]
IETF RFC 3402 [Active*]
IETF RFC 3403 [Active*]
IETF RFC 3865 [Active*]
IETF RFC 3958 [Active*]
IETF RFC 3986 [Active, Amended*]
W3C.html401.19991224 — [HTML-4.01] REC-html401-19991224, W3C Recommendation: HTML 4.01 Specification (December 24 th , 1999). EXTERNAL

Bibliographic Reference(s)

IETF RFC 2795 [Active*]
IETF RFC 2821 [Superseded*]
IETF RFC 3401 [Active*]
IETF RFC 3490 [Superseded*]
IETF RFC 3761 [Superseded*]
IETF RFC 4033 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC4095.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 4095, Attaching Meaning to Solicitation Class Keywords. Available at https://doi.org/10.17487/RFC4095

Snippet:

IETF RFC 4095, Attaching Meaning to Solicitation Class Keywords. Available at https://doi.org/10.17487/RFC4095

HTML (ISO 690 compliant)

Preview:

IETF RFC 4095, Attaching Meaning to Solicitation Class Keywords. Available at https://doi.org/10.17487/RFC4095

Snippet:

<span class="citation"><cite>IETF RFC 4095</cite>, Attaching Meaning to Solicitation Class Keywords. Available at <a href="https://doi.org/10.17487/RFC4095" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4095</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 4095, Attaching Meaning to Solicitation Class Keywords
doi: 10.17487/RFC4095
url: https://doi.org/10.17487/RFC4095

Snippet:

<li>
<cite id="bib-rfc4095">IETF RFC 4095</cite>, Attaching Meaning to Solicitation Class Keywords
<span class="doi">10.17487/RFC4095</span>
</li>

Referenced By

IETF RFC 4848 [Active*]