datatracker.ietf.org/doc/rfc5895

Preview meta tags from the datatracker.ietf.org website.

Linked Hostnames

10

Search Engine Appearance

Google

https://datatracker.ietf.org/doc/rfc5895

RFC 5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008

Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 (RFC 5895, September 2010)



Bing

RFC 5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008

https://datatracker.ietf.org/doc/rfc5895

Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 (RFC 5895, September 2010)



DuckDuckGo

https://datatracker.ietf.org/doc/rfc5895

RFC 5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008

Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 (RFC 5895, September 2010)

  • General Meta Tags

    10
    • title
      RFC 5895 - Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • article:section
      Individual Internet-Draft
  • Open Graph Meta Tags

    5
    • og:title
      RFC 5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008
    • og:url
      https://datatracker.ietf.org/doc/rfc5895/
    • og:site_name
      IETF Datatracker
    • og:description
      In the original version of the Internationalized Domain Names in Applications (IDNA) protocol, any Unicode code points taken from user input were mapped into a set of Unicode code points that "made sense", and then encoded and passed to the domain name system (DNS). The IDNA2008 protocol (described in RFCs 5890, 5891, 5892, and 5893) presumes that the input to the protocol comes from a set of "permitted" code points, which it then encodes and passes to the DNS, but does not specify what to do with the result of user input. This document describes the actions that can be taken by an implementation between receiving user input and passing permitted code points to the new IDNA protocol. This document is not an Internet Standards Track specification; it is published for informational purposes.
    • og:type
      article
  • Link Tags

    13
    • alternate
      /feed/document-changes/rfc5895/
    • apple-touch-icon
      https://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/rfc5895/
    • icon
      https://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-16.png

Emails

5

Links

90