Launch Phase EPP Extension Version 04 Posted

Wil Tan, Gavin Brown and I have updated the Launch Phase EPP Extension Mapping to support the current state of the ICANN TMCH Sunrise and Claims implementation model.  You can find the draft at the URL http://tools.ietf.org/html/draft-tan-epp-launchphase-04.  The draft fully supports the latest  ICANN TMCH Sunrise and Claims Implementation model and also is targeted for ccTLD registries to avoid the proliferation of duplicate similar extensions.  We anticipate changes to the attributes of a mark and broke out the mark definition to its own XML schema for reuse outside of EPP.  In addition, the signedMark definition was broken out into its own XML schema to enable the creation of signed marks without any dependencies to EPP XML schemas.

The following notes are meant to be used as navigation aid for those who are reading it in the context of the TMCH implementation.

Sunrise Process

- the "signed mark" validation model is used (Section 2.4)
- should the TMCH technical implementers converge on the use of base64-encoded XML for signed mark data (SMD), the draft employs the use of <smd:encodedSignedMark> element (Section 2.7.2)
- the <smd:encodedSignedMark> is then sent along in an extended EPP <create> command called "Sunrise Create Form" (Section 3.3.1 - see the fifth example <create> domain command)

Claims (including "Claims 2") Process

- the client uses an extended <check> domain command, referred to as the Claims Check Command, to find out if a mark exists for the given domain names (Section 3.1)
- if one or more mark exists for a domain, a <launch:claimKey> element is returned in the <check> response.
- client can then use the <launch:claimKey> to obtain claims notice from the CNIS endpoint, which returns a <launch:noticeID> value.
- if the registrant wishes to proceed to register the domains, the client will submit the <launch:noticeID> value in an extended EPP <create> command in what is referred to as "Claims Create Form" (Section 3.3.2)

The complete ChangeLog is as follow:

  1.  Removed references to the ICANN model.
  2.  Removed support for the Claims Info Command.
  3.  Removed use of the signedClaim.
  4.  Revised the method for referring to the signedClaim from the XML Signature using the IDREF URI.
  5.  Split the launch-1.0.xsd into three XML schemas including launch-1.0.xsd, signeMark-1.0.xsd, and mark-1.0.xsd.
  6.  Split the "claims" launch phase to the "claims1" and "claims2" launch phases.
  7.  Added support for the encodedSignedMark with base64 encoded signedMark.
  8.  Changed the elements in the createNoticeType to include the noticeID, timestamp, and the source elements.
  9.  Added the class and effectiveDate elements to mark.

--

JG

[cid:B4D29F20-3CF0-43E7-AFE5-2518255440CC]

James Gould
Principal Software Engineer
[email protected]<mailto:[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