RE: Last Call: 'Extensible Provisioning Protocol (EPP)' toDraftStandard (draft-hollenbeck-epp-rfc3730bis)
"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 18 October 2006 11:17 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga9QS-0000ro-7E; Wed, 18 Oct 2006 07:17:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga9QP-0000pO-T2 for ietf@ietf.org; Wed, 18 Oct 2006 07:17:30 -0400
Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ga9QO-0002yI-Kj for ietf@ietf.org; Wed, 18 Oct 2006 07:17:29 -0400
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id k9IBHWwm003239; Wed, 18 Oct 2006 07:17:32 -0400
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 07:17:28 -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"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 18 Oct 2006 07:17:25 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF0701866F11@dul1wnexmb01.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Last Call: 'Extensible Provisioning Protocol (EPP)' toDraftStandard (draft-hollenbeck-epp-rfc3730bis)
Thread-Index: AcbyUczxFaNtflwTRS6LLTluBzX3+QAUvz8Q
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Frank Ellermann <nobody@xyzzy.claranet.de>, ietf@ietf.org
X-OriginalArrivalTime: 18 Oct 2006 11:17:28.0087 (UTC) FILETIME=[FEDA9A70:01C6F2A6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc:
Subject: RE: Last Call: 'Extensible Provisioning Protocol (EPP)' toDraftStandard (draft-hollenbeck-epp-rfc3730bis)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
> -----Original Message----- > From: Frank Ellermann [mailto:nobody@xyzzy.claranet.de] > Sent: Tuesday, October 17, 2006 8:42 PM > To: ietf@ietf.org > Subject: Re: Last Call: 'Extensible Provisioning Protocol > (EPP)' toDraftStandard (draft-hollenbeck-epp-rfc3730bis) > > Hollenbeck, Scott wrote: > > > RFC 3339 (Date and Time on the Internet: Timestamps) > > Referenced by: draft-hollenbeck-epp-rfc3730bis-03, > > draft-hollenbeck-epp-rfc3731bis-04, > draft-hollenbeck-epp-rfc3732bis-03, > > draft-hollenbeck-epp-rfc3733bis-04 > > This reference is sited to capture a format that is also > available in > > the W3C's XML Schema specifications. It can be replaced with an > > existing normative reference to the W3C specification. > > That's odd, why should you be forced to replace a normative > reference to > the perfectly fine RFC 3339 by some spec. published elsewhere ? AFAIK > nothing is wrong with RFC 3339, let's just promote it if > that's what it > takes to reference it. There's more to it than "just promote it". The practical point is that 3339 is only used to specify time and date formats that are a subset of existing XML Schema formats. XML Schema is already a needed normative reference. I don't really need two normative references that specify the same thing, and I can't eliminate the Schema reference. -Scott- _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: Last Call: 'Extensible Provisioning Protocol … Hollenbeck, Scott
- Re: Last Call: 'Extensible Provisioning Protocol … Frank Ellermann