Re: Fwd: New Version Notification for draft-tan-epp-launchphase-01.txt

Wil,

Below is some feedback to the draft:


  1.  Hopefully the trademark clearinghouse interface can be better understood to help drive the elements needed by the launchphase extension, since things could greatly change once that interface is defined.  Hopefully an EPP interface can be defined for the trademark clearinghouse that goes hand in hand with the launchphase extension.
  2.  Please add the XML schema to the Formal Syntax section
  3.  Why is the status optional in <lp:infData>?  Shouldn't an application always have a status?
  4.  The text says that <lp:claim> is "(optional) one or more <lp:claim> elements" where optional kind of conflicts with one or more.  I would state "zero or more <lp:claim> elements" instead.
  5.  Are all of the <lp:claim> elements required?
  6.  Shouldn't the <lp:claimRegDate> be of type dateTime instead of date?
  7.  Shouldn't the <lp:claimExDate> be of type dateTime instead of date?
  8.  Wouldn't it be better to shorten the <lp:claim> element names by not including the "claim" prefix (e.g. <lp:issuer> instead of <lp:claimIssuer>)?
  9.  It would be good if there is guidance or a description of the possible values of the <lp:phase> optional element.
  10. Isn't it assuming a certain trademark clearinghouse interface with the name <lp:pvcs>?  What if the elements are signed by the clearinghouse and the clearinghouse generates a verifiable token?
  11. Would the <lp:claimIssuer> really be a contact identifier defined in RFC 5733 or would it simply be a issuer identifier / handle?  I'm not sure how many issuers there will be and how they would be referenced.
  12. The info response sample needs to change the duplicate <lp:claimCountry> element to a <lp:region> element.

I'll provide more feedback as I work through the draft.

--


JG

[cid:F49929C4-D86D-4FE9-BA78-FE7B430C86DD]

James Gould
Principal Software Engineer
[email protected]

703-948-3271
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

VerisignInc.com

From: Wil Tan <[email protected]<mailto:[email protected]>>
Date: Tue, 18 Oct 2011 01:36:11 +1100
To: <[email protected]<mailto:[email protected]>>
Subject: [provreg] Fwd: New Version Notification for draft-tan-epp-launchphase-01.txt

Dear colleagues,

Gavin and I have published a new version of the draft: http://tools.ietf.org/html/draft-tan-epp-launchphase-01

This is mostly Gavin's work, with the following changes:

- element names are now in camelCase
- renamed <trademark> to <claim>
- a "preValidated" attribute of <claim> element
- there can be one or more <claim> elements

As usual, we'd love to hear any feedback that you may have.

--
.wil
Cloud Registry <http://www.cloudregistry.net>

---------- Forwarded message ----------
From: <[email protected]<mailto:[email protected]>>
Date: Fri, Oct 14, 2011 at 3:16 AM
Subject: New Version Notification for draft-tan-epp-launchphase-01.txt
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]>


A new version of I-D, draft-tan-epp-launchphase-01.txt has been successfully submitted by Wil Tan and posted to the IETF repository.

Filename:        draft-tan-epp-launchphase
Revision:        01
Title:           Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
Creation date:   2011-10-14
WG ID:           Individual Submission
Number of pages: 19

Abstract:
  This document describes an Extensible Provisioning Protocol (EPP)
  extension mapping for the provisioning and management of domain names
  during the launch phase of a domain name registry.




The IETF Secretariat
_______________________________________________ provreg mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/provreg

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