Hi,

I’m sending this message to introduce a new set of EPP and RDAP extensions that 
adds new functionality to EPP with associated publication in RDAP.  We’re only 
looking for review and feedback by the working group at this point.  I would 
like to formally introduce these extensions at the IETF-127 REGEXT meeting.  
The following is the list of extensions in priority order:


  1.  EPP Authentication Token Mapping 
(https://datatracker.ietf.org/doc/html/draft-gould-regext-auth-token) – Defines 
a Java Web Signature (JWS) Authentication Token to authorize actions by 
registrar users.  This extension is a dependency for the EPP Status Set 
Extension to provide M-of-N authorization to disable the status set while 
executing the EPP command.
  2.  EPP Status Set Extension 
(https://datatracker.ietf.org/doc/html/draft-gould-regext-epp-status-set) – 
There can be many overlapping reasons for a EPP status value being applied an 
object, such as implementing a lock service, complying with a court order, or 
addressing domain abuse.  A Status Set defines an object representing the 
reason for setting a list of status values, so clients and servers can manage 
the status sets in place of individual status values to effectively manage the 
overlapping reasons.  The EPP extension supports the provisioning of client 
status sets, disclosure of the server status sets, and an enhanced 
authorization model for client status sets with the EPP Authentication Token 
Mapping.
  3.  RDAP Status Set Extension 
(https://datatracker.ietf.org/doc/html/draft-gould-regext-rdap-status-set) – 
This RDAP extension publishes the status sets supported by the EPP Status Set 
Extension.  RDAP users will be able to view the status sets (client and server) 
that have been assigned to the object with additional information (e.g., mapped 
status values).
  4.  EPP Server Validation Extension 
(https://datatracker.ietf.org/doc/html/draft-gould-regext-epp-server-validation)
 – EPP extension for providing the status of server validations with an 
extensible set of validation types.  The validations can be performed 
synchronously or asynchronously.  The status of the validations can be included 
in an extension to the response (synchronous validation) or in a poll message 
(synchronous validation).  Examples of validations include DNS resolution 
validation with the type “dns” and DNSSEC validation with the type “dnssec”.
  5.  RDAP Server Validation Extension 
(https://datatracker.ietf.org/doc/html/draft-gould-regext-rdap-server-validation)
 – This RDAP extension publishes the status by type of the validations 
performed by the server.

Thanks,

 --

JG

[cid87442*[email protected]]

James Gould
Fellow Engineer
[email protected]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to