[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: EPP Provreg <ietf-provreg@cafax.se>
From: James Gould <jgould@verisign.com>
Date: Tue, 08 Dec 2009 10:01:05 -0500
Sender: owner-ietf-provreg@cafax.se
Thread-Index: Acp4F0PEFpQxGDTfOkWVMDcpTV7R9g==
Thread-Topic: draft-gould-rfc4310bis-00.txt Submitted for Review
User-Agent: Microsoft-Entourage/12.20.0.090605
Subject: [ietf-provreg] draft-gould-rfc4310bis-00.txt Submitted for Review

Title: draft-gould-rfc4310bis-00.txt Submitted for Review
All,

I haven’t received any negative feedback to the draft that I previously sent to the list, so I’m assuming that everyone is fine with it.  I officially submitted the draft.  The official draft is available at the URL below.  I’m looking for feedback to the draft from the list to ensure that we have consensus to move forward.  Please send your feedback to the list or to me privately.  

ftp://ftp.ietf.org/internet-drafts/draft-gould-rfc4310bis-00.txt

The draft meets the following goals that were previously sent to the list:

1. XML schema is backward compatible
2. Support for add and rem in the same command
3. Support for passing all four dsData attributes on a rem
4. Support for a dsData and keyData primary interface.  Only one primary interface should be supported by the server.  
5. Remove support for the wildcard delete of dsData in the rem by just using the keyTag with a clear statement (i.e. Server must return error if the keyTag matches multiple DS records) in the specification.  From my perspective and I believe a couple others this is a key issue that must be addressed.    
6. Clarity in the specification on the use of the chg as a replace or a “change all”.   
7. Clarity around the corner case of a client attempting to add and remove the same dsData or keyData in a single command.  This must result in an error from the server.  Additionally an error must be returned if the client tries to remove dsData or keyData that does not exist or tries to add dsData or keyData that already exists.  

I received confirmation that the URI can stay the same as long as the XML schema is backward compatible.

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.


Home | Date list | Subject list