Merge pull request #2972 from sbingler/Remove3490

Remove references to RFC3490

draft-ietf-httpbis-rfc6265bis.md

@@ -47,18 +47,6 @@ normative:
   RFC1034:
   RFC1123:
   RFC2119:
-  RFC3490:
-    override: yes
-    title: "Internationalizing Domain Names in Applications (IDNA)"
-    seriesinfo:
-      RFC: 3490
-    date: 2003-03
-    author:
-      -
-        ins: P. Faltstrom
-        ins: P. Hoffman
-        ins: A. Costello
-    ann: See {{idna-migration}} for an explanation why the normative reference to an obsoleted specification is needed.
   RFC4790:
   RFC5234:
   RFC5890:
@@ -627,8 +615,8 @@ header fields sent to the server.
 
 The domain-value is a subdomain as defined by {{RFC1034}}, Section 3.5, and
 as enhanced by {{RFC1123}}, Section 2.1. Thus, domain-value is a string of
-{{USASCII}} characters, such as one obtained by applying the "ToASCII" operation
-defined in {{Section 4 of RFC3490}}.
+{{USASCII}} characters, such as an "A-label" as defined in
+{{Section 2.3.2.1 of RFC5890}}.
 
 The portions of the set-cookie-string produced by the cookie-av term are
 known as attributes. To maximize compatibility with user agents, servers SHOULD
@@ -1023,10 +1011,7 @@ A canonicalized host name is the string generated by the following algorithm:
 1.  Convert the host name to a sequence of individual domain name labels.
 
 2.  Convert each label that is not a Non-Reserved LDH (NR-LDH) label, to an
-    A-label (see {{Section 2.3.2.1 of RFC5890}} for the former and latter), or
-    to a "punycode label" (a label resulting from the "ToASCII" conversion in
-    {{Section 4 of RFC3490}}), as appropriate (see {{idna-migration}} of this
-    specification).
+    A-label (see {{Section 2.3.2.1 of RFC5890}} for the former and latter).
 
 3.  Concatenate the resulting labels, separated by a %x2E (".") character.
 
@@ -2014,18 +1999,6 @@ well-served by providing more semantic APIs. It is beyond the scope of this
 document to recommend specific API designs, but there are clear benefits to
 accepting an abstract "Date" object instead of a serialized date string.
 
-## IDNA Dependency and Migration {#idna-migration}
-
-IDNA2008 {{RFC5890}} supersedes IDNA2003 {{RFC3490}}. However, there are
-differences between the two specifications, and thus there can be differences
-in processing (e.g., converting) domain name labels that have been registered
-under one from those registered under the other. There will be a transition
-period of some time during which IDNA2003-based domain name labels will exist
-in the wild. User agents SHOULD implement IDNA2008 {{RFC5890}} and MAY
-implement {{UTS46}} or {{RFC5895}} in order to facilitate their IDNA transition.
-If a user agent does not implement IDNA2008, the user agent MUST implement
-IDNA2003 {{RFC3490}}.
-
 # Privacy Considerations
 
 Cookies' primary privacy risk is their ability to correlate user activity. This