Re: draft-kong-epp-cdn-dnssec-mapping-00 Submitted for Review
"Gould, James" <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <CACC3550.1A3AD%[email protected]> |
Ning, Are you saying that the CDN's inherit all of the attributes of the OCDN except for the DNSSEC attributes that can't? Wouldn't it be easier and more standard to treat the CDN's as separate domains related to the OCDN that are automatically created when creating the OCDN, meaning that the RFC 5910 could be used as is on a <domain:update> with the <domain:name> element containing the CDN instead of the OCDN? It would be up to registry policy what other attributes (e.g. name servers, statuses) can be set on a per CDN basis. Since the CDN is linked to the OCDN the <domain:create>, <domain:delete>, and <domain:transfer> wouldn't apply directly the CDN's, but certainly <domain:check>, <domain:update>, and <domain:info> could. One extension that would be useful for CDN would be to return the list of CDN's in a info response of the OCDN and to require the CDN list on a transfer request of the OCDN to make it explicit from the gaining Registrar that they're transferring the OCDN along with the list of CDN's and that they support the management of CDN's. Returning the list of CDN's could be based on the inclusion of the CDN extension URI in the login services. A nit on the draft is to use camel case for the element names. -- JG James Gould Principal Software Engineer [email protected] 703-948-3271 21345 Ridgetop Circle LS2-2-1 Dulles, VA 20166 VerisignInc.com On 10/25/11 12:27 AM, "Ning Kong" <[email protected]> wrote: >Hi folks, > >I submitted >http://www.ietf.org/id/draft-kong-epp-cdn-dnssec-mapping-00.txt >which proposes an extension of EPP DNSSEC mapping [RFC5910] especially >for variant Chinese Domain Names (CDNs). By this extension, a client >can create, add, and remove DS information or key data information for >more than one domain name in the same time through one EPP >transaction. > >Any comments on this draft are welcomed. > >Thanks, > >Ning >_______________________________________________ >provreg mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/provreg _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg