Where results make sense

About us   |   Why use us?   |   Reviews   |   PR   |   Contact us

[No title] While Nameprep normalizes domain names so that the users have an improved chance of getting the right domain name from information provided in other forms, as required for I18N, Nameprep does not handle any localization (L10N). In step 4.1, IDL validation is done by checking that every code point in the Nameprep processed IDL is a code point allowed by the "valid code point" column of the character variant table for the language. Step 6 generates the list of variants including the Nameprep processed IDL which to be activated and Step 7 generates the list of reserved variants. www.iana.org /cctld/draft-jseng-idn-admin-02.txt   (4875 words)

RFC 3491 (rfc3491) - Nameprep: A Stringprep Profile for Internationalized IDNA calls nameprep for each label in a domain name, not for the whole domain name. Name of this profile: Nameprep RFC in which the profile is defined: This document. Indicator whether or not this is the newest version of the profile: This is the first version of Nameprep. www.faqs.org /rfcs/rfc3491.html   (1053 words)

ICANN : IDN Committee : Briefing Paper on IDN Permissible Code Point Problems It appears that the IETF's IDN Working Group is inclined to permit most such characters: there is no technical reason not to do so, and it is technically rational to take the position that their implementation and use is the responsibility of the implementers and users (or, perhaps, the registries or registrars). A related question is whether the exclusion (temporary or permanent) of the problematic IDN code points in the hostname definition should be performed through the filtering (string preparation or "nameprep") that is part of the advancing IDN standard, or by advising registries and registrars not to permit their registration. Notably, the exclusion of certain code points is already a part of the [NAMEPREP] documentation, and was anticipated both in the original DNS documents [RFC 1034], and in the most recent draft of "Requirements for Internationalized Domain Names," (Z. Wenzel and J. Seng, eds.), draft-ietf-idn-requirements, work in progress, November 2001. www.icann.org /committees/idn/idn-codepoint-paper.htm   (1740 words)

idn.conf Perform NAMEPREP, which is a starndard name preparation process for internationalized domain names. Convert the nameprepped name to IDN encoding, which is the standard encoding for internationalized domain names (also known as ASCII-compatible encoding, ACE), and vice versa. Nameprep entry specifies the version of NAMEPREP, which is a specification of ‘‘canonicalization’’ process of internationalized domain name before it is converted to the IDN encoding. www.math.ucla.edu /computing/docindex/bind-utils-man-6.html   (821 words)

[No title] The prospective IDL is processed by using Nameprep to apply the normalizations and exclusions globally required to use IDNA. If the Nameprep processing fails, then the IDL is invalid and the registration process must stop. If the Nameprep processing fails for any Preferred Variant Label (this is unlikely to occur if the Preferred Variants are processed through Nameprep before being placed in the table), then that variant label will be removed from the list. www.isi.edu /in-notes/rfc3743.txt   (7955 words)

ietf-idn-jpchar-01.txt Local mapping of Japanese characters in multilingual domain name labels Name preparation [NAMEPREP] practically works well for Japanese characters but there are some exceptions. Differences between -00 and -01 drafts Focused on local mapping to make NAMEPREP work as preferred, therefore additional normalization rule is no longer defined and related table was removed. NAMEPREP now works well for compatible characters such as FULL-WIDTH alpha-numerics and/or HALF-WIDTH Katakana, therefore compatible mapping table was removed. ietfreport.isoc.org /idref/draft-ietf-idn-jpchar   (738 words)

RE: iSCSI NDT: Nameprep additions For now, these changes will assume that nameprep will become an RFC before we do; if this is a problem, we will do some more cut-and-paste later. Nameprep is a method designed by the Internationalized Domain Name (IDN) working group to translate human-typed strings into a format that can be compared as opaque strings, and does not include punctuation, spacing, dicritical marks, or other characters that could get in the way of transcribability. Note that in most cases, the nameprep process does not need to be implemented: - If the names are just generated using lower-case (in any character set) plus digits, no normalization is required. www.pdl.cmu.edu /mailinglists/ips/mail/msg05964.html   (386 words)

[No title] Internet Draft Paul Hoffman draft-ietf-idn-nameprep-11.txt IMC & VPNC June 24, 2002 Marc Blanchet Expires in six months ViaGenie Nameprep: A Stringprep Profile for Internationalized Domain Names Status of this memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Name of this profile: Nameprep RFC in which the profile is defined: This document Indicator whether or not this is the newest version of the profile: This is the first version of Nameprep. ---------- Add to the text of section 9 with: ---------- Name of this profile: Nameprep RFC in which the profile is defined: This document Indicator whether or not this is the most current version of the profile: This is the first version of Nameprep. www.iana.org /cctld/draft-ietf-idn-nameprep-11.txt   (1063 words)

[No title] Nameprep is used to process domain name labels, not domain names. Every program that uses "special" characters in conjunction with domain names may be vulnerable to attack based on the new characters allowed by this specification. The IDN Nameprep design team made many useful changes to the document. www.ietf.org /rfc/rfc3491.txt   (1028 words)

Nameprep - Wikipedia, the free encyclopedia Nameprep is the process of Unicode NFKC normalization, case-folding, mapping lookalike characters together, and elimination of restricted codepoints applied to text before it is suitable to represent a domain name, or other such canonical name. Nameprep is defined in RFC 3491, "Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)", as a profile of Stringprep, which is described in RFC 3454, "Preparation of Internationalized Strings ("stringprep")." This page was last modified 12:28, 3 January 2006. en.wikipedia.org /wiki/Nameprep   (108 words)

RFC3490 If it fails when processing a domain name, that domain name cannot be used as an internationalized domain name and the application has to have some method of dealing with this failure. IDNA requires that implementations process input strings with Nameprep [NAMEPREP], which is a profile of Stringprep [STRINGPREP], and then with Punycode [PUNYCODE]. RFC 3490 IDNA March 2003 fully implement Nameprep and Punycode; neither Nameprep nor Punycode are optional. www.unix.org.ua /rfc/rfc3490.html   (6084 words)

Nameprep/IDNA/Stringprep Nameprep and Stringprep have been designed in such a way that new Unicode characters can be accommodated. Nameprep can be revised without revising Stringprep, by simply having Nameprep provide some of its own character tables, rules, etc. Nameprep was designed so that if Unicode evolves in a backward compatible way (new characters added, old normalization mappings unchanged), then Nameprep can evolve along with it in a backward compatible way, with no need to change the ACE prefix. nameprep.org   (2414 words)

RE: [idn] Versions of Nameprep The NamePrep RFC should be either updated or obsoleted. Maybe, but just because the question on what codepoints are allocated or not (and because of that what is possible to register as a domainname) is such an important question, I would belive that both IANA and IESG would suggest handling the registration through an RFC. Some certain applications might though be >implemented to treat them as U, or AIO after first warning the user >about the fact that the character is of class U -- all based on the >use of the domainname in the specific application. psg.com /lists/idn/idn.2000/msg01805.html   (971 words)

[No title] It is not surprising that since CJK is driving internationalization, that proposals would be specific to that. Next step will be for the authors to clarify the relation between the various proposals for processing into a cohesive architecture, namely nameprep, tsconv, jpchar, hangeulchar. Nameprep discussion back (some time remaining) Paul Hoffman: Good (from a marketing sense) user interfaces will do a lot of mucking with input. icann.org /montevideo/idn-london-minutes.txt   (1449 words)

[No title] It specifies that Nameprep is used as the stringprep profile for domain names, and that Punycode is the relevant the encoding mechanism use for use in generating an ASCII-compatible ("ACE") form of the name. The result of the nameprep Klensin & Faltstrom Expires June 5, 2006 [Page 4] Internet-Draft Framework for IDN December 2005 algorithm is a string containing a subset of the Unicode Character set, normalized and case folded so that case insensitive comparison can be made. This would represent a restriction of the model of characters permitted in IDN labels, and it contrasts with the approach used to develop the original IDNA/ nameprep tables: that approach was to include all Unicode characters that there was not a clear reason to exclude. www.iab.org /documents/drafts/draft-iab-idn-nextsteps-00.txt   (6888 words)

UTR# 36: Unicode Security Considerations Although Nameprep itself is currently limited to Unicode 3.2, the same methodology can be applied by implementations that need to support more up-to-date versions of Unicode. If there is a whitelist, and the domain name is visually confusable with a whitelist domain name, but not identical to it (after nameprep), alert the user. The user with valid access rights to a certain resource actually cannot access it, because the binary representation of user ID used for the user registry is different from the one specified in the access control list. www.unicode.org /reports/tr36   (10193 words)

Re: [idn] nameprep vs. stringprep I'll have to wait to see what the impact of this change is, but on the surface, the immediate affect will be that this draft will no longer be able to encourage the creation of stringprep profiles for specific resource record owner names and RR data. Until now, domain names which require syntaxes that were not compatible with nameprep could create their own stringprep profiles, but if the prohibitions go into stringprep, then these domain names will have to be defined separately from the stringprep family altogether. Kerberos realms are normally uppercased, so an i18n equivalent of those may have needed a separate stringprep profile as well. www.imc.org /idn/mail-archive/msg06449.html   (342 words)

ICU Userguide NamePrep is a profile of StringPrep for use in IDNA. The domain labels are processed by StringPrep algorithm by using the rules specified by NamePrep profile. The output of this step is then encoded by using Punycode and an ACE prefix is added to denote that the text is encoded using Punycode. icu.sourceforge.net /userguide/StringPrep.html   (1819 words)

4.9.3 encodings.idna -- Internationalized Domain Names in Applications RFC 3492 (Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)). When receiving host names from the wire (such as in reverse name lookup), no automatic conversion to Unicode is performed: Applications wishing to present such host names to the user should decode them to Unicode. also implements the nameprep procedure, which performs certain normalizations on host names, to achieve case-insensitivity of international domain names, and to unify similar characters. www.indiana.edu /~wmhome/tool_guide_info/python/lib/module-encodings.idna.html   (300 words)

Repository - markup - cvs: libidn/doc/specifications/draft-iab-idn-nextsteps-04.txt   (Site not responding. Last check: 2007-10-10) It specifies that Nameprep is used as the Stringprep profile for domain names, and that Punycode is the relevant encoding mechanism for use in generating an ASCII-compatible ("ACE") form of the name. The IETF should also consider whether there are significant advantages to mapping some groups of characters, such as code points assigned to font variations, into others or whether clarity and comprehensibility for the user would be better served by simply prohibiting those characters. More generally, it appears that it would be worthwhile for the IETF to review whether the Unicode normalization rules now invoked by the Stringprep profile in Nameprep are optimal for the DNS or whether more restrictive rules, or an even more restrictive set of permitted character combinations, would provide better support for DNS internationalization. josefsson.org /cgi-bin/viewcvs.cgi/libidn/doc/specifications/draft-iab-idn-nextsteps-04.txt?rev=1.1&view=auto   (9706 words)

RE: [idn] Versions of Nameprep If "Unicode will be updated fairly frequently", are you suggesting that nameprep ultimately be documented in a base RFC and then a chain of "update" RFCs that track the Unicode updates? In a particular version of NamePrep, the following lists of code points can be generated based on the version of Unicode and the mapping/prohibition tables. In any subsequent version of NamePrep, because of updates to Unicode, code points from U will move to D, AI or AIO. psg.com /lists/idn/idn.2000/msg01804.html   (821 words)

UNIX man pages : idn_decodename2 (3EXT)   (Site not responding. Last check: 2007-10-10) NAMEPREP (IDN_NAMEPREP, IDN_UNASCHECK) Perform name preparation (NAMEPREP), which is a standard process for name canonicalizaion of internationalized domain names. NAMEPREP consists of 5 steps: mapping, normalization, prohibited character check, bidirectional text check, SunOS 5.10 Last change: 15 Aug 2003 4 Extended Library Functions idn_decodename(3EXT) and unassigned codepoint check. NAMEPREP (IDN_NAMEPREP, IDN_UNASCHECK) Perform name preparation (NAMEPREP), which is a standard process for name canonicalizaion of internationalized SunOS 5.10 Last change: 15 Aug 2003 5 Extended Library Functions idn_decodename(3EXT) domain names. www.cs.duke.edu /cgi-bin/man2.cgi?idn_decodename2+3EXT   (1651 words)

trinler.net - Linux/UNIX Befehlssyntax In this mode, local mapping and NAMEPREP are not performed since IDN-encoded names should already be normalized. If it is not, the name will be output in IDN encoding, not in the local encoding. NAMEPREP Perform name preparation (NAMEPREP) for each label in the domain name. www.trinler.de /de/linux/man.html?command=idnconv   (1517 words)

DENIC eG - FAQ about IDNs The first stage is the normalization of the IDN and this is handled by a routine called "nameprep" (RFC3491). The first of these stages is a process called "nameprep" (described fully in RFC3491 "Nameprep: A Stringprep for Internationalized Domain Names (IDN)) and it generates a normalized form of the IDN. This includes converting all upper-case characters to lower-case ones and converting characters that are equivalent into their normalized form (one example of equivalent characters is the German ß and ss). www.denic.de /en/faqs/idn_faqs/index.html   (2672 words)

Repository - markup - cvs: libidn/doc/specifications/draft-iab-idn-nextsteps-03.txt   (Site not responding. Last check: 2007-10-10) It is designed to meet the specific needs of IDNs and, in particular, to support case-folding for scripts that support what are traditionally known as upper and Klensin and Faltstrom Expires August 17, 2006 [Page 4] Internet-Draft IAB -- IDN Next Steps February 2006 lower case forms of the same letters. The result of the nameprep algorithm is a string containing a subset of the Unicode Character set, normalized and case folded so that case insensitive comparison can be made. The current nameprep and stringprep algorithms use mapping tables to "normalize" different representations of the same text to a single form so that matching is possible. josefsson.org /cgi-bin/viewcvs.cgi/libidn/doc/specifications/draft-iab-idn-nextsteps-03.txt?rev=1.1&view=auto   (9516 words)

RE: draft-santesson-tls-ume Last Call comment It is RECOMMENDED that the server > processes the user_principal_name with a stringprep profile > [STRINGPREP] appropriate for the identity in question, such as > Nameprep [NAMEPREP] for the portion domain portion of UPN > and SASLprep [SASLPREP] for the user portion of the UPN. I note that SASLprep is case-insensitive and hence may not be appropriate for the user portion of a UPN. I note that Nameprep has to be applied component wise. www.mail-archive.com /ietf@ietf.org/msg26608.html   (1208 words)

Try your search on: Qwika (all wikis)

About us   |   Why use us?   |   Reviews   |   Press   |   Contact us   Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.