…TF, including the IPv6 documentation prefix [RFC3849] and example domain names [RFC2606]. Documentation also makes use of the ranges reserved in [RFC1918]. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "M…

…nnection to mail.example (where .example is the top-level domain specified in [ RFC2606 ]). The user would input his OpenID into his mail user agent when he configures the account. In this case, no association is attempted between the OpenID RP and the OP. The client will make us…

… including the IPv6 documentation prefix [ RFC3849 ] and example domain names [ RFC2606 ]. Documentation also makes use of the ranges reserved in [ RFC1918 ]. 2 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED"…

… including the IPv6 documentation prefix [ RFC3849 ] and example domain names [ RFC2606 ]. Documentation also makes use of the ranges reserved in [ RFC1918 ]. 2 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED"…

…:02 <dajobe-la> bwm: standard prefix for that too ("ex:") 14:35:16 <danbri> See RFC2606 Reserved Top Level DNS Names 14:35:21 <dajobe-la> Path: want to write things that look triples, but have things that aren't such as variables that want to use for explanation 14:35:23 <danbri>…

…ive subsection (leave the actual example where it was). Add and resolve issues "rfc2606-compliance" and "response-format". Update contact information for Alan Babich, Jim Davis and Surendra Reddy (no change tracking). February 8, 2007 Update BIND reference. TOC C.14. since draft-…

…be revised by updating the RFC through standard IETF RFC update processes (see [RFC2606] for a discussion of IETF process). It should say: Registrations may be revised by updating the RFC through standard IETF RFC update processes (see [RFC2026] for a discussion of IETF process).…

…be revised by updating the RFC through standard IETF RFC update processes (see [RFC2606] for a discussion of IETF process). It should say: Registrations may be revised by updating the RFC through standard IETF RFC update processes (see [RFC2026] for a discussion of IETF process).…

…f the POST method" (< >) o < >: "Normative and Informative references" o < >: " RFC2606 Compliance" o < >: "Informative references" o < >: "Redundant cross-references" Other changes: o Move definitions of 304 and 412 condition codes to [ Part4 F.3 . Since draft-ietf-httpbis-p3-pa…

…f the POST method" (< >) o < >: "Normative and Informative references" o < >: " RFC2606 Compliance" o < >: "Informative references" o < >: "Redundant cross-references" Other changes: o Move definitions of 304 and 412 condition codes to [ Part4 C.3 . Since draft-ietf-httpbis-p2-se…