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

"Gould, James" <JGould@verisign.com> Thu, 10 November 2011 20:33 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A2421F8B6D for <provreg@ietfa.amsl.com>; Thu, 10 Nov 2011 12:33:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.443
X-Spam-Level:
X-Spam-Status: No, score=-5.443 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2KfJ7z-e0Sa for <provreg@ietfa.amsl.com>; Thu, 10 Nov 2011 12:32:59 -0800 (PST)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by ietfa.amsl.com (Postfix) with ESMTP id C844E21F8B68 for <provreg@ietf.org>; Thu, 10 Nov 2011 12:32:57 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKTrw08vQzYjG1VJCRsC2pIVApM4/ZIzhI@postini.com; Thu, 10 Nov 2011 12:32:58 PST
Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id pAAKWnW7014006; Thu, 10 Nov 2011 15:32:50 -0500
Received: from BRN1WNEXCAS02.vcorp.ad.vrsn.com ([10.173.152.206]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 10 Nov 2011 15:32:49 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.01.0323.003; Thu, 10 Nov 2011 15:32:49 -0500
From: "Gould, James" <JGould@verisign.com>
To: Wil Tan <wil@cloudregistry.net>, "provreg@ietf.org" <provreg@ietf.org>
Thread-Topic: [provreg] Fwd: New Version Notification for draft-tan-epp-launchphase-01.txt
Thread-Index: AQHMn+fow85soGNG8Emi3VoJ6dqLsw==
Date: Thu, 10 Nov 2011 20:32:47 +0000
Message-ID: <CAE199C9.1B0A8%jgould@verisign.com>
In-Reply-To: <CACnMJCOnjK1SiLCG0cbNybDb-Sa1b=hpr3UtiRNH6bU377CV4g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_CAE199C91B0A8jgouldverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginalArrivalTime: 10 Nov 2011 20:32:49.0876 (UTC) FILETIME=[E9FBD940:01CC9FE7]
Subject: Re: [provreg] Fwd: New Version Notification for draft-tan-epp-launchphase-01.txt
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 20:33:00 -0000

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
jgould@Verisign.com

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

VerisignInc.com

From: Wil Tan <wil@cloudregistry.net<mailto:wil@cloudregistry.net>>
Date: Tue, 18 Oct 2011 01:36:11 +1100
To: <provreg@ietf.org<mailto:provreg@ietf.org>>
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: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Fri, Oct 14, 2011 at 3:16 AM
Subject: New Version Notification for draft-tan-epp-launchphase-01.txt
To: wil@cloudregistry.net<mailto:wil@cloudregistry.net>
Cc: wil@cloudregistry.net<mailto:wil@cloudregistry.net>, gavin.brown@centralnic.com<mailto:gavin.brown@centralnic.com>


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 provreg@ietf.org<mailto:provreg@ietf.org> https://www.ietf.org/mailman/listinfo/provreg