RFC 4095 on Attaching Meaning to Solicitation Class Keywords
firstname.lastname@example.org Fri, 27 May 2005 17:38 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dbin5-0004b0-OP; Fri, 27 May 2005 13:38:35 -0400
Received: from odin.ietf.org ([184.108.40.206] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dbin3-0004aT-Ab for email@example.com; Fri, 27 May 2005 13:38:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [220.127.116.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01783 for <firstname.lastname@example.org>; Fri, 27 May 2005 13:38:30 -0400 (EDT)
Received: from boreas.isi.edu ([18.104.22.168]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dbj5t-0000zq-DC for email@example.com; Fri, 27 May 2005 13:58:01 -0400
Received: from ISI.EDU (adma.isi.edu [22.214.171.124]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j4RHagL17254; Fri, 27 May 2005 10:36:42 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 27 May 2005 10:36:42 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-Spam-Score: -14.6 (--------------)
Subject: RFC 4095 on Attaching Meaning to Solicitation Class Keywords
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:email@example.com?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 4095 Title: Attaching Meaning to Solicitation Class Keywords Author(s): C. Malamud Status: Standards Track Date: May 2005 Mailbox: firstname.lastname@example.org Pages: 11 Characters: 23539 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-malamud-keyword-discovery-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4095.txt 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. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. 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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce