Re: [ischedule] Section 7.1

Bernard Desruisseaux <bernard.desruisseaux@oracle.com> Mon, 23 November 2009 13:51 UTC

Message-ID: <4B0A9344.5090702@oracle.com>
Date: Mon, 23 Nov 2009 08:51:00 -0500
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Mike Douglass <douglm@rpi.edu>
References: <4B0A1130.4040803@rpi.edu>
In-Reply-To: <4B0A1130.4040803@rpi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ischedule@ietf.org
Subject: Re: [ischedule] Section 7.1
Precedence: list

Indeed.  Fixed.

Thanks,
Bernard

Mike Douglass wrote:
> This doesn't seem correct - it's the originator of the message
> 
>       (originator-specified): The POST request MUST include a valid
>       Originator request header specifying a single calendar user
>       address of the currently authenticated user;
> 
> 
> Shouldn't this be the same as 7.1.1
> 
> Every POST request MUST include a single Originator request header
>    that specifies the calendar user address of the originator of the
>    scheduling message.
> 
> or 9.1
> 
>    The Originator request header value is a URI which specifies the
>    calendar user address of the originator of the scheduling message.
>    Note that the absoluteURI production is defined in RFC3986 [RFC3986].
> 
> 
> 
>

[ischedule] Section 7.1 Mike Douglass
Re: [ischedule] Section 7.1 Bernard Desruisseaux