Corrected Announcement: STD 69, RFC 5733 on Extensible Provisioning Protocol (EPP) Contact Mapping
RFC Editor <rfc-editor@rfc-editor.org> Tue, 01 September 2009 16:59 UTC
Return-Path: <rfc-ed@ISI.EDU>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A31C03A6CE9 for <ietf-announce@core3.amsl.com>; Tue, 1 Sep 2009 09:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.513
X-Spam-Level:
X-Spam-Status: No, score=-16.513 tagged_above=-999 required=5 tests=[AWL=0.486, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KqvyKbNHUwut for <ietf-announce@core3.amsl.com>; Tue, 1 Sep 2009 09:59:48 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id B2BF73A6DD0 for <ietf-announce@ietf.org>; Tue, 1 Sep 2009 09:59:48 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n81GxUsN012340; Tue, 1 Sep 2009 09:59:31 -0700 (PDT)
Received: (from rfc-ed@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n81GxUqH012339; Tue, 1 Sep 2009 09:59:30 -0700 (PDT)
Date: Tue, 01 Sep 2009 09:59:30 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Corrected Announcement: STD 69, RFC 5733 on Extensible Provisioning Protocol (EPP) Contact Mapping
Message-ID: <20090901165930.GB13142@isi.edu>
References: <20090901010623.346F9312E23@bosco.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20090901010623.346F9312E23@bosco.isi.edu>
User-Agent: Mutt/1.4.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@boreas.isi.edu
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2009 16:59:49 -0000
Resending with a correction. Note that the publication date remains August 2009. A new Request for Comments is now available in online RFC libraries. STD 69 RFC 5733 Title: Extensible Provisioning Protocol (EPP) Contact Mapping Author: S. Hollenbeck Status: Standards Track Date: August 2009 Mailbox: shollenbeck@verisign.com Pages: 41 Characters: 80698 Obsoletes: RFC4933 See Also: STD0069 I-D Tag: draft-hollenbeck-rfc4933bis-02.txt URL: http://www.rfc-editor.org/rfc/rfc5733.txt This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 4933. [STANDARDS TRACK] This is now a 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 unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute