[rfc-dist] RFC 4934 on Extensible Provisioning Protocol (EPP) Transport Over TCP

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed May 30 16:50:39 PDT 2007

A new Request for Comments is now available in online RFC libraries.

        RFC 4934

        Title:      Extensible Provisioning Protocol (EPP) Transport 
                    Over TCP 
        Author:     S. Hollenbeck
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    shollenbeck at verisign.com
        Pages:      10
        Characters: 22914
        Obsoletes:  RFC3734

        I-D Tag:    draft-hollenbeck-epp-rfc3734bis-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4934.txt

This document describes how an Extensible Provisioning Protocol (EPP)
session is mapped onto a single Transmission Control Protocol (TCP)
connection.  This mapping requires use of the Transport Layer
Security (TLS) protocol to protect information exchanged between an
EPP client and an EPP server.  This document obsoletes RFC 3734. [STANDARDS TRACK]

This is now a Draft Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list