Re: Domain check in draft-obispo-epp-idn-00.txt

"Gould, James" <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <CB2CD33F.1F5C2%[email protected]>
> I mentioned that very idea on this list before Christmas. The rough
>consensus
> was that things like a registry policy ought to be provided
>independently of
> EPP. Some also expressed scepticism that it'd even be possible to
>account for
> all the possible variations on registry policy. It's something I've been
> working on during my free time, but due to my lack of free time lately,
>is not
> something I've made as much progress on as I'd like.

A goal is to provide 90% of the feature and policy information to help
drive the client logic.  The mapping certainly wouldn't be small and might
have to make external references for things like reserved names.  I have
done some work on it, but I wanted to know if there is interest in it.
One of the key attributes would be the phases of the TLD (sunrise, rights,
steadyState) with start and end dates.  I might be dreaming that something
useful could be created, but it might be worth a shot.
	


-- 


JG



James Gould
Principal Software Engineer
[email protected]

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

VerisignInc.com



On 1/6/12 1:45 PM, "Keith Gaughan" <[email protected]> wrote:

>On 06/01/12 14:24, Gould, James wrote:
>
>> EPP's extensibility is
>> a feature but best practices should be followed (e.g. make them opt-in
>> extensions) when creating them and it makes sense to move some of the
>> custom extensions up the standards track to create consistency.
>
>Severely lacking currently are informational RFCs concerning best current
>practice for those implementing EPP clients and servers.
>
>> I believe with the launch of a large
>> set of new TLD's it makes sense to at a minimum have a BoF to discuss
>>the
>> custom extensions to see if a set of common / standard extensions can be
>> identified.
>
>I concur.
>
>> I also have the idea of creating a Domain Registry
>> EPP Mapping that at a minimum would include support for an info command
>> and response for providing the features and policies for a TLD or set of
>> TLD's. This would provide information to the Registrars that could help
>> automate and subsequently scale the number of TLD's.
>
>I mentioned that very idea on this list before Christmas. The rough
>consensus
>was that things like a registry policy ought to be provided independently
>of
>EPP. Some also expressed scepticism that it'd even be possible to account
>for
>all the possible variations on registry policy. It's something I've been
>working on during my free time, but due to my lack of free time lately,
>is not
>something I've made as much progress on as I'd like.
>
>-- 
>Keith Gaughan, Senior Developer
>PGP/GPG key ID: 3E896381
>Blacknight Internet Solutions Ltd. <http://blacknight.com/>
>12A Barrowside Business Park, Carlow, Ireland
>Registered in Ireland, Company No.: 370845
>_______________________________________________
>provreg mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/provreg

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.