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

My reply...

Scott

-----Original Message-----
From: Hollenbeck, Scott =

Sent: Monday, December 15, 2014 11:20 AM
To: RFC Errata System; [email protected]
Cc: [email protected]
Subject: RE: [Technical Errata Reported] RFC5731 (4200)

> -----Original Message-----
> From: RFC Errata System [mailto:[email protected]]
> Sent: Monday, December 15, 2014 10:55 AM
> To: Hollenbeck, Scott; [email protected]
> Cc: [email protected]; [email protected]
> 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=3D5731&eid=3D4200
> =

> --------------------------------------
> Type: Technical
> Reported by: St=C3=A9phane Bortzmeyer <[email protected]>
> =

> 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 define=
d 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 dat=
e, 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 menti=
oned in the normative XML Schema reference.

Scott

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg