[provreg] FW: RE: [Technical Errata Reported] RFC5731 (4200)

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 16 December 2014 14:16 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323AD1A1B1E for <provreg@ietfa.amsl.com>; Tue, 16 Dec 2014 06:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhRSqvYiKchr for <provreg@ietfa.amsl.com>; Tue, 16 Dec 2014 06:16:15 -0800 (PST)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0486B1A1AB3 for <provreg@ietf.org>; Tue, 16 Dec 2014 06:16:15 -0800 (PST)
Received: from brn1lxmailout01.verisign.com ([72.13.63.41]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKVJA+rjFsMKbDxLcfV3DfjlfmtqPvVhxu@postini.com; Tue, 16 Dec 2014 06:16:15 PST
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id sBGEGDeP024979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <provreg@ietf.org>; Tue, 16 Dec 2014 09:16:13 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 16 Dec 2014 09:16:13 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "provreg@ietf.org" <provreg@ietf.org>
Thread-Topic: RE: [Technical Errata Reported] RFC5731 (4200)
Thread-Index: AdAZOtgggWsTMkq+Sdm6tmoKP1OMig==
Date: Tue, 16 Dec 2014 14:16:12 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4954494E@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/provreg/o4Sz0Wxc6xMZa27KcD-cc1JnxHE
Subject: [provreg] FW: RE: [Technical Errata Reported] RFC5731 (4200)
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2014 14:16:17 -0000

My reply...

Scott

-----Original Message-----
From: Hollenbeck, Scott 
Sent: Monday, December 15, 2014 11:20 AM
To: RFC Errata System; iesg@ietf.org
Cc: bortzmeyer+rfceditor@nic.fr
Subject: RE: [Technical Errata Reported] RFC5731 (4200)

> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> Sent: Monday, December 15, 2014 10:55 AM
> To: Hollenbeck, Scott; iesg@ietf.org
> Cc: bortzmeyer+rfceditor@nic.fr; rfc-editor@rfc-editor.org
> Subject: [Technical Errata Reported] RFC5731 (4200)
> 
> The following errata report has been submitted for RFC5731,
> "Extensible Provisioning Protocol (EPP) Domain Name Mapping".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5731&eid=4200
> 
> --------------------------------------
> Type: Technical
> Reported by: Stéphane Bortzmeyer <bortzmeyer+rfceditor@nic.fr>
> 
> Section: 3.2.3
> 
> Original Text
> -------------
>  C:        <domain:curExpDate>2000-04-03</domain:curExpDate>
> 
> Corrected Text
> --------------
>  C:        <domain:curExpDate>2000-04-03Z</domain:curExpDate>
> 
> Notes
> -----
> The Z for UTC seems mandatory, per section 2.4 (in XML schema, it is
> optional http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#date ).
> Since <renew> is the only command with date (and not date-times), one
> may think dates are not forced to have a trailing Z but it is not
> mentioned in the RFC.

This is the text from Section 2.4 of RFC 5731:

"The extended date-time form using upper case "T" and "Z" characters defined in [W3C.REC-xmlschema-2-20041028] MUST be used to represent **date-time** values, as XML Schema does not support truncated date-time forms or lower case "T" and "Z" characters."

I used "**" to emphasize the requirement in the text for date-time, not date, values. The date in the example is described by the XML Schema date (not dateTime) data type, which does not require use of the optional time zone. This isn't explicitly mentioned in RFC 5731 because it is explicitly mentioned in the normative XML Schema reference.

Scott