
From ietf-calsify-bounces@osafoundation.org  Wed May 12 10:49:02 2010
Return-Path: <ietf-calsify-bounces@osafoundation.org>
X-Original-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78FB83A6D38 for <ietfarch-calsify-archive-Feit0ahl@core3.amsl.com>; Wed, 12 May 2010 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.197
X-Spam-Level: 
X-Spam-Status: No, score=0.197 tagged_above=-999 required=5 tests=[AWL=-1.703, BAYES_50=0.001, FB_CIALIS_LEO3=3.899, GB_I_INVITATION=-2]
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 YuOrZ0jy8ErH for <ietfarch-calsify-archive-Feit0ahl@core3.amsl.com>; Wed, 12 May 2010 10:49:00 -0700 (PDT)
Received: from leka.osafoundation.org (leka.osafoundation.org [149.20.54.96]) by core3.amsl.com (Postfix) with ESMTP id D34E83A68C7 for <calsify-archive-Feit0ahl@lists.ietf.org>; Wed, 12 May 2010 10:24:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id A8F547841F2; Wed, 12 May 2010 10:24:23 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNw19oX4DIr7; Wed, 12 May 2010 10:24:10 -0700 (PDT)
Received: from leka.osafoundation.org (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id B0ECD7841F7; Wed, 12 May 2010 10:24:05 -0700 (PDT)
X-Original-To: ietf-calsify@osafoundation.org
Delivered-To: ietf-calsify@osafoundation.org
Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 808FD7841F2 for <ietf-calsify@osafoundation.org>; Wed, 12 May 2010 10:24:02 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaCP60gCPsQF for <ietf-calsify@osafoundation.org>; Wed, 12 May 2010 10:23:39 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by leka.osafoundation.org (Postfix) with ESMTP id 55B807841FA for <ietf-calsify@osafoundation.org>; Wed, 12 May 2010 10:23:38 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C0D9640D06 for <ietf-calsify@osafoundation.org>; Wed, 12 May 2010 11:23:36 -0600 (MDT)
Message-ID: <4BEAE417.4070304@stpeter.im>
Date: Wed, 12 May 2010 11:23:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: ietf-calsify@osafoundation.org
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Subject: [ietf-calsify] AD review of iMIP I-D
X-BeenThere: ietf-calsify@osafoundation.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RFC2445, 2446 and 2447 Discusions" <ietf-calsify.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-calsify>
List-Post: <mailto:ietf-calsify@osafoundation.org>
List-Help: <mailto:ietf-calsify-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-calsify>,  <mailto:ietf-calsify-request@osafoundation.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0928161997=="
Mime-version: 1.0
Sender: ietf-calsify-bounces@osafoundation.org
Errors-To: ietf-calsify-bounces@osafoundation.org

This is a cryptographically signed message in MIME format.

--===============0928161997==
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040204070609020004080909"

This is a cryptographically signed message in MIME format.

--------------ms040204070609020004080909
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Because Alexey is my co-AD, I'll act as the sponsoring AD for
draft-ietf-calsify-rfc2447bis. Here are some comments based on my review.=
=2E.

1. The Table of Contents does not match the actual contents (section
names and numbers are different in some places).

2. IMHO we don't need the second two paragraphs of the Abstract.

3. Update iTIP reference to RFC 5546.

4. In Section 2, this issue is confusing:

   The [RFC-5322] "Reply-To" header field typically contains the email
   address of the originator of the scheduling message. <<However, this
   cannot be guaranteed as Mail User Agents (MUA) are not required to
   enforce iMIP semantics.>>

I don't see "scheduling message" defined in RFC 5545 or RFC 5546 (is it
the email message containing the iCAL data or the iCAL data itself?).
However, I think this could be phrased a bit better:

   Ideally the [RFC-5322] "Reply-To" header field of the iMIP message
   will contain the email address of the originator of the scheduling
   message.  However, this cannot be guaranteed because the sender of
   the iMIP message might not be the originator of the scheduling
   message and the sender's Mail User Agent (MUA) might not enforce
   iMIP semantics by translating the originator's address into the
   "Reply-To" email header.

But perhaps that's not what we are trying to say... :)

5. It would be nice to spell out the base64-encoded data from the
DESCRIPTION field of the example in Section 2.5.

6. In Section 3, the term "CU" is not spelled out -- I assume it means
"Calendar User".

7. In Section 3:

   1. The iCalendar object MUST be signed by the "Organizer" sending an
   update/initial request; the "Attendee" sending a reply; or another
   ("uninvited") CU, who was forwarded a REQUEST, sending a reply.  <<Or
   the person sending on their behalf? Clearly if somebody else is
   sending the invitation, she can't sign using the key belonging to the
   organizer>>

Although there is no automated method for discovering whether someone is
an authorized delegate for an Organizer (or an Attendee), a signed iCAL
object from another entity in the same trust domain might provide some
level of assurance regarding authorization (e.g., if the object is
signed by someone else at isode.com then I might have more trust in it
than if it were signed by someone at mail.ru).

[This problem is related to a number of other delegation use cases we've
stumbled upon lately -- Richard Barnes and I plan to write an I-D that
describes this problem for a number of different technologies.]

In any case, the MUST here seems strange, because we are talking about
processing of a signed iMIP message, not generation of a signed iMIP
message. What is the force of the MUST here? Is it REQUIRED for the
processing MUA/CUA to discard the object if it is not signed, or not
signed by the Organizer, an Attendee, or an uninvited calendar user? The
latter entity provides a loophole here anyway, so I'm not sure how
valuable the restriction really is...

Then we have:

   3. Correlate the signer to either an "ATTENDEE" property or to the
   "ORGANIZER" property in the iCalendar object, based on the method and
   the calendar component specified in the iCalendar object, as defined
   in Section 1.4 of [iTIP].  If the signer cannot be correlated to an
   "ATTENDEE"/"ORGANIZER" property (or is not authorized to act on her
   behalf), ignore the message.

Realistically, ignoring the message might be too strict, given that it
will simply discourage people from signing iCAL objects (don't we all
accept unsigned email messages and calendaring invites?). Perhaps we
need some language here similar to what we use for server certificate
checking, such as:

   3. Correlate the signer to either an "ATTENDEE" property or to the
   "ORGANIZER" property in the iCalendar object, based on the method and
   the calendar component specified in the iCalendar object, as defined
   in Section 1.4 of [iTIP].  If the signer cannot be correlated to an
   "ATTENDEE"/"ORGANIZER" property, then actively warn the user
   controlling the calendar user agent that the iCalendar object is
   untrusted and encourage the user to terminate the connection, but
   give advanced users the option to (a) view the signature and the
   entire certificate chain (if any), (b) accept the certificate either
   temporarily (i.e., for this iCalendar object only) or permanently
   (i.e., for all future iCalendar objects), and then (c) continue with
   processing of the iCalendar object.

My reasoning is that a user might have knowledge outside the context of
automated processing that a particular entity has delegated authority to
send (and sign) iCalendar objects on behalf of an Originator or Attendee.=


These considerations might lead us to change this paragraph, too:

   It is possible to receive iMIP messages sent by someone working on
   behalf of another "Calendar User". This is determined by examining
   the "sent-by" parameter in the relevant "ORGANIZER" or "ATTENDEE"
   property.  [iCAL] and [iTIP] provide no mechanism to verify that a
   "Calendar User" has authorized someone else to work on their behalf.
   To address this security issue, implementations MUST provide
   mechanisms for the "Calendar Users" to make that decision before
   applying changes from someone working on behalf of a "Calendar User".
   One way to achieve this is to reject iMIP messages sent by users
   other than the "ORGANIZER" or the "ATTENDEE"s.

8. Also in Section 3:

   If an unsigned iMIP message is received from the same
   sender later on, the receiving CUA SHOULD warn the receiving user
   about a possible man-in-the-middle attack and SHOULD ignore the
   message, unless explicitly overridden by the user. <<Should it also
   try to notify the other end?>>

I don't see a good reason to try to notify the other end -- if there
really is a MITM then presumably Mallory can masquerade as either side.

9. Please spell out URI on first use (Section 2.3) and/or in Section 5.1.=


10. In Section 5.1 we have:

   The [iCAL] specification makes frequent use of the URI for data types
   in properties such as "DESCRIPTION", "ATTACH", "CONTACT" and others.
   Two forms of URIs are Message ID (MID) and Content ID (CID). These
   are defined in [RFC-2392]. Although [RFC-2392] allows referencing
   messages or MIME body parts in other MIME entities or stores, it is
   strongly recommended that iMIP implementations include all referenced
   messages and body parts in a single MIME entity. Simply put, if an
   iCalendar object contains CID or MID references to other messages or
   body parts, implementations should ensure that these messages and/or
   body parts are transmitted with the iCalendar object. If they are
   not, there is no guarantee that the receiving CUA will have the
   access or the authorization to view those objects.

s/recommended/RECOMMENDED/ ?

s/should/SHOULD/ ?

That's all I found, but I'm not a MIME expert!

Peter

--
Peter Saint-Andre
https://stpeter.im/




--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms040204070609020004080909
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC
B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT
aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG
EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q
UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0
aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN
AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs
hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP
XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5
wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV//
Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID
hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA
c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg
RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw
ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG
CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8
BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0
eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv
bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC
hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA
A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R
gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA
X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/
kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM
UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g
AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw
DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k
YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl
IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0
cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue
HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/
+Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1
siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz
yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9
sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud
EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy
LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI
KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH
AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF
BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk
IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy
dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0
c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j
cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz
cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV
HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/
jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh
BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk
/eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw
xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i
bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP
MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD
EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x
MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr
MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv
U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO
0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx
c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B
x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ
bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ
6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd
BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX
aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE
AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr
BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et
Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD
VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j
ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z
dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg
Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy
ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu
c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB
DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt
YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT
fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T
lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H
jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h
dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX
luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ
FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC
IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO
3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+
YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20
OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTEwMDUxMjE3MjMzNVowIwYJKoZIhvcNAQkEMRYEFMz33WrTS13jsdgWvQd0
R6KyL/amMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ
KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk
LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE
AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw
gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg
Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAcKTnwkT9vzDxNjFvTFOjEwBadAd1IqKEpaVttCw9
yxWdh1viIAu6/5GAMERILqbofJbLTTiidWSWONqeejOWUA2+v2oxuZufQR2eXd7F3B99+Lpr
Eige6uRVvPPuSvmDuSfgjVgh8pzOWFJ7h7nnn3EHDgl5o/EX0YvgKJkc54/GUHv16j/sUx9v
v6QYhKqbiWeBOpbRndfh4nfSi1ZgyDd7jTXkax5HaFYObNNOCRETCRsFgToBfNqGd1zQclMs
TKDXNneyB/g6a0xg70oU2QvKiKkDfhAgC2ceCZA83sNXMBZSkNXCc6tLOCsgUfYq1/VjW9uZ
xn+bQA4tqFC+8QAAAAAAAA==
--------------ms040204070609020004080909--

--===============0928161997==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ietf-calsify mailing list
ietf-calsify@osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

--===============0928161997==--

From ciny.joy@oracle.com  Wed May 12 10:58:34 2010
Return-Path: <ciny.joy@oracle.com>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3704B3A6A30 for <calsify@core3.amsl.com>; Wed, 12 May 2010 10:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 XT5+AMZHIEpP for <calsify@core3.amsl.com>; Wed, 12 May 2010 10:58:33 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 695593A69B2 for <calsify@ietf.org>; Wed, 12 May 2010 10:36:49 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4CHabuT001618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <calsify@ietf.org>; Wed, 12 May 2010 17:36:38 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4CAweNK021421 for <calsify@ietf.org>; Wed, 12 May 2010 17:36:26 GMT
Received: from abhmt018.oracle.com by acsmt354.oracle.com with ESMTP id 235818491273685779; Wed, 12 May 2010 10:36:19 -0700
Received: from [192.168.1.100] (/129.150.235.180) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 12 May 2010 10:36:19 -0700
Message-Id: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: calsify@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 12 May 2010 10:36:17 -0700
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090205.4BEAE726.0169:SCFMA922111,ss=1,fgs=0
Subject: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2010 17:58:34 -0000

Hello,
    A draft defining the schema for representing resources for  
calendaring and scheduling services has been submitted to the IETF as  
an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00 
  . A resource in the scheduling context is any shared entity that can  
be scheduled by a calendar user, but does not control its own  
attendance status. Would really appreciate review and comments.

Thank you,
Ciny

From calsify-bounces@ietf.org  Wed May 12 10:58:35 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54BC928C24A; Wed, 12 May 2010 10:58:35 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3704B3A6A30 for <calsify@core3.amsl.com>; Wed, 12 May 2010 10:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 XT5+AMZHIEpP for <calsify@core3.amsl.com>; Wed, 12 May 2010 10:58:33 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 695593A69B2 for <calsify@ietf.org>; Wed, 12 May 2010 10:36:49 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4CHabuT001618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <calsify@ietf.org>; Wed, 12 May 2010 17:36:38 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4CAweNK021421 for <calsify@ietf.org>; Wed, 12 May 2010 17:36:26 GMT
Received: from abhmt018.oracle.com by acsmt354.oracle.com with ESMTP id 235818491273685779; Wed, 12 May 2010 10:36:19 -0700
Received: from [192.168.1.100] (/129.150.235.180) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 12 May 2010 10:36:19 -0700
Message-Id: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: calsify@ietf.org
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 12 May 2010 10:36:17 -0700
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090205.4BEAE726.0169:SCFMA922111,ss=1,fgs=0
Subject: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

Hello,
    A draft defining the schema for representing resources for  
calendaring and scheduling services has been submitted to the IETF as  
an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00 
  . A resource in the scheduling context is any shared entity that can  
be scheduled by a calendar user, but does not control its own  
attendance status. Would really appreciate review and comments.

Thank you,
Ciny
_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From timhare@comcast.net  Thu May 13 20:16:56 2010
Return-Path: <timhare@comcast.net>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B14663A6852 for <calsify@core3.amsl.com>; Thu, 13 May 2010 20:16:56 -0700 (PDT)
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 G9ykB0-QVW8U for <calsify@core3.amsl.com>; Thu, 13 May 2010 20:16:35 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by core3.amsl.com (Postfix) with ESMTP id 243183A67D4 for <calsify@ietf.org>; Thu, 13 May 2010 20:16:35 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta04.westchester.pa.mail.comcast.net with comcast id HBk21e0031GhbT854FGSNF; Fri, 14 May 2010 03:16:26 +0000
Received: from THARE ([71.203.98.77]) by omta07.westchester.pa.mail.comcast.net with comcast id HFGR1e0041gAkVz3TFGRzU; Fri, 14 May 2010 03:16:26 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>, <calsify@ietf.org>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
In-Reply-To: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
Date: Thu, 13 May 2010 23:16:24 -0400
Message-ID: <008401caf313$d5e8ea60$81babf20$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acrx/LmE4yZQviTCRh66ZQ0wtjwlxgA+tTrA
Content-Language: en-us
Subject: Re: [calsify] Request for review - Schema for representing resources	for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 03:16:57 -0000

My comments on the document:

In many places, you have an LPAP example without any text describing it as
an example.  This did not seem clear to me until the third or fourth item
that was treated that way.

You have a comment on many items that says "Not required for a resource
scheduling query".  I think if you are going to take pains to do that, it
would be nice to have comments to say which things are required, and
possibly a table showing the attributes and whether they are required or
not.  On the other hand, I am not sure this information is required for a
schema and perhaps it might be better in a document describing how resources
are scheduled.

Tim Hare
Interested Bystander, Non-Inc.


-----Original Message-----
From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On Behalf
Of Ciny Joy
Sent: Wednesday, May 12, 2010 1:36 PM
To: calsify@ietf.org
Subject: [calsify] Request for review - Schema for representing resources
for calendaring and scheduling services

Hello,
    A draft defining the schema for representing resources for  
calendaring and scheduling services has been submitted to the IETF as  
an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00 
  . A resource in the scheduling context is any shared entity that can  
be scheduled by a calendar user, but does not control its own  
attendance status. Would really appreciate review and comments.

Thank you,
Ciny
_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify


From calsify-bounces@ietf.org  Thu May 13 20:17:02 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 727D63A6852; Thu, 13 May 2010 20:17:02 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B14663A6852 for <calsify@core3.amsl.com>; Thu, 13 May 2010 20:16:56 -0700 (PDT)
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 G9ykB0-QVW8U for <calsify@core3.amsl.com>; Thu, 13 May 2010 20:16:35 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by core3.amsl.com (Postfix) with ESMTP id 243183A67D4 for <calsify@ietf.org>; Thu, 13 May 2010 20:16:35 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta04.westchester.pa.mail.comcast.net with comcast id HBk21e0031GhbT854FGSNF; Fri, 14 May 2010 03:16:26 +0000
Received: from THARE ([71.203.98.77]) by omta07.westchester.pa.mail.comcast.net with comcast id HFGR1e0041gAkVz3TFGRzU; Fri, 14 May 2010 03:16:26 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>, <calsify@ietf.org>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
In-Reply-To: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com>
Date: Thu, 13 May 2010 23:16:24 -0400
Message-ID: <008401caf313$d5e8ea60$81babf20$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acrx/LmE4yZQviTCRh66ZQ0wtjwlxgA+tTrA
Content-Language: en-us
Subject: Re: [calsify] Request for review - Schema for representing resources	for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

My comments on the document:

In many places, you have an LPAP example without any text describing it as
an example.  This did not seem clear to me until the third or fourth item
that was treated that way.

You have a comment on many items that says "Not required for a resource
scheduling query".  I think if you are going to take pains to do that, it
would be nice to have comments to say which things are required, and
possibly a table showing the attributes and whether they are required or
not.  On the other hand, I am not sure this information is required for a
schema and perhaps it might be better in a document describing how resources
are scheduled.

Tim Hare
Interested Bystander, Non-Inc.


-----Original Message-----
From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On Behalf
Of Ciny Joy
Sent: Wednesday, May 12, 2010 1:36 PM
To: calsify@ietf.org
Subject: [calsify] Request for review - Schema for representing resources
for calendaring and scheduling services

Hello,
    A draft defining the schema for representing resources for  
calendaring and scheduling services has been submitted to the IETF as  
an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00 
  . A resource in the scheduling context is any shared entity that can  
be scheduled by a calendar user, but does not control its own  
attendance status. Would really appreciate review and comments.

Thank you,
Ciny
_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From ciny.joy@oracle.com  Fri May 14 13:03:04 2010
Return-Path: <ciny.joy@oracle.com>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 821BE3A6452 for <calsify@core3.amsl.com>; Fri, 14 May 2010 13:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 FmNasLFN096Y for <calsify@core3.amsl.com>; Fri, 14 May 2010 13:03:03 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id EE62C28C160 for <calsify@ietf.org>; Fri, 14 May 2010 13:02:52 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4EK2TiC008988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 May 2010 20:02:33 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4EID49q000854; Fri, 14 May 2010 20:02:28 GMT
Received: from abhmt008.oracle.com by acsmt355.oracle.com with ESMTP id 242903321273867262; Fri, 14 May 2010 13:01:02 -0700
Received: from [192.168.1.111] (/129.150.0.50) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 14 May 2010 13:01:02 -0700
Message-Id: <6DA4C48C-8B27-4AE2-83D1-664D68E30071@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <008401caf313$d5e8ea60$81babf20$@net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 14 May 2010 13:00:58 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090201.4BEDAC5A.00DE:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 20:03:04 -0000

Thank you so much for your review and comments.
I will certainly try to mark the examples more clearly.

As far as the comment on scheduling query, I guess I could change so  
that the attributes that could be used for scheduling are indicated in  
some way in their description itself.

Thanks,
Ciny

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>


From calsify-bounces@ietf.org  Fri May 14 13:03:05 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3E7B3A694F; Fri, 14 May 2010 13:03:05 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 821BE3A6452 for <calsify@core3.amsl.com>; Fri, 14 May 2010 13:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 FmNasLFN096Y for <calsify@core3.amsl.com>; Fri, 14 May 2010 13:03:03 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id EE62C28C160 for <calsify@ietf.org>; Fri, 14 May 2010 13:02:52 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4EK2TiC008988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 May 2010 20:02:33 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4EID49q000854; Fri, 14 May 2010 20:02:28 GMT
Received: from abhmt008.oracle.com by acsmt355.oracle.com with ESMTP id 242903321273867262; Fri, 14 May 2010 13:01:02 -0700
Received: from [192.168.1.111] (/129.150.0.50) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 14 May 2010 13:01:02 -0700
Message-Id: <6DA4C48C-8B27-4AE2-83D1-664D68E30071@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <008401caf313$d5e8ea60$81babf20$@net>
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 14 May 2010 13:00:58 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090201.4BEDAC5A.00DE:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

Thank you so much for your review and comments.
I will certainly try to mark the examples more clearly.

As far as the comment on scheduling query, I guess I could change so  
that the attributes that could be used for scheduling are indicated in  
some way in their description itself.

Thanks,
Ciny

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From calsify-bounces@ietf.org  Tue May 18 16:12:30 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B61553A6916; Tue, 18 May 2010 16:12:30 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACAAD3A6916 for <calsify@core3.amsl.com>; Tue, 18 May 2010 16:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level: 
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=-0.651, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 Nqswrbxi2gvD for <calsify@core3.amsl.com>; Tue, 18 May 2010 16:12:28 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 4ABCD3A6902 for <calsify@ietf.org>; Tue, 18 May 2010 16:12:25 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4INC3gG030614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 May 2010 23:12:04 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4IKrRo6027463; Tue, 18 May 2010 23:12:02 GMT
Received: from abhmt004.oracle.com by acsmt354.oracle.com with ESMTP id 278684801274224316; Tue, 18 May 2010 16:11:56 -0700
Received: from dhcp-usca15-127-88.Red.IPlanet.COM (/192.18.127.88) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 18 May 2010 16:11:56 -0700
Message-Id: <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <008401caf313$d5e8ea60$81babf20$@net>
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 18 May 2010 16:11:33 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090203.4BF31EC4.01B8:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

Hello Tim,

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
Going through the document, I am not sure which LDAP examples you are  
referring to. I would really appreciate it, if you could point me to  
one such case.

Thanks,
Ciny

>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From ciny.joy@oracle.com  Tue May 18 16:12:29 2010
Return-Path: <ciny.joy@oracle.com>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACAAD3A6916 for <calsify@core3.amsl.com>; Tue, 18 May 2010 16:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level: 
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=-0.651, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=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 Nqswrbxi2gvD for <calsify@core3.amsl.com>; Tue, 18 May 2010 16:12:28 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 4ABCD3A6902 for <calsify@ietf.org>; Tue, 18 May 2010 16:12:25 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4INC3gG030614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 May 2010 23:12:04 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4IKrRo6027463; Tue, 18 May 2010 23:12:02 GMT
Received: from abhmt004.oracle.com by acsmt354.oracle.com with ESMTP id 278684801274224316; Tue, 18 May 2010 16:11:56 -0700
Received: from dhcp-usca15-127-88.Red.IPlanet.COM (/192.18.127.88) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 18 May 2010 16:11:56 -0700
Message-Id: <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <008401caf313$d5e8ea60$81babf20$@net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 18 May 2010 16:11:33 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090203.4BF31EC4.01B8:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 23:12:30 -0000

Hello Tim,

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
Going through the document, I am not sure which LDAP examples you are  
referring to. I would really appreciate it, if you could point me to  
one such case.

Thanks,
Ciny

>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft - http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>


From calsify-bounces@ietf.org  Tue May 18 18:27:13 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74E053A6A2B; Tue, 18 May 2010 18:27:13 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4BCD3A6A2B for <calsify@core3.amsl.com>; Tue, 18 May 2010 18:27:11 -0700 (PDT)
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 LFEtv+-sYHsY for <calsify@core3.amsl.com>; Tue, 18 May 2010 18:27:10 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 222753A69C8 for <calsify@ietf.org>; Tue, 18 May 2010 18:27:10 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta10.westchester.pa.mail.comcast.net with comcast id K1gk1e0030SCNGk5ADT3By; Wed, 19 May 2010 01:27:03 +0000
Received: from THARE ([71.203.98.77]) by omta09.westchester.pa.mail.comcast.net with comcast id KDT11e00A1gAkVz3VDT2JQ; Wed, 19 May 2010 01:27:02 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
In-Reply-To: <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
Date: Tue, 18 May 2010 21:26:52 -0400
Message-ID: <001201caf6f2$5cf8fae0$16eaf0a0$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr235Tq8p+gVBJHT569B2aMxEgL6QAEoCSw
Content-Language: en-us
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is followed
only by an expression in parenthesis.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: Ciny Joy [mailto:ciny.joy@oracle.com] 
Sent: Tuesday, May 18, 2010 7:12 PM
To: Tim Hare
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing
resources for calendaring and scheduling services

Hello Tim,

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
Going through the document, I am not sure which LDAP examples you are  
referring to. I would really appreciate it, if you could point me to  
one such case.

Thanks,
Ciny

>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft -
http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>


_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From timhare@comcast.net  Tue May 18 18:27:11 2010
Return-Path: <timhare@comcast.net>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4BCD3A6A2B for <calsify@core3.amsl.com>; Tue, 18 May 2010 18:27:11 -0700 (PDT)
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 LFEtv+-sYHsY for <calsify@core3.amsl.com>; Tue, 18 May 2010 18:27:10 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 222753A69C8 for <calsify@ietf.org>; Tue, 18 May 2010 18:27:10 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta10.westchester.pa.mail.comcast.net with comcast id K1gk1e0030SCNGk5ADT3By; Wed, 19 May 2010 01:27:03 +0000
Received: from THARE ([71.203.98.77]) by omta09.westchester.pa.mail.comcast.net with comcast id KDT11e00A1gAkVz3VDT2JQ; Wed, 19 May 2010 01:27:02 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
In-Reply-To: <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com>
Date: Tue, 18 May 2010 21:26:52 -0400
Message-ID: <001201caf6f2$5cf8fae0$16eaf0a0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr235Tq8p+gVBJHT569B2aMxEgL6QAEoCSw
Content-Language: en-us
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 01:27:11 -0000

4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is followed
only by an expression in parenthesis.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: Ciny Joy [mailto:ciny.joy@oracle.com] 
Sent: Tuesday, May 18, 2010 7:12 PM
To: Tim Hare
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing
resources for calendaring and scheduling services

Hello Tim,

On May 13, 2010, at 8:16 PM, Tim Hare wrote:

> My comments on the document:
>
> In many places, you have an LPAP example without any text describing  
> it as
> an example.  This did not seem clear to me until the third or fourth  
> item
> that was treated that way.
Going through the document, I am not sure which LDAP examples you are  
referring to. I would really appreciate it, if you could point me to  
one such case.

Thanks,
Ciny

>
> You have a comment on many items that says "Not required for a  
> resource
> scheduling query".  I think if you are going to take pains to do  
> that, it
> would be nice to have comments to say which things are required, and
> possibly a table showing the attributes and whether they are  
> required or
> not.  On the other hand, I am not sure this information is required  
> for a
> schema and perhaps it might be better in a document describing how  
> resources
> are scheduled.
>
> Tim Hare
> Interested Bystander, Non-Inc.
>
>
> -----Original Message-----
> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On  
> Behalf
> Of Ciny Joy
> Sent: Wednesday, May 12, 2010 1:36 PM
> To: calsify@ietf.org
> Subject: [calsify] Request for review - Schema for representing  
> resources
> for calendaring and scheduling services
>
> Hello,
>    A draft defining the schema for representing resources for
> calendaring and scheduling services has been submitted to the IETF as
> an Internet Draft -
http://tools.ietf.org/html/draft-cal-resource-schema-00
>  . A resource in the scheduling context is any shared entity that can
> be scheduled by a calendar user, but does not control its own
> attendance status. Would really appreciate review and comments.
>
> Thank you,
> Ciny
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>



From ciny.joy@oracle.com  Wed May 19 09:05:44 2010
Return-Path: <ciny.joy@oracle.com>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 716E63A6892 for <calsify@core3.amsl.com>; Wed, 19 May 2010 09:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.988
X-Spam-Level: 
X-Spam-Status: No, score=-4.988 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 5Z9xVyKi4plE for <calsify@core3.amsl.com>; Wed, 19 May 2010 09:05:43 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 31EB13A6883 for <calsify@ietf.org>; Wed, 19 May 2010 09:05:43 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JG4kcF009572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 May 2010 16:04:47 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JG4g8E018974; Wed, 19 May 2010 16:04:42 GMT
Received: from abhmt009.oracle.com by acsmt354.oracle.com with ESMTP id 251042761274285001; Wed, 19 May 2010 09:03:21 -0700
Received: from [192.168.1.100] (/129.150.250.187) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 May 2010 09:03:21 -0700
Message-Id: <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <001201caf6f2$5cf8fae0$16eaf0a0$@net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 19 May 2010 09:03:18 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: rcsinet13.oracle.com [148.87.113.125]
X-CT-RefId: str=0001.0A090202.4BF40C20.0008:SCFMA4539811,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 16:05:44 -0000

On May 18, 2010, at 6:26 PM, Tim Hare wrote:

> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is  
> followed
> only by an expression in parenthesis.
Actually, those are not examples. They are actual LDAP attribute  
definitions as specified by the header. Would it help to add a line  
explicitly stating that before each one?

Thanks,
Ciny

>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Tuesday, May 18, 2010 7:12 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
> Hello Tim,
>
> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>
>> My comments on the document:
>>
>> In many places, you have an LPAP example without any text describing
>> it as
>> an example.  This did not seem clear to me until the third or fourth
>> item
>> that was treated that way.
> Going through the document, I am not sure which LDAP examples you are
> referring to. I would really appreciate it, if you could point me to
> one such case.
>
> Thanks,
> Ciny
>
>>
>> You have a comment on many items that says "Not required for a
>> resource
>> scheduling query".  I think if you are going to take pains to do
>> that, it
>> would be nice to have comments to say which things are required, and
>> possibly a table showing the attributes and whether they are
>> required or
>> not.  On the other hand, I am not sure this information is required
>> for a
>> schema and perhaps it might be better in a document describing how
>> resources
>> are scheduled.
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>>
>> -----Original Message-----
>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>> Behalf
>> Of Ciny Joy
>> Sent: Wednesday, May 12, 2010 1:36 PM
>> To: calsify@ietf.org
>> Subject: [calsify] Request for review - Schema for representing
>> resources
>> for calendaring and scheduling services
>>
>> Hello,
>>   A draft defining the schema for representing resources for
>> calendaring and scheduling services has been submitted to the IETF as
>> an Internet Draft -
> http://tools.ietf.org/html/draft-cal-resource-schema-00
>> . A resource in the scheduling context is any shared entity that can
>> be scheduled by a calendar user, but does not control its own
>> attendance status. Would really appreciate review and comments.
>>
>> Thank you,
>> Ciny
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>
>


From calsify-bounces@ietf.org  Wed May 19 09:05:45 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 957293A6A46; Wed, 19 May 2010 09:05:45 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 716E63A6892 for <calsify@core3.amsl.com>; Wed, 19 May 2010 09:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.988
X-Spam-Level: 
X-Spam-Status: No, score=-4.988 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
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 5Z9xVyKi4plE for <calsify@core3.amsl.com>; Wed, 19 May 2010 09:05:43 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 31EB13A6883 for <calsify@ietf.org>; Wed, 19 May 2010 09:05:43 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JG4kcF009572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 May 2010 16:04:47 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JG4g8E018974; Wed, 19 May 2010 16:04:42 GMT
Received: from abhmt009.oracle.com by acsmt354.oracle.com with ESMTP id 251042761274285001; Wed, 19 May 2010 09:03:21 -0700
Received: from [192.168.1.100] (/129.150.250.187) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 May 2010 09:03:21 -0700
Message-Id: <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <001201caf6f2$5cf8fae0$16eaf0a0$@net>
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 19 May 2010 09:03:18 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: rcsinet13.oracle.com [148.87.113.125]
X-CT-RefId: str=0001.0A090202.4BF40C20.0008:SCFMA4539811,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

On May 18, 2010, at 6:26 PM, Tim Hare wrote:

> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is  
> followed
> only by an expression in parenthesis.
Actually, those are not examples. They are actual LDAP attribute  
definitions as specified by the header. Would it help to add a line  
explicitly stating that before each one?

Thanks,
Ciny

>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Tuesday, May 18, 2010 7:12 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
> Hello Tim,
>
> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>
>> My comments on the document:
>>
>> In many places, you have an LPAP example without any text describing
>> it as
>> an example.  This did not seem clear to me until the third or fourth
>> item
>> that was treated that way.
> Going through the document, I am not sure which LDAP examples you are
> referring to. I would really appreciate it, if you could point me to
> one such case.
>
> Thanks,
> Ciny
>
>>
>> You have a comment on many items that says "Not required for a
>> resource
>> scheduling query".  I think if you are going to take pains to do
>> that, it
>> would be nice to have comments to say which things are required, and
>> possibly a table showing the attributes and whether they are
>> required or
>> not.  On the other hand, I am not sure this information is required
>> for a
>> schema and perhaps it might be better in a document describing how
>> resources
>> are scheduled.
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>>
>> -----Original Message-----
>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>> Behalf
>> Of Ciny Joy
>> Sent: Wednesday, May 12, 2010 1:36 PM
>> To: calsify@ietf.org
>> Subject: [calsify] Request for review - Schema for representing
>> resources
>> for calendaring and scheduling services
>>
>> Hello,
>>   A draft defining the schema for representing resources for
>> calendaring and scheduling services has been submitted to the IETF as
>> an Internet Draft -
> http://tools.ietf.org/html/draft-cal-resource-schema-00
>> . A resource in the scheduling context is any shared entity that can
>> be scheduled by a calendar user, but does not control its own
>> attendance status. Would really appreciate review and comments.
>>
>> Thank you,
>> Ciny
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>
>

_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From timhare@comcast.net  Wed May 19 14:44:28 2010
Return-Path: <timhare@comcast.net>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D20D13A687E for <calsify@core3.amsl.com>; Wed, 19 May 2010 14:44:28 -0700 (PDT)
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 pmguaTZmFpp0 for <calsify@core3.amsl.com>; Wed, 19 May 2010 14:44:27 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by core3.amsl.com (Postfix) with ESMTP id EE6903A6885 for <calsify@ietf.org>; Wed, 19 May 2010 14:44:24 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta15.westchester.pa.mail.comcast.net with comcast id KNtT1e0011wpRvQ5FZkKs7; Wed, 19 May 2010 21:44:19 +0000
Received: from THARE ([71.203.98.77]) by omta18.westchester.pa.mail.comcast.net with comcast id KZkH1e00M1gAkVz3eZkJq9; Wed, 19 May 2010 21:44:18 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net> <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
In-Reply-To: <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
Date: Wed, 19 May 2010 17:44:06 -0400
Message-ID: <004301caf79c$68b3e7a0$3a1bb6e0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr3bSsYtu+E8MBqQHeEwspebOamLwALvcDA
Content-Language: en-us
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 21:44:28 -0000

It would help if on at least the first one it specified what it was, for
those who may not have experience working with LDAP directly.

-----Original Message-----
From: Ciny Joy [mailto:ciny.joy@oracle.com] 
Sent: Wednesday, May 19, 2010 12:03 PM
To: Tim Hare
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing
resources for calendaring and scheduling services


On May 18, 2010, at 6:26 PM, Tim Hare wrote:

> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is  
> followed
> only by an expression in parenthesis.
Actually, those are not examples. They are actual LDAP attribute  
definitions as specified by the header. Would it help to add a line  
explicitly stating that before each one?

Thanks,
Ciny

>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Tuesday, May 18, 2010 7:12 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
> Hello Tim,
>
> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>
>> My comments on the document:
>>
>> In many places, you have an LPAP example without any text describing
>> it as
>> an example.  This did not seem clear to me until the third or fourth
>> item
>> that was treated that way.
> Going through the document, I am not sure which LDAP examples you are
> referring to. I would really appreciate it, if you could point me to
> one such case.
>
> Thanks,
> Ciny
>
>>
>> You have a comment on many items that says "Not required for a
>> resource
>> scheduling query".  I think if you are going to take pains to do
>> that, it
>> would be nice to have comments to say which things are required, and
>> possibly a table showing the attributes and whether they are
>> required or
>> not.  On the other hand, I am not sure this information is required
>> for a
>> schema and perhaps it might be better in a document describing how
>> resources
>> are scheduled.
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>>
>> -----Original Message-----
>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>> Behalf
>> Of Ciny Joy
>> Sent: Wednesday, May 12, 2010 1:36 PM
>> To: calsify@ietf.org
>> Subject: [calsify] Request for review - Schema for representing
>> resources
>> for calendaring and scheduling services
>>
>> Hello,
>>   A draft defining the schema for representing resources for
>> calendaring and scheduling services has been submitted to the IETF as
>> an Internet Draft -
> http://tools.ietf.org/html/draft-cal-resource-schema-00
>> . A resource in the scheduling context is any shared entity that can
>> be scheduled by a calendar user, but does not control its own
>> attendance status. Would really appreciate review and comments.
>>
>> Thank you,
>> Ciny
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>
>



From calsify-bounces@ietf.org  Wed May 19 14:44:30 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35FC13A6885; Wed, 19 May 2010 14:44:30 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D20D13A687E for <calsify@core3.amsl.com>; Wed, 19 May 2010 14:44:28 -0700 (PDT)
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 pmguaTZmFpp0 for <calsify@core3.amsl.com>; Wed, 19 May 2010 14:44:27 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by core3.amsl.com (Postfix) with ESMTP id EE6903A6885 for <calsify@ietf.org>; Wed, 19 May 2010 14:44:24 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta15.westchester.pa.mail.comcast.net with comcast id KNtT1e0011wpRvQ5FZkKs7; Wed, 19 May 2010 21:44:19 +0000
Received: from THARE ([71.203.98.77]) by omta18.westchester.pa.mail.comcast.net with comcast id KZkH1e00M1gAkVz3eZkJq9; Wed, 19 May 2010 21:44:18 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Ciny Joy'" <ciny.joy@oracle.com>
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net> <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
In-Reply-To: <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com>
Date: Wed, 19 May 2010 17:44:06 -0400
Message-ID: <004301caf79c$68b3e7a0$3a1bb6e0$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr3bSsYtu+E8MBqQHeEwspebOamLwALvcDA
Content-Language: en-us
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

It would help if on at least the first one it specified what it was, for
those who may not have experience working with LDAP directly.

-----Original Message-----
From: Ciny Joy [mailto:ciny.joy@oracle.com] 
Sent: Wednesday, May 19, 2010 12:03 PM
To: Tim Hare
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing
resources for calendaring and scheduling services


On May 18, 2010, at 6:26 PM, Tim Hare wrote:

> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is  
> followed
> only by an expression in parenthesis.
Actually, those are not examples. They are actual LDAP attribute  
definitions as specified by the header. Would it help to add a line  
explicitly stating that before each one?

Thanks,
Ciny

>
> Tim Hare
> Interested Bystander, Non-Inc.
>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Tuesday, May 18, 2010 7:12 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
> Hello Tim,
>
> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>
>> My comments on the document:
>>
>> In many places, you have an LPAP example without any text describing
>> it as
>> an example.  This did not seem clear to me until the third or fourth
>> item
>> that was treated that way.
> Going through the document, I am not sure which LDAP examples you are
> referring to. I would really appreciate it, if you could point me to
> one such case.
>
> Thanks,
> Ciny
>
>>
>> You have a comment on many items that says "Not required for a
>> resource
>> scheduling query".  I think if you are going to take pains to do
>> that, it
>> would be nice to have comments to say which things are required, and
>> possibly a table showing the attributes and whether they are
>> required or
>> not.  On the other hand, I am not sure this information is required
>> for a
>> schema and perhaps it might be better in a document describing how
>> resources
>> are scheduled.
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>>
>> -----Original Message-----
>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>> Behalf
>> Of Ciny Joy
>> Sent: Wednesday, May 12, 2010 1:36 PM
>> To: calsify@ietf.org
>> Subject: [calsify] Request for review - Schema for representing
>> resources
>> for calendaring and scheduling services
>>
>> Hello,
>>   A draft defining the schema for representing resources for
>> calendaring and scheduling services has been submitted to the IETF as
>> an Internet Draft -
> http://tools.ietf.org/html/draft-cal-resource-schema-00
>> . A resource in the scheduling context is any shared entity that can
>> be scheduled by a calendar user, but does not control its own
>> attendance status. Would really appreciate review and comments.
>>
>> Thank you,
>> Ciny
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>
>


_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify

From ciny.joy@oracle.com  Wed May 19 18:32:57 2010
Return-Path: <ciny.joy@oracle.com>
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F2F93A67CC for <calsify@core3.amsl.com>; Wed, 19 May 2010 18:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.763
X-Spam-Level: 
X-Spam-Status: No, score=-5.763 tagged_above=-999 required=5 tests=[AWL=0.836,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 jYFYMxdkMeap for <calsify@core3.amsl.com>; Wed, 19 May 2010 18:32:56 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 8030E3A6978 for <calsify@ietf.org>; Wed, 19 May 2010 18:32:53 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4K1WGNg003984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 May 2010 01:32:17 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JHFrsV031207; Thu, 20 May 2010 01:32:15 GMT
Received: from abhmt018.oracle.com by acsmt354.oracle.com with ESMTP id 252455781274319088; Wed, 19 May 2010 18:31:28 -0700
Received: from [192.168.1.100] (/129.150.24.5) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 May 2010 18:31:28 -0700
Message-Id: <A386C80F-BC47-4DF4-A245-D123339AF182@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <004301caf79c$68b3e7a0$3a1bb6e0$@net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 19 May 2010 18:31:26 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net> <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com> <004301caf79c$68b3e7a0$3a1bb6e0$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090205.4BF49122.0016:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 01:32:57 -0000

On May 19, 2010, at 2:44 PM, Tim Hare wrote:

> It would help if on at least the first one it specified what it was,  
> for
> those who may not have experience working with LDAP directly.

Will sure do. Thanks a lot for the feedback.

Ciny

>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Wednesday, May 19, 2010 12:03 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
>
> On May 18, 2010, at 6:26 PM, Tim Hare wrote:
>
>> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is
>> followed
>> only by an expression in parenthesis.
> Actually, those are not examples. They are actual LDAP attribute
> definitions as specified by the header. Would it help to add a line
> explicitly stating that before each one?
>
> Thanks,
> Ciny
>
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>> -----Original Message-----
>> From: Ciny Joy [mailto:ciny.joy@oracle.com]
>> Sent: Tuesday, May 18, 2010 7:12 PM
>> To: Tim Hare
>> Cc: calsify@ietf.org
>> Subject: Re: [calsify] Request for review - Schema for representing
>> resources for calendaring and scheduling services
>>
>> Hello Tim,
>>
>> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>>
>>> My comments on the document:
>>>
>>> In many places, you have an LPAP example without any text describing
>>> it as
>>> an example.  This did not seem clear to me until the third or fourth
>>> item
>>> that was treated that way.
>> Going through the document, I am not sure which LDAP examples you are
>> referring to. I would really appreciate it, if you could point me to
>> one such case.
>>
>> Thanks,
>> Ciny
>>
>>>
>>> You have a comment on many items that says "Not required for a
>>> resource
>>> scheduling query".  I think if you are going to take pains to do
>>> that, it
>>> would be nice to have comments to say which things are required, and
>>> possibly a table showing the attributes and whether they are
>>> required or
>>> not.  On the other hand, I am not sure this information is required
>>> for a
>>> schema and perhaps it might be better in a document describing how
>>> resources
>>> are scheduled.
>>>
>>> Tim Hare
>>> Interested Bystander, Non-Inc.
>>>
>>>
>>> -----Original Message-----
>>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>>> Behalf
>>> Of Ciny Joy
>>> Sent: Wednesday, May 12, 2010 1:36 PM
>>> To: calsify@ietf.org
>>> Subject: [calsify] Request for review - Schema for representing
>>> resources
>>> for calendaring and scheduling services
>>>
>>> Hello,
>>>  A draft defining the schema for representing resources for
>>> calendaring and scheduling services has been submitted to the IETF  
>>> as
>>> an Internet Draft -
>> http://tools.ietf.org/html/draft-cal-resource-schema-00
>>> . A resource in the scheduling context is any shared entity that can
>>> be scheduled by a calendar user, but does not control its own
>>> attendance status. Would really appreciate review and comments.
>>>
>>> Thank you,
>>> Ciny
>>> _______________________________________________
>>> calsify mailing list
>>> calsify@ietf.org
>>> https://www.ietf.org/mailman/listinfo/calsify
>>>
>>
>>
>
>


From calsify-bounces@ietf.org  Wed May 19 18:32:59 2010
Return-Path: <calsify-bounces@ietf.org>
X-Original-To: calsify-archive-feit0ahl@lists.ietf.org
Delivered-To: ietfarch-calsify-archive-Feit0ahl@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A5693A6858; Wed, 19 May 2010 18:32:59 -0700 (PDT)
X-Original-To: calsify@core3.amsl.com
Delivered-To: calsify@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F2F93A67CC for <calsify@core3.amsl.com>; Wed, 19 May 2010 18:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.763
X-Spam-Level: 
X-Spam-Status: No, score=-5.763 tagged_above=-999 required=5 tests=[AWL=0.836,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 jYFYMxdkMeap for <calsify@core3.amsl.com>; Wed, 19 May 2010 18:32:56 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 8030E3A6978 for <calsify@ietf.org>; Wed, 19 May 2010 18:32:53 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4K1WGNg003984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 May 2010 01:32:17 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4JHFrsV031207; Thu, 20 May 2010 01:32:15 GMT
Received: from abhmt018.oracle.com by acsmt354.oracle.com with ESMTP id 252455781274319088; Wed, 19 May 2010 18:31:28 -0700
Received: from [192.168.1.100] (/129.150.24.5) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 May 2010 18:31:28 -0700
Message-Id: <A386C80F-BC47-4DF4-A245-D123339AF182@oracle.com>
From: Ciny Joy <ciny.joy@oracle.com>
To: Tim Hare <TimHare@comcast.net>
In-Reply-To: <004301caf79c$68b3e7a0$3a1bb6e0$@net>
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 19 May 2010 18:31:26 -0700
References: <093E9039-5A9C-44BB-9963-2409768A4A4C@oracle.com> <008401caf313$d5e8ea60$81babf20$@net> <BC814CE5-F4B7-46FC-9047-78EBE2BFEA83@oracle.com> <001201caf6f2$5cf8fae0$16eaf0a0$@net> <9D3FC8FD-41EE-4745-BF2A-96D0648503F2@oracle.com> <004301caf79c$68b3e7a0$3a1bb6e0$@net>
X-Mailer: Apple Mail (2.936)
X-Auth-Type: Internal IP
X-Source-IP: acsinet15.oracle.com [141.146.126.227]
X-CT-RefId: str=0001.0A090205.4BF49122.0016:SCFMA922111,ss=1,fgs=0
Cc: calsify@ietf.org
Subject: Re: [calsify] Request for review - Schema for representing resources for calendaring and scheduling services
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: calsify-bounces@ietf.org
Errors-To: calsify-bounces@ietf.org

On May 19, 2010, at 2:44 PM, Tim Hare wrote:

> It would help if on at least the first one it specified what it was,  
> for
> those who may not have experience working with LDAP directly.

Will sure do. Thanks a lot for the feedback.

Ciny

>
> -----Original Message-----
> From: Ciny Joy [mailto:ciny.joy@oracle.com]
> Sent: Wednesday, May 19, 2010 12:03 PM
> To: Tim Hare
> Cc: calsify@ietf.org
> Subject: Re: [calsify] Request for review - Schema for representing
> resources for calendaring and scheduling services
>
>
> On May 18, 2010, at 6:26 PM, Tim Hare wrote:
>
>> 4.1.1, 4.4.1, 4.7.1 ... All places where the paragraph header is
>> followed
>> only by an expression in parenthesis.
> Actually, those are not examples. They are actual LDAP attribute
> definitions as specified by the header. Would it help to add a line
> explicitly stating that before each one?
>
> Thanks,
> Ciny
>
>>
>> Tim Hare
>> Interested Bystander, Non-Inc.
>>
>> -----Original Message-----
>> From: Ciny Joy [mailto:ciny.joy@oracle.com]
>> Sent: Tuesday, May 18, 2010 7:12 PM
>> To: Tim Hare
>> Cc: calsify@ietf.org
>> Subject: Re: [calsify] Request for review - Schema for representing
>> resources for calendaring and scheduling services
>>
>> Hello Tim,
>>
>> On May 13, 2010, at 8:16 PM, Tim Hare wrote:
>>
>>> My comments on the document:
>>>
>>> In many places, you have an LPAP example without any text describing
>>> it as
>>> an example.  This did not seem clear to me until the third or fourth
>>> item
>>> that was treated that way.
>> Going through the document, I am not sure which LDAP examples you are
>> referring to. I would really appreciate it, if you could point me to
>> one such case.
>>
>> Thanks,
>> Ciny
>>
>>>
>>> You have a comment on many items that says "Not required for a
>>> resource
>>> scheduling query".  I think if you are going to take pains to do
>>> that, it
>>> would be nice to have comments to say which things are required, and
>>> possibly a table showing the attributes and whether they are
>>> required or
>>> not.  On the other hand, I am not sure this information is required
>>> for a
>>> schema and perhaps it might be better in a document describing how
>>> resources
>>> are scheduled.
>>>
>>> Tim Hare
>>> Interested Bystander, Non-Inc.
>>>
>>>
>>> -----Original Message-----
>>> From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On
>>> Behalf
>>> Of Ciny Joy
>>> Sent: Wednesday, May 12, 2010 1:36 PM
>>> To: calsify@ietf.org
>>> Subject: [calsify] Request for review - Schema for representing
>>> resources
>>> for calendaring and scheduling services
>>>
>>> Hello,
>>>  A draft defining the schema for representing resources for
>>> calendaring and scheduling services has been submitted to the IETF  
>>> as
>>> an Internet Draft -
>> http://tools.ietf.org/html/draft-cal-resource-schema-00
>>> . A resource in the scheduling context is any shared entity that can
>>> be scheduled by a calendar user, but does not control its own
>>> attendance status. Would really appreciate review and comments.
>>>
>>> Thank you,
>>> Ciny
>>> _______________________________________________
>>> calsify mailing list
>>> calsify@ietf.org
>>> https://www.ietf.org/mailman/listinfo/calsify
>>>
>>
>>
>
>

_______________________________________________
calsify mailing list
calsify@ietf.org
https://www.ietf.org/mailman/listinfo/calsify
