RFC 3730 on Extensible Provisioning Protocol (EPP)

rfc-editor@rfc-editor.org Sat, 27 March 2004 01:29 UTC

Received: from asgard.ietf.org (asgard.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01197 for <ietf-announce-archive@odin.ietf.org>; Fri, 26 Mar 2004 20:29:30 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B72a7-0005an-VK for ietf-announce-list@asgard.ietf.org; Fri, 26 Mar 2004 20:25:51 -0500
Received: from ietf.org ([]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B72V1-0005HG-D6 for all-ietf@asgard.ietf.org; Fri, 26 Mar 2004 20:20:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00586 for <all-ietf@ietf.org>; Fri, 26 Mar 2004 20:20:33 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1B72Uz-00069r-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:20:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B72U2-00064f-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:19:34 -0500
Received: from gamma.isi.edu ([]) by ietf-mx with esmtp (Exim 4.12) id 1B72TJ-00060P-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:18:49 -0500
Received: from ISI.EDU (jet.isi.edu []) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i2R1Ink27791; Fri, 26 Mar 2004 17:18:49 -0800 (PST)
Message-Id: <200403270118.i2R1Ink27791@gamma.isi.edu>
To: IETF-Announce: ;
Subject: RFC 3730 on Extensible Provisioning Protocol (EPP)
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:18:49 -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 3730

        Title:      Extensible Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    shollenbeck@verisign.com
        Pages:      69
        Characters: 134337
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3730.txt

This document describes an application layer client-server protocol
for the provisioning and management of objects stored in a shared
central repository.  Specified in XML, the protocol defines generic
object management operations and an extensible framework that maps
protocol operations to objects.  This document includes a protocol
specification, an object mapping template, and an XML media type

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

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.