Re: U-labels and draft-obispo-epp-idn-00
James Mitchell <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <8CEF048B9EC83748B1517DC64EA130FB6B2AB34671@off-win2003-01.ausregistrygroup.local> |
I agree with Andrew for including an optional "U-label" element. Server policy can dictate how it is used. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Andrew Sullivan > Sent: Wednesday, 15 February 2012 8:25 AM > To: [email protected] > Subject: [provreg] U-labels and draft-obispo-epp-idn-00 > > Hi, > > draft-obispo-epp-idn-00 includes a mechanism for indicating some sort > of code point selector (there called a language tag). I mentioned > before my reservation about this term "language tag", and suggested > that future developments would likely make something more generic > somewhat more useful (even if we continue to use RFC 5646 to generate > the tags that serve as identifiers, as I think we should). > > I noted today, however, another thing that bugs me. RFC 5731 makes > the <domain:name> data conform to RFC 952 as updated by RFC 1123. > At the risk of oversimplifying, this is the LDH rule. > > RFC 5891 section 4.1 suggests that it would be desirable to require > both the A-label and U-label as input, so that the registry side could > valdate whether the A-label actually corresponds to the desired > U-label. I know that some don't think this is a good policy to have, > but that's not relevant for this discussion; the question is, if > someone were going to implement such a policy, how could they? > > I'm wondering whether we couldn't make an optional element in this > proposed extension that would contain the name in U-label form. In > other words, in the U-label format, A-labels wouldn't be allowed. > > A repository, on receiving this, could validate that the A-label and > U-label matched. If they did not, it would be an error. > > Thoughts? > > A > > > -- > Andrew Sullivan > [email protected] > _______________________________________________ > provreg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/provreg _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg