RFC 4466
Collected Extensions to IMAP4 ABNF
RFC 4466: Collected Extensions to IMAP4 ABNF 💌
Network Working Group 🌸 Request for Comments: 4466
- Authors: A. Melnikov (Isode Ltd.) and C. Daboo 🧑💻
- Category: Standards Track ✅
- Date: April 2006 📅
- Updates: 2088, 2342, 3501, 3502, 3516 🔁
- Obsoletes: nothing listed 🙅♀️
Status of This Memo ✨
okay so this doc is an Internet standards track protocol for the whole Internet community 🌐, and it's literally asking everyone to chat about it and suggest improvements 💬. For where this protocol stands right now, check the current edition of "Internet Official Protocol Standards" (STD 1) 📖. And the good news: distribution of this memo is unlimited 🦋.
Copyright Notice 🔒
Copyright (C) The Internet Society (2006). 💜
Abstract 📝
so for years, a bunch of docs from the IMAPEXT and LEMONADE working groups 👯, plus a pile of individual docs, kept slipping little syntax extensions onto the base IMAP commands from RFC 3501 🧩. For ease of reference, this document gathers most of those ABNF changes into one place 📦, so you don't have to hop around ✨.
This doc also suggests a set of standard patterns for adding options and extensions to several existing IMAP commands from RFC 3501 🎀. The patterns keep existing and future extensions compatible with each other 🫶.
This document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516 🔁. It also includes part of the errata to RFC 3501 🩹. This document doesn't specify any semantic changes to the listed RFCs 🙅♀️. (The vibe is "same meaning, cleaner syntax" 💅.)
Table of Contents 📚
1. Introduction ....................................................2
1.1. Purpose of This Document ...................................2
1.2. Conventions Used in This Document ..........................3
2. IMAP ABNF Extensions ............................................3
2.1. Optional Parameters with the SELECT/EXAMINE Commands .......3
2.2. Extended CREATE Command ....................................4
2.3. Extended RENAME Command ....................................5
2.4. Extensions to FETCH and UID FETCH Commands .................6
2.5. Extensions to STORE and UID STORE Commands .................6
2.6. Extensions to SEARCH Command ...............................7
2.6.1. Extended SEARCH Command .............................7
2.6.2. ESEARCH untagged response ...........................8
2.7. Extensions to APPEND Command ...............................8
3. Formal Syntax ...................................................9
4. Security Considerations ........................................14
5. Normative References ...........................................15
6. Acknowledgements ...............................................151. Introduction ✨
1.1. Purpose of This Document 🎯
this doc has a few goals, bestie 👑:
- rationalize and generalize ABNF for some existing IMAP extensions;
- collect the ABNF in one place in order to minimize cross references between documents;
- define building blocks for future extensions so that they can be used together in a compatible way.
it's expected that a future revision of this document will get folded into a revision of RFC 3501 🧚.
this document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516 🔁. It also includes part of the errata to RFC 3501 🩹. This document doesn't specify any semantic changes to the listed RFCs 🙅♀️.
the ABNF in section 6 of RFC 2342 got rewritten so it matches the ABNF syntax defined in RFC 4234 🪄, and it now references new non-terminals from RFC 3501 🔗. It was also restructured to be easier to read 📖. There were no changes "on the wire" 🫶, so nothing changes for anyone actually talking to a server 💖.
Section 2 extends ABNF for the SELECT, EXAMINE, CREATE, RENAME, FETCH/UID FETCH, STORE/UID STORE, SEARCH, and APPEND commands in a consistent manner 💅. Extensions to all the commands but APPEND have the same structure. Extensibility for the APPEND command was done slightly differently 🙈, in order to preserve backward compatibility with existing extensions 💜.
Section 2 also defines a new ESEARCH response 🔥, whose purpose is to be a better version of the SEARCH response defined in RFC 3501 ✨.
Section 3 defines the collected ABNF that replaces pieces of ABNF in the aforementioned RFCs 📦. The collected ABNF got generalized so future extensions are easier to add 🦋.
1.2. Conventions Used in This Document 📏
in the examples, "C:" and "S:" mean lines sent by the client and server, respectively 🎀.
the key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as defined in "Key words for use in RFCs to Indicate Requirement Levels" [KEYWORDS] 📚.
2. IMAP ABNF Extensions 🧩
this section is not normative 🙌. It gives some background on the intended use of different extensions, and some guidance on how future extensions should extend the described commands 🌈.
2.1. Optional Parameters with the SELECT/EXAMINE Commands 🌸
this part adds the ability to slap one or more parameters onto the IMAP SELECT (section 6.3.1 of [IMAP4]) or EXAMINE (section 6.3.2 of [IMAP4]) commands 💅. You can use them to turn certain standard behaviors on or off, or to add new optional behaviors that a particular extension needs 🔥.
there are two possible modes of operation, bestie 👯:
- A global state change where a single use of the optional parameter will affect the session state from that time on, irrespective of subsequent SELECT/EXAMINE commands ✨.
- A per-mailbox state change that will affect the session only for the duration of the new selected state 🦋. A subsequent SELECT/EXAMINE without the optional parameter will cancel its effect for the newly selected mailbox 🙈.
optional parameters to the SELECT or EXAMINE commands are added as a parenthesized list of attribute/value pairs 🎀. They show up after the mailbox name in the standard SELECT or EXAMINE command 💖. The order of individual parameters is arbitrary 🌈. A parameter value is optional and may be made of atoms, strings, or lists in a specific order 🧚. If the parameter value is present, it always appears in parentheses (*) 🫶. Any parameter not defined by extensions that the server supports must be rejected with a BAD response 💀.
Example:
C: a SELECT INBOX (ANNOTATE)
S: ...
S: a OK SELECT completein the above example, a single parameter is used with the SELECT command 🍓.
Example:
C: a EXAMINE INBOX (ANNOTATE RESPONSES ("UID Responses")
CONDSTORE)
S: ...
S: a OK EXAMINE completein the above example, three parameters are used with the EXAMINE command 🌟. The second parameter consists of two items: an atom "RESPONSES" followed by a quoted string 🧁.
Example:
C: a SELECT INBOX (BLURDYBLOOP)
S: a BAD Unknown parameter in SELECT commandin the above example, a parameter the server doesn't support gets used 🙅♀️. This results in the BAD response from the server 😭.
(*) - if a parameter has a mandatory value, which can always be represented as a number or a sequence-set, the parameter value does not need the enclosing (). See ABNF for more details 📐.
2.2. Extended CREATE Command 🏗️
Arguments: mailbox name
OPTIONAL list of CREATE parameters
Responses: no specific responses for this command
Result: OK - create completed
NO - create failure: cannot create mailbox with
that name
BAD - argument(s) invalidthis part adds the ability to include one or more parameters with the IMAP CREATE command (see section 6.3.3 of [IMAP4]) 🎀. Same deal as before: turn standard behaviors on or off, or add new optional behaviors a particular extension needs 💅. No CREATE parameters are defined in this document 🫠.
optional parameters to the CREATE command are added as a parenthesized list of attribute/value pairs after the mailbox name 🌸. The order of individual parameters is arbitrary 🌈. A parameter value is optional and may be made of atoms, strings, or lists in a specific order ✨. If the parameter value is present, it always appears in parentheses (*) 🫶. Any parameter not defined by extensions that the server supports must be rejected with a BAD response 💀.
(*) - if a parameter has a mandatory value, which can always be represented as a number or a sequence-set, the parameter value does not need the enclosing (). See ABNF for more details 📐.
2.3. Extended RENAME Command 🔁
Arguments: existing mailbox name
new mailbox name
OPTIONAL list of RENAME parameters
Responses: no specific responses for this command
Result: OK - rename completed
NO - rename failure: cannot rename mailbox with
that name, cannot rename to mailbox with
that name, etc.
BAD - argument(s) invalidthis part adds the ability to include one or more parameters with the IMAP RENAME command (see section 6.3.5 of [IMAP4]) 🦋, so you can toggle standard behaviors or add optional ones for a particular extension 💖. No RENAME parameters are defined in this document 🙃.
optional parameters to the RENAME command are added as a parenthesized list of attribute/value pairs after the new mailbox name 🎀. The order of individual parameters is arbitrary 🌈. A parameter value is optional and may be made of atoms, strings, or lists in a specific order 🧚. If the parameter value is present, it always appears in parentheses (*) 🫶. Any parameter not defined by extensions that the server supports must be rejected with a BAD response 💀.
(*) - if a parameter has a mandatory value, which can always be represented as a number or a sequence-set, the parameter value does not need the enclosing (). See ABNF for more details 📐.
2.4. Extensions to FETCH and UID FETCH Commands 📥
Arguments: sequence set
message data item names or macro
OPTIONAL fetch modifiers
Responses: untagged responses: FETCH
Result: OK - fetch completed
NO - fetch error: cannot fetch that data
BAD - command unknown or arguments invalidthis doc extends the syntax of the FETCH and UID FETCH commands (see section 6.4.5 of [IMAP4]) so they can take optional FETCH modifiers 💅. No fetch modifiers are defined in this document 🫠.
the order of individual modifiers is arbitrary 🌈. Each modifier is an attribute/value pair 🎀. A modifier value is optional and may be made of atoms, strings, and/or lists in a specific order ✨. If the modifier value is present, it always appears in parentheses (*) 🫶. Any modifiers not defined by extensions that the server supports must be rejected with a BAD response 💀.
(*) - if a modifier has a mandatory value, which can always be represented as a number or a sequence-set, the modifier value does not need the enclosing (). See ABNF for more details 📐.
2.5. Extensions to STORE and UID STORE Commands
okay bestie, STORE and UID STORE get a glow-up 💅 here's the whole vibe:
Arguments: message set
OPTIONAL store modifiers
message data item name
value for message data item
Responses: untagged responses: FETCH
Result: OK - store completed
NO - store error: cannot store that data
BAD - command unknown or arguments invalidso this doc extends the syntax of STORE and UID STORE (see section 6.4.6 of [IMAP4]) to add optional STORE modifiers 🎀 and NO modifiers are actually defined here. the vibe is just "we made room for them" 🫶
the order of individual modifiers is totally arbitrary, so it doesn't matter which one comes first 🦋 each modifier is an attribute/value pair. the modifier value is optional and can be made of atoms, strings, and/or lists, in a specific order. if a modifier value is there, it always goes in parentheses (*) 🌸 and any modifier that the server doesn't support through an extension must be rejected with a BAD response. no ghosting, bestie 💀
(*) - if a modifier has a mandatory value (it can always be a number or a sequence-set), the value doesn't need the enclosing (). see the ABNF for the details 🧚
2.6. Extensions to SEARCH Command
2.6.1. Extended SEARCH Command
Arguments: OPTIONAL result specifier
OPTIONAL [CHARSET] specification
searching criteria (one or more)
Responses: REQUIRED untagged response: SEARCH (*)
Result: OK - search completed
NO - search error: cannot search that [CHARSET] or
criteria
BAD - command unknown or arguments invalidokay so this section updates the definition of SEARCH from section 6.4.4 of [IMAP4] 💜
SEARCH is getting result options, which is giving main character energy ✨ this doc doesn't define any result options though, so it's basically the stage being set 🎭 the order of the options is arbitrary 🍓 each option can have parameters in parentheses (**), and if an option has parameters, they're atoms, strings, and/or lists in a specific order. anything the server doesn't support through an extension must be rejected with a BAD response 🙈
(*) - an extension to SEARCH might need another untagged response, or none at all. section 2.6.2 defines a new ESEARCH untagged response that replaces the SEARCH one 🦋 for any given extended SEARCH command, the SEARCH and ESEARCH responses SHOULD be mutually exclusive, which means only one of them should come back. no double-texting the client 😭
(**) - if an option has a mandatory parameter (always a number or a sequence-set), the parameter doesn't need the enclosing (). see the ABNF for more 🧚
2.6.2. ESEARCH untagged response
Contents: one or more search-return-data pairsthe ESEARCH response SHOULD be sent as the result of an extended SEARCH or UID SEARCH command from section 2.6.1 🌈
it starts with an optional search correlator 💅 if that's missing, the response wasn't caused by a specific IMAP command. if it's there, it has the tag of the command that caused the response 🎀
after the correlator comes an optional UID indicator 🫶 if it's present, all the data in the ESEARCH response is about UIDs. if not, all the returned data is about message numbers 🔢
the rest of the response is one or more search data pairs 🍰 each pair starts with a unique return item name, then a space, then the matching data. the pairs can come back in any order 🦋 unless an extension says otherwise, any return item name SHOULD only show up once in an ESEARCH response. one and done, bestie 💖
examples, because we love a visual 👀
Example: S: * ESEARCH UID COUNT 5 ALL 4:19,21,28Example: S: * ESEARCH (TAG "a567") UID COUNT 5 ALL 4:19,21,28Example: S: * ESEARCH COUNT 5 ALL 1:17,212.7. Extensions to APPEND Command
the IMAP BINARY extension [BINARY] lets a client append data with NULs in it, using the <literal8> syntax 🌊 the ABNF got rewritten so it's easier for other IMAP extensions to extend it later 🧩 this document hasn't specified any semantical changes to [BINARY] though, so the meaning stays the same 💜
also, the non-terminal "literal8" from [BINARY] got extended to allow non-synchronizing literals, but only if the server supports both [BINARY] and [LITERAL+] 🎀 that's the kind of combo glow-up I'm obsessed with 😭
the IMAP MULTIAPPEND extension [MULTIAPPEND] lets a client append multiple messages atomically, meaning all or nothing 🍓 this document defines a common syntax for APPEND that takes into account the syntax extensions from both [BINARY] and [MULTIAPPEND] 🫶 it's giving teamwork, periodt 🌸
3. Formal Syntax 💅
okay so the grammar is written in ABNF, which is the notation from [ABNF] 🎀. Anything that isn't defined in here is borrowed from [IMAP4], so you'd better have that one open too ✨
Everything is case-insensitive, bestie. Uppercase or lowercase is only there so it's easier to read, and it doesn't change anything. Implementations MUST accept these strings in a case-insensitive fashion 🫶
append = "APPEND" SP mailbox 1*append-message
;; only a single append-message may appear
;; if MULTIAPPEND [MULTIAPPEND] capability
;; is not present
append-message = append-opts SP append-data
append-ext = append-ext-name SP append-ext-value
;; This non-terminal define extensions to
;; to message metadata.
append-ext-name = tagged-ext-label
append-ext-value= tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
append-data = literal / literal8 / append-data-ext
append-data-ext = tagged-ext
;; This non-terminal shows recommended syntax
;; for future extensions,
;; i.e., a mandatory label followed
;; by parameters.
append-opts = [SP flag-list] [SP date-time] *(SP append-ext)
;; message metadata
charset = atom / quoted
;; Exact syntax is defined in [CHARSET].
create = "CREATE" SP mailbox
[create-params]
;; Use of INBOX gives a NO error.
create-params = SP "(" create-param *( SP create-param) ")"
create-param-name = tagged-ext-label
create-param = create-param-name [SP create-param-value]
create-param-value= tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
esearch-response = "ESEARCH" [search-correlator] [SP "UID"]
*(SP search-return-data)
;; Note that SEARCH and ESEARCH responses
;; SHOULD be mutually exclusive,
;; i.e., only one of the response types
;; should be
;; returned as a result of a command.
examine = "EXAMINE" SP mailbox [select-params]
;; modifies the original IMAP EXAMINE command
;; to accept optional parameters
fetch = "FETCH" SP sequence-set SP ("ALL" / "FULL" /
"FAST" / fetch-att /
"(" fetch-att *(SP fetch-att) ")")
[fetch-modifiers]
;; modifies the original IMAP4 FETCH command to
;; accept optional modifiers
fetch-modifiers = SP "(" fetch-modifier *(SP fetch-modifier) ")"
fetch-modifier = fetch-modifier-name [ SP fetch-modif-params ]
fetch-modif-params = tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
fetch-modifier-name = tagged-ext-label
literal8 = "~{" number ["+"] "}" CRLF *OCTET
;; A string that might contain NULs.
;; <number> represents the number of OCTETs
;; in the response string.
;; The "+" is only allowed when both LITERAL+ and
;; BINARY extensions are supported by the server.
mailbox-data =/ Namespace-Response /
esearch-response
Namespace = nil / "(" 1*Namespace-Descr ")"
Namespace-Command = "NAMESPACE"
Namespace-Descr = "(" string SP
(DQUOTE QUOTED-CHAR DQUOTE / nil)
*(Namespace-Response-Extension) ")"
Namespace-Response-Extension = SP string SP
"(" string *(SP string) ")"
Namespace-Response = "NAMESPACE" SP Namespace
SP Namespace SP Namespace
;; This response is currently only allowed
;; if the IMAP server supports [NAMESPACE].
;; The first Namespace is the Personal Namespace(s)
;; The second Namespace is the Other Users' Namespace(s)
;; The third Namespace is the Shared Namespace(s)
rename = "RENAME" SP mailbox SP mailbox
[rename-params]
;; Use of INBOX as a destination gives
;; a NO error, unless rename-params
;; is not empty.
rename-params = SP "(" rename-param *( SP rename-param) ")"
rename-param = rename-param-name [SP rename-param-value]
rename-param-name = tagged-ext-label
rename-param-value= tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
response-data = "*" SP response-payload CRLF
response-payload= resp-cond-state / resp-cond-bye /
mailbox-data / message-data / capability-data
search = "SEARCH" [search-return-opts]
SP search-program
search-correlator = SP "(" "TAG" SP tag-string ")"
search-program = ["CHARSET" SP charset SP]
search-key *(SP search-key)
;; CHARSET argument to SEARCH MUST be
;; registered with IANA.
search-return-data = search-modifier-name SP search-return-value
;; Note that not every SEARCH return option
;; is required to have the corresponding
;; ESEARCH return data.
search-return-opts = SP "RETURN" SP "(" [search-return-opt
*(SP search-return-opt)] ")"
search-return-opt = search-modifier-name [SP search-mod-params]
search-return-value = tagged-ext-val
;; Data for the returned search option.
;; A single "nz-number"/"number" value
;; can be returned as an atom (i.e., without
;; quoting). A sequence-set can be returned
;; as an atom as well.
search-modifier-name = tagged-ext-label
search-mod-params = tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
select = "SELECT" SP mailbox [select-params]
;; modifies the original IMAP SELECT command to
;; accept optional parameters
select-params = SP "(" select-param *(SP select-param) ")"
select-param = select-param-name [SP select-param-value]
;; a parameter to SELECT may contain one or
;; more atoms and/or strings and/or lists.
select-param-name= tagged-ext-label
select-param-value= tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
status-att-list = status-att-val *(SP status-att-val)
;; Redefines status-att-list from RFC 3501.
;; status-att-val is defined in RFC 3501 errata
status-att-val = ("MESSAGES" SP number) /
("RECENT" SP number) /
("UIDNEXT" SP nz-number) /
("UIDVALIDITY" SP nz-number) /
("UNSEEN" SP number)
;; Extensions to the STATUS responses
;; should extend this production.
;; Extensions should use the generic
;; syntax defined by tagged-ext.
store = "STORE" SP sequence-set [store-modifiers]
SP store-att-flags
;; extend [IMAP4] STORE command syntax
;; to allow for optional store-modifiers
store-modifiers = SP "(" store-modifier *(SP store-modifier)
")"
store-modifier = store-modifier-name [SP store-modif-params]
store-modif-params = tagged-ext-val
;; This non-terminal shows recommended syntax
;; for future extensions.
store-modifier-name = tagged-ext-label
tag-string = string
;; tag of the command that caused
;; the ESEARCH response, sent as
;; a string.
tagged-ext = tagged-ext-label SP tagged-ext-val
;; recommended overarching syntax for
;; extensions
tagged-ext-label = tagged-label-fchar *tagged-label-char
;; Is a valid RFC 3501 "atom".
tagged-label-fchar = ALPHA / "-" / "_" / "."
tagged-label-char = tagged-label-fchar / DIGIT / ":"
tagged-ext-comp = astring /
tagged-ext-comp *(SP tagged-ext-comp) /
"(" tagged-ext-comp ")"
;; Extensions that follow this general
;; syntax should use nstring instead of
;; astring when appropriate in the context
;; of the extension.
;; Note that a message set or a "number"
;; can always be represented as an "atom".
;; An URL should be represented as
;; a "quoted" string.
tagged-ext-simple = sequence-set / number
tagged-ext-val = tagged-ext-simple /
"(" [tagged-ext-comp] ")"4. Security Considerations 💀
this part is serious, so let's go 🙈 This document updates the ABNF in RFCs 2088, 2342, 3501, 3502, and 3516. The updated documents are where you need to look for the security considerations of the extensions they define 🔍
okay, real talk: the more complex a protocol gets, the more parser bugs show up. That includes buffer overflows, denial of service, and other classic security coding mistakes 😭 Whatever makes the parser more complicated also makes that situation worse. Whatever makes the parser more consistent and simpler helps 🫶 How much it helps depends on how many deployed IMAP extensions follow this document. Implementers are encouraged to deal with these issues when they extend existing implementations, and future IMAP extensions should aim for consistency and simplicity as much as they can 🌸
extensions to IMAP commands that are allowed in the NOT AUTHENTICATED state are even more sensitive to these issues. There's a bigger group of possible attackers before anyone logs in, and some IMAP servers run with elevated privileges in that state, so it's a whole vibe 😳 This document doesn't extend any commands allowed in the NOT AUTHENTICATED state. Future IMAP extensions to commands allowed in that state should favor simplicity over consistency or extensibility 👑
5. Normative References ✨
okay bestie, here's the reading list this spec leans on 📚
[KEYWORDS]Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 🔑[IMAP4]Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, March 2003. 📬[ABNF]Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005. 🧩[CHARSET]Freed, N. and J. Postel, "IANA Charset Registration Procedures", BCP 19, RFC 2978, October 2000. 🔤[MULTIAPPEND]Crispin, M., "Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension", RFC 3502, March 2003. 📎[NAMESPACE]Gahrns, M. and C. Newman, "IMAP4 Namespace", RFC 2342, May 1998. 🗂️[LITERAL+]Myers, J., "IMAP4 non-synchronizing literals", RFC 2088, January 1997. ⚡[BINARY]Nerenberg, L., "IMAP4 Binary Content Extension", RFC 3516, April 2003. 💾
6. Acknowledgements 🫶
this document is based on ideas from Pete Resnick, Mark Crispin, Ken Murchison, Philip Guenther, Randall Gellens, and Lyndon Nerenberg. they're literally the reason this exists, so main character energy for all of them 👑
BUT, and this is important, all errors and omissions are on the authors of this document. no blaming the brainstorm crew 💅
thanks to Philip Guenther, Dave Cridland, Mark Crispin, Chris Newman, Elwyn Davies, and Barry Leiba for comments and corrections. absolute legends 🌸
the literal8 syntax was taken from RFC 3516. ✨
Authors' Addresses 📮
Alexey Melnikov
Isode Limited
5 Castle Business Village
36 Station Road
Hampton, Middlesex, TW12 2BX
UK
EMail: Alexey.Melnikov@isode.comCyrus Daboo
EMail: cyrus@daboo.nameFull Copyright Statement 🔒
Copyright (C) The Internet Society (2006).
this document is subject to the rights, licenses and restrictions in BCP 78, and except as set forth there, the authors keep all their rights. 🧾
this document and the info in it are provided on an "AS IS" basis. THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. no warranties, no drama 🙈
Intellectual Property 💜
the IETF takes no position on the validity or scope of any Intellectual Property Rights or other rights that might be claimed to apply to the implementation or use of the technology in this document, or on whether any license under those rights might or might not be available. it also doesn't claim to have made any independent effort to find such rights. the procedures for rights in RFC documents are in BCP 78 and BCP 79. 📜
copies of IPR disclosures made to the IETF Secretariat, any assurances of licenses to be made available, or the result of an attempt to get a general license or permission for implementers or users to use those proprietary rights can be found in the IETF online IPR repository at http://www.ietf.org/ipr. 🗃️
the IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology required to implement this standard. send that info to the IETF at ietf-ipr@ietf.org. 🦋
Acknowledgement 🌈
funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). the end, and what a ride it was 🎀💖
📦 where this page comes from
- ietf: rfc4466 2006-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms