Re: [ietf-provreg] draft-gould-rfc4310bis-04.txt Submitted for Review

[James Gould <jgould@verisign.com>]

Title: Re: [ietf-provreg] draft-gould-rfc4310bis-04.txt Submitted for Review

Anthony,

Thanks for the feedback.  I originally had maxSigLife under the secDNS:update but it was pointed out in a private message that it should be under secDNS:chg to be consistent with the other EPP RFC’s.  The secDNS:chg follows the other EPP RFC’s by having minOccurs=”0” and subsequently any attributes that can be changed have minOccurs=”0” which in this case is only the single attribute maxSigLife.  With this structure additional attributes can be more easily added that are consistent with the other EPP RFC’s.  I sent a question out to the list about the option of adding the ttl attribute, which would add a second optional element under secDNS:chg. 

Thanks, 

-- 


JG 

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

 
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary and/or Registry  Sensitive information intended solely for the recipient and, thus may not be  retransmitted, reproduced or disclosed without the prior written consent of  VeriSign Naming and Directory Services.  If you have received  this e-mail message in error, please notify the sender immediately by  telephone or reply e-mail and destroy the original message without making a  copy.  Thank you.

---

From: <Anthony.Kirby@nominet.org.uk>
Date: Fri, 12 Feb 2010 11:35:31 -0500
To: James Gould <jgould@verisign.com>
Cc: EPP Provreg <ietf-provreg@cafax.se>, "owner-ietf-provreg@cafax.se" <owner-ietf-provreg@cafax.se>
Subject: Re: [ietf-provreg] draft-gould-rfc4310bis-04.txt Submitted for Review

owner-ietf-provreg@cafax.se wrote on 11/02/2010 04:07:31:
> James Gould <jgould@verisign.com>
> I submitted 04 of the draft.  The official draft is available at theURL
below:
>
> http://www.ietf.org/id/draft-gould-rfc4310bis-04.txt

thanks, James
just a picky detail; ISTM that the minOccurs="0" for maxSigLife in chgType
is redundant, because chgType is already optional in updateType (it was
required when it was a member of dsDataType but isn't any more).  Come to
think of it, maxSigLife could just be an element in updateType.
kind regards,
Anthony

e.g.
<!-- Child elements of the <update> element. -->
<complexType name="updateType">
  <sequence>
    <element name="rem" type="secDNS:remType" minOccurs="0"/>
    <element name="add" type="secDNS:dsOrKeyType" minOccurs="0"/>
    <element name="maxSigLife" type="secDNS:maxSigLifeType" minOccurs="0"/>
  </sequence>
  <attribute name="urgent" type="boolean" default="false"/>
</complexType>