
datatracker.ietf.org/doc/rfc5895
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
10- 72 links todatatracker.ietf.org
- 6 links towww.ietf.org
- 4 links towww.rfc-editor.org
- 2 links togithub.com
- 1 link tomailarchive.ietf.org
- 1 link tostatus.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.iab.org
Search Engine Appearance
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

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- titleRFC 5895 - Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- article:sectionIndividual Internet-Draft
Open Graph Meta Tags
5- og:titleRFC 5895: Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008
- og:urlhttps://datatracker.ietf.org/doc/rfc5895/
- og:site_nameIETF Datatracker
- og:descriptionIn 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:typearticle
Link Tags
13- alternate/feed/document-changes/rfc5895/
- apple-touch-iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/rfc5895/
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.43.1/ietf/images/ietf-logo-nor-16.png
Emails
5- paul.hoffman%40icann.org
- resnick%40episteme.net
- stpeter%40stpeter.im
- [email protected]?subject=Mail%20regarding%20rfc5895
- [email protected]
Links
90- https://datatracker.ietf.org
- https://datatracker.ietf.org/accounts/create
- https://datatracker.ietf.org/accounts/login/?next=/doc/rfc5895
- https://datatracker.ietf.org/accounts/reset
- https://datatracker.ietf.org/accounts/settings