RE: EPP To-Do List

["Damaraju, Ayesha" <ayesha.damaraju@NeuStar.com>]

Scott,

If it is not noted already.
THe info response of contact and domain have authinfo as
required field in the schemas.....text says it is optional.

-A

-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Thursday, September 06, 2001 9:10 AM
To: 'ietf-provreg@cafax.se'
Subject: EPP To-Do List


Before I get started with edits to produce the next version of the EPP
drafts, I wanted to let everyone know what's been queued for incorporation.
I'd also like to ensure that everyone is OK with the changes, and I'll note
places where I'd like to see more discussion before changing anything.
Here's the list, sorted by date posted to the mailing list:

1. Addition of data collection policy elements based on suggestions received
from Eric Brunner-Williams:
http://www.cafax.se/ietf-provreg/maillist/2001-04/msg00108.html

2. Minor typos noted by Asbjorn Steira:
http://www.cafax.se/ietf-provreg/maillist/2001-06/msg00059.html

3. More typos noted by Dan Manley:
http://www.cafax.se/ietf-provreg/maillist/2001-07/msg00012.html

4. Fix text to note that XML Schema requires extended date-time forms:
http://www.cafax.se/ietf-provreg/maillist/2001-07/msg00015.html

5. Changing all of the schema and namespace URIs to use a new format
suggested in the Mealling XML registry I-D:
http://www1.ietf.org/mail-archive/ietf-announce/Current/msg14309.html

6. Additional text to provide a note to implementers that command-response
interactions may require some smarts if not exchanged on a strict
one-for-one basis:
http://www.cafax.se/ietf-provreg/maillist/2001-09/msg00033.html

7. Making the contact object street and postal code elements OPTIONAL:
http://www.cafax.se/ietf-provreg/maillist/2001-09/msg00034.html

There were also a few ideas suggested by Sheer El-Showk for which I'm not
sure we came to a conclusion.  First was a suggestion to add host transfer
features:
http://www.cafax.se/ietf-provreg/maillist/2001-08/msg00003.html

The ensuing discussion focused more on glue generation than host transfers.
We've certainly covered this topic before, and my read of the debate is that
there are still more people who feel that independent host transfers should
not be supported.  If that's still the case, I intend to leave things as-is.

Second was a suggestion to add an option to the domain <info> command to
allow a client to select if subordinate host and/or delegated name server
data is returned in the <info> response:
http://www.cafax.se/ietf-provreg/maillist/2001-08/msg00006.html

No one objected, so I'm inclined to add features to support this.

We've talked about push vs. poll, and seemed to reach consensus (I say
seemed because I haven't seen any straw poll results) on providing an
optional way to do pushing.  I don't think the current extension mechanisms
suffice, because we're not talking about extending either a type of object
or a currently defined command or response.  However, I think we can add a
new <any> hook at the <command>, <response>, <greeting>, <hello> level so
that a new type of element (maybe an <alert> or something similar) can be
defined in an extension document.  This means that we open up the
possibility of all sorts of extensions, but it seems like the only real way
to provide for server-initiated message pushing.  Thoughts?  If you'd like
to comment, please start a new thread.

I've had multiple private conversations with people who believe we need to
provide support to identify explicit registrant consent for use of personal
data, such as contact data.  The suggestions I've received boil down to
adding an attribute to some of the contact elements to note explicit
"opt-in" desire.  I'd like to talk about this further, so if anyone is
inclined to support or flame the idea, let's start a new thread for this
topic, too.

Lastly, I'd like to make the Acknowledgement sections more explicit so that
folks who've made material contributions (new features, suggested fixes,
etc.) are explicitly named.  please contact me directly if you've
participated in that way and you wish to have your name listed.

<Scott/>