Re: [ietf-provreg] FW: Protocol Action: 'Extensible Provisioning Protocol (EPP) Transportover TCP' to Full Standard

[Eric Brunner-Williams <[e-mail]>]

+1

Francisco Obispo wrote:
> Congratulations,!!..
>
> Good job!.
>
> Francisco
>
>
> On Aug 20, 2009, at 8:02 AM, Hollenbeck, Scott wrote:
>
>> 4934bis has been approved by the IESG.  That's the last of the document
>> updates for Full Standard.  An updated implementation report can be
>> found here:
>>
>> http://www.ietf.org/iesg/implementation/report-rfc4930-4934.txt
>>
>> Thanks to everyone who helped move this forward.
>>
>> -Scott-
>>
>> -----Original Message-----
>> From: [e-mail]
>> [mailto:[e-mail]] On Behalf Of The IESG
>> Sent: Wednesday, August 19, 2009 4:01 PM
>> To: IETF-Announce
>> Cc: Internet Architecture Board; RFC Editor
>> Subject: Protocol Action: 'Extensible Provisioning Protocol (EPP)
>> Transportover TCP' to Full Standard
>>
>> The IESG has approved the following document:
>>
>> - 'Extensible Provisioning Protocol (EPP) Transport over TCP '
>>   <draft-hollenbeck-rfc4934bis-01.txt> as a Full Standard
>>
>> This document has been reviewed in the IETF but is not the product of an
>> IETF Working Group.
>>
>> The IESG contact person is Alexey Melnikov.
>>
>> A URL of this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-hollenbeck-rfc4934bis-01.txt
>>
>> Technical Summary
>>  This set of documents advances EPP to Standard.  References
>>  have been updated and non-normative text updates have been made.
>>  Some clarifications on TLS server sertificate verification were done.
>>
>> Working Group Summary
>>  This is the product of an individual submitter, though the working
>>  group mailing list of PROVREG (now closed) was used to review the
>>  updates to the documents.
>>
>> Document Quality
>>  Issues raised by AD review were addressed.
>>  There are multiple implementations of the protocol, as described in
>> the implementation report.
>>
>> Personnel
>>  Edward Lewis is the document shepherd for this series
>> (draft-hollenbeck-rfc493*bis) of documents.
>>  Alexey Melnikov is the responsible Area Director.
>>
>> RFC Editor note:
>>
>> In Section 9, insert a new paragraph after the paragraph starting with
>> "If the server identity check fails". (The new paragraph would be 3rd to
>> the last):
>>
>> During the TLS negotiation, the EPP server MUST verify that the client
>> certificate matches the reference identity previously negotiated out of
>> band, as specified in section 8. The server should match the entire
>> subject name or the subjectAltName as described in RFC 5280. The server
>> MAY enforce other restrictions on the subjectAltName, for example if it
>> knows that a particular client is always connecting from a particular
>> hostname/IP address.
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
>>
>> List run by majordomo software.  For (Un-)subscription and similar 
>> details
>> send "help" to [e-mail]
>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
>
> List run by majordomo software.  For (Un-)subscription and similar 
> details
> send "help" to [e-mail]
>
>
>

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software.  For (Un-)subscription and similar details
send "help" to [e-mail]