To:
"Klaus Malorny" <Klaus.Malorny@knipp.de>, <ietf-provreg@cafax.se>
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Thu, 28 Jul 2005 09:24:03 -0400
Content-class:
urn:content-classes:message
Sender:
owner-ietf-provreg@cafax.se
Thread-Index:
AcWTVARsK0qyUOJmQ2urNk1fmVK5TwAIxqPw
Thread-Topic:
Clarification re. localized data in EPP Contact Mapping (RFC3733)
Subject:
[ietf-provreg] RE: Clarification re. localized data in EPP Contact Mapping (RFC3733)
> -----Original Message----- > From: Klaus Malorny [mailto:Klaus.Malorny@knipp.de] > Sent: Thursday, July 28, 2005 5:09 AM > To: ietf-provreg@cafax.se; Hollenbeck, Scott > Subject: Clarification re. localized data in EPP Contact > Mapping (RFC3733) > > > > Hi Scott et al., > > I am a bit in doubt whether I understand the EPP Contact > Mapping document > (RFC3733) correctly regarding the use of localized data for the > name/organization and address, therefore I would appreciate > if you could comment it: This is the relevent text: "One or two <contact:postalInfo> elements that contain postal address information." and "If an internationalized form (type="int") is provided, element content MUST be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, element content MAY be represented in unrestricted UTF-8." > - IMHO it is within the registry's policy to accept only > "loc" versions or > only "int" versions. EPP does not mandate that both are accepted. Agreed. "One or two". > - IMHO it is within the registry's policy to accept only a > subset of > the Unicode character set (which is still a superset of > ASCII) for > the "loc" versions. EPP does not mandate that the full > Unicode set > is accepted. Agreed. "MAY be represented in unrestricted UTF-8", not "MUST". -Scott-