[Ietf-calsify] Issue 26: BYHOUR, BYMINUTE,
and BYSECOND recurrence rules where value type is DATE
lear at cisco.com
Sat Sep 30 03:09:00 PDT 2006
Sam Roberts wrote:
> On Fri, Sep 29, 2006 at 04:25:21PM +0200, Eliot Lear wrote:
>> NEW TEXT:
>> of hours of the day. Valid values are 0 to 23. Implementations
>> MUST NOT generate BYHOUR, BYMINUTE, OR BYSECOND when the associated
>> DTSTART uses VALUE=DATE. Similarly, Implementations MUST ignore
>> such constructs when see, optionally logging an error.
> Are you sure you want to tell people that they MUST accept as valid
> files that were generated in violation of a MUST? Seems odd to me to be
> in the business of telling people what to do with invalid data, its
> hard enough to specify what to do with valid data.
See Dave's not about the history of the combo. Host Requirements (RFC
1122 / RFC 1123) made use of it first, as I recall.
To remind people the current text is based on the group's consensus. In
this case the intentions of the sender are almost completely
unfathomable as it's a bit of a non-sequitor.
> Anyhow, its not clear to me what it means to ignore the "construct". Is
> it the entire calendar, the VEVENT, the RRULE, the "BYMINUTE=..." that
> shouldn't be there?
You're right. I believe Bernard actually has better wording to address
More information about the Ietf-calsify