Re: Launch Phase EPP Extension Version 08/Notifications

On 28/03/13 14:58, Gould, James wrote:
> Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension
> Mapping to Version 08.  You can find the draft at the URL
> http://tools.ietf.org/html/draft-tan-epp-launchphase-08.  This version
> includes the following changes:
>
>     1.  Added support for use of the launch statuses and poll messaging for
> Launch Registrations based on feedback from Sharon Wodjenski and Trung
> Tran.
>     2.  Incorporated changes based on updates or clarifications in
> draft-lozano-tmch-func-spec-01
> <http://tools.ietf.org/html/draft-lozano-tmch-func-spec-01>, which include:
>         1.  Removed the unused <launch:generatedDate> element.
>         2.  Removed the <launch:source> element.
>         3.  Added the <launch:notAfter> element based on the required
> <tmNotice:notAfter> element.
>
> We are hoping that the draft can be stabilized to help with the
> implementations.  Please reply with any feedback.
>
> Thanks,
>
> JG

Hi James,

another topic, another e-mail. I have a comprehension question regarding the 
poll messages, which have actually been introduced in the 07 version (section 
2.4). Do I see this correctly that the poll message for intermediate status 
changes shall include a <domain:infData> element as the base message, as defined 
in RFC 5731, section 3.1.2?

The exact use is unclear to me, the example contains merely ellipses: Shall 
(SHOULD/MAY or other RFC 2119 keywords) it contain the full data, e.g. 
registrant, contacts, ns, status values (which ones?) or would it be sufficient 
to supply only the mandatory elements? Should other extensions be included as 
well, for example for DNSSEC data or IDN variants?

Regards,

Klaus



_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg