[ischedule] Section 7.1

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

Return-Path: <douglm@rpi.edu>
X-Original-To: ischedule@core3.amsl.com
Delivered-To: ischedule@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 313F93A6896 for <ischedule@core3.amsl.com>; Sun, 22 Nov 2009 20:36:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fLON2g1wZcEg for <ischedule@core3.amsl.com>; Sun, 22 Nov 2009 20:36:07 -0800 (PST)
Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by core3.amsl.com (Postfix) with ESMTP id 51A683A6827 for <ischedule@ietf.org>; Sun, 22 Nov 2009 20:36:07 -0800 (PST)
Received: from [192.168.2.10] (cpe-24-92-49-115.nycap.res.rr.com [24.92.49.115]) (authenticated bits=0) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id nAN4a1VM000459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ischedule@ietf.org>; Sun, 22 Nov 2009 23:36:01 -0500
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
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always)
X-CanItPRO-Stream: outgoing
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225
Subject: [ischedule] Section 7.1
X-BeenThere: ischedule@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Calendar Scheduling Protocol \(iSchedule\) discussion list" <ischedule.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ischedule>, <mailto:ischedule-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ischedule>
List-Post: <mailto:ischedule@ietf.org>
List-Help: <mailto:ischedule-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ischedule>, <mailto:ischedule-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2009 04:36:08 -0000

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