idnits 2.17.00 (12 Aug 2021) /tmp/idnits44449/draft-klyne-hdrreg-mail-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2444. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2428. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2434. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 2450), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 37. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 7, 2004) is 6581 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '4' is defined on line 2172, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 2180, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 2190, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 2215, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2225, but no explicit reference was found in the text == Outdated reference: draft-klyne-msghdr-registry has been published as RFC 3864 ** Obsolete normative reference: RFC 822 (ref. '2') (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 1327 (ref. '3') (Obsoleted by RFC 2156) ** Downref: Normative reference to an Historic RFC: RFC 1496 (ref. '4') ** Downref: Normative reference to an Experimental RFC: RFC 1505 (ref. '5') ** Obsolete normative reference: RFC 1766 (ref. '6') (Obsoleted by RFC 3066, RFC 3282) ** Obsolete normative reference: RFC 2110 (ref. '10') (Obsoleted by RFC 2557) ** Obsolete normative reference: RFC 2298 (ref. '14') (Obsoleted by RFC 3798) ** Obsolete normative reference: RFC 2421 (ref. '16') (Obsoleted by RFC 3801) ** Obsolete normative reference: RFC 2424 (ref. '17') (Obsoleted by RFC 3803) ** Obsolete normative reference: RFC 2821 (ref. '19') (Obsoleted by RFC 5321) ** Obsolete normative reference: RFC 2822 (ref. '20') (Obsoleted by RFC 5322) -- Possible downref: Non-RFC (?) normative reference: ref. '26' Summary: 18 errors (**), 0 flaws (~~), 9 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Klyne 3 Internet-Draft Nine by Nine 4 Expires: November 5, 2004 J. Palme 5 Stockholm University/KTH 6 May 7, 2004 8 Registration of mail and MIME header fields 9 draft-klyne-hdrreg-mail-05 11 Status of this Memo 13 By submitting this Internet-Draft, I certify that any applicable 14 patent or other IPR claims of which I am aware have been disclosed, 15 and any of which I become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that other 20 groups may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at http:// 28 www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on November 5, 2004. 35 Copyright Notice 37 Copyright (C) The Internet Society (2004). All Rights Reserved. 39 Abstract 41 This document defines the initial IANA registration for permanent 42 mail and MIME message header fields, per [[[RFC XXXX (xref 43 target="msghdr-registry" /)]]]. 45 Discussion of this document 47 Please send comments to . To subscribe to this 48 list, send a message with the body 'subscribe' to 49 . 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 54 1.1 Structure of this document . . . . . . . . . . . . . . . . 5 55 1.2 Document terminology and conventions . . . . . . . . . . . 5 56 2. Registration templates . . . . . . . . . . . . . . . . . . . 5 57 2.1 Permanent mail header field registrations . . . . . . . . 5 58 2.1.1 Header field: Date . . . . . . . . . . . . . . . . . . 7 59 2.1.2 Header field: From . . . . . . . . . . . . . . . . . . 8 60 2.1.3 Header field: Sender . . . . . . . . . . . . . . . . . 8 61 2.1.4 Header field: Reply-To . . . . . . . . . . . . . . . . 9 62 2.1.5 Header field: To . . . . . . . . . . . . . . . . . . . 9 63 2.1.6 Header field: Cc . . . . . . . . . . . . . . . . . . . 10 64 2.1.7 Header field: Bcc . . . . . . . . . . . . . . . . . . 10 65 2.1.8 Header field: Message-ID . . . . . . . . . . . . . . . 11 66 2.1.9 Header field: In-Reply-To . . . . . . . . . . . . . . 11 67 2.1.10 Header field: References . . . . . . . . . . . . . . 12 68 2.1.11 Header field: Subject . . . . . . . . . . . . . . . 12 69 2.1.12 Header field: Comments . . . . . . . . . . . . . . . 13 70 2.1.13 Header field: Keywords . . . . . . . . . . . . . . . 13 71 2.1.14 Header field: Resent-Date . . . . . . . . . . . . . 13 72 2.1.15 Header field: Resent-From . . . . . . . . . . . . . 14 73 2.1.16 Header field: Resent-Sender . . . . . . . . . . . . 14 74 2.1.17 Header field: Resent-To . . . . . . . . . . . . . . 15 75 2.1.18 Header field: Resent-Cc . . . . . . . . . . . . . . 15 76 2.1.19 Header field: Resent-Bcc . . . . . . . . . . . . . . 16 77 2.1.20 Header field: Resent-Reply-To . . . . . . . . . . . 16 78 2.1.21 Header field: Resent-Message-ID . . . . . . . . . . 17 79 2.1.22 Header field: Return-Path . . . . . . . . . . . . . 17 80 2.1.23 Header field: Received . . . . . . . . . . . . . . . 18 81 2.1.24 Header field: Encrypted . . . . . . . . . . . . . . 18 82 2.1.25 Header field: Disposition-Notification-To . . . . . 18 83 2.1.26 Header field: Disposition-Notification-Options . . . 19 84 2.1.27 Header field: Accept-Language . . . . . . . . . . . 19 85 2.1.28 Header field: Original-Message-ID . . . . . . . . . 20 86 2.1.29 Header field: PICS-Label . . . . . . . . . . . . . . 20 87 2.1.30 Header field: Encoding . . . . . . . . . . . . . . . 21 88 2.1.31 Header field: List-Archive . . . . . . . . . . . . . 21 89 2.1.32 Header field: List-Help . . . . . . . . . . . . . . 22 90 2.1.33 Header field: List-ID . . . . . . . . . . . . . . . 22 91 2.1.34 Header field: List-Owner . . . . . . . . . . . . . . 23 92 2.1.35 Header field: List-Post . . . . . . . . . . . . . . 23 93 2.1.36 Header field: List-Subscribe . . . . . . . . . . . . 24 94 2.1.37 Header field: List-Unsubscribe . . . . . . . . . . . 24 95 2.1.38 Header field: Message-Context . . . . . . . . . . . 25 96 2.1.39 Header field: DL-Expansion-History . . . . . . . . . 25 97 2.1.40 Header field: Alternate-Recipient . . . . . . . . . 25 98 2.1.41 Header field: Original-Encoded-Information-Types . . 26 99 2.1.42 Header field: Content-Return . . . . . . . . . . . . 26 100 2.1.43 Header field: Generate-Delivery-Report . . . . . . . 27 101 2.1.44 Header field: Prevent-NonDelivery-Report . . . . . . 27 102 2.1.45 Header field: Obsoletes . . . . . . . . . . . . . . 28 103 2.1.46 Header field: Supersedes . . . . . . . . . . . . . . 28 104 2.1.47 Header field: Content-Identifier . . . . . . . . . . 29 105 2.1.48 Header field: Delivery-Date . . . . . . . . . . . . 29 106 2.1.49 Header field: Expiry-Date . . . . . . . . . . . . . 30 107 2.1.50 Header field: Expires . . . . . . . . . . . . . . . 30 108 2.1.51 Header field: Reply-By . . . . . . . . . . . . . . . 31 109 2.1.52 Header field: Importance . . . . . . . . . . . . . . 31 110 2.1.53 Header field: Incomplete-Copy . . . . . . . . . . . 32 111 2.1.54 Header field: Priority . . . . . . . . . . . . . . . 32 112 2.1.55 Header field: Sensitivity . . . . . . . . . . . . . 32 113 2.1.56 Header field: Language . . . . . . . . . . . . . . . 33 114 2.1.57 Header field: Conversion . . . . . . . . . . . . . . 33 115 2.1.58 Header field: Conversion-With-Loss . . . . . . . . . 34 116 2.1.59 Header field: Message-Type . . . . . . . . . . . . . 34 117 2.1.60 Header field: Autosubmitted . . . . . . . . . . . . 35 118 2.1.61 Header field: Autoforwarded . . . . . . . . . . . . 35 119 2.1.62 Header field: Discarded-X400-IPMS-Extensions . . . . 36 120 2.1.63 Header field: Discarded-X400-MTS-Extensions . . . . 36 121 2.1.64 Header field: Disclose-Recipients . . . . . . . . . 37 122 2.1.65 Header field: Deferred-Delivery . . . . . . . . . . 37 123 2.1.66 Header field: Latest-Delivery-Time . . . . . . . . . 38 124 2.1.67 Header field: Originator-Return-Address . . . . . . 38 125 2.1.68 Header field: X400-Content-Identifier . . . . . . . 39 126 2.1.69 Header field: X400-Content-Return . . . . . . . . . 39 127 2.1.70 Header field: X400-Content-Type . . . . . . . . . . 39 128 2.1.71 Header field: X400-MTS-Identifier . . . . . . . . . 40 129 2.1.72 Header field: X400-Originator . . . . . . . . . . . 40 130 2.1.73 Header field: X400-Received . . . . . . . . . . . . 41 131 2.1.74 Header field: X400-Recipients . . . . . . . . . . . 41 132 2.1.75 Header field: X400-Trace . . . . . . . . . . . . . . 42 133 2.2 Permanent MIME header field registrations . . . . . . . . 43 134 2.2.1 Header field: MIME-Version . . . . . . . . . . . . . . 43 135 2.2.2 Header field: Content-ID . . . . . . . . . . . . . . . 44 136 2.2.3 Header field: Content-Description . . . . . . . . . . 44 137 2.2.4 Header field: Content-Transfer-Encoding . . . . . . . 44 138 2.2.5 Header field: Content-Type . . . . . . . . . . . . . . 45 139 2.2.6 Header field: Content-Base . . . . . . . . . . . . . . 45 140 2.2.7 Header field: Content-Location . . . . . . . . . . . . 46 141 2.2.8 Header field: Content-features . . . . . . . . . . . . 46 142 2.2.9 Header field: Content-Disposition . . . . . . . . . . 47 143 2.2.10 Header field: Content-Language . . . . . . . . . . . 47 144 2.2.11 Header field: Content-Alternative . . . . . . . . . 48 145 2.2.12 Header field: Content-MD5 . . . . . . . . . . . . . 48 146 2.2.13 Header field: Content-Duration . . . . . . . . . . . 49 148 3. IANA considerations . . . . . . . . . . . . . . . . . . . . 49 149 4. Security considerations . . . . . . . . . . . . . . . . . . 49 150 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 49 151 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 50 152 6.1 Normative references . . . . . . . . . . . . . . . . . . . . 50 153 6.2 Informative references . . . . . . . . . . . . . . . . . . . 52 154 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 52 155 A. Revision history . . . . . . . . . . . . . . . . . . . . . . 52 156 A.1 draft-klyne-hdrreg-mail-05 . . . . . . . . . . . . . . . . 52 157 A.2 draft-klyne-hdrreg-mail-04 . . . . . . . . . . . . . . . . 53 158 A.3 draft-klyne-hdrreg-mail-03 . . . . . . . . . . . . . . . . 53 159 A.4 draft-klyne-hdrreg-mail-02 . . . . . . . . . . . . . . . . 54 160 A.5 draft-klyne-hdrreg-mail-01 . . . . . . . . . . . . . . . . 54 161 A.6 draft-klyne-hdrreg-mail-00 . . . . . . . . . . . . . . . . 55 162 B. TODO: . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 163 Intellectual Property and Copyright Statements . . . . . . . 56 165 1. Introduction 167 This document defines IANA registration for a number of mail message 168 and MIME header fields, per Registration procedures for message 169 header fields [1]. 171 The main body of this document is automatically generated from RDF/N3 172 data. Some experimental HTML registry pages have been prepared from 173 the same data, and can be found at [29]. 175 1.1 Structure of this document 177 Section Section 2.1 contains the templates for initial registration 178 of mail message header fields. 180 Section Section 2.2 contains templates for initial registration of 181 MIME header fields. 183 1.2 Document terminology and conventions 185 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 186 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 187 document are to be interpreted as described in RFC 2119 [11]. 189 [[[Editorial comments and questions about outstanding issues are 190 provided in triple brackets like this. These working comments should 191 be resolved and removed prior to final publication.]]] 193 2. Registration templates 195 Header field registry entries are summarized in tabular form for 196 convenience of reference, and presented in full in the following 197 sections. 199 2.1 Permanent mail header field registrations 201 Header name Protocol 202 ----------- -------- 203 Date Mail Message date and time 204 From Mail Mailbox of message author 205 Sender Mail Mailbox of message sender 206 Reply-To Mail Mailbox for replies to message 207 To Mail Primary recipient mailbox 208 Cc Mail Carbon-copy recipient mailbox 209 Bcc Mail Blind-carbon-copy recipient 210 mailbox 211 Message-ID Mail Message identifier 212 In-Reply-To Mail Identify replied-to message(s) 213 References Mail Related message identifier(s) 214 Subject Mail Topic of message 215 Comments Mail Additional comments about the 216 message 217 Keywords Mail Message key words and/or phrases 218 Resent-Date Mail Date and time message is resent 219 Resent-From Mail Mailbox of person for whom message 220 is resent 221 Resent-Sender Mail Mailbox of person who actually 222 resends the message 223 Resent-To Mail Mailbox to which message is resent 224 Resent-Cc Mail Mailbox(es) to which message is 225 cc'ed on resend 226 Resent-Bcc Mail Mailbox(es) to which message is 227 bcc'ed on resend 228 Resent-Reply-To Mail Resent reply-to 229 Resent-Message-ID Mail Message identifier for resent 230 message 231 Return-Path Mail Message return path 232 Received Mail Mail transfer trace information 233 Encrypted Mail Message encryption information 234 Disposition-Notification-To 235 Mail Mailbox for sending disposition 236 notification 237 Disposition-Notification-Options 238 Mail Disposition notification options 239 Accept-Language Mail Language(s) for auto-responses 240 Original-Message-ID Mail Original message identifier 241 PICS-Label Mail PICS rating label 242 Encoding Mail Message encoding and other 243 information 244 List-Archive Mail URL of mailing list archive 245 List-Help Mail URL for mailing list information 246 List-ID Mail Mailing list identifier 247 List-Owner Mail URL for mailing list owner's 248 mailbox 249 List-Post Mail URL for mailing list posting 250 List-Subscribe Mail URL for mailing list subscription 251 List-Unsubscribe Mail URL for mailing list 252 unsubscription 253 Message-Context Mail Type or context of message 254 DL-Expansion-History 255 Mail Trace of distribution lists passed 256 Alternate-Recipient Mail Controls forwarding to alternate 257 recipients 258 Original-Encoded-Information-Types 259 Mail Body part types in message 261 Content-Return Mail Return content on non-delivery? 262 Generate-Delivery-Report 263 Mail Request delivery report generation 264 Prevent-NonDelivery-Report 265 Mail Non-delivery report required? 266 Obsoletes Mail Reference message to be replaced 267 Supersedes Mail Reference message to be replaced 268 Content-Identifier Mail Message content identifier 269 Delivery-Date Mail Message delivery time 270 Expiry-Date Mail Message expiry time 271 Expires Mail Message expiry time 272 Reply-By Mail Time by which a reply is requested 273 Importance Mail Message importance 274 Incomplete-Copy Mail Body parts are missing. 275 Priority Mail Message priority 276 Sensitivity Mail Message content sensitivity 277 Language Mail X.400 message content lenguage 278 Conversion Mail Conversion allowed? 279 Conversion-With-Loss 280 Mail Lossy conversion allowed? 281 Message-Type Mail Message type: delivery report? 282 Autosubmitted Mail Automatically submitted indicator 283 Autoforwarded Mail Automatically forwarded indicator 284 Discarded-X400-IPMS-Extensions 285 Mail X.400 IPM extensions discarded 286 Discarded-X400-MTS-Extensions 287 Mail X.400 MTS extensions discarded 288 Disclose-Recipients Mail Disclose names of other 289 recipients? 290 Deferred-Delivery Mail Deferred delivery information 291 Latest-Delivery-Time 292 Mail Latest delivery time requested 293 Originator-Return-Address 294 Mail Originator return address 295 X400-Content-Identifier 296 Mail Message content identifier 297 X400-Content-Return Mail Return content on non-delivery? 298 X400-Content-Type Mail X400 content type 299 X400-MTS-Identifier Mail X400 MTS-Identifier 300 X400-Originator Mail X400 Originator 301 X400-Received Mail X400 Received 302 X400-Recipients Mail X400 Recipients 303 X400-Trace Mail X400 Trace 305 2.1.1 Header field: Date 306 Description: 307 Message date and time 309 Applicable protocol: Mail [20] 311 Status: standard 313 Author/change controller: 314 IETF (mailto:iesg@ietf.org) 315 Internet Engineering Task Force 317 Specification document(s): 318 RFC 2822 [20] (section 3.6.1) 320 Related information: 321 Specifies the date and time at which the creator of the message 322 indicated that the message was complete and ready to enter the 323 mail delivery system. Defined as standard by RFC 822. 325 2.1.2 Header field: From 327 Description: 328 Mailbox of message author 330 Applicable protocol: Mail [20] 332 Status: standard 334 Author/change controller: 335 IETF (mailto:iesg@ietf.org) 336 Internet Engineering Task Force 338 Specification document(s): 339 RFC 2822 [20] (section 3.6.2) 341 Related information: 342 Specifies the author(s) of the message, that is, the mailbox(es) 343 of the person(s) or system(s) responsible for the writing of the 344 message. Defined as standard by RFC 822. 346 2.1.3 Header field: Sender 348 Description: 349 Mailbox of message sender 351 Applicable protocol: Mail [20] 353 Status: standard 355 Author/change controller: 356 IETF (mailto:iesg@ietf.org) 357 Internet Engineering Task Force 359 Specification document(s): 360 RFC 2822 [20] (section 3.6.2) 362 Related information: 363 Specifies the mailbox of the agent responsible for the actual 364 transmission of the message. Defined as standard by RFC 822. 366 2.1.4 Header field: Reply-To 368 Description: 369 Mailbox for replies to message 371 Applicable protocol: Mail [20] 373 Status: standard 375 Author/change controller: 376 IETF (mailto:iesg@ietf.org) 377 Internet Engineering Task Force 379 Specification document(s): 380 RFC 2822 [20] (section 3.6.2) 382 Related information: 383 When the "Reply-To:" field is present, it indicates the 384 mailbox(es) to which the author of the message suggests that 385 replies be sent. Defined as standard by RFC 822. 387 2.1.5 Header field: To 389 Description: 390 Primary recipient mailbox 392 Applicable protocol: Mail [20] 394 Status: standard 395 Author/change controller: 396 IETF (mailto:iesg@ietf.org) 397 Internet Engineering Task Force 399 Specification document(s): 400 RFC 2822 [20] (section 3.6.3) 402 Related information: 403 Contains the address(es) of the primary recipient(s) of the 404 message. Defined as standard by RFC 822. 406 2.1.6 Header field: Cc 408 Description: 409 Carbon-copy recipient mailbox 411 Applicable protocol: Mail [20] 413 Status: standard 415 Author/change controller: 416 IETF (mailto:iesg@ietf.org) 417 Internet Engineering Task Force 419 Specification document(s): 420 RFC 2822 [20] (section 3.6.3) 422 Related information: 423 Contains the addresses of others who are to receive the message, 424 though the content of the message may not be directed at them. 425 Defined as standard by RFC 822. 427 2.1.7 Header field: Bcc 429 Description: 430 Blind-carbon-copy recipient mailbox 432 Applicable protocol: Mail [20] 434 Status: standard 436 Author/change controller: 437 IETF (mailto:iesg@ietf.org) 438 Internet Engineering Task Force 440 Specification document(s): 441 RFC 2822 [20] (section 3.6.3) 443 Related information: 444 Contains addresses of recipients of the message whose addresses 445 are not to be revealed to other recipients of the message. Defined 446 as standard by RFC 822. 448 2.1.8 Header field: Message-ID 450 Description: 451 Message identifier 453 Applicable protocol: Mail [20] 455 Status: standard 457 Author/change controller: 458 IETF (mailto:iesg@ietf.org) 459 Internet Engineering Task Force 461 Specification document(s): 462 RFC 2822 [20] (section 3.6.4) 464 Related information: 465 Contains a single unique message identifier that refers to a 466 particular version of a particular message. If the message is 467 resent without changes, the original Message-ID is retained. 468 Defined as standard by RFC 822. 470 2.1.9 Header field: In-Reply-To 472 Description: 473 Identify replied-to message(s) 475 Applicable protocol: Mail [20] 477 Status: standard 479 Author/change controller: 480 IETF (mailto:iesg@ietf.org) 481 Internet Engineering Task Force 483 Specification document(s): 484 RFC 2822 [20] (section 3.6.4) 486 Related information: 487 The message identifier(s) of the original message(s) to which the 488 current message is a reply. Defined as standard by RFC 822. 490 2.1.10 Header field: References 492 Description: 493 Related message identifier(s) 495 Applicable protocol: Mail [20] 497 Status: standard 499 Author/change controller: 500 IETF (mailto:iesg@ietf.org) 501 Internet Engineering Task Force 503 Specification document(s): 504 RFC 2822 [20] (section 3.6.4) 506 Related information: 507 The message identifier(s) of other message(s) to which the current 508 message may be related. In RFC2822, the definition was changed to 509 say that this header field contains a list of all Message-IDs of 510 messages in the preceding reply chain. Defined as standard by RFC 511 822. 513 2.1.11 Header field: Subject 515 Description: 516 Topic of message 518 Applicable protocol: Mail [20] 520 Status: standard 522 Author/change controller: 523 IETF (mailto:iesg@ietf.org) 524 Internet Engineering Task Force 526 Specification document(s): 527 RFC 2822 [20] (section 3.6.5) 529 Related information: 530 Contains a short string identifying the topic of the message. 531 Defined as standard by RFC 822. 533 2.1.12 Header field: Comments 535 Description: 536 Additional comments about the message 538 Applicable protocol: Mail [20] 540 Status: standard 542 Author/change controller: 543 IETF (mailto:iesg@ietf.org) 544 Internet Engineering Task Force 546 Specification document(s): 547 RFC 2822 [20] (section 3.6.5) 549 Related information: 550 Contains any additional comments on the text of the body of the 551 message. Warning: Some mailers will not show this field to 552 recipients. Defined as standard by RFC 822. 554 2.1.13 Header field: Keywords 556 Description: 557 Message key words and/or phrases 559 Applicable protocol: Mail [20] 561 Status: standards 563 Author/change controller: 564 IETF (mailto:iesg@ietf.org) 565 Internet Engineering Task Force 567 Specification document(s): 568 RFC 2822 [20] (section 3.6.5) 570 Related information: 571 Contains a comma-separated list of important words and phrases 572 that might be useful for the recipient. Defined as standard by RFC 573 822. 575 2.1.14 Header field: Resent-Date 576 Description: 577 Date and time message is resent 579 Applicable protocol: Mail [20] 581 Status: standard 583 Author/change controller: 584 IETF (mailto:iesg@ietf.org) 585 Internet Engineering Task Force 587 Specification document(s): 588 RFC 2822 [20] (section 3.6.6) 590 Related information: 591 Contains the date and time that a message is reintroduced into the 592 message transfer system. Defined as standard by RFC 822. 594 2.1.15 Header field: Resent-From 596 Description: 597 Mailbox of person for whom message is resent 599 Applicable protocol: Mail [20] 601 Status: standard 603 Author/change controller: 604 IETF (mailto:iesg@ietf.org) 605 Internet Engineering Task Force 607 Specification document(s): 608 RFC 2822 [20] (section 3.6.6) 610 Related information: 611 Contains the mailbox of the agent who has reintroduced the message 612 into the message transfer system, or on whose behanlf the message 613 has been resent. Defined as standard by RFC 822. 615 2.1.16 Header field: Resent-Sender 617 Description: 618 Mailbox of person who actually resends the message 620 Applicable protocol: Mail [20] 622 Status: standard 624 Author/change controller: 625 IETF (mailto:iesg@ietf.org) 626 Internet Engineering Task Force 628 Specification document(s): 629 RFC 2822 [20] (section 3.6.6) 631 Related information: 632 Contains the mailbox of the agent who has reintroduced the message 633 into the message transfer system, if this is different from the 634 Resent-From value. Defined as standard by RFC 822. 636 2.1.17 Header field: Resent-To 638 Description: 639 Mailbox to which message is resent 641 Applicable protocol: Mail [20] 643 Status: standards 645 Author/change controller: 646 IETF (mailto:iesg@ietf.org) 647 Internet Engineering Task Force 649 Specification document(s): 650 RFC 2822 [20] (section 3.6.6) 652 Related information: 653 Contains the mailbox(es) to which the message has been resent. 654 Defined as standard by RFC 822. 656 2.1.18 Header field: Resent-Cc 658 Description: 659 Mailbox(es) to which message is cc'ed on resend 661 Applicable protocol: Mail [20] 663 Status: standard 664 Author/change controller: 665 IETF (mailto:iesg@ietf.org) 666 Internet Engineering Task Force 668 Specification document(s): 669 RFC 2822 [20] (section 3.6.6) 671 Related information: 672 Containes the mailbox(es) to which message is cc'ed on resend. 673 Defined as standard by RFC 822. 675 2.1.19 Header field: Resent-Bcc 677 Description: 678 Mailbox(es) to which message is bcc'ed on resend 680 Applicable protocol: Mail [20] 682 Status: standard 684 Author/change controller: 685 IETF (mailto:iesg@ietf.org) 686 Internet Engineering Task Force 688 Specification document(s): 689 RFC 2822 [20] (section 3.6.6) 691 Related information: 692 Containes the mailbox(es) to which message is bcc'ed on resend. 693 Defined as standard by RFC 822. 695 2.1.20 Header field: Resent-Reply-To 697 Description: 698 Resent reply-to 700 Applicable protocol: Mail [20] 702 Status: obsolete 704 Author/change controller: 705 IETF (mailto:iesg@ietf.org) 706 Internet Engineering Task Force 708 Specification document(s): 709 RFC 2822 [20] 711 Related information: 712 Resent Reply-to. Defined by RFC 822, obsoleteed by RFC2822. 714 2.1.21 Header field: Resent-Message-ID 716 Description: 717 Message identifier for resent message 719 Applicable protocol: Mail [20] 721 Status: standard 723 Author/change controller: 724 IETF (mailto:iesg@ietf.org) 725 Internet Engineering Task Force 727 Specification document(s): 728 RFC 2822 [20] (section 3.6.6) 730 Related information: 731 Contains a message identifier for a resent message. Defined as 732 standard by RFC 822. 734 2.1.22 Header field: Return-Path 736 Description: 737 Message return path 739 Applicable protocol: Mail [20] 741 Status: standard 743 Author/change controller: 744 IETF (mailto:iesg@ietf.org) 745 Internet Engineering Task Force 747 Specification document(s): 748 RFC 2822 [20] (section 3.6.7) 750 Related information: 751 Return path for message response diagnostics. See also, RFC 2821. 752 Defined as standard by RFC 822. 754 2.1.23 Header field: Received 756 Description: 757 Mail transfer trace information 759 Applicable protocol: Mail [20] 761 Status: standard 763 Author/change controller: 764 IETF (mailto:iesg@ietf.org) 765 Internet Engineering Task Force 767 Specification document(s): 768 RFC 2822 [20] (section 3.6.7) 770 Related information: 771 Contains information about receipt of the current message by a 772 mail transfer agent on the transfer path. See also, RFC 2821. 773 Defined as standard by RFC 822. 775 2.1.24 Header field: Encrypted 777 Description: 778 Message encryption information 780 Applicable protocol: Mail [20] 782 Status: obsolete 784 Author/change controller: 785 IETF (mailto:iesg@ietf.org) 786 Internet Engineering Task Force 788 Specification document(s): 789 RFC 822 [2] 791 Related information: 792 Defined by RFC 822, but was found to be inadequately specified, 793 not widely implemented, and removed in RFC 2822. Current practice 794 is to use separate encryption, such as S/MIME or OpenPGP, possibly 795 in conjunction with RFC 1847 MIME security multiparts. 797 2.1.25 Header field: Disposition-Notification-To 798 Description: 799 Mailbox for sending disposition notification 801 Applicable protocol: Mail [20] 803 Status: standards-track 805 Author/change controller: 806 IETF (mailto:iesg@ietf.org) 807 Internet Engineering Task Force 809 Specification document(s): 810 RFC 2298 [14] 812 Related information: 813 Indicates that the sender wants a disposition notification when 814 this message is received (read, processed, etc.) by its 815 recipients. 817 2.1.26 Header field: Disposition-Notification-Options 819 Description: 820 Disposition notification options 822 Applicable protocol: Mail [20] 824 Status: standards-track 826 Author/change controller: 827 IETF (mailto:iesg@ietf.org) 828 Internet Engineering Task Force 830 Specification document(s): 831 RFC 2298 [14] 833 Related information: 834 For optional modifiers on disposition notification requests. 836 2.1.27 Header field: Accept-Language 838 Description: 839 Language(s) for auto-responses 841 Applicable protocol: Mail [20] 842 Status: standards-track 844 Author/change controller: 845 IETF (mailto:iesg@ietf.org) 846 Internet Engineering Task Force 848 Specification document(s): 849 RFC 3282 [23] 851 Related information: 852 Indicates a language that the message sender requests be used for 853 responses. Accept-language was not designed for email, but has 854 been considered to be useful as input to the generation of 855 automatic replies. Some problems have been noted concerning its 856 use with email, including but not limited to: determination of the 857 email address to which it refers; cost and lack of effective 858 internationalization of email responses; interpretation of 859 language subtags; determining what character set encoding should 860 be used. 862 2.1.28 Header field: Original-Message-ID 864 Description: 865 Original message identifier 867 Applicable protocol: Mail [20] 869 Status: standards-track 871 Author/change controller: 872 IETF (mailto:iesg@ietf.org) 873 Internet Engineering Task Force 875 Specification document(s): 876 RFC 3297 [24] 878 Related information: 879 Original message identifier used with resend of message with 880 alternative content format, identifies the original message data 881 to which it corresponds. 883 2.1.29 Header field: PICS-Label 884 Description: 885 PICS rating label 887 Applicable protocol: Mail [20] 889 Status: standard 891 Author/change controller: 892 W3C (mailto:web-human@w3.org) 893 World Wide Web Consortium 895 Specification document(s): 896 PICS-labels [26] 898 Related information: 899 Ratings label to control selection (filtering) of messages 900 according to the PICS protocol. Specified for general use with 901 RFC822 message format, with HTTP-specific extensions 903 2.1.30 Header field: Encoding 905 Description: 906 Message encoding and other information 908 Applicable protocol: Mail [20] 910 Status: experimental 912 Author/change controller: 913 Albert K. Costanzo (mailto:AL@AKC.COM) 914 AKC Consulting Inc. 916 Specification document(s): 917 RFC 1505 [5] 919 Related information: 920 Used in several different ways by different mail systems. Some use 921 it for a kind of content-type information, some for encoding and 922 length information, some for a kind of boundary information, some 923 in other ways. 925 2.1.31 Header field: List-Archive 926 Description: 927 URL of mailing list archive 929 Applicable protocol: Mail [20] 931 Status: standards-track 933 Author/change controller: 934 IETF (mailto:iesg@ietf.org) 935 Internet Engineering Task Force 937 Specification document(s): 938 RFC 2369 [15] 940 Related information: 941 Contains URL to use to browse the archives of the mailing list 942 from which this message was relayed. 944 2.1.32 Header field: List-Help 946 Description: 947 URL for mailing list information 949 Applicable protocol: Mail [20] 951 Status: standards-track 953 Author/change controller: 954 IETF (mailto:iesg@ietf.org) 955 Internet Engineering Task Force 957 Specification document(s): 958 RFC 2369 [15] 960 Related information: 961 Contains URL to use to get a information about the mailing list 962 from which this message was relayed. 964 2.1.33 Header field: List-ID 966 Description: 967 Mailing list identifier 969 Applicable protocol: Mail [20] 970 Status: standards-track 972 Author/change controller: 973 IETF (mailto:iesg@ietf.org) 974 Internet Engineering Task Force 976 Specification document(s): 977 RFC 2919 [22] 979 Related information: 980 Stores an identification of the mailing list, through which this 981 message was distributed. 983 2.1.34 Header field: List-Owner 985 Description: 986 URL for mailing list owner's mailbox 988 Applicable protocol: Mail [20] 990 Status: standards-track 992 Author/change controller: 993 IETF (mailto:iesg@ietf.org) 994 Internet Engineering Task Force 996 Specification document(s): 997 RFC 2369 [15] 999 Related information: 1000 Contains URL to send e-mail to the owner of the mailing list from 1001 which this message was relayed. 1003 2.1.35 Header field: List-Post 1005 Description: 1006 URL for mailing list posting 1008 Applicable protocol: Mail [20] 1010 Status: standards-track 1012 Author/change controller: 1013 IETF (mailto:iesg@ietf.org) 1014 Internet Engineering Task Force 1016 Specification document(s): 1017 RFC 2369 [15] 1019 Related information: 1020 Contains URL to use to send contributions to the mailing list from 1021 which this message was relayed. 1023 2.1.36 Header field: List-Subscribe 1025 Description: 1026 URL for mailing list subscription 1028 Applicable protocol: Mail [20] 1030 Status: standards-track 1032 Author/change controller: 1033 IETF (mailto:iesg@ietf.org) 1034 Internet Engineering Task Force 1036 Specification document(s): 1037 RFC 2369 [15] 1039 Related information: 1040 Contains URL to use to get a subscription to the mailing list from 1041 which this message was relayed. 1043 2.1.37 Header field: List-Unsubscribe 1045 Description: 1046 URL for mailing list unsubscription 1048 Applicable protocol: Mail [20] 1050 Status: standards-track 1052 Author/change controller: 1053 IETF (mailto:iesg@ietf.org) 1054 Internet Engineering Task Force 1056 Specification document(s): 1057 RFC 2369 [15] 1059 Related information: 1060 Contains URL to use to unsubscribe the mailing list from which 1061 this message was relayed. 1063 2.1.38 Header field: Message-Context 1065 Description: 1066 Type or context of message 1068 Applicable protocol: Mail [20] 1070 Status: Standards track 1072 Author/change controller: 1073 IETF (mailto:iesg@ietf.org) 1074 Internet Engineering Task Force 1076 Specification document(s): 1077 RFC3458 [25] 1079 Related information: 1080 Provides information about the context and presentation 1081 characteristics of a message. Can have the values 1082 'voice-message', 'fax-message', 'pager-message', 1083 'multimedia-message', 'text-message', 'none'. 1085 2.1.39 Header field: DL-Expansion-History 1087 Description: 1088 Trace of distribution lists passed 1090 Applicable protocol: Mail [20] 1092 Status: standards-track 1094 Author/change controller: 1095 IETF (mailto:iesg@ietf.org) 1096 Internet Engineering Task Force 1098 Specification document(s): 1099 RFC 2156 [12] 1101 Related information: 1102 Trace of distribution lists passed. (MIXER X.400 mapping, not for 1103 general use.) 1105 2.1.40 Header field: Alternate-Recipient 1106 Description: 1107 Controls forwarding to alternate recipients 1109 Applicable protocol: Mail [20] 1111 Status: standards-track 1113 Author/change controller: 1114 IETF (mailto:iesg@ietf.org) 1115 Internet Engineering Task Force 1117 Specification document(s): 1118 RFC 2156 [12] 1120 Related information: 1121 Controls whether this message may be forwarded to alternate 1122 recipients such as a postmaster if delivery is not possible to the 1123 intended recipient. Default: Allowed. RFC 2156 (MIXER), not for 1124 general use. 1126 2.1.41 Header field: Original-Encoded-Information-Types 1128 Description: 1129 Body part types in message 1131 Applicable protocol: Mail [20] 1133 Status: standards-track 1135 Author/change controller: 1136 IETF (mailto:iesg@ietf.org) 1137 Internet Engineering Task Force 1139 Specification document(s): 1140 RFC 2156 [12] 1142 Related information: 1143 Which body part types occur in this message. RFC 2156 (MIXER), not 1144 for general use. 1146 2.1.42 Header field: Content-Return 1148 Description: 1149 Return content on non-delivery? 1151 Applicable protocol: Mail [20] 1153 Status: obsolete 1155 Author/change controller: 1156 IETF (mailto:iesg@ietf.org) 1157 Internet Engineering Task Force 1159 Specification document(s): 1160 RFC 1327 [3] 1162 Related information: 1163 Indicates whether the content of a message is to be returned with 1164 non-delivery notifications. Introduced by RFC 1327, and 1165 subsequently changed by RFC 2156 to avoid confusion with MIME 1166 defined fields. 1168 2.1.43 Header field: Generate-Delivery-Report 1170 Description: 1171 Request delivery report generation 1173 Applicable protocol: Mail [20] 1175 Status: standards-track 1177 Author/change controller: 1178 IETF (mailto:iesg@ietf.org) 1179 Internet Engineering Task Force 1181 Specification document(s): 1182 RFC 2156 [12] 1184 Related information: 1185 Indicates whether a delivery report is wanted at successful 1186 delivery. Default is not to generate such a report. RFC 2156 1187 (MIXER), not for general use. 1189 2.1.44 Header field: Prevent-NonDelivery-Report 1191 Description: 1192 Non-delivery report required? 1194 Applicable protocol: Mail [20] 1195 Status: standards-track 1197 Author/change controller: 1198 IETF (mailto:iesg@ietf.org) 1199 Internet Engineering Task Force 1201 Specification document(s): 1202 RFC 2156 [12] 1204 Related information: 1205 Indicates whether non-delivery report is wanted on delivery error. 1206 Default is to generate such a report. RFC 2156 (MIXER), not for 1207 general use. 1209 2.1.45 Header field: Obsoletes 1211 Description: 1212 Reference message to be replaced 1214 Applicable protocol: Mail [20] 1216 Status: obsolete 1218 Author/change controller: 1219 IETF (mailto:iesg@ietf.org) 1220 Internet Engineering Task Force 1222 Specification document(s): 1223 RFC 1327 [3] 1225 Related information: 1226 Reference to a previous message being corrected and replaced. 1227 Compare to 'Supersedes:' used in Usenet News. Introduced by RFC 1228 1327, and subsequently renamed by RFC 2156 to 'Supersedes'. 1230 2.1.46 Header field: Supersedes 1232 Description: 1233 Reference message to be replaced 1235 Applicable protocol: Mail [20] 1237 Status: standards-track 1238 Author/change controller: 1239 IETF (mailto:iesg@ietf.org) 1240 Internet Engineering Task Force 1242 Specification document(s): 1243 RFC 2156 [12] 1245 Related information: 1246 Reference to a previous message being corrected and replaced. 1247 Renamed version of obsolete 'Obsoletes' header field. RFC 2156 1248 (MIXER), not for general use. 1250 2.1.47 Header field: Content-Identifier 1252 Description: 1253 Message content identifier 1255 Applicable protocol: Mail [20] 1257 Status: obsolete 1259 Author/change controller: 1260 IETF (mailto:iesg@ietf.org) 1261 Internet Engineering Task Force 1263 Specification document(s): 1264 RFC 1327 [3] 1266 Related information: 1267 A text string which identifies the content of a message. 1268 Introduced by RFC 1327, and subsequently changed by RFC 2156 to 1269 avoid confusion with MIME defined fields. Gateways which reverse 1270 map may support the old field. 1272 2.1.48 Header field: Delivery-Date 1274 Description: 1275 Message delivery time 1277 Applicable protocol: Mail [20] 1279 Status: standards-track 1281 Author/change controller: 1282 IETF (mailto:iesg@ietf.org) 1283 Internet Engineering Task Force 1285 Specification document(s): 1286 RFC 2156 [12] 1288 Related information: 1289 The time when a message was delivered to its recipient. RFC 2156 1290 (MIXER), not for general use. 1292 2.1.49 Header field: Expiry-Date 1294 Description: 1295 Message expiry time 1297 Applicable protocol: Mail [20] 1299 Status: obsolete 1301 Author/change controller: 1302 IETF (mailto:iesg@ietf.org) 1303 Internet Engineering Task Force 1305 Specification document(s): 1306 RFC 1327 [3] 1308 Related information: 1309 Time at which a message loses its validity. Introduced by RFC 1310 1327, and subsequently changed by RFC 2156 to 'Expires:'. 1312 2.1.50 Header field: Expires 1314 Description: 1315 Message expiry time 1317 Applicable protocol: Mail [20] 1319 Status: standards-track 1321 Author/change controller: 1322 IETF (mailto:iesg@ietf.org) 1323 Internet Engineering Task Force 1325 Specification document(s): 1326 RFC 2156 [12] 1328 Related information: 1329 Time at which a message loses its validity. Renamed version of 1330 obsolete Expiry-Date header field. RFC 2156 (MIXER), not for 1331 general use. 1333 2.1.51 Header field: Reply-By 1335 Description: 1336 Time by which a reply is requested 1338 Applicable protocol: Mail [20] 1340 Status: standards-track 1342 Author/change controller: 1343 IETF (mailto:iesg@ietf.org) 1344 Internet Engineering Task Force 1346 Specification document(s): 1347 RFC 2156 [12] 1349 Related information: 1350 Latest time at which a reply is requested (not demanded). RFC 2156 1351 (MIXER), not for general use. 1353 2.1.52 Header field: Importance 1355 Description: 1356 Message importance 1358 Applicable protocol: Mail [20] 1360 Status: standards-track 1362 Author/change controller: 1363 IETF (mailto:iesg@ietf.org) 1364 Internet Engineering Task Force 1366 Specification document(s): 1367 RFC 2156 [12] 1369 Related information: 1370 A hint from the originator to the recipients about how important a 1371 message is. Values: High, normal or low. Not used to control 1372 transmission speed. Proposed for use with RFC 2156 (MIXER) and RFC 1373 2421 (VPIM). 1375 2.1.53 Header field: Incomplete-Copy 1377 Description: 1378 Body parts are missing. 1380 Applicable protocol: Mail [20] 1382 Status: standards-track 1384 Author/change controller: 1385 IETF (mailto:iesg@ietf.org) 1386 Internet Engineering Task Force 1388 Specification document(s): 1389 RFC 2156 [12] 1391 Related information: 1392 Body parts are missing. RFC 2156 (MIXER), not for general use. 1394 2.1.54 Header field: Priority 1396 Description: 1397 Message priority 1399 Applicable protocol: Mail [20] 1401 Status: standards-track 1403 Author/change controller: 1404 IETF (mailto:iesg@ietf.org) 1405 Internet Engineering Task Force 1407 Specification document(s): 1408 RFC 2156 [12] 1410 Related information: 1411 Can be 'normal', 'urgent' or 'non-urgent' and can influence 1412 transmission speed and delivery. RFC 2156 (MIXER), not for general 1413 use. 1415 2.1.55 Header field: Sensitivity 1417 Description: 1418 Message content sensitivity 1420 Applicable protocol: Mail [20] 1422 Status: standards-track 1424 Author/change controller: 1425 IETF (mailto:iesg@ietf.org) 1426 Internet Engineering Task Force 1428 Specification document(s): 1429 RFC 2156 [12] 1431 Related information: 1432 How sensitive it is to disclose this message to other people than 1433 the specified recipients. Values: Personal, private, company 1434 confidential. The absence of this header field in messages 1435 gatewayed from X.400 indicates that the message is not sensitive. 1436 Proposed for use with RFC 2156 (MIXER) and RFC 2421 (VPIM). 1438 2.1.56 Header field: Language 1440 Description: 1441 X.400 message content lenguage 1443 Applicable protocol: Mail [20] 1445 Status: standards-track 1447 Author/change controller: 1448 IETF (mailto:iesg@ietf.org) 1449 Internet Engineering Task Force 1451 Specification document(s): 1452 RFC 2156 [12] 1454 Related information: 1455 Can include a code for the natural language used in a message, 1456 e.g. 'en' for English. See also 'Content-Language'. RFC 2156 1457 (MIXER), not for general use. 1459 2.1.57 Header field: Conversion 1461 Description: 1462 Conversion allowed? 1464 Applicable protocol: Mail [20] 1466 Status: standards-track 1468 Author/change controller: 1469 IETF (mailto:iesg@ietf.org) 1470 Internet Engineering Task Force 1472 Specification document(s): 1473 RFC 2156 [12] 1475 Related information: 1476 The body of this message may not be converted from one character 1477 set to another. Values: Prohibited and allowed. RFC 2156 (MIXER), 1478 not for general use. 1480 2.1.58 Header field: Conversion-With-Loss 1482 Description: 1483 Lossy conversion allowed? 1485 Applicable protocol: Mail [20] 1487 Status: standards-track 1489 Author/change controller: 1490 IETF (mailto:iesg@ietf.org) 1491 Internet Engineering Task Force 1493 Specification document(s): 1494 RFC 2156 [12] 1496 Related information: 1497 The body of this message may not be converted from one character 1498 set to another if information will be lost. Values: Prohibited and 1499 allowed. RFC 2156 (MIXER), not for general use. 1501 2.1.59 Header field: Message-Type 1503 Description: 1504 Message type: delivery report? 1506 Applicable protocol: Mail [20] 1507 Status: standards-track 1509 Author/change controller: 1510 IETF (mailto:iesg@ietf.org) 1511 Internet Engineering Task Force 1513 Specification document(s): 1514 RFC 2156 [12] 1516 Related information: 1517 Only used with the value 'Delivery Report' to indicates that this 1518 is a delivery report gatewayed from X.400. RFC 2156 (MIXER), not 1519 for general use. 1521 2.1.60 Header field: Autosubmitted 1523 Description: 1524 Automatically submitted indicator 1526 Applicable protocol: Mail [20] 1528 Status: standards-track 1530 Author/change controller: 1531 IETF (mailto:iesg@ietf.org) 1532 Internet Engineering Task Force 1534 Specification document(s): 1535 RFC 2156 [12] 1537 Related information: 1538 Has been automatically submitted. RFC 2156 (MIXER), not for 1539 general use. 1541 2.1.61 Header field: Autoforwarded 1543 Description: 1544 Automatically forwarded indicator 1546 Applicable protocol: Mail [20] 1548 Status: standards-track 1550 Author/change controller: 1551 IETF (mailto:iesg@ietf.org) 1552 Internet Engineering Task Force 1554 Specification document(s): 1555 RFC 2156 [12] 1557 Related information: 1558 Has been automatically forwarded. RFC 2156 (MIXER), not for 1559 general use. 1561 2.1.62 Header field: Discarded-X400-IPMS-Extensions 1563 Description: 1564 X.400 IPM extensions discarded 1566 Applicable protocol: Mail [20] 1568 Status: standards-track 1570 Author/change controller: 1571 IETF (mailto:iesg@ietf.org) 1572 Internet Engineering Task Force 1574 Specification document(s): 1575 RFC 2156 [12] 1577 Related information: 1578 Can be used in Internet mail to indicate X.400 IPM extensions 1579 which could not be mapped to Internet mail format. RFC 2156 1580 (MIXER), not for general use. 1582 2.1.63 Header field: Discarded-X400-MTS-Extensions 1584 Description: 1585 X.400 MTS extensions discarded 1587 Applicable protocol: Mail [20] 1589 Status: standards-track 1591 Author/change controller: 1592 IETF (mailto:iesg@ietf.org) 1593 Internet Engineering Task Force 1595 Specification document(s): 1596 RFC 2156 [12] 1598 Related information: 1599 Can be used in Internet mail to indicate X.400 MTS extensions 1600 which could not be mapped to Internet mail format. RFC 2156 1601 (MIXER), not for general use. 1603 2.1.64 Header field: Disclose-Recipients 1605 Description: 1606 Disclose names of other recipients? 1608 Applicable protocol: Mail [20] 1610 Status: standards-track 1612 Author/change controller: 1613 IETF (mailto:iesg@ietf.org) 1614 Internet Engineering Task Force 1616 Specification document(s): 1617 RFC 2156 [12] 1619 Related information: 1620 Tells whether recipients are to be told the names of other 1621 recipients of the same message. This is primarily an X.400 1622 facility. In X.400, this is an envelope attribute and refers to 1623 disclosure of the envelope recipient list. Disclosure of other 1624 recipients is in Internet mail done via the To:, cc: and bcc: 1625 header fields. Not for general use. 1627 2.1.65 Header field: Deferred-Delivery 1629 Description: 1630 Deferred delivery information 1632 Applicable protocol: Mail [20] 1634 Status: standards-track 1636 Author/change controller: 1637 IETF (mailto:iesg@ietf.org) 1638 Internet Engineering Task Force 1640 Specification document(s): 1641 RFC 2156 [12] 1643 Related information: 1644 Provides information about deferred delivery service to the 1645 recipient. RFC 2156 (MIXER), not for general use. 1647 2.1.66 Header field: Latest-Delivery-Time 1649 Description: 1650 Latest delivery time requested 1652 Applicable protocol: Mail [20] 1654 Status: standards-track 1656 Author/change controller: 1657 IETF (mailto:iesg@ietf.org) 1658 Internet Engineering Task Force 1660 Specification document(s): 1661 RFC 2156 [12] 1663 Related information: 1664 Provides the recipient information about requested delivery, but 1665 will not be acted on by the SMTP infrastrucuture. RFC 2156 1666 (MIXER), not for general use. 1668 2.1.67 Header field: Originator-Return-Address 1670 Description: 1671 Originator return address 1673 Applicable protocol: Mail [20] 1675 Status: standards-track 1677 Author/change controller: 1678 IETF (mailto:iesg@ietf.org) 1679 Internet Engineering Task Force 1681 Specification document(s): 1682 RFC 2156 [12] 1684 Related information: 1685 Originator return address. RFC 2156 (MIXER), not for general use. 1687 2.1.68 Header field: X400-Content-Identifier 1689 Description: 1690 Message content identifier 1692 Applicable protocol: Mail [20] 1694 Status: standards-track 1696 Author/change controller: 1697 IETF (mailto:iesg@ietf.org) 1698 Internet Engineering Task Force 1700 Specification document(s): 1701 RFC 2156 [12] 1703 Related information: 1704 A text string which identifies the content of a message. Renamed 1705 version of obsolete Content-Identifier field. RFC 2156 (MIXER), 1706 not for general use. 1708 2.1.69 Header field: X400-Content-Return 1710 Description: 1711 Return content on non-delivery? 1713 Applicable protocol: Mail [20] 1715 Status: standards-track 1717 Author/change controller: 1718 IETF (mailto:iesg@ietf.org) 1719 Internet Engineering Task Force 1721 Specification document(s): 1722 RFC 2156 [12] 1724 Related information: 1725 Indicates whether the content of a message is to be returned with 1726 non-delivery notifications. Renamed version of obsolete 1727 Content-Return field. RFC 2156 (MIXER), not for general use. 1729 2.1.70 Header field: X400-Content-Type 1730 Description: 1731 X400 content type 1733 Applicable protocol: Mail [20] 1735 Status: standards-track 1737 Author/change controller: 1738 IETF (mailto:iesg@ietf.org) 1739 Internet Engineering Task Force 1741 Specification document(s): 1742 RFC 2156 [12] 1744 Related information: 1745 X400 content type. RFC 2156 (MIXER), not for general use. 1747 2.1.71 Header field: X400-MTS-Identifier 1749 Description: 1750 X400 MTS-Identifier 1752 Applicable protocol: Mail [20] 1754 Status: standards-track 1756 Author/change controller: 1757 IETF (mailto:iesg@ietf.org) 1758 Internet Engineering Task Force 1760 Specification document(s): 1761 RFC 2156 [12] 1763 Related information: 1764 X400 MTS-Identifier. RFC 2156 (MIXER), not for general use. 1766 2.1.72 Header field: X400-Originator 1768 Description: 1769 X400 Originator 1771 Applicable protocol: Mail [20] 1773 Status: standards-track 1774 Author/change controller: 1775 IETF (mailto:iesg@ietf.org) 1776 Internet Engineering Task Force 1778 Specification document(s): 1779 RFC 2156 [12] 1781 Related information: 1782 X400 Originator. RFC 2156 (MIXER), not for general use. 1784 2.1.73 Header field: X400-Received 1786 Description: 1787 X400 Received 1789 Applicable protocol: Mail [20] 1791 Status: standards-track 1793 Author/change controller: 1794 IETF (mailto:iesg@ietf.org) 1795 Internet Engineering Task Force 1797 Specification document(s): 1798 RFC 2156 [12] 1800 Related information: 1801 X400 Received. RFC 2156 (MIXER), not for general use. 1803 2.1.74 Header field: X400-Recipients 1805 Description: 1806 X400 Recipients 1808 Applicable protocol: Mail [20] 1810 Status: standards-track 1812 Author/change controller: 1813 IETF (mailto:iesg@ietf.org) 1814 Internet Engineering Task Force 1816 Specification document(s): 1817 RFC 2156 [12] 1819 Related information: 1820 X400 Recipients. RFC 2156 (MIXER), not for general use. 1822 2.1.75 Header field: X400-Trace 1824 Description: 1825 X400 Trace 1827 Applicable protocol: Mail [20] 1829 Status: standards-track 1831 Author/change controller: 1832 IETF (mailto:iesg@ietf.org) 1833 Internet Engineering Task Force 1835 Specification document(s): 1836 RFC 2156 [12] 1838 Related information: 1839 X400 Trace. RFC 2156 (MIXER), not for general use. 1841 2.2 Permanent MIME header field registrations 1843 Header name Protocol 1844 ----------- -------- 1845 MIME-Version MIME MIME version number 1846 Content-ID MIME Identify content body part 1847 Content-Description MIME Description of message body part 1848 Content-Transfer-Encoding 1849 MIME Content transfer encoding applied 1850 Content-Type MIME MIME content type 1851 Content-Base MIME Base to be used for resolving 1852 relative URIs within this content 1853 part. 1854 Content-Location MIME URI for retrieving a body part 1855 Content-features MIME Indicates content features of a 1856 MIME body part 1857 Content-Disposition MIME Intended content disposition and 1858 file name 1859 Content-Language MIME Language of message content 1860 Content-Alternative MIME Alternative content available 1861 Content-MD5 MIME MD5 checksum of content 1862 Content-Duration MIME Time duration of content 1864 2.2.1 Header field: MIME-Version 1866 Description: 1867 MIME version number 1869 Applicable protocol: MIME [8] 1871 Status: standards-track 1873 Author/change controller: 1874 IETF (mailto:iesg@ietf.org) 1875 Internet Engineering Task Force 1877 Specification document(s): 1878 RFC 2045 [8] (section 4) 1880 Related information: 1881 An indicator that this message is formatted according to the MIME 1882 standard, and an indication of which version of MIME is utilized. 1884 2.2.2 Header field: Content-ID 1886 Description: 1887 Identify content body part 1889 Applicable protocol: MIME [8] 1891 Status: standards-track 1893 Author/change controller: 1894 IETF (mailto:iesg@ietf.org) 1895 Internet Engineering Task Force 1897 Specification document(s): 1898 RFC 2045 [8] (section 7) 1900 Related information: 1901 Specifies a Unique ID for one MIME body part of the content of a 1902 message. 1904 2.2.3 Header field: Content-Description 1906 Description: 1907 Description of message body part 1909 Applicable protocol: MIME [8] 1911 Status: standards-track 1913 Author/change controller: 1914 IETF (mailto:iesg@ietf.org) 1915 Internet Engineering Task Force 1917 Specification document(s): 1918 RFC 2045 [8] (section 8) 1920 Related information: 1921 Description of a particular body part of a message, for example a 1922 caption for an image body part. 1924 2.2.4 Header field: Content-Transfer-Encoding 1926 Description: 1927 Content transfer encoding applied 1929 Applicable protocol: MIME [8] 1931 Status: standards-track 1933 Author/change controller: 1934 IETF (mailto:iesg@ietf.org) 1935 Internet Engineering Task Force 1937 Specification document(s): 1938 RFC 2045 [8] (section 6) 1940 Related information: 1941 Coding method used in a MIME message body part. 1943 2.2.5 Header field: Content-Type 1945 Description: 1946 MIME content type 1948 Applicable protocol: MIME [8] 1950 Status: standards-track 1952 Author/change controller: 1953 IETF (mailto:iesg@ietf.org) 1954 Internet Engineering Task Force 1956 Specification document(s): 1957 RFC 2045 [8] (section 5) 1959 Related information: 1960 Format of content (character set etc.) Note that the values for 1961 this header field are defined in different ways in RFC 1049 and in 1962 MIME (RFC 2045), look for the 'MIME-version' header field to 1963 understand if Content-Type is to be interpreted according to RFC 1964 1049 or according to MIME. The MIME definition should be used in 1965 generating mail. RFC 1049 has 'historic' status. RFC 1766 defines 1966 a parameter 'difference' to this header field. Various other 1967 Content-Type define various additional parameters. For example, 1968 the parameter 'charset' is mandatory for all textual 1969 Content-Types. See also: RFC 1049, RFC 1123: 5.2.13, RFC 1766: 1970 4.1. 1972 2.2.6 Header field: Content-Base 1973 Description: 1974 Base to be used for resolving relative URIs within this content 1975 part. 1977 Applicable protocol: MIME [8] 1979 Status: standards-track 1981 Author/change controller: 1982 IETF (mailto:iesg@ietf.org) 1983 Internet Engineering Task Force 1985 Specification document(s): 1986 RFC 2110 [10] 1988 Related information: 1989 Base to be used for resolving relative URIs within this content 1990 part. See also Content-Location. This header was included in the 1991 first version of MHTML and HTTP 1.1 but removed in the second 1992 version (RFC2557). 1994 2.2.7 Header field: Content-Location 1996 Description: 1997 URI for retrieving a body part 1999 Applicable protocol: MIME [8] 2001 Status: standards-track 2003 Author/change controller: 2004 IETF (mailto:iesg@ietf.org) 2005 Internet Engineering Task Force 2007 Specification document(s): 2008 RFC 2557 [18] 2010 Related information: 2011 URI using which the content of this body-part part was retrieved, 2012 might be retrievable, or which otherwise gives a globally unique 2013 identification of the content. 2015 2.2.8 Header field: Content-features 2016 Description: 2017 Indicates content features of a MIME body part 2019 Applicable protocol: MIME [8] 2021 Status: standards-track 2023 Author/change controller: 2024 IETF (mailto:iesg@ietf.org) 2025 Internet Engineering Task Force 2027 Specification document(s): 2028 RFC 2912 [21] (section 3) 2030 Related information: 2031 The 'Content-features:' header can be used to annotate a MIME body 2032 part with a media feature expression, to indicate features of the 2033 body part content. See also: RFC 2533, RFC 2506, RFC 2045. 2035 2.2.9 Header field: Content-Disposition 2037 Description: 2038 Intended content disposition and file name 2040 Applicable protocol: MIME [8] 2042 Status: standards-track 2044 Author/change controller: 2045 IETF (mailto:iesg@ietf.org) 2046 Internet Engineering Task Force 2048 Specification document(s): 2049 RFC 2183 [13] 2051 Related information: 2052 Whether a MIME body part is to be shown inline or is an 2053 attachment; can also indicate a suggested filename for use when 2054 saving an attachment to a file. 2056 2.2.10 Header field: Content-Language 2058 Description: 2059 Language of message content 2061 Applicable protocol: MIME [8] 2063 Status: standards-track 2065 Author/change controller: 2066 IETF (mailto:iesg@ietf.org) 2067 Internet Engineering Task Force 2069 Specification document(s): 2070 RFC 3282 [23] 2072 Related information: 2073 Can include a code for the natural language used in a message, 2074 e.g. 'en' for English. Can also contain a list of languages for a 2075 message containing more than one language. 2077 2.2.11 Header field: Content-Alternative 2079 Description: 2080 Alternative content available 2082 Applicable protocol: MIME [8] 2084 Status: work-in-progress 2086 Author/change controller: 2087 IETF (mailto:iesg@ietf.org) 2088 Internet Engineering Task Force 2090 Specification document(s): 2091 RFC 3297 [24] 2093 Related information: 2094 Information about the media features of alternative content 2095 formats available for the current message. 2097 2.2.12 Header field: Content-MD5 2099 Description: 2100 MD5 checksum of content 2102 Applicable protocol: MIME [8] 2104 Status: standards-track 2105 Author/change controller: 2106 IETF (mailto:iesg@ietf.org) 2107 Internet Engineering Task Force 2109 Specification document(s): 2110 RFC 1864 [7] 2112 Related information: 2113 Checksum of content to ensure that it has not been modified. 2115 2.2.13 Header field: Content-Duration 2117 Description: 2118 Time duration of content 2120 Applicable protocol: MIME [8] 2122 Status: standards-track 2124 Author/change controller: 2125 IETF (mailto:iesg@ietf.org) 2126 Internet Engineering Task Force 2128 Specification document(s): 2129 RFC 2424 [17] 2131 Related information: 2132 Time duration of body part content, in seconds (e.g. for audio 2133 message). 2135 3. IANA considerations 2137 This specification provides initial registrations of mail and MIME 2138 header fields in the "Permanent Message Header Field Registry", 2139 defined by Registration procedures for message header fields [1]. 2141 4. Security considerations 2143 No security considerations are introduced by this registration 2144 document beyond those already inherent in use of the mail message 2145 header fields referenced. 2147 5. Acknowledgements 2149 Most of the information in this document has been derived from Jacob 2150 Palme's work in RFC 2076 [27] and subsequent updates [28]. 2152 The authors also gratefully acknowledge contributions and 2153 constructive input from: Mark Nottingham, Bruce Lilly, Keith Moore 2154 and Charles Lindsey (the mention of whom is not intended to imply 2155 their unqualified support for material herein). 2157 6. References 2159 6.1 Normative references 2161 [1] Klyne, G., Nottingham, M. and J. Mogul, "Registration 2162 procedures for message headers", Oct 2003, . 2166 [2] Crocker, D., "Standard for the format of ARPA Internet text 2167 messages", STD 11, RFC 822, August 1982. 2169 [3] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 2170 and RFC 822", RFC 1327, May 1992. 2172 [4] Alvestrand, H., Jordan, K. and J. Romaguera, "Rules for 2173 downgrading messages from X.400/88 to X.400/84 when MIME 2174 content-types are present in the messages", RFC 1496, August 2175 1993. 2177 [5] Costanzo, A., Robinson, D. and R. Ullmann, "Encoding Header 2178 Field for Internet Messages", RFC 1505, August 1993. 2180 [6] Alvestrand, H., "Tags for the Identification of Languages", RFC 2181 1766, March 1995. 2183 [7] Myers, J. and M. Rose, "The Content-MD5 Header Field", RFC 2184 1864, October 1995. 2186 [8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 2187 Extensions (MIME) Part One: Format of Internet Message Bodies", 2188 RFC 2045, November 1996. 2190 [9] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 2191 Extensions (MIME) Part Two: Media Types", RFC 2046, November 2192 1996. 2194 [10] Palme, J. and A. Hopmann, "MIME E-mail Encapsulation of 2195 Aggregate Documents, such as HTML (MHTML)", RFC 2110, March 2196 1997. 2198 [11] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2199 Levels", BCP 14, RFC 2119, March 1997. 2201 [12] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping 2202 between X.400 and RFC 822/MIME", RFC 2156, January 1998. 2204 [13] Troost, R., Dorner, S. and K. Moore, "Communicating 2205 Presentation Information in Internet Messages: The 2206 Content-Disposition Header Field", RFC 2183, August 1997. 2208 [14] Fajman, R., "An Extensible Message Format for Message 2209 Disposition Notifications", RFC 2298, March 1998. 2211 [15] Neufeld, G. and J. Baer, "The Use of URLs as Meta-Syntax for 2212 Core Mail List Commands and their Transport through Message 2213 Header Fields", RFC 2369, July 1998. 2215 [16] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet Mail 2216 - version 2", RFC 2421, September 1998. 2218 [17] Vaudreuil, G. and G. Parsons, "Content Duration MIME Header 2219 Definition", RFC 2424, September 1998. 2221 [18] Palme, F., Hopmann, A., Shelness, N. and E. Stefferud, "MIME 2222 Encapsulation of Aggregate Documents, such as HTML (MHTML)", 2223 RFC 2557, March 1999. 2225 [19] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, April 2226 2001. 2228 [20] Resnick, P., "Internet Message Format", RFC 2822, April 2001. 2230 [21] Klyne, G., "Indicating Media Features for MIME Content", RFC 2231 2912, September 2000. 2233 [22] Chandhok, R. and G. Wenger, "List-Id: A Structured Field and 2234 Namespace for the Identification of Mailing Lists", RFC 2919, 2235 March 2001. 2237 [23] Alvestrand, H., "Content Language Headers", RFC 3282, May 2002. 2239 [24] Klyne, G., Iwazaki, R. and D. Crocker, "Content Negotiation for 2240 Messaging Services based on Email", RFC 3297, July 2002. 2242 [25] Burger, E., Candell, E., Eliot, C. and G. Klyne, "Message 2243 Context for Internet Mail", RFC 3458, January 2003. 2245 [26] Miller, J., Krauskopf, T., Resnick, P. and W. Treese, "PICS 2246 Label Distribution Label Syntax and Communication Protocols", 2247 W3C Recommendation REC-PICS-labels, October 1996, . 2250 6.2 Informative references 2252 [27] Palme, J., "Common Internet Message Headers", RFC 2076, 2253 February 1997. 2255 [28] Palme, J., "Common Internet Message Header Fields", Internet 2256 draft draft-palme-mailext-headers-08, November 2001, . 2260 URIs 2262 [29] 2265 Authors' Addresses 2267 Graham Klyne 2268 Nine by Nine 2270 UK 2272 EMail: GK-IETF@ninebynine.org 2273 URI: http://www.ninebynine.net/ 2275 Jacob Palme 2276 Stockholm University/KTH 2277 Forum 100 2278 Kista S-164 40 2279 Sweden 2281 Phone: +46-8-16 16 67 2282 Fax: +46-8-783 08 29 2283 EMail: jpalme@dsv.su.se 2285 Appendix A. Revision history 2287 [[[Please remove this section on final publication]]] 2289 A.1 draft-klyne-hdrreg-mail-05 2291 05a 07-May-2004: 2293 * Change status of headers defined by RFC822 to standard, except 2294 Encrypted which is obsolete. 2296 * Add RFC822 to references. 2298 * Set ?RFC strict=yes, and clean up ID-nits. 2300 A.2 draft-klyne-hdrreg-mail-04 2302 04b 19-Apr-2004: 2304 * Final editorial tidying. 2306 * Acknowledge additional contributions. 2308 04a 14-Apr-2004: 2310 * Minor editorial fixes. 2312 * Fix up message-headers I-D reference. [28] 2314 A.3 draft-klyne-hdrreg-mail-03 2316 03c 13-Apr-2004: 2318 * Added Accept-Language header, with some warning text concerning 2319 its use with email. 2321 * Removed Originator headere, since it is not used as a mail 2322 message header. 2324 * Fix up report generator error in author/change controller 2325 handling. 2327 03b 06-Apr-2004: 2329 * Using a new version of the RDF-to-documentation generator for 2330 registry entry data. 2332 * Revised format of registry entries to avoid some duplication of 2333 document and author details. 2335 * Added documents referenced by the regsitration entries to the 2336 references section, and added citations to the entries 2337 themselves. 2339 03a 15-Mar-2004: 2341 * Added and revised header details, per comments from Bruce 2342 Lilly. 2344 A.4 draft-klyne-hdrreg-mail-02 2346 02d 19-Feb-2004: 2348 * Incorporated small changes to specific header field 2349 descriptions, suggested by Jacob. 2351 02c 18-Feb-2004: 2353 * Separated Mail and MIME header fields. 2355 * Corrected specification reference for MIXER headers (RFC 2156). 2357 * Changed applicable protocol for MIME header fields. 2359 * Other smaller corrections. 2361 02b 17-Feb-2004: 2363 * Removed provisional mail header registrations from this 2364 document. 2366 02a 05-Aug-2002: 2368 * Added Jacob Palme as co-editor. 2370 A.5 draft-klyne-hdrreg-mail-01 2372 01c 05-Jun-2002: 2374 * Minor editorial. 2376 01b 10-May-2002: 2378 * Updated some contact information. 2380 * Regenerated registry tables with revised software. 2382 01a 08-May-2002: 2384 * Revised change controller information in line with registry 2385 specification. 2387 * Cleaned up some table layout. 2389 A.6 draft-klyne-hdrreg-mail-00 2391 00c 05-May-2002: 2393 * Added data for permanent and provisional registries. 2395 00b 01-May-2002: 2397 * Revised form of registry entry content. (Auto-generated from 2398 RDF data.) 2400 00a 22-Jan-2002: 2402 * Document initially created. 2404 Appendix B. TODO: 2406 [[[Please remove this section on final publication]]] 2408 o Resolve reference to registration procedure RFC [1]. 2410 o Remove any remaining [[[editorial comments]]]. 2412 Intellectual Property Statement 2414 The IETF takes no position regarding the validity or scope of any 2415 Intellectual Property Rights or other rights that might be claimed to 2416 pertain to the implementation or use of the technology described in 2417 this document or the extent to which any license under such rights 2418 might or might not be available; nor does it represent that it has 2419 made any independent effort to identify any such rights. Information 2420 on the IETF's procedures with respect to rights in IETF Documents can 2421 be found in BCP 78 and BCP 79. 2423 Copies of IPR disclosures made to the IETF Secretariat and any 2424 assurances of licenses to be made available, or the result of an 2425 attempt made to obtain a general license or permission for the use of 2426 such proprietary rights by implementers or users of this 2427 specification can be obtained from the IETF on-line IPR repository at 2428 http://www.ietf.org/ipr. 2430 The IETF invites any interested party to bring to its attention any 2431 copyrights, patents or patent applications, or other proprietary 2432 rights that may cover technology that may be required to implement 2433 this standard. Please address the information to the IETF at 2434 ietf-ipr@ietf.org. 2436 Disclaimer of Validity 2438 This document and the information contained herein are provided on an 2439 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2440 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2441 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2442 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2443 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2444 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2446 Copyright Statement 2448 Copyright (C) The Internet Society (2004). This document is subject 2449 to the rights, licenses and restrictions contained in BCP 78, and 2450 except as set forth therein, the authors retain all their rights. 2452 Acknowledgment 2454 Funding for the RFC Editor function is currently provided by the 2455 Internet Society.