Re: Launch EPP SDK 2.0.0.2 Preview

Seth Goldman <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <CAAHh_-J6gGe+WJyotD=OR7CkWHBH-DiE6ZGQCtXgXdfGGQip+Q@mail.gmail.com>
Hi James,

I had a number of questions around launch phases and subphases.

First, do you envision that a registry would define separate subphases for
the initial sunrise and landrush periods (when applications are accepted),
and a subsequent subphase where conflicting applications are resolved (e.g.
via auction)? I could imagine a server wanting to distinguish that during
the former <info> and <update> commands may still be allowed on unallocated
applications, while <create> and <delete> would be disallowed. If so,
should that be explicitly defined as a first class phase type (perhaps
"evaluation"), or do you think a custom sub-phase (via the name attribute)
would be sufficient there?

Second, I notice that there's no advertising of the current phase(s) of the
registry - only of an application or registration (via the <info> command).
It seems like the registrars must know beforehand (via some out-of-band
mechanism) what the supported launch phases are and what operations are
allowed or disallowed during each phase - which perhaps makes sense the
complex business logic required. Was there any consideration given to
extending the EPP greeting format to enumerate the current phase(s) and
subphase(s) of the server? That might be a nice way for registrars to find
out when a phases has begun or ended, rather than relying on some other
communication channel.

Last, the specification doesn't really say if clients must specify the
launch subphase (if there is one) when sending an EPP launch command. I'm
drawing a blank at the moment of a concrete scenario where this might make
a difference, but it seems like some mention of it might be in order -
either to say that they must match, or that it's up to server policy
whether it matters.

Thanks,
Seth



On Thu, Mar 14, 2013 at 8:46 AM, Gould, James <[email protected]> wrote:

>   Verisign has released the second release of a preview version of the
> Launch EPP SDK, named Launch EPP SDK 2.0.0.2.  This SDK fully implements
> draft-tan-epp-launchphase-07 (
> http://tools.ietf.org/html/draft-tan-epp-launchphase-07 ) and
> draft-lozano-tmch-smd-00 (
> http://tools.ietf.org/html/draft-lozano-tmch-smd-00 ), referred to simply
> as 07/00, and includes the following features that can be of use to
> multiple stakeholders:
>
>
>    1. Packet encoder / decoder (CODEC) that will encode the XML from
>    objects and decode the objects from XML.
>    2. Creation and validation code for signed marks (SMD) using an XML
>    signed mark or a base64 encoded signed mark that complies with
>    draft-lozano-tmch-smd-00.
>    3. Use of a test CA issued certificate that is included in the signed
>    mark or base64 encoded signed mark that is chained to the test CA
>    certificate by the EPP Stub Server.  A test certificate in a test
>    Certificate Revocation List (CRL) is also validated by the EPP Stub Server.
>    4. Sample of poll messaging compliant
>    with draft-tan-epp-launchphase-07 in the EPP Stub Server.
>    5. A client API that utilizes the packet encoder / decoder (CODEC)
>    along with other code (e.g. transport, configuration, XML parsing pooling)
>    to interface with an EPP server.
>    6. An EPP Stub Server that includes pre-defined responses to support
>    the client tests.  The EPP Stub Server behavior can be easily customized to
>    suite your testing needs.
>
> The Launch EPP SDK includes support for RFC 5730, 5731, 5732, 5733, and
> 5734.
>
>  Verisign will be integrating the preview of the Launch Phase EPP
> Extension into its NameStore / SRS Bundle EPP SDK, at which time updates
> will not be made to the Launch EPP SDK.
>
>  The Launch EPP SDK is open source, requires Java 6 or higher, and below
> are the distributions and documents:
>
>
>    - Unix Binary Distribution (.tar.gz) -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-bin.tar.gz
>    - Unix Source Distribution (.tag.gz) -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-src.tar.gz
>    - Windows Binary Distribution (.zip) -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-bin.zip
>    - Windows Source Distribution (.zip) -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch-2.0.0.2-src.zip
>    - Readme File -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch.README
>    - Install Instructions -
>    http://www.verisigninc.com/assets/2-0-0-2/epp-launch.INSTALL
>
>   -- ****
>
>
>
> JG****
>
>  ****
>
> ****
>
>  ****
>
> James Gould****
>
> Principal Software Engineer****
>
> [email protected]****
>
>  ****
>
> 703-948-3271 (Office)****
>
> 12061 Bluemont Way****
>
> Reston, VA 20190****
>
> VerisignInc.com
>
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg
>
>

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg
8A7A655D-9ED0-4D38-898D-E9E8B754666E[21].png (image/png, 4 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.