> -----Original Message----- > From: Gould, James > Sent: Thursday, April 27, 2017 10:17 AM > To: Hollenbeck, Scott <shollenb...@verisign.com>; 'gal...@elistx.com' > <gal...@elistx.com>; 'regext@ietf.org' <regext@ietf.org> > Subject: Re: [EXTERNAL] Re: [regext] WG Last Call: > https://datatracker.ietf.org/doc/draft-ietf-regext-launchphase/ > > Scott, > > Thanks for review the draft. My responses to your feedback are embedded > below with a “JG-“ prefix.
[snip] > Section 2.2: > > "The Internet Corporation for Assigned Names and Numbers (ICANN) > Trademark Clearinghouse (TMCH) is the default Trademark Validator and is > reserved the Validator Identifier of "tmch"." > > And > > "The list of validator identifiers and the relationship to issuer > identifiers is out of scope for this document." > > This sounds like we might need an IANA registry of trademark validator > identifiers. If we don't have a registry, how do processors know which > values are valid? Does it matter? The text should be clear about this. I > don't the text can say "out of scope" while reserving a specific value for > one validator. > > JG-There is no intention on setting up an IANA registry for trademark > validator identifiers. The processor in this case is the server who will > define the set of accepted trademark validator identifiers based on > registry policy (e.g., what validators they decide to support). The only > generic trademark validator identifier that is known is “tmch”. The > intent of the extension is not to manage the set of validator identifiers > but to allow for the passing of the validator identifiers from client to > server. It is the responsibility of the server to ensure that the set of > acceptable validator identifiers are unique, which could be added to the > draft. Do you agree? Yes, if text is added to the draft to make it clear that these values are server-assigned I think the intent would be much clearer, but it still begs the question of how a client will be able to learn the set of valid values. How do you see that working? Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
