…acter) repertoire" and "character encoding scheme" are defined in Section 2 of [RFC6365] . 2 . The 'Basic' Authentication Scheme The Basic authentication scheme is based on the model that the client needs to authenticate itself with a user-id and a password for each protection sp…
…s used in this document are defined in [ RFC7564 ], [ RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to …
…nology Many important terms used in this document are defined in [ RFC5890 ], [ RFC6365 ], [ RFC7564 ], and [ Unicode ]. The term "non-ASCII space" refers to any Unicode code point having a Unicode general category of "Zs", with the exception of U+0020 (here called "ASCII space")…
US
rfc7622
https://www.rfc-editor.org/rfc/inline-errata/rfc7622.html
…nt terms used in this document are defined in [RFC7564], [RFC5890], [RFC6120], [RFC6365], and [Unicode]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be …
…rms used in this document are defined in [ RFC7564 ], RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to …
…acter) repertoire" and "character encoding scheme" are defined in Section 2 of [RFC6365] . The 'Basic' Authentication Scheme The Basic authentication scheme is based on the model that the client needs to authenticate itself with a user-id and a password for each protection space …
…s define many IDN-specific terms such as "LDH label", "A-label", and "U-label". RFC6365 defines more terms that relate to internationalization (some of which relate to IDNs); RFC6055 has a much more extensive discussion of IDNs, including some new terminology. Subdomain: "A domai…
…ization", "protocol element", and "regular expression" as they are defined in [ RFC6365 ]. The ABNF notation defines its terminal values to be non-negative integers (code points) that are a superset of the US-ASCII coded character set [ ASCII ]. This specification defines termina…
…osen to adopt the file extension of .mjs for this purpose. 4. Encoding Refer to RFC6365 for a discussion of terminology used in this section. Source text (as defined in the section "Source Text" in ECMA-262 ) can be binary source text. Binary source text is a textual data object …
…rms used in this document are defined in [ RFC7564 ], RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to …
…cter encoding scheme", "charset", and "protocol element" as they are defined in RFC6365 2.2. Requirements Notation The key words " MUST ", " MUST NOT ", REQUIRED ", " SHALL ", " SHALL NOT ", SHOULD ", " SHOULD NOT ", RECOMMENDED ", " NOT RECOMMENDED ", MAY ", and " OPTIONAL " in …
…define many IDN-specific terms such as "LDH label", "A-label", and "U-label". [ RFC6365 ] defines more terms that relate to internationalization (some of which relate to IDNs); [ RFC6055 ] has a much more extensive discussion of IDNs, including some new terminology. Subdomain: "A…
…ter encoding scheme", "charset", and "protocol element" as they are defined in [RFC6365] 2.2. Requirements Notation The key words " MUST ", " MUST NOT ", " REQUIRED ", " SHALL ", " SHALL NOT ", " SHOULD ", " SHOULD NOT ", " RECOMMENDED ", " NOT RECOMMENDED ", " MAY ", and " OPTIO…
…cter encoding scheme", "charset", and "protocol element" as they are defined in RFC6365 2.2. Requirements Notation The key words " MUST ", " MUST NOT ", REQUIRED ", " SHALL ", " SHALL NOT ", SHOULD ", " SHOULD NOT ", RECOMMENDED ", " NOT RECOMMENDED ", MAY ", and " OPTIONAL " in …
…acter) repertoire" and "character encoding scheme" are defined in Section 2 of [RFC6365] . The 'Basic' Authentication Scheme The Basic authentication scheme is based on the model that the client needs to authenticate itself with a user-id and a password for each protection space …