IETF Logo Mail Archive

RE: [Simple] WGLC Extension for RPID, CIPID and future status [Future]

mikko.lonnfors@nokia.com Wed, 12 May 2004 10:23 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21872 for <simple-archive@ietf.org>; Wed, 12 May 2004 06:23:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNqtB-0003ST-6k for simple-archive@ietf.org; Wed, 12 May 2004 06:23:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNqs7-0002wC-00 for simple-archive@ietf.org; Wed, 12 May 2004 06:21:56 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BNqrF-0002Qh-00; Wed, 12 May 2004 06:21:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNqmS-0006eI-FV; Wed, 12 May 2004 06:16:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNqhm-00054h-Gs for simple@optimus.ietf.org; Wed, 12 May 2004 06:11:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21317 for <simple@ietf.org>; Wed, 12 May 2004 06:11:11 -0400 (EDT)
From: mikko.lonnfors@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNqhi-00058R-Rp for simple@ietf.org; Wed, 12 May 2004 06:11:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNqgq-0004d7-00 for simple@ietf.org; Wed, 12 May 2004 06:10:16 -0400
Received: from mgw-x2.nokia.com ([131.228.20.22]) by ietf-mx with esmtp (Exim 4.12) id 1BNqfm-00045d-00 for simple@ietf.org; Wed, 12 May 2004 06:09:10 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i4CA95H19786; Wed, 12 May 2004 13:09:05 +0300 (EET DST)
X-Scanned: Wed, 12 May 2004 13:08:48 +0300 Nokia Message Protector V1.3.30 2004040916 - RELEASE
Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i4CA8mvq009826; Wed, 12 May 2004 13:08:48 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks004.ntc.nokia.com 00Rt3gmG; Wed, 12 May 2004 13:08:44 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i4CA8iH07219; Wed, 12 May 2004 13:08:44 +0300 (EET DST)
Received: from esebe004.NOE.Nokia.com ([172.21.138.44]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 12 May 2004 13:08:42 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Simple] WGLC Extension for RPID, CIPID and future status [Future]
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF01D1731D@esebe004.ntc.nokia.com>
Thread-Topic: [Simple] WGLC Extension for RPID, CIPID and future status [Future]
Thread-Index: AcQ39CPcTUZiDs7aRSqh1mCLBiAWLwACWAoA
To: hgs@cs.columbia.edu
Cc: simple@ietf.org
X-OriginalArrivalTime: 12 May 2004 10:08:42.0818 (UTC) FILETIME=[1AC4C220:01C43809]
Content-Transfer-Encoding: quoted-printable
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Wed, 12 May 2004 13:08:43 +0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, HTML_MESSAGE, NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Hi,

Here are my comments to draft-ietf-simple-future-01. Sorry if I have
duplicated issues which have already been discussed. Other than these I
think draft is ready to go.

Page 1:
IPR statement section contains wrong RFC reference. 
in accordance with RFC 3667 -> in accordance with RFC 3668

Section 2, second parachaph:
time until which is element is expected to be valid ->
time until which this element is expected to be valid

Section 3, example
I think XML elements should be reordered to match how they are defined
in PIDF:

<?xml version="1.0" encoding="UTF-8"?>
      <presence xmlns="urn:ietf:params:xml:ns:pidf"
           xmlns:fs="urn:ietf:params:xml:ns:pidf:timed-status"
           entity="pres:someone@example.com">

        <tuple id="7c8dqui">
          <contact>sip:someone@example.com</contact>
          <status>
            <basic>open</basic>
          </status>
          <fs:time-status from="2003-08-15T10:20:00.000-05:00"
             until="2003-08-22T19:30:00.000-05:00">
             <basic>closed</basic>
          </fs:timed-status>
        </tuple>
        <note>I'll be in Tokyo next week</note>
     </presence>

->

<?xml version="1.0" encoding="UTF-8"?>
      <presence xmlns="urn:ietf:params:xml:ns:pidf"
           xmlns:fs="urn:ietf:params:xml:ns:pidf:timed-status"
           entity="pres:someone@example.com">

        <tuple id="7c8dqui">
          <status>
            <basic>open</basic>
          </status>
          <contact>sip:someone@example.com</contact>
        </tuple>
        <note>I'll be in Tokyo next week</note>
          <fs:time-status from="2003-08-15T10:20:00.000-05:00"
             until="2003-08-22T19:30:00.000-05:00">
             <basic>closed</basic>
          </fs:timed-status>
     </presence>

Section 5.1,
Line 
<title>Timed-Status Information in Presence Information Data
Format</title>
Seems to exceed maximum allowed number of characters.

References:
Can PIDF (draft-ietf-impp-cpim-pidf-08) be informative reference if
timed-status XML schemas uses elements defined in PIDF? I think it
should be normative.

- Mikko


> -----Original Message-----
> From: simple-admin@ietf.org [mailto:simple-admin@ietf.org] On 
> Behalf Of ext hisham.khartabil@nokia.com
> Sent: Wednesday, May 12, 2004 10:39 AM
> To: simple@ietf.org
> Subject: [Simple] WGLC Extension for RPID, CIPID and future status
> 
> 
> The WGLC for RPID, CIPID and future status has completed. 
> Unfortunately, they did not get enough comments or reviews 
> and therefore the SIMPLE WG chairs will not pass those drafts 
> to IESG for consideration yet. We have decided to extend the 
> WGLC until May 24th hoping that more reviews, commented and 
> consensus that the drafts are ready can be gathered.
> 
http://www.ietf.org/internet-drafts/draft-ietf-simple-rpid-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-simple-cipid-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-simple-future-01.txt

Regards,
Hisham

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple

v2.23.0 | Report a Bug | By Email