…I参照 (IRI reference) は、以下のステップを適用してURI参照に変換することのできる文字列である。] ホスト名部が存在する場合には、それを、 [RFC3490] の Section 4.1 に指定された ToASCII 演算を、UseSTD3ASCIIRules フラグと AllowUnassigned フラグを TRUE に設定して使って変換する。 すべての 追加文字 を、以下のとおりエスケーピングする。 それぞれの追加文字を、1個以上のバイトとして、UTF-8 [RFC3629] を変換する。 結果として得られたバイトを、URIエスケ…

…plications of internationalization The IETF has adopted a series of proposals ([RFC3490] - [RFC3492]) whose purpose is to permit encoding internationalized (i.e., non- ASCII) names in the DNS. The primary standard, and the group generically, are known as "IDNA". The actual string…

…lications of internationalization The IETF has adopted a series of proposals ([ RFC3490 ] - [ RFC3492 ]) whose purpose is to permit encoding internationalized (i.e., non- ASCII) names in the DNS. The primary standard, and the group generically, are known as "IDNA". The actual str…

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

…DNA2003 The IDNA2003 specification is defined by a cluster of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): …

…tibility, many existing XMPP implementations and deployments support IDNA2003 [ RFC3490 for domainparts, and the stringprep [ RFC3454 ] profiles Nodeprep and Resourceprep [ RFC3920 ] for localparts and resourceparts. Saint-Andre Standards Track [Page 15] RFC 7622 XMPP Address For…

…lications of internationalization The IETF has adopted a series of proposals ([ RFC3490 ] - [ RFC3492 ]) whose purpose is to permit encoding internationalized (i.e., non- ASCII) names in the DNS. The primary standard, and the group generically, are known as "IDNA". The actual str…

…lications of internationalization The IETF has adopted a series of proposals ([ RFC3490 ] - [ RFC3492 ]) whose purpose is to permit encoding internationalized (i.e., non- ASCII) names in the DNS. The primary standard, and the group generically, are known as "IDNA". The actual str…

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

…DNA2003 The IDNA2003 specification is defined by a cluster of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): …

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

…ules are aligned with comparison rules established in current RFCs, including [ RFC3490 ], [ RFC3987 ], and [ RFC4518 ]. * Sections 4.1.2.4 and 4.1.2.6 incorporate the conditions for continued use of legacy text encoding schemes that were specified in [ RFC4630 ]. Where in use by…

… for resolution via the DNS, the name must be transformed to the IDNA encoding [RFC3490] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI resol…

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…

…for resolution via the DNS, the name must be transformed to the IDNA encoding [ RFC3490 ] prior to name lookup. URI producers should provide these registered names in the IDNA encoding, rather than a percent-encoding, if they wish to maximize interoperability with legacy URI reso…