[ischedule] Section 7.1

Mike Douglass <douglm@rpi.edu> Mon, 23 November 2009 04:36 UTC

Message-ID: <4B0A1130.4040803@rpi.edu>
Date: Sun, 22 Nov 2009 23:36:00 -0500
From: Mike Douglass <douglm@rpi.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: ischedule@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [ischedule] Section 7.1
Precedence: list

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].




-- 

Mike Douglass                           douglm@rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180

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