RFC 3735 on Guidelines for Extending the Extensible Provisioning Protocol (EPP)

rfc-editor@rfc-editor.org Sat, 27 March 2004 01:57 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 UAA03315 for <ietf-announce-archive@odin.ietf.org>; Fri, 26 Mar 2004 20:57:03 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B72x2-0001wI-6v for ietf-announce-list@asgard.ietf.org; Fri, 26 Mar 2004 20:49:32 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B72mG-0000Tb-O9 for all-ietf@asgard.ietf.org; Fri, 26 Mar 2004 20:38:24 -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 UAA02165 for <all-ietf@ietf.org>; Fri, 26 Mar 2004 20:38:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B72mF-0000O9-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:38:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B72lH-0000KL-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:37:24 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1B72kR-0000GX-00 for all-ietf@ietf.org; Fri, 26 Mar 2004 20:36:31 -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 i2R1aVk02065; Fri, 26 Mar 2004 17:36:31 -0800 (PST)
Message-Id: <200403270136.i2R1aVk02065@gamma.isi.edu>
To: IETF-Announce: ;
Subject: RFC 3735 on Guidelines for Extending the 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:36:31 -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 3735

        Title:      Guidelines for Extending the Extensible
                    Provisioning Protocol (EPP)
        Author(s):  S. Hollenbeck
        Status:     Informational
        Date:       March 2004
        Mailbox:    shollenbeck@verisign.com
        Pages:      13
        Characters: 27326
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-provreg-epp-ext-03.txt

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


The Extensible Provisioning Protocol (EPP) is 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 presents guidelines for use of EPP's extension mechanisms to
define new features and object management capabilities.

This document is a product of the Provisioning Registry Working Group
of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.
ftp://ftp.isi.edu/in-notes/rfc3735.txt"><ftp://ftp.isi.edu/in-notes/rfc3735.txt>