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

[Gould, James]

+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 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 just 
vote on the milestones as proposed.  You can also vote on the milestones 
without the two new documents.

Please review the milestones and respond to the list with “+1” or 
“+1 with any updates or comments” or just respond with your 
questions or comments.


Here are the proposed milestones:


July 2019 - Login Security
https://datatracker.ietf.org/doc/draft-ietf-regext-login-security/


August 2019 - Registry Data Escrow Specification
https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/


August 2019 - Domain Name Registration Data (DNRD) Objects Mapping
https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/


September 2019 - RDAP Partial Response
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/


October 2019 - RDAP Sorting and Paging
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/


November 2019 - RDAP Reverse Search
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/


March 2020 - Federated Authentication for the RDAP using OpenID Connect
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/


Please consider whether this is the right order for the documents and 
whether or not you believe enough time has been allotted to complete the 
working group review of each document.

Thanks,

Antoin and Jim

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[James Galvin]

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 just 
vote on the milestones as proposed.  You can also vote on the milestones 
without the two new documents.


Please review the milestones and respond to the list with “+1” or 
“+1 with any updates or comments” or just respond with your 
questions or comments.



Here are the proposed milestones:


July 2019 - Login Security
https://datatracker.ietf.org/doc/draft-ietf-regext-login-security/


August 2019 - Registry Data Escrow Specification
https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/


August 2019 - Domain Name Registration Data (DNRD) Objects Mapping
https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/


September 2019 - RDAP Partial Response
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/


October 2019 - RDAP Sorting and Paging
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/


November 2019 - RDAP Reverse Search
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/


March 2020 - Federated Authentication for the RDAP using OpenID Connect
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/


Please consider whether this is the right order for the documents and 
whether or not you believe enough time has been allotted to complete the 
working group review of each document.


Thanks,

Antoin and Jim

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[James Galvin]

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 your view.


Please also indicate if you are willing to contribute text, review text, 
or be a document shepherd.


This call for adoption ends Thursday, 2 May 2019.

If there are no objections, and we receive enough consensus for 
adoption, the chairs will consider this document adopted.


Thanks,

Your REGEXT co-chairs Antoin and Jim

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[James Galvin]

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 also indicate if you are willing to contribute text, review text, 
or be a document shepherd.


This call for adoption ends Thursday, 2 May 2019.

If there are no objections, and we receive enough consensus for 
adoption, the chairs will consider this document adopted.


Thanks,

Your REGEXT co-chairs Antoin and Jim

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

[regext] Adopting Documents and Adding Milestones

[James Galvin]

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.


It had been previously suggested we limit ourselves to at most 5 
milestones at a time, even though we have about 20 documents on our 
prospect list.  With the observation of two tracks of work, our area 
director agreed that we could have about 7 milestones at a time, which 
allows us to have about 3 documents per track active at a time.


Recall that in December 2018 we conducted a poll of our prospective 
documents that easily identified 5 documents with the greatest interest. 
 We have already gone through the process of adopting those 5 documents 
and we are ready to set milestones.


However, those 5 documents break down to the OpenID document, 3 RDAP 
related documents, and 1 registration related document.  The suggestion 
is to adopt two additional registration related documents to balance our 
work.


As it turns out, the next two documents from the interest poll conducted 
in December 2018 are registration related documents:


Registry Data Escrow Specification
https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/

Domain Name Registration Data Objects Mapping
https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/

As a result, the chairs are proposing we adopt these two additional 
documents and then move forward with 7 milestones.


Following this message you will see two messages, one for each of the 
above documents to adopt it.  You will have the opportunity to indicate 
your preference for adopting or not each of those documents separately.


Following those messages you will see a message with a proposed set of 
milestones.  The chairs have decided to take one liberty with the 
proposed set of milestones and that is we are including the two 
documents above assuming that they will be adopted.  This will speed up 
our process!


However, rest assured, if the working group does not want to adopt these 
documents and prefers something different we will make the necessary 
adjustment.  Read the voting request carefully when you see it.


Thanks!

Antoin and Jim

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[Patrick Mevzek]

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 not 
> rely only on the CN, but CN+specific public key.
> 2) Run your own private CA. This is what we do in both .br and our gTLD 
> back-end, where we tailor the CN to be the registrar ID. BTW, it would 
> be nice if ICANN run a CA that identified gTLD registrars in the gTLD 
> space... but until they do, we have our own.

3) the registry accepts any certificate, even self-signed ones.

It is maybe not common, but as secure as the previous ones: the registry
whitelists certificates in advance and out of band, and they are
associated specifically per registrar.

Hence the certificate content, and specifically the issuer part
does not matter a lot.

In that case it leaves the registrar free to organize itself how
he wants, either by generating a local self-signed certificate (one for all,
one per registry but key for all or one per registry with separate key), or
using one from a well-known CA.
If all registries start to maintain their own PKI then again it is
a maintenance nightmare for registrars (those connecting to multiple
registries).

I am not sure a new CA would help tremendously here. At least it just adds
an additional case for all registrars not dealing with only one gTLD
(because even if it exists I doubt that one could mandate all gTLD registries
to accept this CA and only this CA as it is a matter of trust and transitive
trust, so why should any gTLD registry trust unconditionnaly this new CA?)

-- 
  Patrick Mevzek
  p...@dotandco.com

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

[regext] Milestones update

[Antoin Verschuren]

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 publication "Validate Mapping for the Extensible Provisioning 
Protocol”
-Submit for publication an informational RFC with requirements for a 
registration protocol for third-party DNS providers

Formally these documents will remain adopted WG documents, but they will no 
longer be prioritised WG work items. 

If anyone objects to this decision, then please send a message to the list 
before May 2nd so we can update the milestone list next week.

Regards,

Jim and Antoin

- -- 
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392






___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext