[cabfpub] Voting Begins: Ballot 224: WHOIS and RDAP

[林維聰(Robin.Lin)]

TWCA votes YES.

Robin Lin


From: Public [mailto:public-bounces at cabforum.org] On Behalf Of Wayne Thayer via Public
Sent: Wednesday, May 16, 2018 3:22 AM
To: CA/Browser Forum Public Discussion List
Subject: [cabfpub] Voting Begins: Ballot 224: WHOIS and RDAP

Ballot 224: WHOIS and RDAP

Purpose of Ballot: The Registry Data Access Protocol (RDAP) is the successor to WHOIS, and this ballot adds explicit support for RDAP to the BRs by adding a definition of "WHOIS". The new definition permits the use of the registry or registrar's web interface, and requires WHOIS information to be retrieved directly from the registrar or registry of the domain name.

The following motion has been proposed by Wayne Thayer of Mozilla and endorsed by Tim Hollebeek of DigiCert and Adriano Santoni of Actalis.

— MOTION BEGINS –
This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as follows, based upon Version 1.5.7:

In section 1.6.1, add the following definition:

WHOIS: information retrieved directly from the Domain Name Registrar or registry operator via the protocol defined in RFC 3912, the Registry Data Access Protocol defined in RFC 7482, or an HTTPS website.

In section 1.6.3, add the following references:

RFC3912, Request for Comments: 3912, WHOIS Protocol Specification, Daigle, September 2004.

RFC7482, Request for Comments: 7482, Registration Data Access Protocol (RDAP) Query Format, Newton, et al, March 2015.

— MOTION ENDS –

A comparison of the changes can be found at https://github.com/cabforum/documents/compare/Ballot220...wthayer:Ballot224

The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: 2018-05-03  19:00 UTC

End Time: after 2018-05-15 19:00 UTC

Vote for approval (7 days)

Start Time: 2018-05-15  19:00 UTC

End Time: 2018-05-22  19:00 UTC


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20180522/8008048c/attachment-0003.html>