Re: [regext] CALL FOR ADOPTION: Proposed Milestones for the next year

+1 — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 4/26/19, 4:26 PM, "regext on behalf of James Galvin" wrote: As discussed at our last meeting at IETF104 Prague, we need to se

[regext] CALL FOR ADOPTION: Proposed Milestones for the next year

As discussed at our last meeting at IETF104 Prague, we need to set milestones for ourself. This is a formal request for adoption of a set of milestones. As previously explained, we have included the two proposed new documents in this set. If you support the adoption of the documents you can j

[regext] CALL FOR ADOPTION: draft-arias-noguchi-dnrd-objects-mapping

This is a formal adoption request for Domain Name Registration Data (DNRD) Objects Mapping: https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/. Please review this draft to see if you think it is suitable for adoption by REGEXT, and comment to the list, clearly stating

[regext] CALL FOR ADOPTION: draft-arias-noguchi-registry-data-escrow

This is a formal adoption request for Registry Data Escrow Specification: https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/. Please review this draft to see if you think it is suitable for adoption by REGEXT, and comment to the list, clearly stating your view. Please

[regext] Adopting Documents and Adding Milestones

As discussed at our last meeting at IETF104 Prague, we need to set milestones for ourself. As part of the discussion we considered the set of documents we have and reminded ourselves that we have two separate tracks of work: RDAP related and registry, registrar, and EPP (registration) related.

Re: [regext] 2nd factor for Login Security Extension for EPP

On Tue, Apr 23, 2019, at 05:02, Rubens Kuhl wrote: > Certificates can be made as secure as one wants to. The two most common > ways in the EPP ecosystem are: > 1) Accept certificates from a number of established CAs, but tag an > specific certificate as being authorised. So the authorisation does

[regext] Milestones update

Hi all, As we have discussed during IETF 104 in Prague, we will update our milestones. Before we add the newly adopted documents to the milestones, we first need to clean up the current milestone list. We have decided to delete the current 2 open items from the milestone list: -Submit for public