[ietf-provreg] IESG Review Request: EPP to Draft

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 25 September 2006 16:50 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GRtec-0002Bu-Mr for provreg-archive@ietf.org; Mon, 25 Sep 2006 12:50:02 -0400
Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GRtYe-0002HB-QM for provreg-archive@ietf.org; Mon, 25 Sep 2006 12:43:54 -0400
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id k8PGZ4Es005527 for <ietf-provreg-outgoing@nic.cafax.se>; Mon, 25 Sep 2006 18:35:04 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id k8PGZ4EW003453 for ietf-provreg-outgoing; Mon, 25 Sep 2006 18:35:04 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from osprey.verisign.com (osprey.verisign.com [216.168.239.75]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id k8PGZ1hQ003469 for <ietf-provreg@cafax.se>; Mon, 25 Sep 2006 18:35:02 +0200 (MEST)
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id k8PGZ8dX028856; Mon, 25 Sep 2006 12:35:08 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Sep 2006 12:33:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [ietf-provreg] IESG Review Request: EPP to Draft
Date: Mon, 25 Sep 2006 12:34:59 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF0701801AB2@dul1wnexmb01.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IESG Review Request: EPP to Draft
Thread-Index: AcbgwIrrMk14ZYQiSma9iV8/vOlJsQ==
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Ted Hardie <hardie@qualcomm.com>, Lisa Dusseault <lisa@osafoundation.org>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se
X-OriginalArrivalTime: 25 Sep 2006 16:33:52.0312 (UTC) FILETIME=[62D53380:01C6E0C0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by nic.cafax.se id k8PGZ3hQ022921
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

Ted, Lisa:

With recent Internet-Draft document updates and posting of an
implementation report I believe that all of the RFC 2026
proposed-to-draft milestones that can be met by the former provreg
working group have been met.  I would like to ask you to evaluate the
Internet-Draft documents for elevation to Draft Standard status.  Here
is a link to the implementation report:

http://www.ietf.org/IESG/Implementations/RFCs3730-3734_implem.txt

There are some normative references that are still at Proposed Standard
status.  Here's a list of the documents and the references in question:

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3730bis-03.t
xt
RFC 3023 (XML Media Types)
RFC 3339 (Date and Time on the Internet: Timestamps)

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3731bis-04.t
xt
RFC 3339 (Date and Time on the Internet: Timestamps)

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3732bis-03.t
xt
RFC 3339 (Date and Time on the Internet: Timestamps)
RFC 3513 (Internet Protocol Version 6 (IPv6) Addressing Architecture)

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3733bis-04.t
xt
RFC 2822 (Internet Message Format)
RFC 3339 (Date and Time on the Internet: Timestamps)

http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc3734bis-03.t
xt
RFC 2246 (The TLS Protocol Version 1.0)

Each document includes an appendix containing a list of changes from the
relevant RFC.  While there were several text changes to clarify portions
of the text as a result of implementation experience, there were no
schema changes needed when updating the documents.  The EPP version
specified in the original RFCs and the -bis documents remains the same.

I'm available to answer any questions.  Thank you for your
consideration.

-Scott-