RFC 3734 on Extensible Provisioning Protocol (EPP) Transport Over TCP
rfc-editor@rfc-editor.org Sat, 27 March 2004 01:39 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02211 for <ietf-announce-archive@odin.ietf.org>; Fri, 26 Mar 2004 20:39:54 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B72lk-0000T7-BJ for ietf-announce-list@asgard.ietf.org; Fri, 26 Mar 2004 20:37:52 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B72kR-0000LM-Ni for all-ietf@asgard.ietf.org; Fri, 26 Mar 2004 20:36:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02083 for <all-ietf@ietf.org>; Fri, 26 Mar 2004 20:36:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B72kQ-0000GL-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:36:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B72jg-0000BQ-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:35:45 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1B72iz-00003y-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:35:01 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2R1Z1k02002; Fri, 26 Mar 2004 17:35:01 -0800 (PST)
Message-Id: <200403270135.i2R1Z1k02002@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3734 on Extensible Provisioning Protocol (EPP) Transport Over TCP
Cc: rfc-editor@rfc-editor.org, ietf-provreg@cafax.se
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 26 Mar 2004 17:35:01 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.2 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3734 Title: Extensible Provisioning Protocol (EPP) Transport Over TCP Author(s): S. Hollenbeck Status: Standards Track Date: March 2004 Mailbox: shollenbeck@verisign.com Pages: 9 Characters: 19550 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-provreg-epp-tcp-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3734.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 is a product of the Provisioning Registry Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. 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 unlimited. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.