[ietf-provreg] RFC 3735 on Guidelines for Extending the Extensible Provisioning Protocol (EPP)
rfc-editor@rfc-editor.org Sat, 27 March 2004 18:55 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25000 for <provreg-archive@ietf.org>; Sat, 27 Mar 2004 13:55:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B7IyO-0003f1-00 for provreg-archive@ietf.org; Sat, 27 Mar 2004 13:56:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B7IxS-0003ZJ-00 for provreg-archive@ietf.org; Sat, 27 Mar 2004 13:55:03 -0500
Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx with esmtp (Exim 4.12) id 1B7IwW-0003UC-00 for provreg-archive@ietf.org; Sat, 27 Mar 2004 13:54:04 -0500
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i2RIeJ6l023147 for <ietf-provreg-outgoing@nic.cafax.se>; Sat, 27 Mar 2004 19:40:19 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.11/8.12.11/Submit) id i2RIeJqx023146 for ietf-provreg-outgoing; Sat, 27 Mar 2004 19:40:19 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from bartok.sidn.nl (bartok.sidn.nl [193.176.144.164]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i2RIeGPd023141 for <ietf-provreg@cafax.se>; Sat, 27 Mar 2004 19:40:17 +0100 (MET)
Received: from bartok.sidn.nl (localhost.sidn.nl [127.0.0.1]) by bartok.sidn.nl (8.12.11/8.12.11) with ESMTP id i2RIeFJd048057 for <ietf-provreg@cafax.se>; Sat, 27 Mar 2004 19:40:15 +0100 (CET) (envelope-from jaap@bartok.sidn.nl)
Received: (from jaap@localhost) by bartok.sidn.nl (8.12.11/8.12.10/Submit) id i2RIeFNZ048056 for ietf-provreg@cafax.se; Sat, 27 Mar 2004 19:40:15 +0100 (CET) (envelope-from jaap)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i2R1aXTC016051 for <ietf-provreg@cafax.se>; Sat, 27 Mar 2004 02:36:34 +0100 (MET)
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: [ietf-provreg] 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
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
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.