Re: Launch: check command use beyond claims
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CD8C313E.4D4D9%[email protected]> |
James, We would need to define two forms (models) of the check extension, where the existing one defines a new verb of Claims Check when passing the "claims" phase and the second would not define a new verb but would simply be an extension to the availability check. Is this how you see it as well? Does anyone have an issue with adding support for both forms of the check extension? If would be up to server policy what forms of the check extension to support, where the first form is required to support the TMCH. -- JG [cid:A33273F3-033E-43FF-8A61-1BBD067A7B2C] James Gould Principal Software Engineer [email protected] 703-948-3271 (Office) 12061 Bluemont Way Reston, VA 20190 VerisignInc.com From: James Mitchell <[email protected]<mailto:[email protected]>> Date: Tuesday, April 9, 2013 11:28 AM To: EPP Provreg <[email protected]<mailto:[email protected]>> Subject: [provreg] Launch: check command use beyond claims Jim et al, The check command text should be updated to allow for checking availability of names available to a particular phase. One example is the phased-launch of an IDN table post general registration, where registrars can provide a phase, e.g. ZH-release, and the list of names they require availability for. The registrar would feed this information back to the registrant prior to their selection of names for submission in create commands. This should not require any change to the schema. I can provide text if required. Regards, James _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg
8A7A655D-9ED0-4D38-898D-E9E8B754666E[9].png
(image/png, 4 KB) - not displayed