…s, web pages and software. Must , Required , or Shall - an absolute requirement RFC2119 . Must Not or Shall Not - an absolute prohibition RFC2119 . Should or Recommended - there may be valid reasons to ignore this requirement but the full implications must be understood and caref…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 3 . Addresses 3.1 . Fundamentals An XMPP entity is anything that can communicate using XMPP. For historical reasons, the network address of an XMPP entity is called a JID. A valid JID is a …

…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Addresses 3.1. Fundamentals An XMPP entity is anything that can communicate using XMPP. For historical reasons, the network address of an XMPP entity is called a JID. A valid JID is a str…

…", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 ]. . Addresses 3.1 . Fundamentals An XMPP entity is anything that can communicate using XMPP. For historical reasons, the network address of an XMPP entity is called a JID. A valid JID is a st…

… RFC - Best Current Practice (May 2017) Errata Updates RFC 2119 Was draft-leiba-rfc2119-update (individual) Author Barry Leiba 2019-07-11 RFC stream Internet Engineering Task Force (IETF) Formats txt html pdf htmlized bibtex IESG Responsible AD Ben Campbell Send notices to (None)…

…", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 ]. . Addresses 3.1 . Fundamentals An XMPP entity is anything that can communicate using XMPP. For historical reasons, the network address of an XMPP entity is called a JID. A valid JID is a st…

…2017 . Clarifying Capitalization of Key Words The following change is made to [ RFC2119 ]: === OLD === In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words a…

rfc2119 This is a purely informative rendering of an RFC that includes verified errata. This rendering may not be used as a reference. The following 'Verified' errata have been incorporated in this document: EID 493 EID 494 EID 495 EID 496 EID 498 EID 499 EID 500 EID 5101 Network…

…references will be mentioned for each checkpoint. This document uses RFC 2119 [ RFC2119 ] keywords (capitalized MUST, MAY, SHOULD etc.) when referring to behaviors clearly defined by a normative specification. When not capitalized, these words should be interpreted as regular lan…

…g terms are used in this specification. These terms extend the definitions in [ RFC2119 ] in ways based upon similar definitions in ISO/ IEC 9945-1:1990 [ POSIX.1 ]: May With respect to implementations, the word "may" is to be interpreted as an optional feature that is not requir…

…", and "OPTIONAL" in this specification are to be interpreted as described in [ RFC2119 ]. 2.2 . Characters, Encodings, Charsets Both XML (in an XML or Text declaration using the encoding pseudo- attribute) and MIME (in a Content-Type header field using the charset parameter) use…

… and SHOULD NOT in this document are to be interpreted as described in BCP 14 [ RFC2119 ] [ RFC8174 ] when, and only when, they appear in all capitals, as shown here. This document describes best practices for the authors of other specifications, as well as recommendations for im…

…17 2 . Clarifying Capitalization of Key Words The following change is made to [ RFC2119 ]: === OLD === In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words a…

… SHOULD, and SHOULD NOT are used in this document in accordance with RFC 2119 [ RFC2119 ]. Please send comments on this finding to the publicly archived TAG mailing list www-tag@w3.org ( archive ). Relevant Principles of Web Architecture Use GET for addressability Dereferencing U…

… SHOULD, and SHOULD NOT are used in this document in accordance with RFC 2119 [ RFC2119 ]. Please send comments on this finding to the publicly archived TAG mailing list www-tag@w3.org ( archive ). Registration of Media Types by W3C Working Groups Consistency of Media Types and R…