Re: Standard Extensions

Scott,

Let me add a few more to the list, since we have some custom extensions
that could be of general interest:

1. Account finance (balance, credit limit, available credit, low credit
thresholds) information.  Our custom Low Balance Mapping for poll
messaging of low balance conditions and the Balance Mapping for on-demand
balance commands. 
2. General Key / Value Pair attribute extension which is defined by our
custom Client Object Attribute Extension.
3. A registry routing extension for servers that support more than one
TLD.  Our custom NameStore Extension handles this.
4. Additional domain attributes needed to support transfers.  Our custom
Whois Info Extension supports returning the domain's registrar name, the
registrar whois server, and the registrar URL to support transfers without
the need to hit whois for the information.
5. Add poll messaging for the expiry of restore commands due to not
receiving the restore report command in RFC 3915.  Our custom RGP Poll
Mapping addresses this.
6. Registry mapping that support returning the list of supported TLD's of
the server along with features and policy information for the TLD's.  Past
postings on the list recommended to do this out-of-band, but I still
believe that this information can and should be provided in-band.
7. Support for .NAME objects elsewhere.  Specifically if there is interest
in support for Defensive Registration or NameWatch objects in other
registries.  
8. We have a custom IDN Language Tag extension that can be discussed with
the "An IDN Extension" item.
9. ConsoliDate Mapping (sync command) that supports synchronizing domain
expiration dates.  
10. Premium Domain Extension for dealing with the registration of premium
domains (is a domain a premium domain, what is the price, etc.).  Our
custom Premium Domain Extension addresses this.




--
  
JG
 

 
James Gould
Principal Software Engineer
[email protected]
 
703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com







On 8/22/12 1:32 PM, "Hollenbeck, Scott" <[email protected]> wrote:

>It's been a long time since I started this thread back in January.
>Someone recently asked me a question about an EPP extension, so I thought
>it wise to see if I could revisit the discussion and post a summary.
>Here's the original question:
>
>> Let's assume for a moment that we have enough interest to form a
>> working group focused on the development of a set of standard EPP
>> extensions. If we had to start writing a charter today, what
>> functionality would people most like to see included?
>
>and here's a summary of the suggestions (my apologies if I missed any),
>including new efforts that have recently surfaced:
>
>1. A garbage collection mechanism.
>
>2. Extension for registrars to get registry/zone policy information.
>
>3. Extension to provide account status information to registrars.
>
>4. An IDN extension*.
>
>5. A TLD launch extension*.
>
>6. A trademark management extension*.
>
>7. Standardized registry-to-registrar notifications.
>
>8. An extension for VAT and/or tax ID information.
>
>9. An extension for a legal/personal attribute on contact objects.
>
>10. An extension for additional status value and/or result codes, perhaps
>with an associated IANA registry.
>
>11. An extension for cryptographic signatures.
>
>12. An extension for delegation errors/warnings.
>
>Those that are described in a draft I've seen are marked with an
>asterisk. IMHO twelve is probably too many to bootstrap a new working
>group. If we could whittle this down to 6 or 7 AND we have actual drafts
>written for consideration it may be possible for us to get something
>going.
>
>Which of the above topics has been addressed in a draft? Who is willing
>to write drafts for those topics that haven't yet been addressed?
>
>Scott
>_______________________________________________
>provreg mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/provreg

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg