…ng an insecure or untrusted directory service, such as the Domain Name System [ RFC1034 ] without DNS Security (DNSSEC) [ RFC4033 ]. SHA-1 is used to derive SASL mechanism names, but no traditional cryptographic properties are required -- the required property is that the truncat…
…S, and DNS terminology. See [ RFC5280 ], [ RFC4033 ], [ RFC5246 ], and STD 13 [ RFC1034 ] [ RFC1035 ], respectively, for these terms. In addition, terms related to TLS-protected application services and DNS names are taken from [ RFC6125 ]. Hoffman & Schlyter Standards Track [Pag…
…t following the at-sign MUST be a valid, fully qualified internet domain name [ RFC1034 ] controlled by the person or organization defining the name. Names are case-sensitive, and MUST NOT be longer than 64 characters. It is up to each domain how it manages its local namespace. I…
…it "." 1*digit port = *digit Hostnames take the form described in Section 3 of [RFC1034] and Section 2.1 of [RFC1123] : a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumeric character and possibly also containing "-" characters. …
…er Agent ( [RFC5598], Section 4.2.1 ). RR: A DNS resource record as defined in [RFC1034], Section 3.6 . RRset: An RRset ( [RFC2181], Section 5 ) is a group of DNS resource records that share the same label, class, and type. Dukhovni & Hardaker Standards Track [Page 5] RFC 7672 SM…
… verification by looking up a fingerprint of the server public key in the DNS [ RFC1034 ][RFC1035] and using Domain Name System Security Extensions (DNSSEC) [ RFC4033 ][RFC4034][ RFC4035 ] to verify the lookup. RFC 4255 [ RFC4255 ] describes how to store the cryptographic fingerp…
…ation to claim some responsibility for a message by associating a domain name [ RFC1034 ] with the message [ RFC5322 ], which they are authorized to use. This can be an author's organization, an operational relay, or one of their agents. Assertion of responsibility is validated t…
…t following the at-sign MUST be a valid, fully qualified internet domain name [ RFC1034 ] controlled by the person or organization defining the name. Names are case-sensitive, and MUST NOT be longer than 64 characters. It is up to each domain how it manages its local namespace. I…
…he name MUST be in the "preferred name syntax", as specified by Section 3.5 of [RFC1034] and as modified by Section 2.1 of [RFC1123] . Note that while uppercase and lowercase letters are allowed in domain names, no significance is attached to the case. In Cooper, et al. Standards…
…h 9 domain-av = "Domain=" domain-value domain-value = <subdomain> ; defined in [RFC1034], Section 3.5 , as ; enhanced by [RFC1123], Section 2.1 path-av = "Path=" path-value path-value = <any CHAR except CTLs or ";"> secure-av = "Secure" httponly-av = "HttpOnly" extension-av = <an…
…k [Page 20] RFC 3986 URI Generic Syntax January 2005 defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123] . Such a name consists of a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumeric character and possibly also con…
…k [Page 20] RFC 3986 URI Generic Syntax January 2005 defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123] . Such a name consists of a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumeric character and possibly also con…
…h 9 domain-av = "Domain=" domain-value domain-value = <subdomain> ; defined in [RFC1034], Section 3.5, as ; enhanced by [RFC1123], Section 2.1 path-av = "Path=" path-value path-value = <any CHAR except CTLs or ";"> secure-av = "Secure" httponly-av = "HttpOnly" extension-av = <any…
…. The part following the at-sign MUST be a valid, fully qualified domain name [ RFC1034 ] controlled by the person or organization defining the name. Names are case-sensitive, and MUST NOT be longer than 64 characters. It is up to each domain how it manages its local namespace. I…
…. The part following the at-sign MUST be a valid, fully qualified domain name [ RFC1034 ] controlled by the person or organization defining the name. Names are case-sensitive, and MUST NOT be longer than 64 characters. It is up to each domain how it manages its local namespace. I…