[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Tue, 18 Aug 2009 07:16:48 -0400
Content-class: urn:content-classes:message
Sender: owner-ietf-provreg@cafax.se
Thread-Index: Acof9WCQ6p4pq/w8S7i3z62KD+oq+Q==
Thread-Topic: EPP Server Implementer Help Needed
Subject: [ietf-provreg] EPP Server Implementer Help Needed

I still need info from one server implementer that is willing to be
included in an implementation report and confirm that they have
implemented the TLS client identification features described in section
9 of 4934bis.  Specifically:

1. TLS implementations are REQUIRED to support the mandatory cipher
suite specified in the implemented version:

2. Mutual client and server authentication using the TLS Handshake
Protocol is REQUIRED.

3. Signatures on the complete certification path for both client machine
and server machine MUST be validated as part of the TLS handshake.

4. Information included in the client and server certificates, such as
validity periods and machine names, MUST also be validated.

5. EPP service MUST NOT be granted until successful completion of a TLS
handshake and certificate validation

Most of these come for free with a good TLS toolkit.  Are there any
server implementers willing to confirm that they've implemented these
features?  I've already confirmed that VeriSign has implemented these
features.

-Scott-

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software.  For (Un-)subscription and similar details
send "help" to ietf-provreg-request@cafax.se


Home | Date list | Subject list