launch:phase requirement for Sunrise FCFS
"Wodjenski, Sharon" <[email protected]> Mon, 3 Jun 2013 18:05:21 +0000
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <0607A83C894B824F8778BD69F357FE580AB5A946@stntexmb13.cis.neustar.com> |
Hi Everybody,
We've run into a condition during development and are seeking feedback/guidance from the group.
This case is specific to First Come, First Served Sunrises, and the delete/update commands.
When we read this in the spec:
2.2. Launch Phases
The server MAY support multiple launch phases sequentially or
simultaneously. The <launch:phase> element MUST be included by the
client to define the target launch phase of the command.
We interpreted that to mean that the launch:phase was mandatory, and would come in with each command in the extension.
Currently, the XSD for the delete/update commands do not support the application id being optional. And of course, for a FCFS registration, the application id is not needed/used.
<element name="update" type="launch:idContainerType"/>
<element name="delete" type="launch:idContainerType"/>
<!--
Common container of id (identifier) element
-->
<complexType name="idContainerType">
<sequence>
<element name="phase" type="launch:phaseType"/>
<element name="applicationID" type="launch:applicationIDType"/>
</sequence>
</complexType>
So, the question from a client perspective is:
1. Is the launch:phase, and therefore the extension, mandatory for all commands and the XSD should be modified so that the application id is optional (as it is in the Info command)?
Or
2. For FCFS update/delete commands, the extension is not required at all, and therefore the launch:phase is not specified.
Thank you for your input on this topic.
Sharon
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg