From iptel-admin@lists.bell-labs.com  Fri Sep  1 03:30:33 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06267
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 03:30:33 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id EF1BD44356; Fri,  1 Sep 2000 02:30:22 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 120CB4434C
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 02:30:20 -0400 (EDT)
Received: from dynamicsoft.com (1Cust105.tnt1.freehold.nj.da.uu.net [63.17.113.105])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id DAA05167;
	Fri, 1 Sep 2000 03:31:51 -0400 (EDT)
Message-ID: <39AF5AC2.1016B520@dynamicsoft.com>
Date: Fri, 01 Sep 2000 03:29:06 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
Cc: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

I want to come to closure ASAP on this time-switch issue.

James Undery wrote:
> 
> Jonathan Rosenberg wrote:
> 
> > James Undery wrote:
> > >
> > > > I understand the desire to be compatible with iCal, but I fear that no
> > > > one will implement this thing completely, and even fewer folks will
> > > > implement it correctly. Is there any way to simplify and retain some
> > > > level of interoperability with ical? What if we keep the time and
> > > > duration formats, and allow for repition, but eliminate the "by*"
> > > > parameters which is most of the nightmare of this thing?
> > > >
> > >
> > > >From a quick first glance this would appear to be a good solution, however, I am
> > > less convinced about simplifying recurrence this way, principally because I like
> > > the idea of specifying the last concepts like "the last friday of the month". I
> > > also understand that compatibility with iCalendar may be nice from a philosophical
> > > viewpoint, but, as a CPL implementor it is too complex for my needs and I would
> > > prefer to return to something closer to the syntax of draft 01 for time nodes.
> >
> > I agree, although I'll note that this syntax does not, AFAIK, allow you
> > to say things like "the last Friday of every month".
> 
> >From what I can recall there was a suggestion in the "implementation notes" about using
> negative numbers in a similar way to the "by*" parameters in version 02.
> 
> >
> > We could always add support for iCal style time switches in the next
> > revision of CPL, which could then support both.
> 
> This would be nice as I'd like first CPL RFC to be a simple as it need be and then
> problems with backward compatibility in future versions would be minimised. (When CPL is
> in use and we have a better idea of how it is to be used in practise.)

So, is there consensus around this? We keep the time-switch from the
older drafts, and then think about defining the iCal one for the next
CPL rev once we understand its usage better? Any objections?

-Jonathan R.


-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep  1 04:22:47 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06755
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 04:22:47 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 368A244339; Fri,  1 Sep 2000 03:22:44 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ubiquity.net (mail.ubiquity.net [194.128.96.72])
	by lists.bell-labs.com (Postfix) with ESMTP id 9C92C44336
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 03:22:38 -0400 (EDT)
Received: from ubiquity.net by ubiquity.net with ESMTP (8.8.8+Sun/25-eef)
	id JAA09760; Fri, 1 Sep 2000 09:20:49 +0100 (BST)
Message-ID: <39AF66E3.AED1763@ubiquity.net>
Date: Fri, 01 Sep 2000 09:20:51 +0100
From: James Undery <jundery@ubiquity.net>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: IPTEL <iptel@lists.bell-labs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [IPTEL] CPL log nodes
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Hi,
    This isn't really a bug, but may I suggest some text be added to 8.2
to the effect of "name SHOULD be a legal filename without any path
specification", the reason for this is to prevent the modification of
any files outside of the script owners file space. e.g.

<log name="/etc/hosts.allow" comment="   <-- intentional line break
blackhathost">

Could be very bad for security. Also it is questionable how useful log
is to anyone outside of administrators and developers of CPL (non UA)
servers as the users will require an account on the server and access to
the log files, doesn't mail provide a more useful "logging" mechanism
for users. Log would appear to be useful for UAs only as is.

James Undery



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From mailman-owner@lists.bell-labs.com  Fri Sep  1 06:30:55 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07703
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 06:30:55 -0400 (EDT)
From: mailman-owner@lists.bell-labs.com
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP id B633D44E4C
	for <iptel-archive@lists.ietf.org>; Fri,  1 Sep 2000 05:08:14 -0400 (EDT)
Subject: lists.bell-labs.com mailing list memberships reminder
To: iptel-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: External Test Mailing List <extest.lists.bell-labs.com>
Message-Id: <20000901090814.B633D44E4C@lists.bell-labs.com>
Date: Fri,  1 Sep 2000 05:08:14 -0400 (EDT)

This is a reminder, sent out once a month, about your
lists.bell-labs.com mailing list memberships.  It includes your
subscription info and how to use it to change it or unsubscribe from a
list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, iptel-request@lists.bell-labs.com) containing
just the word 'help' in the message body, and an email message will be
sent to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@lists.bell-labs.com.  Thanks!

Passwords for iptel-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
iptel@lists.bell-labs.com                Gfcn      
http://lists.bell-labs.com/mailman/options/iptel/iptel-archive@lists.ietf.org


From iptel-admin@lists.bell-labs.com  Fri Sep  1 09:40:21 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11623
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 09:40:21 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 8B6ED44338; Fri,  1 Sep 2000 08:39:57 -0400 (EDT)
Delivered-To: iptel@share.research.bell-labs.com
Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6])
	by lists.bell-labs.com (Postfix) with SMTP id AFCD944336
	for <iptel@share.research.bell-labs.com>; Fri,  1 Sep 2000 08:26:03 -0400 (EDT)
Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Fri Sep  1 09:25:11 EDT 2000
Received: by lists.bell-labs.com (Postfix)
	id 69C4A44347; Fri,  1 Sep 2000 09:12:01 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com [135.180.160.8])
	by lists.bell-labs.com (Postfix) with ESMTP id 411A844341
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 09:12:01 -0400 (EDT)
Received: from cs.columbia.edu (ume [135.180.240.103])
	by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with ESMTP id JAA29553;
	Fri, 1 Sep 2000 09:11:57 -0400 (EDT)
Message-ID: <39AFAB1E.D73D303D@cs.columbia.edu>
Date: Fri, 01 Sep 2000 09:11:58 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
X-Mailer: Mozilla 4.05 [en] (WinNT; U)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

> 
> So, is there consensus around this? We keep the time-switch from the
> older drafts, and then think about defining the iCal one for the next
> CPL rev once we understand its usage better? Any objections?
> 

I'm *very* uncomfortable with this. At the very least, we need to define
how CPL can be reasonably extended in the future. Also, if we go that
route, I would suggest going for real simplicity, i.e., fixed time range
only, as a proper subset of the iCal specification. That will make for a
much cleaner transition strategy rather than mixing two models. That
way, we have an overall implementation that's simpler.



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep  1 09:43:22 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11708
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 09:43:21 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id A245044342; Fri,  1 Sep 2000 08:40:15 -0400 (EDT)
Delivered-To: iptel@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id 937B744336
	for <iptel@share.research.bell-labs.com>; Fri,  1 Sep 2000 08:32:03 -0400 (EDT)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Sep  1 09:30:06 EDT 2000
Received: by lists.bell-labs.com (Postfix)
	id DFCC844370; Fri,  1 Sep 2000 09:16:55 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com [135.180.160.8])
	by lists.bell-labs.com (Postfix) with ESMTP id B1A3244341
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 09:16:55 -0400 (EDT)
Received: from cs.columbia.edu (ume [135.180.240.103])
	by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with ESMTP id JAA29670;
	Fri, 1 Sep 2000 09:16:54 -0400 (EDT)
Message-ID: <39AFAC48.C3399D1A@cs.columbia.edu>
Date: Fri, 01 Sep 2000 09:16:56 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
X-Mailer: Mozilla 4.05 [en] (WinNT; U)
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
Cc: IPTEL <iptel@lists.bell-labs.com>
Subject: Re: [IPTEL] CPL log nodes
References: <39AF66E3.AED1763@ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

I would even argue that absolute file name references are bad in the
context. This should be a *logical* name, which the system should
translate in whatever way it sees fit.

I believe this feature is useful only under two circumstances:

- the ability to retrieve the log file and/or

- the ability to check whether a new call matches an existing call in
one of the logs

That way, for example, one can easily build a service such as "only
allow this person to call me if I have called the person before". This
type of abstraction is fully within the scope of CPL and easy to express
as a switch.

One could imagine that a CPL-implementing server makes the log file
available as a web page, say, so maybe we just need to recommend or
mention the access issue.

Having such a service is very useful if all you have is an Ethernet
phone. It won't be able to store long call lists.

James Undery wrote:
> 
> Hi,
>     This isn't really a bug, but may I suggest some text be added to 8.2
> to the effect of "name SHOULD be a legal filename without any path
> specification", the reason for this is to prevent the modification of
> any files outside of the script owners file space. e.g.
> 
> <log name="/etc/hosts.allow" comment="   <-- intentional line break
> blackhathost">
> 
> Could be very bad for security. Also it is questionable how useful log
> is to anyone outside of administrators and developers of CPL (non UA)
> servers as the users will require an account on the server and access to
> the log files, doesn't mail provide a more useful "logging" mechanism
> for users. Log would appear to be useful for UAs only as is.
> 
> James Undery
> 
> _______________________________________________
> IPTEL mailing list
> IPTEL@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/iptel



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep  1 10:39:27 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12904
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 10:39:27 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 1E05C44342; Fri,  1 Sep 2000 09:38:51 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from hvmta01-stg.us.psimail.psi.net (hvmta01-ext.us.psimail.psi.net [38.202.36.29])
	by lists.bell-labs.com (Postfix) with ESMTP id CE9BF44336
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 09:38:47 -0400 (EDT)
Received: from orit ([38.150.216.6]) by hvmta01-stg.us.psimail.psi.net
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000901143846.BCSA17786.hvmta01-stg@orit>;
          Fri, 1 Sep 2000 10:38:46 -0400
Message-ID: <006001c01424$9f0ecf60$6dd8a8c0@orit.us.radvision.com>
Reply-To: "Orit Levin" <orit@radvision.com>
From: "Orit Levin" <orit@radvision.com>
To: "Lennox, Jonathan" <lennox@cs.columbia.edu>,
        "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
Cc: "IPTEL WG" <iptel@lists.bell-labs.com>
Date: Fri, 1 Sep 2000 10:55:07 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_005C_01C01403.1790D900"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Subject: [IPTEL] [CPL] The Liaison Statement from ITU-T SG16
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

This is a multi-part message in MIME format.

------=_NextPart_000_005C_01C01403.1790D900
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_005D_01C01403.1790D900"


------=_NextPart_001_005D_01C01403.1790D900
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello!
As the result of the last SG16 meeting and on behalf of SG16, I am =
attaching the "The Liaison Statement" on CPL for your review and =
response.
Best Regards,
Orit Levin
RADVision Inc.
575 Corporate Drive Suite 420
Mahwah, NJ 07430
Tel: 1 201 529 4300  (230)
Fax: 1 201 529 3516
www.radvision.com
orit@radvision.com

------=_NextPart_001_005D_01C01403.1790D900
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Hello!</FONT></DIV>
<DIV><FONT size=3D2>As the result of the last SG16 meeting and on behalf =
of SG16,=20
I am attaching the "The Liaison Statement"&nbsp;on CPL for your review =
and=20
response.</FONT></DIV>
<DIV><FONT size=3D2>Best Regards,</FONT></DIV>
<DIV><FONT size=3D2>Orit Levin<BR>RADVision Inc.<BR>575 Corporate Drive =
Suite=20
420<BR>Mahwah, NJ 07430<BR>Tel: 1 201 529 4300&nbsp; (230)<BR>Fax: 1 201 =
529=20
3516<BR><A href=3D"http://www.radvision.com">www.radvision.com</A><BR><A =

href=3D"mailto:orit@radvision.com">orit@radvision.com</A></FONT></DIV></B=
ODY></HTML>

------=_NextPart_001_005D_01C01403.1790D900--

------=_NextPart_000_005C_01C01403.1790D900
Content-Type: application/x-zip-compressed;
	name="TD-44d.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="TD-44d.zip"
Content-Transfer-Encoding: base64

UEsDBAoABgAGAL1LGikOJVM5EzMAAADWAAAKABIAVEQtNDRkLmRvYwUnDgBaUElUV0RCTk1TV0QB
AKIDJQYlFgcGBwUHBtcJBwNXCTcGBwYJFwZ3CQcKBwkWFwYnFgcJFyYJJgcJFyoHGhcFJgQXBgUJ
BwUGFQYHJQYnBgcKCSonCwcqCRoMCQwLDAoLCgcGGwwJGwoHChsHCwcLBwoLChs6CwoGCgkrKgwK
GwoLCgcaCwoNBxoJGzoHCwkKCxoLCgkKCwoHCwoHCxobCQtKCwoJBxkNBwkaCwkHGhcJKBECAyQV
BDYHJicFFwkKGQhZGAkICQsJCwkLDQkLCQoLChsNGwodChgEDxEDJAUUBWYHBgcGhwb39wfRg6xu
1IATrFUChMuonP/8I4Ri+h9NJq4GnwpjUe//dpNlhFCEIhQkdxs8xYdCYNofCoGpSmAET9D95H96
9v+ZOkEva/n/X+Tjlv+//u8Ke1fY58XmxewMcnq2xi8x+n+NkavBjlzp/2GX76Qa+b+N8aTFwH+B
ZUgr7AjlvsPc4Bpa/EzZ/xs4fK2yNqvDrJbgRMmyDkPkdfjUXsu5w+fymSje93+68/9RPL6kx1cr
838Nhx8v47M6DCf7H+IOT3Kxy7iuoe3//+Lwoel3Wh0Gxu8S9PwfmVU8WYb/g8jja+J+TaL1C8zc
E8FSBmfE/07BBovDaNf7Ah9YpT3HOCzGy3gOHTQ+P+E24TDK94LGcYTHqND2+475Aksvi6rlMPhg
8RztUAH89D3iQS6nDx2jcL6h/wse/EZ+gQHEe+GZaPQ0MlFvgp5Q1Y95dQyV2KNbHT6F28cnH+Bf
YAox2J3hFX3d9+buXLW1tay3nbv5drV+PfPdumO37Ngm9ljenfPV8k13D79AWLBg576nO8NwyL0s
vf0Z+l7h/Pv9vm+1nG/MfuLVft2DGbO9tKOvXMfLmDFjxonX3NzcXO7VGivwRlpStizmE2+sSJEi
Nff7cGbI1tM92D/Qk3s6nONjY+EtXPiVTOX8u071K/H2Pf0ZerNn0/nChcLr/N2D3Zk0Pnt/xozZ
Brp7Xv/Ay96X6Q33jmTt3qdJIzCxzzQ4Mtjj8z3dI93ZtG7f3Z97ejBbd9Y32NedLdN76bM82fa7
/UhfX29/OEYy5Z4eSbm87443X73d/IVznH2/3l1rq2/fLcvFa7vv+Xad8pUUjxwrXJQ2LptL7LP2
91p+dtt6yzt5y3aJ+st70bpaL+7X1fwKU/3AKtnd1nUvzbahn71/oNvse3K/6YzL8Te829yvJ8Vy
t54QiHg+HkxyGs6ee7pY4Zev0NjLb9CFihQp9JKMFRnb96zWLYs3cM+TrpYpFhPTWXdJck/vCxYs
UuT1rlrm98vzehy+feL1tGw5vlCBIkUmprO17baiX/sNhVxftt5MgwPhQrQvCGoUdK/v+TiUudy7
1mIZUXOfFc9vX21M/IHMr0i+fGN5J16GnpH9fvpwAO79fj/StZgvee25X3f7dvE6V+v5ctvVgmzc
sV10tiwW9+K1rhaLbRd/t2j5q1RI1tv1m7ffYvtOMle5ofFCY4Uegf21LlfJth1wv7zbdt6N5Nba
LcvlvZ4D7kXr3blNJazl+L7Bft+9bKa0YdtaWzfNShvjXdf9SGfnSkAcaF3J+y3rjnu5kBFD+Qk8
s01mvtVym3K73m0Ed8rVbrN4SXcLt2vbpbiJdsedarveOuet47feCA/TqZarNp+tk1BeNzA5+26z
eT3blLLPcX3L1XzVudqMv8H569ytXxfb33cbrRn7PT7eTtdl0xvpGySfoYo2nhzhbgiXEw/5V0l9
D+k6tqlS3WTuVu0lYzb9Fqdvftu21o34+/x2Pr7vhmvynvC/LckvzFdA0R275gmlBKPdVDSRvZPb
LuLadbfvkm3NH9FnenXXnnuZ7MbXD9wMr/Sbe7GY4No0+rW+rfNerqVv3i6kngOkthajc+vV/Fn4
LW5NL0b3OxJ7M3akhn+37pZgK6OVfk5A79b5Asjy7VKgW1vpbrsW8TSdXDQv5ncbgllmdZkLunip
tvemYzH+Mq6Wt7l6OUH562b1hV/JzxdNb7e8GZ1LyW21ut+dZKfvLaSvdWX9GnpVr2ewr+jy3uzm
YA8suGPV2WJkI39l0bD2znuBvZMutdVL+pmIrXXueF0I3O6Xate23Wx3y5d0O2+303LuIl9Qi4bx
F9TicK4LRBunXmkzNLCNSw9jYv/FFs3s697INIkS23XnpmWh7nL3Ntu2LSjf/lZVc+sS/KlE6dJY
xqsOMMfaalJDfP0WcNW5s5NjmezfcZTI0WUqO56eNo5WVqOVJ8efsLa7OIgwYcfrXe06FMxN+xw7
j1ut2YzsSLbjMnc0gbrasdEen/IW34SCNLKZak214tACqFuZF3gCp3aWe7/PiiogNM0LRWV+UQ3n
bL6e8JKNNVF6d2wBWW93m6Z3L5erpZOPoUQHLV9oRHa271rnTjq1CHU3rJHj+z2XVTWmnDdLvZUw
m1ZVe5u0/qXa3EkUeQZ2pN4qIHnX7avV6BcLdq0Elg/cSV+8VPcOUqUj3oao7iLdy1VHSyfWKvcq
PPUxCATxkhza8di432str8nJJ2bWeU/YF55hTk8kjRCWjosu8VRMeuxbW+ZaRtXemR2Ca5exlh2y
bk8ujzeyXt9JXn8To2ipRWtL12a7aCfk8cG1vr3NeXNy782andoXqPWKl5MOT72sFBFmkxxZ1GT3
pmn8jTwi/nMtfimXq5ZWNZEpriUXLZ3t3tdxw3JVQ+TzbRu7cYecawlJvuU9e55N+clxSHwtjTiQ
I1zfjtUIeeKZL7DEO5RtYsKL1Qae5aa3Wa1SFG1p9XclHrbHl6/kCu34W0COIvJJ2qWCuLfwwqOx
XeMh+RjvMhbUJZgW8cxty6KGrh6dcts58bq2qAbSzElsF8g81XbO4pg29leQW+jf3lS2vJnt+mZq
Jdak1Hkq7H4QVMEu76K7JTrjlLdIvMedgxXTa7vNEsaZsbEEAs1A2Uru4KEs+RayErnQYz7X08+T
3rfqsK5Stspa3eFwJSBTnyEbkspJNbYgiXfda3d/7qiZJ/PlK7kdv8cZOShfjpZQS0hQvaILC24l
KNP3bg1+rn/vcPTxvKvJk84QH0xvylF4DrpJjorcYTJIFpaKXrLtnZSPr05yOTsqw52YdKnFJl3Z
Ht8zWkElZXZV/nys+LnKSEXAfjxHTm20muT9lCuOrU+xSDJkQPyQzv3idSe1/lWrqlZUEumpxtAj
M1nuR7qYoLKCMt9LCiE2P2n7zceok1QHoN8m8/uk7aI+tc2ONTGbU1A46dqXSaJYDY9UhkogDxgu
hfQnyniIcf/eDyrSJfEGbge6cbj52D3MplRSm4qzcGz/WznGYArlQKl+mvSV5o5o8lbqyNOB/m4S
PRCF8pMmnGIICiKhfFdg071JxUQVieRbd4VItl2YaU3eslKmatfFSB+Ez/YZXUWp/SM9A+OF8SnJ
hbWoIzkGsu7DsVtuVy5EMxuFWlEFttDS87ULZyeV/gp34twsSAZrJro9ydWGKeiEiKVy0E7ZwiyE
KApAMh1/2eQoBQxbAvTYWIHxIm8Emv5iRMqlRAyGX99uOW8eaCGiGfTaVl3bzZ1hMGN4WCzv5uC/
kKFlOFKJxJKOVmNyDo6Cz7ZrJxbqorzplPB3t72SLr28WxWXJHtOYAI1FmZxRY47teQdJcb5WI7n
k+hR8zvbm/bZDakIYEW0KzCD0tikqwlhKSgZcTLFhDaHS2iBGUGvRhPVSAoeQlkUULPx1y9KI5e7
pRbxAK4sUhdGpKqohS5HopOYgErqtKBo07fhoahJsRT05roqMFo7cJvgtqEP91t0lQirzc2/pGJL
wmekaI6qZWf7arWw2IjvtbRcVwhUuntrKaMWz4eviKTPt+amBTIZyWpiXtGI1Z6/Md+kFAgHukpo
haEah1Kasb01JfAOEe94g6kc8JlIKsEkNWnkvLmV1I1vv0EJpT1HgpPLrQrm8gw+AeYaok0vgwe9
eYuZ/d4025LKVSs4X2zuVHMAFyRMGN6mIsX64ApAaWuJJKUJNlxIb0FFSZ/fWpO4mi9wtY1ZHNu5
C8mgZKp98TB9xG/RYobK0fWmuQlrt9szZ0wgugTElxyC3HIQCUOrrjRJaJXGX3Y40LFN6LjYhS3X
isQpiJhBHpYBUJ8vYFgcQBFIXOD0eFg9Z20mPNJbEBZ4b1GIY3lYQQezoUYac5EOCT5CQBc7SoKA
vPEnyQgPX4KT2po0BTaBz1Ied9MEr0uuFKPMizwdsZBM4cFcYjkhGFJfuXPDa940QxALBIffqtjC
i7Lm1wbdcphPmFkBRL7a4u5AW5uAiIkS+0wrIC0zUZLd0ipiHM9ibaIn5SJ0I1p00a0GBkGZRDH2
zV0raJfW6CS7i92ys92avjFbwbBQXasWOjJVdrHxSWxMkvIslbRkqpYlF4lXrba43Jqt+DzzceQc
z1u0bOaIxETnrnVnLfBU2w2GGf4FKKZBD3FOwCc5KeFWbLgUBWnPLOmKjEou3CkIy1TFOf5cWwoi
mpZQKsADx5Q3BSFJp47HYXPvPmg212MqyxYX041s4kMe0Kb42oaEt+gmYbZEY+8RYeS8mabidZKv
reSTTXZohKfyQikFq7YbGtNiFDFTqxvhmnp9HK453JZHdjUDcRmciQGPL17I6AdESEMLMl4WEJKX
WGRntSl3/NTUGyCuWXDZdm3FJFmZyeK2nm+RKA0kObjmIxsp0lK2u2ChBDkCm3owlm2ZYyDYlC2p
jDKQq5wegqV4heimCg6HQHBKvZVFovdOuXXhcnoK7qXK5iGXwrWSNCmmMWl5kZAKWAQFjlER+Nwh
KHQ+AXLje0rDm/Yjz0hMnWMJRKVn3IaOzJERDHrmvj/T2sp0pLrA4XJ1Gt89I82VBZG0fYunduJK
o1bmxMCOSmmGXnaseWBuuxnCYjDeAaRM5CQEubfaIgcmsUHkxLvHEd6bzwV6ee8Wvsw0dZ447ZIJ
EL5DwlA4Dld1ZWh2Ct3R4ygENqlBEK+xgWCnp7AJypOyJIxlSy9KYYzxTYIOa4EQ4N1zxBVaJPH4
t8yhqVX+lnqQyrcu5i0dorbdGoYpdkgwu3ImxFR1GJQklbCSOu4PnT/uF18l9ckZh7d0ghBIdJLA
M2QSiuJJb1u9g3q4aMGC++npPlqUar++kSzZXq2CNaWvkPIX72fA+2VyI94OopHhcGwd8uC6c3zi
eUE8VqTwKzCWp6AXxBO+hM1Hl4bII21IyJCw2++xQejDF5j2f4Fp/xeY9n+Baf8XmPZ/gWn/F5hG
zf4/bvBFDD6fwec1+GGDz2rwQwbfY/DdBr8x+DaDD5vBh4TBh5jBB6HBB6bBJz65vMEHIAZf4/h/
dYPPa/B5DD63wWc0+AGDbzf4rcG3Gfza4JMbfEgafKAYfJin/49j8Ilq/R8Wgw9egw+YBh/sBh/M
Bh/T4KMbfKWa/1c0+NAbfOAbfOgMPpLB91d3aoMPVTXTrvp/q8EHUoMPfoMPXoOvUOX/ggYfylAF
kMD8ofqhixa6aEEcLXRBGmRBGuCC1OKDPlowRQvdD9KA8oMz4P7A/MErsAyEEnOBdX8Ou5hXJHMI
/wwz13P+mYQ1CswkzJ652u/P/H84Db595q+Hpmd/bZQRsyb3GxTJHFaZ+a9+mUmIuh5nrioL2z8M
Fb+2DU3PHHzf4WYR7jcQWrQNsdnrwq1qEzOu87PbT9rkSkDzg8d+f8rhoebh+eZWZvG2ctDgQ9zX
yjgGH2wGH5TWVgaGwR+M7ekMPgA1+LCYWxl6gw+twfc72lMafChd6gssQ4UxC3SMWWBhDBk4GLMA
hTG46BhDAg4WY4igwZgFE8aQwY4x+/83DKFfuMx1Mn7lY40y132M07+mrvYboIyZ+ZfU1QJaZa2f
gtkoe+qfqx9Zlr/h/2ewO/+68SOGonasJN/o/p+MX/1YN35gh1Jk4XvwYtdiYF/s144VVP8fi/36
8YO0aqmO4/VfVdbA/f9U7Gvt4C59+bX8LZVwVoXd4FMY/MZbESuDb3VX0lwV0eAjGHylw//hnnF9
6y4/5dEGHxwGH+wGn6fB/7kNPhZ5B4/Bzyf/bzH44DP46Xr/xzX4EK5r1QYfFAZX5/8gN/gw1vb9
iAIXKZLAItACTeAjRdaxGmrPDuzQBW6ACqIgCUOQBWUYYwSEmMEQzMEW3MEX5kAU/H6Wf4HF6RiG
CKEIxekYpAprKEIRihqXyz9djwGU4g/Xmbx/+jplcX/ycv2nD7IbXuR+8hiikUIRiplhj7t6fMNj
tUDxWKp+iASK5wWHwg52hR22iAoXEgo7gGrvwFHY81AoXIvCDmyFd55dhXLACmSbC3qtHXhC31Bo
8p8vy385X//hEkL/fD01nEU4lZcy5/eyVCAylrPAxJgFSIxZEGDMQi8zJMZgAzTT4JpoB/QLjMh+
/dliJGIUKx8UQwHrKjTiSjgIRoMFHMTlP38Q+ZnyOMTl1dXLXH/39V8C4ebPBPHxX5tCUbsUJHt3
idYQoH89bxEQAUkkFowYU5lgwZitMGZfYEzW/xuW+lNZh/Us05lXlxvkLzDy+ouCDfgXGE1nrxs/
+sXO5mmAu4AOrKcB1cCPj8tysC0YszGMWRGMIb/A0rou1mHPSCPPUOsXGJBGNy4eAIo7cGfFgRV3
UCIajKcEJ6IBerJii9AafIcjxc0Gf1boWYMPPIMPXIOPASUPaoMPox/FEfVmJgorMzapzJAYU4Yv
MOASGpyDAUFCg1IIaH8FgkKg6faUvQUi9AafsNL/CQw+2Ay+0eEqOrzBN6jwf3WDD/Tn+QYfxeBD
Y/CRDT5f+f9zGnwGgw+Hwac3+EBg8HENPjSBHjVaEAboABNggzzABUMwBnNwBszgiR28AXBYQjhB
iIUtceKkiefzsJEG4F9gyNMl4d9fT5dECn+56jOqbMVwJYWfuYTIP1aE+C+xwy9xp2OoFBlXdqbS
kAy1MxVvaEDxnwI5qx0Gq1WGrmEIhQ+dPIv/MQvLHy4+dM0itQ5J7Si2kwEx0GwnSW1TIHc6Bq8n
lQOewk7oQXcChZ3ab+8UdmAqTpYNZMVJONNUWbkdhM4TEYUm5a1B7lcwodVi8CFk8EFt8EFl8Ga2
UBl8Nh97VoPPZPAZDX7A4PsNvtvOSgp1xB9oP7SBEdoAFtrAgLEA/AWm/V9gIYt/Ahl8r3Xwm9U4
MTwygQ9+fnjIX99VAeNNBTYp0+AwxsoysV9gynENkZ/9LM/HnJCGJVARq1z5gFQ7eX7jRlRAf4GR
Jgwws5CDN+CCmnHjgZDXjgcV8A0++Byk9DEQWLgQJAaCaYhgxRiSaWxwYMyCi2lIjCG+wKCvCf+f
TfhLdTQAth0TeeN+uMYsfw2CshcFnb8F8gQ9eH8Lql74fsMi11J911/J4Cs0Rg/va4wa8uUb45zK
GXzZEIhzKmPwpRuFB6AvMO3/AlOOgG3ww4iDjh7GwGoOZTAGed2wJPAWD1fAmGLhh6I7s2oZk2Gl
J10Q4d+xSLHcrUd7VuuWxfqej3eu2n4oQhHsAVIh0F9g2v8Fpv1fYNr/Bab9X2Da/wWm/V9g2v8F
pv1fYNr/Bab9X2Da/wWm/V9gQNT5IfgbYhEcMn9SE41P/D8amlBcHO4f/8Bf/eVv+7u/8XhceP/2
GWnkp6WRn579ff86enX5Ppmf/kP/lvqOv/3rn/K/X1jlqyNgVubKDua8v3asKL9WrFx/tNT/tX+B
mYTZM1f64Rqq9PszX344DV78L6J7QHSYMdF9EV2vomOuni36+VGvGuh86J8995DnMIU899lzvXiO
ufwGX3KWSQRlycskOUxByT0ruZ4lx5x9/QIsYX4uX4w1L5fmMAVUvpbQNyw1Szlmdtaka/xRG7ve
jeoNk19vH/X+pDfmdPg87hrI9n8QHOR8gvsg+EfBMccZwvjwnxHcw4LD5BXcM4J/EBxzmDIoB+eZ
7V7xMisOk0dxTyv+jOKYGWtL1hGJ5/ojo6EORcAxdddw6fun0vwWO/3c8vssfmnwKRV26283+ay+
+rXOf4GJ4j+HSIfa4UUqh9B3/Gar7/b8JFb74mk//5zFr0ZfTi9b3eFnd91zvVa9/0+/3j+XuVq9
VQt3hP7yV+n09Hs1f/HT/LIaH/5f1+nqdETB/H2MerNVzsE9W/AYdIdLaOpELR10QatnZC3oPkM3
LObpLP/6x67pLOedlstSCuLnMudTmetRdIUWjxX9so9R/7POv4+7gIRRPBftM1c86FL/CJOSYqn1
s+xqX1vX3mi88NXWKuExUb7wYIoI7xzXIkZ//D2u3yy7C8u6a9n6/ZlnwX4WbGFp1q6LqfHJ61cm
2cZozT8Zf/TIkO5jmIrHLH85yM0nrHfXVVNoVsBw96sBaU6iKfjaNnRwg9Qu5728dgl9A/PeibxM
pTFX327mW9XeYfNlzWRlzvwRyflDKvk2mokk8ot0IL7GvhqppozHGjvb/2qScthPwpT//yElmRNc
Q0ra2G2mbgvfr2piE4nId6mlEoyKxXPad3KXzmn0DV1Cu2tR/VeR/UBC0oFE9hvCju31yWG69lr8
jJS7xY274CWTtX6/spk3GT/Kx7KCJvSklcOWNP1gvQbttaTpiDFF60r69oLHL7WD7hoGqWEKSe2K
Uu986Zzy5adT2VnN/ZRWv5TVMvyyGujaH9ARFjBHmEx+DfV13M9aduZnUJePDrmNdiC+1rlMmGWv
MWUVrB+4IM2voNYn1JMXtNHWGiNnWMNfXm3JV93aeezSrWY84v9rTWvh9ekJn5UkSNJBG7rmuBh6
06pje835lr2ysrOwGjpQXTpWCqimZMcax8oI/FnIslqxKl39JRgrU/lL16WklntEjHerjJVbGeeX
X1rIysKXpZB1A6kR2omLnPl/V6GRy+W7CtXXGiEYu4ip/w9Z7Rz8l5B1dGuuTmOerF5NXDoRVTkg
Q8p2GVK6xraTlkqU/CU8lFY5140fukCWsoBl9d2xL1l998asF/Icz4W/zeQrmbA/GVlhOqwQjxw2
5ztMF0Vms/4s7lrF5CP3MWb+pdAhgFa8agQVNo2uq+qHDevrqFFin8KnUslLi5/bOlHQ1y7FVhxK
934DF3mu5GKjpab3Mer+U5Vz/0zYp7dTwdAArozpSlDhEqXPv+xT07LPMHe6742edVE9ywKBERvI
TKI71BdreuIcUtZUxVluz8WE1Z2jIVjqUsOE+ovmiBxqvk+5UncyMPdLUa9DrtV+eNnj1Fy13CFQ
puFepsIzk1DYhaTUy7nb2zrbT64v31lTExV12joCpab+ucpZkLrvJqzBhg6HNlPP4TAxHpT8VN4M
e9f/5Y3akppPxg/u2brxQy5QqFlEcM/qaFzEarmziFV3lqrryrlxV9cOnmPd+CETSq1EUAsbDeTZ
4DmKjvtydOzcK5VHjLpDn++FwP8ffmXumqIUcGb6Oao3VzUd109z6OfTD6eiyP8vraP33EEwUzd+
mUB1iqm6g+4QBDN+Jtehrax2WVmfDKm4Dl0L6NCBVtbuz4zSBs+6FFc6dhVXTetRLKU0jZj1Si3L
km9gSFt9juLH7JnByHIcm8qf309wTuW4O2QEyyhMSX+yZZS4yigWUL6M4vz2Kmd16hXIRC3mUQou
Eyi4nWcCfNXla14zjTKhRqiOGXPl63nM1j3iR/mAiNqOUvN4WNcz+6PZH83mxaVZnWOfixu5zSaf
g9qfTMf9dm6Fb3fl67nd4htajfXxHAi02A+PDZ9V/NP5Lms7fRDM1J7KvA+muqVqNFXRq/8drDKR
oFmSolqDVlR71pptI6Nl/EhWcSLAQ9IfVuFC19Fx2GEJvjQhUkU6y2pKbFEv5HVnla7GjlC8YD0H
3lnx6hk4VsmQaTycqP9zUn5woUjtvn4jWrV0RXtQrSvagwrVq8SxiiyFzpf74damqE5HnlCYVDgM
iDGVrvmcCGfUpDZPztrKZmT6/kldDfF/FVPawm3JBsnHYDLZUjn2VZunOUx7Z+V3CmmPfCnlyDL5
++vz0FNgbIgkT33UN/uCgsRSit5BX3EraiFKmB1jnfI15wfmcXGujs1m0nL3qG1dnhCmo7JbUhyC
J8Lz48hna1ADcoyuOWYHdKyVdS0S5D9PIphK3vZzGdItQBO+EZa2Mna0dLp3NrP/0nNUWbWczYyv
NHX8NkEO6fB1VgRbLScHFAWLVC0ts6B1UBnydD0bgqfvQ4oY0tZySFC032T5n8Xv6mpwbWo0lxxP
JQw55SdaXLORS4LZYZk9qEa3OyWynvQTudaO1UdhriWExemt2hIVIK6xZ22JOotr+X8dzz+VAdZq
t4bVbYvxO7j9QYW7j/CsIqWe3JYOFHqS923smm/JW8HKoJ3NLOey3RtP2jLyWuv8cAmSkAdmU8xz
bee5Nc3TM+I5p7FqtuucU87actTcgobN9A9lnMllcH1NXGlAqmGYdSTWhSI+12BV+WfkNIcxYm0W
MrgU9X6Ph7OEUpmQymngKedZk14aG/9fU9heuVQiPq9K/HyX8MZP/scN3lud29nEzmsG82cwZ8oV
mlCEela5nEy+tur+jPXZnJzBe8/CJhlMk6SE52B2pSxoL3L8ZqTZXnpLO5wSRYU0hL1dDSmlJ7mw
IsuKzQUcVV3NGJAy/wgVy0MTijonrzSHMs2VZah3Fb32ZxzGiP4MYu3PuIHhTxv+NFgOv7vqVO4U
fgHtbj3hIcndq2alz42cxnwmsisb9zhh+n9DksJ5ynEq4jNXsFWTeFKj9ePnIW5n9rEa0Pki5I2L
5YsgW6Y3IPfUz+BATQiFye21zO21u78Os0kr7mcRS0a92iCJanRjPXy7NYfdHnC0/1/B/EXpPPgD
xXARRcjVk57/mDHD5ZiIkf1eOZ3hX7ySk/YMdZ8wDjPkLKxhCjkWhvQapj80oYh98lozqRvPaBNt
6FrPTEpjTAU71zDZbHBdQQV+AUpY17g+PdcwxQ130J6KG+6sX4etaY2SBg4Pw2nMwMrsBu6QlpPk
NwpZSZPV6aLF3d41vcMfVTDXwdWcgsmcgkmdq+woFwxWLyi/5dFdi0J+O7WsJd01VtUi3UTpNy/o
t3f+k35j/cfL+c0L+O0uv7X2lN/o2lN+o/L6J/OKulQXq6kmrImFRsG23CDqklfDVi63EuOyKHKj
h+R273FIbqlnKqUjDD4r03G8/mtphV1KYYdPYesH79KPF9bPqfTTfBf90BpU+Q1f+i1DVk3+fyVD
zhKJF+HzszWQ/NGqNBT2GzPstxMch/2WklVFhDOdo/j3VE0dKZ6OxGRS3MF/zKS4zODwJRw5e5Pw
+lrcJ+O3enYIREQd3WoabC7NHfuYS3OZ3iSH3SRIvTEWaZgs4uGyyCksQonSGOY8uFV5sKO2So+j
mstuXeONrkGiwW/j0AXFlR4LCi7FVXUFyBecaL+6WFgnqYF3HFNbugtNmrC34jnMV/GLeZYP5vLl
0yELSJf2Yu+ITwTdoW78cAdg9dA07CT5yJzqUg+yJg+ODihrt3pwsIHP6DbhiH2Mg5D8GviMvjdH
1jl4c0hjck2uyvD/Wb8snKqLHeSw3WqKS9RWZm1FQljASxsC2VCpGwrjkHrkPsjprn5aLhRIQZak
JNr4XpMSdi/CXoKqxAq/del2j7bBSx1WzNVhQZLC196DajU0R+cpfqCJfqvrtvZabCNdsy9FqGG/
KyZroNq6VFnU0qJNMWpRArdnJXNysDYkujw46I4a9i7RV8QqscdOCrcnjYjtAs1sOSU/JDgUt7PO
pIQjLUjU6+P3kjMOYBHUiVQB3ofgP9izmzIAs1mJlaxlRy3KaYW+sLE3wQd3WFXC0622W2uynk9P
xo8OJy8CJ6W1k5qQGqaDGKNZTVJ3yOTjD0mzPalNBDuqSK6HUVV3FqPOqEC9L5i2KfVGxP01UV37
IzCYAS4mDAcX1bQrKEL/QsLSfbB0oWcPv4w+8IS0GzjlNoG/9fFsC8pmfoi7UnNvEmQlGZAOQlqV
UTBmJEITRBv8ENPPkuMTv8KorHlmwiqrIwsZrfufiJ1Yo9aL6QXS/xP/aX0drWVWbyyptUioNbrU
LzEa+5efKSVg3Cfjvn2JbAJVl9vy//w/fE5feEZIqK6Iw3oR6O1Nbgv8bl+rzGTnleDv6c/kFTPu
87Le6uFYCIjF//IWmdnrPcUyK/xBmYiwQNYqP0TFpCYRk5iYMWPGnHQwViJh47+iid81ow0lTFzX
Mi4twoSIwuf9pbQ7uVqu4zXCO/j5DxW/aqCfIXXsn3CmpLbxkJy4odSNek5hYs1JfI7iTjBHWAmw
drK+mOIcboc//RD6hct8UbqlUEnGnq1U9/+4Ff+/aliLcMoqsVVWYqpHxb1QhCIUoWBZfoHx8BuM
1oPKr/j+F+RmHrf892L/f0WTZUrcL29Iddx6/wd5nf/DaPQNKjitNYi+msGjIf+lqKtsuqxgtwxj
bae1OsdbUBSKUJibDtrMLTxPL6nCN1RV7zxofrYkp5BRXkv8/16YKcFWg+3zGHxGg/eu2q87FIEo
LLXT1QpFzfh7n6/1LVLHql1+HopAlCgUoRDldDIzL0T10ndSQPRO0NpOyAS+2wFaygktZMxpxOwb
kS8ox72wK8p5BXZ+YcolTIMGH+IGP6zQwcvj/t/DZlogtI3GZjOaKIX0hQ0+YBp8mAw+kaQfFoMP
XoMPmAYf7AYfLAYf0+CjG3wrvx9IDb4CaRc0+BaDD6vBB6fBB2SDD/jkfhyDDzO7H/AMPhq9H3gG
H5XfD1yDj0zt57X/gF/RID3Y+wYDPuuwFLiLYfapYDb49A76kDP4QCBrD7gGH3pae4Ay+BoOXdng
Yzr0lEGvDD5sFsFUMRgx67D0XkMRCk9bQ2feS1munwiQkwmKHrXX55YiPqnG7hA0Xnh8tzfjjL7y
tE7sWwygrI2pK7f3F2tWfD12yZSNV7qI7nY3F7W2F3S3J5Xe7dLf4qnsKqQsYMb1fiH+LkHnl/+0
euaVKcdpfXaLwyd3NI8pf2HlT6souFN1bzWYTmsQYNrQahB0aYNA7YTn9Uz4Xsq5zGSL4rU6Vy68
RIdXwsr08n4OLfWQ0PdavMgJXK9R9yu+Q7rwiCgisPOKd58K2wJBGwdd1Dga8MyFVct3IT5ltebD
U1taPijPeljt0+t8Wh/70kr0VgtNpvXkW22RVowuU3iLbtXZtmtRZ76Lan63Ne+0pvpCcl1I5NUZ
WlSiW3SNXbUWVUKXKax+zMfIZ2T8jIycO8PLDuewXa7Ryk7X6Ge4fwQs6kIh8JNKbP0C8+svOBWm
S+k/PRuKSYFR/4fYwOTparPdRoZE+PoONuO9eQLEtM144AwHasOSUaosvUdefxib09WfdBsqdom4
9U3Hg69ilUm38UWVU91J32CkSM8URHVNx4OxXMCoYzMeHEkCpM2QIZK3Wg2b8dCWbqvqFF5ol6iK
zXh7npHKpuMVUgeA5avlD3sw+AYP6gwBO3ym43VmA0ZJm/FgSBru4t7jKasG9OIhGPQNg83LwFNk
DqLipuOBni5SMdPx4K80VsT0DEg7C1F/Uqb4IE78tM4H1yGYC5uOB7hLYI2ZjodkyObPN9MR4gHZ
ZnjNltDlcRuP1RH63DbjmTLnDfnNcdhmmDgVquR0Cg/KmWAabQri2AHWzOEhHVI/m/d4MFcskznG
2DpEbYbHCN8us6vGI4UrYGWyCA8khUJoQJl4IwudL5T97auQDUg2w/OG5CKcTuElkuTo9R6PFPLV
u23Gwx6el950vC1/gE9vER6OUgXSuf2MzfBoITaULndASJzbxeGhmAkI6bzHg+ClDzmb8ap1i4eM
zfj1ECmkbcbD89u7KgVGAJ62CB5oWdo73Mbz9GS6bcYjDATJNmeg9uW0GZ45TfGVteNB0hlYyU3H
w14zrEub8XjFg3thOj6aLLjmbuNBWKo5qdt4hO1LbDPeWGwmJO0lZIgF1BBzG/8Cg3yVwvjqNC5N
8mT8xmvd+H0Raoqh1Xg9XqXm17PX0KPmmMeM6LVHL0ekG7cwmS1PZsM4YajZjn45nsyW4+bCbvOD
2/DUiujHCWS3nfp8PLhNjGvxt5ucthsRxe7r2a1Rzsdpu9Hj1vz9Jqb8RiYSRDpRoPjtRLPHKb8R
41q8DWd7w2HrnerGjxLJcNc7HfeGQ42b83YcO+k4Ko7jp3Zc45yOk46DPK7H3XJMXcvRReggjh5K
y13keKxrOfhxC86eVx3IsV9gT3nudj9zmP2Mtl+P/Zmvmthf/6okIq8odFOaTzfUGUMjyHZRIxG8
9hgrvMZVHDT2ACY2/Cw2AvmFogN007f/SZ0KiFs68ekGqTIWbFSCVj7T/RTdT9GtayxDy/6sL5f6
f18u3f32fLqCpam/3wgsTf2xNMQo9phGjpv5WJpbs6iPT6h2nzi0LswRtNkAg1LUX42U+tMN9Kf7
/x3JwNszgGcUIdBWdDJaw0FOWQycjioQQpkRU9hPNxQTAXioKAyNzUbDq9loosDMzz/zcxb/2TPX
+iiSoObqg5GQ9IZeEIn0DF2BYYmyYA8QWRWeGi6sGQNMHsMDI0Si2G4m5HxmHotcIeyz0oHlcWHx
GB04HksSmPxmHovhsPqsFLD5zDwWTT5LTsR8xnLB7TE8gHst+WDzmbGA5TEjA81jRgWex4wMKo8Z
HWweMwLQPGb8iHnMaEHzmFHB5zEjgM9jxgyfx4wZLo8ZO3geMzLwPGakEHnMCMHymDEA5zGjgclj
RgeWx4wSNo8ZL0QeMxLoPGZEIHnMGKDymJHC5DHjgMljxgWWx4wXIo8ZC1geMz6QPGYUoHnMWIDz
HUsCt8eMDCKPGRFsHjNuiDxmLDB5zBjB85h5iqJgCEXhADUVTD4zOtA8ZoQQecwYIfOY0YPlMaOA
yWMWfBWr4MJiOWDymBWcCtPFY8YInMeMBSyP2aLKyc9iuYDymAXOcKA29JiRQeYx44TIY8avDoXA
IgAbyt/PrsaAASKCllsMhbDcRb3S84FUuzCr7cKofFUWsP9XRvkptd3riFYETD6a7yLz7QJ8w7Tz
zb2IlG9EKAS+L6yEF/PsFojkRExuEUfuU/+VMB0gpZ1Fcd9xLnoDPBQC0yi0qgdL2+GAdA5Xx2EZ
pMFX+OBwTQ7Lmv8q7q7hs6zusAwin5eIAoRb07FfYBoTitFzouuP5sDd4DpCKPTfxYvmwpUOi0s9
rmXcip/STG431Dfw+Cw1QkDDv4Dif5o9Xc6zIZybd7TDsvtvf9u//4LSPODwSR2+l0Tf9nd/7fMF
HP/yT6fr5Xo4XlTxeT3KiUQI1/Obzb5L7jcaX6iU/p46zl4ul8tFf8iRv/T/ndnurGP2zGyCCxcF
rEX2n8Wo3WIlf3oAeQnNgO0vbPwzxgOz+i02+f5Lj2FtF/9nyxEC11AcPIf4Asue36m3W/9cc7k0
+LXie1y4C2i5D+fpy+V0mdVySIXw9PVUA5dDx7pD7vtE+n8tByF7uRBQlVjX8Yya/wxe7RYS+1bK
qWzuGf7ecOAy2P32J5PbphZjZNjIEwmc5vABzR2eo6e222hPjUzv9+ufUst3WL2pKmeJ80iisFb7
P7onf2K+f9WgGApY5Q0+sLpyZz0b4/x/kdn/A7+6RTmoZs2ItqUXqD72CoVUTk7VRr0MGjCDf4Ep
u7BX71f9qhRJUNSnwb9GLr2BCvRKKsNFGRqKUMjSRc4/KCaewV761tDfpmorsTYTtbap00g/d3hX
lYHY3EN0h8IvFY0T+4z2u7mEdBqB+bDHd3q+imqt809f3+euLmqQnLQX3tjsB0v8UuJbjPfGf7f/
hoK/E9rCl0LoJZV+gWn/F5gGRWDgPtvw4jIsg1DUEA24oQ5lf3u94AzEM79Y+AJa6PXJCg6YR2SI
EDB4uQuzwZPLoho8k/APDIO34IcJFyOneg4Pye05PCxpBR3eX6dLT4SstCIUOby9kK7Q3OFxeUlR
T8dyWBxeirQmhyflF9fhazt8rKv/GsDRP/wOz8tosDvD6743d+eqra1lve3czber9euZ79Ydu2XH
NrHH8u6cr5Zp0gj88Kqzpe1ez99IX/aijisBz45vcd6XZXOvX9bl3bLu2Gw7240mXd7ijGtgtWzb
EYl7nGUN7zb360mx3K3/xuScqhDYW5xdZdx2LleLVar5S79adry840X+CorMseIFMcNZ7FqBtDeo
agX91WIHwiCrG7l+TIs1RmCHN1QWf3ZIOpwPN4cz4sbPo/5fYNr/Bab9X2Da/wWm/V9g2v8Fpv1f
YNr/Bab9X2Da/wWm/V9gmuJPgIvcJUiCIkjijleuFy8A8id4IpQBfdjkTyajwwZAeF43AmlBWLvB
WxHUanUGHxaD90OryeDd8Itr8KiwxTJ4J1rBYfDGtAKqwbvQCkgGjw9b0Bi8AX5B+W3X6tYE6FoG
n6mlE46g7ruzfb3arFJu74U9od0wOrstHc4NI4crXHPGfP//HYYMP0Y7liU+DWhQjyzlKgKvezvf
3B+NQPz/Kzn8rPuyJMuy96OtIWuXDJPH0uCscEvTNzicJkuGwWHhuMgeyjQ4EK4eIecjDj9g8CFp
APbIz/cLmviFxTHOZ47xyM/j8SMSX1jgh2Xe5PJLvM4VEfj8Bp9H4/O67IJuX+SHhFJ2vdScSf/L
+Es7bIPF/w6rvK2CwSvZOpSRNkMXo37oS6HVYvJOcDrujSa9Vm5wzBeY9n+Baf8XmPZ/gWn/F5j2
f4Fp/xeY9n+Baf8XmPZ/gWn/F5iGipOkRpQacRaEyRGnS9zB4GcMftrg3YnyoaVNlAlB9Q3emCA3
gkwJqmPwdgRpE1fT4P0IMiaomsFXNfgqBl/Z4CsZPAXBIDRrE/cMPkIoQhGKcg5f1uDLGHxpgy9l
8OEz+JI+y+IOX8zgJwy+qMGPG3x4Db6IwRc2eG+CChl8QYMvYPD5DT6fwec1+DwGn9vgw2PwuQw+
5A0+p8H7EjRq8KKE5TD47Abvi1c2g89q8FkMfsjgBw0+s8GHy+AzGXxGg5el1W/wfQYfToM3I6jH
4LsN3qvC4fDpDT6dwYecwVsSFDIGn9ZnGVIOn8bgJWntDL7L4DsNvsNnGdHgU1osDRahEJhW9OrT
XjkQ/OR77fDL3yz/X2AwNf7parkwNB2nLbE1Js+aVWGn/gUi1495jRM9UHtC5fBbkk/ktxwW8OcK
7i8wgDb8l6tnzGxgyiNcPYu1sJp9J2DfaOD9BQa0vp64oZj/QJQw+IFwWKzp9f2lvH3Y4TtdcG9z
aAfbFxhsFf/2Urmp/AfqC3yJUYf1JKdXvzYF3942qP+pTHKbjPXWC8dfYMiS/g5oBoSr57+QD+UR
4Hn9303IfyBC2n/iKq/2x65VVN31w843MF9gVsf/xXVe/PwdCOmF+noL+HNPuYVqQzhQX+BqCLa/
g+AuCoeFzQzjfCXVCIXAtD8UAtOOq779DMza4ux4KD9WGbedy9VilWr+0q+WHU8YSZgwnbHH5Ege
U7TFjfssxvP+yHnClJxPA/8Fpv1fYNBQSwECFAAKAAYABgC9SxopDiVTORMzAAAA1gAACgASAAAA
AAAAAAAApIEAAAAAVEQtNDRkLmRvYwUnDgBaUElUV0RCTk1TV0QBAFBLBQYAAAAAAQABAEoAAABN
MwAAAAA=

------=_NextPart_000_005C_01C01403.1790D900--



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep  1 22:28:18 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25446
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 22:28:17 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id B242B44338; Fri,  1 Sep 2000 21:27:58 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 3BB0744336
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 21:27:55 -0400 (EDT)
Received: from dynamicsoft.com (1Cust214.tnt4.freehold.nj.da.uu.net [63.36.112.214])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id WAA11142;
	Fri, 1 Sep 2000 22:25:52 -0400 (EDT)
Message-ID: <39B0648B.F4D99D53@dynamicsoft.com>
Date: Fri, 01 Sep 2000 22:23:07 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: James Undery <jundery@ubiquity.net>, IPTEL <iptel@lists.bell-labs.com>
Subject: Re: [IPTEL] CPL log nodes
References: <39AF66E3.AED1763@ubiquity.net> <39AFAC48.C3399D1A@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:
> 
> I would even argue that absolute file name references are bad in the
> context. This should be a *logical* name, which the system should
> translate in whatever way it sees fit.

I agree completely. In fact, I don't even think its really a requirement
that the log be a physically separate file; it could just be content
labeled in some way within a larger CPL-wide log.

> 
> I believe this feature is useful only under two circumstances:
> 
> - the ability to retrieve the log file and/or
> 
> - the ability to check whether a new call matches an existing call in
> one of the logs
> 
> That way, for example, one can easily build a service such as "only
> allow this person to call me if I have called the person before". This
> type of abstraction is fully within the scope of CPL and easy to express
> as a switch.

I'd rather keep things simple and stick to what we have in CPL now; this
can wait till the next rev or an extension or something.

-Jonathan R.
-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep  1 22:47:02 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26598
	for <iptel-archive@odin.ietf.org>; Fri, 1 Sep 2000 22:47:01 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 49FF344370; Fri,  1 Sep 2000 21:46:56 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 4449144360
	for <iptel@lists.bell-labs.com>; Fri,  1 Sep 2000 21:46:53 -0400 (EDT)
Received: from dynamicsoft.com (1Cust214.tnt4.freehold.nj.da.uu.net [63.36.112.214])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id WAA11171;
	Fri, 1 Sep 2000 22:48:34 -0400 (EDT)
Message-ID: <39B069DC.6B063419@dynamicsoft.com>
Date: Fri, 01 Sep 2000 22:45:48 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Orit Levin <orit@radvision.com>
Cc: "Lennox, Jonathan" <lennox@cs.columbia.edu>,
        IPTEL WG <iptel@lists.bell-labs.com>
References: <006001c01424$9f0ecf60$6dd8a8c0@orit.us.radvision.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [IPTEL] Re: [CPL] The Liaison Statement from ITU-T SG16
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

For the benefit of this list, enclosed is the text of this liaison
statement in ASCII form.

Comments?

ITU - Telecommunication Standardization Sector 	TD -44c
STUDY GROUP 16


Portland, 25 August, 2000

QUESTIONS:	Q.22/11 (for action) 
SOURCE:	Q13/16
TITLE:	COMMENTS ON CPL DRAFT
LIAISON STATEMENT TO:	IETF IPTEL  WG on CPL
APPROVAL:	Agreed to at Q.13/16 Rapporteurs meeting (Portland, 21-25
August 2000)
FOR:	ACTION required response by 1st November 2000
CONTACTS: 	Mr. Dale Skran, Rapporteur for Q.13/16	
                Tel: +1 732 625 3003 x202
                Sonus Networks,
                4400 Route 9 South, Suite 3500,	
                Freehold, NJ 07728, USA	
                Email:	dskran@Sonusnet.com


Abstract: This contribution discusses possible use of CPL in the
context of H.323 and provides remarks for the current CPL
specification.
 


1	Trying to apply CPL to H.323 

According to our understanding, one of the original CPL goals was to
make the definition independent from the specific underlying Call
Signaling Protocol. It can be seemed as an "abstract" API definition
for a specific Application, allowing for different protocols to
actually implement it.  The CPL, as it is defined today, can be used
to describe the behavior of an H.323 Server. Nevertheless, the main
concern is that the CPL specification is not structured in a way
allowing a separation of the "abstract" concepts from their mapping
into a specific system or into specific protocol fields. Moreover,
many of the CPL "abstracts" are defined by providing examples or
pointers to SIP-related IETF documents. This forces the writer of the
CPL script to become familiar with the details and considerations
behind the SIP design.  This situation led for the inclusion of a
limiting H.323 interpretation into the body of the CPL definition. In
some cases, this interpretation is inconsistent with the SIP
interpretation of the CPL.  2 The Proposed "Roadmap" Based on the
"advanced" CPL standardization stage within the IETF, the following is
proposed for the consideration:

For the current CPL version, it is proposed to correct the "editorial"
errors, described in the following chapter, within the CPL document.

H.323 community will define a more flexible interpretation of H.323
behavior being expressed by the CPL. New "features" may be introduced
by expanding the CPL definitions. (This "extension" practice, in some
cases, is allowed by the CPL specification.) The output of this work
will be included into H.323 "Annex O" and will be published as an
Informational RFC.

CPL nodes differ in their "abstraction level". A certain group of the
CPL nodes (such as dealing with the time conditions) is naturally not
dependent on the Call Signaling Protocol. Another group, such as
"address-resolution" look-ups, is dependent on the System
definition. In addition, the CPL "address-processing" and
"string-processing" nodes define a "lower-level" logic, binding the
CPL definitions with the certain fields of the Call Signaling
messages.

Therefore, for the next CPL version, It is proposed to re-arrange the
CPL Specification by grouping the nodes, based on their "abstraction
level".  
- For the "low level" nodes, it is proposed to split between
their "abstract description" and the actual mapping into a specific
Signaling protocol
- For the benefit of the CPL user (i.e. the CPL script writer), it is
also proposed to define the meaning of each "node" and provide its
"design considerations" from the application point of view, without
referencing to the SIP details. 

3 Specific H.323 Comments 

3.1 Thedefinition of "incoming" and "outgoing" 

From the [CPL]: "Two top-level action names are defined: incoming, the
action performed when a call arrives whose destination is the owner of
the script; and outgoing, the action performed when a call arrives
whose originator is the owner of the script."

In H.323, there is no explicit concept of the "intermediate Call
Signaling Server" and the CPL "destination" field will NOT usually
hold the address of the Call Signaling Server itself. Therefore, it is
proposed to revise the quoted above definition.

3.2 Mapping of ASN.1 structures into ABNF

Various H.323 ASN.1 definitions should be mapped to ABNF in order to
be used within text based languages and protocols. Examples include
H.225.0 AliasAddress definitions for PartyNumber and mobileUIM; and
the TransportAddress definition. It is proposed to introduce such
definitions in H.323 "Annex O" and reference them (or reproduce them
till the "Annex O" is decided).

3.3	CPL "Address Switch"

Current CPL definition has a concept of two, applicable to H.323,
"address" field definitions: "origin" and "original-destination". On
the contrary, H.323 defines many address fields that may be of
interest of the CPL user. Moreover, more then one alias may exist in a
single H.323 message. Mandating of choosing one single alias out of a
number of possibilities is limiting for H.323 systems.

The current CPL version allows for an expression like that: "If one of
the alias fields of different types matches, the specified for it,
condition, then ...". Unfortunately, this option is left out of the
CPL Specification.

Based on the remarks above, it is proposed that the current CPL
specification will state that the "Address switch mapping for H.323"
Chapter is "an illustration only" for how the CPL fields can be mapped
into the H.323 fields.

The third CPL "address" definition is called "destination". It
reflects the SIP concept of intermediate Call Signaling
Server. Therefore, the current mapping of H.225.0 redirectingNumberIE
into the CPL "destination" concept is inconsistent with the SIP
interpretation of the same field. For example, in case of the
"incoming call", the H.225.0 destCallSignalAddress field fits the
concept of CPL "destination" more closely. (This redirectingNumberIE
element is, by mistake, called a "redirectedNumber" by the CPL)

3.4	Location Lookup

The "Lookup" CPL node is a Call Signaling-independent concept. It fits
both the H.323 and the SIP architectures. Nevertheless, bounding of
the "location lookup" itself with the further operations to be applied
to its results (such as capabilities filtering), seems to be a
limiting design consideration. It is proposed to define these two
actions (i.e. the lookup and the filtering on the output) as two
separate CPL nodes.

3.4.1	"Caller Preferences and Callee Capabilities"

As a part of CPL "Location Lookup" Switch, a filtering capability on
"caller preferences" is defined. These CPL parameters are based solely
on the "caller preferences" specified by one of the SIP extensions
["Caller Preferences and Callee Capabilities"].

The "Generic Framework", lately introduced into H.323, has essentially
the same concept. Although, the following difference exists: CPL is
limited to the scope of a Call. The "Generic Framework" of H.323
addresses both the Registration and the Call Establishment stages.
H.323 Community will work to apply the "Generic Framework" to the CPL
work.

3.5	"Location"

A significant problem is that CPL generates outbound call signaling
based on a Location element which currently can only be a URL.  Some
significant data that should be used in the outgoing signaling, e.g,
redirection reason, are not available in current H.323 URL and may not
naturally fit into such URLs.  It would be desirable to have a more
flexible way to set such parameters, but this may require more study
than can be accomplished for the current version of CPL.



  


-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Sun Sep  3 01:24:40 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23472
	for <iptel-archive@odin.ietf.org>; Sun, 3 Sep 2000 01:24:39 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id CCC3344390; Sun,  3 Sep 2000 00:24:13 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 97EF244336
	for <iptel@lists.bell-labs.com>; Sun,  3 Sep 2000 00:24:10 -0400 (EDT)
Received: from dynamicsoft.com (1Cust182.tnt5.freehold.nj.da.uu.net [63.36.113.182])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA12069;
	Sun, 3 Sep 2000 01:25:55 -0400 (EDT)
Message-ID: <39B1E044.BF12899D@dynamicsoft.com>
Date: Sun, 03 Sep 2000 01:23:16 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:
> 
> >
> > So, is there consensus around this? We keep the time-switch from the
> > older drafts, and then think about defining the iCal one for the next
> > CPL rev once we understand its usage better? Any objections?
> >
> 
> I'm *very* uncomfortable with this. At the very least, we need to define
> how CPL can be reasonably extended in the future. Also, if we go that
> route, I would suggest going for real simplicity, i.e., fixed time range
> only, as a proper subset of the iCal specification. That will make for a
> much cleaner transition strategy rather than mixing two models. That
> way, we have an overall implementation that's simpler.

I have no problem using a subset of iCal; namely the start and stop
times, duration, and repitition stuff. The complexity is all in the byX
attributes. I wouldn't be so concerned about doing these if someone
could show me some pseudocode about how these might be implemented in a
reasonable way. If the pseudocode for this is many pages, then I
definitely need to question whether its worth it...

Regarding extensibility:

Ignoreing unknown attributes and tags (but parsing the content of
unknown tags) seems a reasonable thing for extensibility, but has the
unfortunate side effect of eliminating the possibility of DTD
validation. Is there any way to build extensibility in without ruling
out validation of a script against the DTD in the baseline CPL
specification? 

-Jonathan R.
-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Sun Sep  3 09:08:17 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08774
	for <iptel-archive@odin.ietf.org>; Sun, 3 Sep 2000 09:08:15 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id D962F44387; Sun,  3 Sep 2000 08:08:10 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157])
	by lists.bell-labs.com (Postfix) with ESMTP id 81E8C4436F
	for <iptel@lists.bell-labs.com>; Sun,  3 Sep 2000 08:08:07 -0400 (EDT)
Received: from cs.columbia.edu (adsl-151-198-20-48.bellatlantic.net [151.198.20.48])
	by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id JAA28275;
	Sun, 3 Sep 2000 09:07:20 -0400 (EDT)
Message-ID: <39B24D1B.2D64DA2A@cs.columbia.edu>
Date: Sun, 03 Sep 2000 09:07:39 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD BA45DSL  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



> I have no problem using a subset of iCal; namely the start and stop
> times, duration, and repitition stuff. The complexity is all in the byX
> attributes. I wouldn't be so concerned about doing these if someone
> could show me some pseudocode about how these might be implemented in a
> reasonable way. If the pseudocode for this is many pages, then I
> definitely need to question whether its worth it...

I think a subset makes sense for now.


> Regarding extensibility:
> 
> Ignoreing unknown attributes and tags (but parsing the content of
> unknown tags) seems a reasonable thing for extensibility, but has the
> unfortunate side effect of eliminating the possibility of DTD
> validation. Is there any way to build extensibility in without ruling
> out validation of a script against the DTD in the baseline CPL
> specification?

I don't like just ignoring attributes. That's why I suggested that, in
addition, CPL itself has the ability to switch on extensions, so that
one can implement default behavior if a particular feature is not
supported. 

Outside of making extensions just parameter values, it will be hard to
anticipate DTDs. I'm also not sure it matters. If the creator can
generate new features, it presumably can validate them. If the server
doesn't understand the feature, it doesn't much matter whether it is
syntactically correct. The only borderline case is that a new feature is
really just a mis-spelling of an old one. Having the switch around the
feature would tell the server whether it should go checking, but
unfortunately, I suspect that no XML checker would be smart enough for
that. Namespaces?


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Sun Sep  3 14:40:39 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11247
	for <iptel-archive@odin.ietf.org>; Sun, 3 Sep 2000 14:40:39 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 617C144351; Sun,  3 Sep 2000 13:40:30 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by lists.bell-labs.com (Postfix) with ESMTP id E835A44348
	for <iptel@lists.bell-labs.com>; Sun,  3 Sep 2000 13:40:26 -0400 (EDT)
Received: from fokus.gmd.de (shaky [193.175.132.94])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id UAA28968;
	Sun, 3 Sep 2000 20:40:18 +0200 (MET DST)
Message-ID: <39B29B1E.D3290525@fokus.gmd.de>
Date: Sun, 03 Sep 2000 20:40:30 +0200
From: Jiri Kuthan <kuthan@fokus.gmd.de>
Organization: GMD Fokus
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Henning Schulzrinne wrote:
> At the very least, we need to define
> how CPL can be reasonably extended in the future. 

I second this. Extensibility is needed since both signaling
and signaling processing are likely to evolve further.
CPL's extensibility concept is not documented right now.
(There is only a recommendation in Section 12.1 of RFC2824
to inform users of unknown features included in 
scripts.)

In particular, we need to document how CPL interpreters 
deal with unknown elements (UE) in CPL scripts. Two possible 
(RFC-2824-conformant) strategies I see are: 
1)  conservative
    '- on installation: reject scripts that include unknown elements (UE)'
2) liberal
    '- on installation: accept scripts with UEs, issue warnings;
     - in run-time: if UEs encountered, skip them and pass control
       to UE handlers embedded in the CPL scripts'

My preference is 2.

Jiri


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep  4 00:50:24 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17121
	for <iptel-archive@odin.ietf.org>; Mon, 4 Sep 2000 00:50:24 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id E5F3A44398; Sun,  3 Sep 2000 23:50:18 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 12B6D44348
	for <iptel@lists.bell-labs.com>; Sun,  3 Sep 2000 23:50:16 -0400 (EDT)
Received: from dynamicsoft.com (1Cust19.tnt1.freehold.nj.da.uu.net [63.17.113.19])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id AAA00878;
	Mon, 4 Sep 2000 00:50:15 -0400 (EDT)
Message-ID: <39B3296F.1D28EC17@dynamicsoft.com>
Date: Mon, 04 Sep 2000 00:47:43 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:
> 
> > I have no problem using a subset of iCal; namely the start and stop
> > times, duration, and repitition stuff. The complexity is all in the byX
> > attributes. I wouldn't be so concerned about doing these if someone
> > could show me some pseudocode about how these might be implemented in a
> > reasonable way. If the pseudocode for this is many pages, then I
> > definitely need to question whether its worth it...
> 
> I think a subset makes sense for now.

OK, so the trick is to define exactly which subset. My initial proposal
is:

Parameters:  dtstart      Start of interval (RFC 2445 DATE-TIME)
                dtend        End of interval (RFC 2445 DATE-TIME)
                duration     Length of interval (RFC 2445 DURATION)
                freq         Frequency of recurrence (one of "secondly",
                             "minutely", "hourly", "daily", "weekly",
                             "monthly", or "yearly")
                interval     How often the recurrence repeats
                until        Bound of recurrence (RFC 2445 DATE-TIME)
                count        Number of occurences of recurrence


I wouldn't even object to adding the byX attributes under the condition
of "contraction", that is, the unit in the by component is always a
greater interval than the freq component. These cases are easier to
handle, it seems. You compute the start time of the next interval as if
there were bo byX parameter, and then check if this start time is within
the interval indicated by the byX parameter.

What do people think?

> 
> > Regarding extensibility:
> >
> > Ignoreing unknown attributes and tags (but parsing the content of
> > unknown tags) seems a reasonable thing for extensibility, but has the
> > unfortunate side effect of eliminating the possibility of DTD
> > validation. Is there any way to build extensibility in without ruling
> > out validation of a script against the DTD in the baseline CPL
> > specification?
> 
> I don't like just ignoring attributes. That's why I suggested that, in
> addition, CPL itself has the ability to switch on extensions, so that
> one can implement default behavior if a particular feature is not
> supported.
> 
> Outside of making extensions just parameter values, it will be hard to
> anticipate DTDs. I'm also not sure it matters. If the creator can
> generate new features, it presumably can validate them. If the server
> doesn't understand the feature, it doesn't much matter whether it is
> syntactically correct. The only borderline case is that a new feature is
> really just a mis-spelling of an old one. Having the switch around the
> feature would tell the server whether it should go checking, but
> unfortunately, I suspect that no XML checker would be smart enough for
> that. Namespaces?

THe problem isn't restricted to mis-spellings. Here is what I am talking
about. If I have some extension foo, and I use your approach of having a
tag which indicates what to do if the extension isn't supported:

<if understand="foo">
 <foo bar="baz"/>
</if>

This little CPL won't be accepted by baseline CPLs, since they won't
know about foo in the DTD and thus the script is immediately rejected.
The only way I know of to turn off parsing for subcompnents is via
CDATA:

<if understand="foo">
 <![CDATA[
  <foo bar="baz"/>
 ]]>
</if>

Parsers that do understand foo could conceivably extract the content of
the CDATA and then re-validate. A bit of a pain, but it would work.
Nesting of if tags is a bit annoying, since the XML parser will pick up
the first ]] and not the last, as you would want. Not sure what to do
about that...

-Jonathan R.


-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep  4 21:50:31 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09909
	for <iptel-archive@odin.ietf.org>; Mon, 4 Sep 2000 21:50:31 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 1B29144337; Mon,  4 Sep 2000 20:50:27 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id D80CF44337
	for <iptel@lists.bell-labs.com>; Mon,  4 Sep 2000 11:45:52 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id MAA04520;
	Mon, 4 Sep 2000 12:45:25 -0400 (EDT)
Message-ID: <39B3D1A5.1812CCAD@cs.columbia.edu>
Date: Mon, 04 Sep 2000 12:45:25 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> 

> 
> Parameters:  dtstart      Start of interval (RFC 2445 DATE-TIME)
>                 dtend        End of interval (RFC 2445 DATE-TIME)
>                 duration     Length of interval (RFC 2445 DURATION)
>                 freq         Frequency of recurrence (one of "secondly",
>                              "minutely", "hourly", "daily", "weekly",
>                              "monthly", or "yearly")
>                 interval     How often the recurrence repeats
>                 until        Bound of recurrence (RFC 2445 DATE-TIME)
>                 count        Number of occurences of recurrence
> 
> I wouldn't even object to adding the byX attributes under the condition
> of "contraction", that is, the unit in the by component is always a
> greater interval than the freq component. These cases are easier to
> handle, it seems. You compute the start time of the next interval as if
> there were bo byX parameter, and then check if this start time is within
> the interval indicated by the byX parameter.
> 
> What do people think?

Seems like a good idea. We should probably check whether this covers the
common recurrence cases such as

- Tu and Th, some time range
- first Monday of the month (as in Labor Day...)



> THe problem isn't restricted to mis-spellings. Here is what I am talking
> about. If I have some extension foo, and I use your approach of having a
> tag which indicates what to do if the extension isn't supported:
> 
> <if understand="foo">
>  <foo bar="baz"/>
> </if>
> 
> This little CPL won't be accepted by baseline CPLs, since they won't
> know about foo in the DTD and thus the script is immediately rejected.
> The only way I know of to turn off parsing for subcompnents is via
> CDATA:
> 
> <if understand="foo">
>  <![CDATA[
>   <foo bar="baz"/>
>  ]]>
> </if>
> 
> Parsers that do understand foo could conceivably extract the content of
> the CDATA and then re-validate. A bit of a pain, but it would work.
> Nesting of if tags is a bit annoying, since the XML parser will pick up
> the first ]] and not the last, as you would want. Not sure what to do
> about that...

This seems ugly. Would namespaces help?

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 06:18:53 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26879
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 06:18:53 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 10C0244345; Tue,  5 Sep 2000 05:18:47 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ubiquity.net (mail.ubiquity.net [194.128.96.72])
	by lists.bell-labs.com (Postfix) with ESMTP id 67E8144336
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 05:18:43 -0400 (EDT)
Received: from ubiquity.net by ubiquity.net with ESMTP (8.8.8+Sun/25-eef)
	id LAA21792; Tue, 5 Sep 2000 11:16:18 +0100 (BST)
Message-ID: <39B4C7F4.BD4D03FF@ubiquity.net>
Date: Tue, 05 Sep 2000 11:16:20 +0100
From: James Undery <jundery@ubiquity.net>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B3D1A5.1812CCAD@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:

> Jonathan Rosenberg wrote:
> >
>
> >
> > Parameters:  dtstart      Start of interval (RFC 2445 DATE-TIME)
> >                 dtend        End of interval (RFC 2445 DATE-TIME)
> >                 duration     Length of interval (RFC 2445 DURATION)
> >                 freq         Frequency of recurrence (one of "secondly",
> >                              "minutely", "hourly", "daily", "weekly",
> >                              "monthly", or "yearly")
> >                 interval     How often the recurrence repeats
> >                 until        Bound of recurrence (RFC 2445 DATE-TIME)
> >                 count        Number of occurences of recurrence
> >
> > I wouldn't even object to adding the byX attributes under the condition
> > of "contraction", that is, the unit in the by component is always a
> > greater interval than the freq component. These cases are easier to

This is a bit late in the day to have a change of heart, but I've just
actually thought about implementing this efficiently, and I can't see what the
fuss was.

Firstly check all the byX's are satisfied.
Secondly find if the if the time lies in a repetition of the time period.

Jonathan, correctly state if there is repetition the second step is harder,
however, this can be calculated in constant time with the correct time
representation (depends on the freq, yearly and monthly RFC 2445 DATE-TIME is
good, all other seconds are fine), then normalise your timeframe on dtstart
and use modulo arithmetic to check if you are in a repetition. I assume
calculating the bounds of occurences (if they exist) cause no problem for
anyone.

There is a mistake in the spec though "No parameters other than dtstart, dtend
and duration SHOULD be specified unless freq is present." The byX parameters
need not be excluded as they make perfect sense in a single period. (Also I
removed a surplus comma after dtend)

>
> > handle, it seems. You compute the start time of the next interval as if
> > there were bo byX parameter, and then check if this start time is within
> > the interval indicated by the byX parameter.
> >
> > What do people think?
>
> Seems like a good idea. We should probably check whether this covers the
> common recurrence cases such as
>
> - Tu and Th, some time range

<time dtstart="20000805T090000" duration="P5W" byday="TU,TH">

>
> - first Monday of the month (as in Labor Day...)
>

<time dtstart="20000805T090000" duration="P52W" byday="1MO">

James Undery



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 11:14:37 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04489
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 11:14:37 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id A0E064433F; Tue,  5 Sep 2000 10:14:22 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id E0CA244336
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 10:14:18 -0400 (EDT)
Received: from dynamicsoft.com (1Cust235.tnt1.freehold.nj.da.uu.net [63.17.113.235])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id LAA04620;
	Tue, 5 Sep 2000 11:15:49 -0400 (EDT)
Message-ID: <39B50D80.DEEF34AE@dynamicsoft.com>
Date: Tue, 05 Sep 2000 11:13:04 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
Cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B3D1A5.1812CCAD@cs.columbia.edu> <39B4C7F4.BD4D03FF@ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



James Undery wrote:
> 
> > > I wouldn't even object to adding the byX attributes under the condition
> > > of "contraction", that is, the unit in the by component is always a
> > > greater interval than the freq component. These cases are easier to
> 
> This is a bit late in the day to have a change of heart, but I've just
> actually thought about implementing this efficiently, and I can't see what the
> fuss was.
> 
> Firstly check all the byX's are satisfied.
> Secondly find if the if the time lies in a repetition of the time period.

This is true for byXs that represent contraction, that is, elimination
of some of the 
allowed repittion periods. Thats why I am proposing this.

> 
> Jonathan, correctly state if there is repetition the second step is harder,
> however, this can be calculated in constant time with the correct time
> representation (depends on the freq, yearly and monthly RFC 2445 DATE-TIME is
> good, all other seconds are fine), then normalise your timeframe on dtstart
> and use modulo arithmetic to check if you are in a repetition. I assume
> calculating the bounds of occurences (if they exist) cause no problem for
> anyone.

This doesn't cover the expansion cases, whereby you can have occurrences
more frequently than the recurrence interval.

Also, you can't use real modulo arithmetic, because date addition is too
convoluted. The only way to do this, as I see it, is to start with
dtstart, and add the recurrence interval using calendar addition
functions (the java Calendar class seems to do most of this for you,
thank goodness). THen, add the duration to that, and check if the
current time is between the two. If the current time is after the end of
the event, add another recurrence interval (keeping track of bounds of
recurrences). Separately, before doing this, you would check to see if
the byX relations are satisfied.

> 
> There is a mistake in the spec though "No parameters other than dtstart, dtend
> and duration SHOULD be specified unless freq is present." The byX parameters
> need not be excluded as they make perfect sense in a single period. (Also I
> removed a surplus comma after dtend)

I don't think so. byX only make sense for repitions. It would be
pointless to define a single event (via dtstart, dtend, and duration),
and then eliminate it with a byX.

> 
> >
> > > handle, it seems. You compute the start time of the next interval as if
> > > there were bo byX parameter, and then check if this start time is within
> > > the interval indicated by the byX parameter.
> > >
> > > What do people think?
> >
> > Seems like a good idea. We should probably check whether this covers the
> > common recurrence cases such as
> >
> > - Tu and Th, some time range
> 
> <time dtstart="20000805T090000" duration="P5W" byday="TU,TH">

Ahh. Now I see why you wanted to allow byX without freq. You want to
express an event as *really* long, and then eliminate blocks of its time
with byX. Thats not how it works. byX modifies when the *beginning* of
an event occurs, it does not block out certain times during the event.
So, the correct way to express this is:

<time dtstart="20000805T090000" duration="P1H" freq="daily"
byday="TU,TH" count="104">

This would specify a one hour window from 9am to 10am, every tuesday and
thursday, for a year. 

> 
> >
> > - first Monday of the month (as in Labor Day...)
> >
> 
> <time dtstart="20000805T090000" duration="P52W" byday="1MO">

Same as above. The correct way is:

<time dtstart="20000805T090000" duration="P1H" freq="monthly"
byday="1MO" count="100">

This, unfortunately, represents the expansion case, and its one of the
things I can't figure out how to handle. The problem is that you can't
really use the month repitition any more. The rule specifies the first
monday of the month, 9am-10am. What confuses me is that the monthly
repititons on the dtstart may not even fall on Monday; so, in this case,
do you ignore those repititions? Its like byX is specifying an alternate
repition mechanism, and I can't figure out how it interacts with the
regular freq mechanism.

-Jonathan R.


-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 11:19:27 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04600
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 11:19:27 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 660244435F; Tue,  5 Sep 2000 10:19:20 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 6360A4435E
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 10:19:17 -0400 (EDT)
Received: from dynamicsoft.com (1Cust235.tnt1.freehold.nj.da.uu.net [63.17.113.235])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id LAA04657;
	Tue, 5 Sep 2000 11:20:52 -0400 (EDT)
Message-ID: <39B50EB0.5B48498B@dynamicsoft.com>
Date: Tue, 05 Sep 2000 11:18:08 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B3D1A5.1812CCAD@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:
> 
> > THe problem isn't restricted to mis-spellings. Here is what I am talking
> > about. If I have some extension foo, and I use your approach of having a
> > tag which indicates what to do if the extension isn't supported:
> >
> > <if understand="foo">
> >  <foo bar="baz"/>
> > </if>
> >
> > This little CPL won't be accepted by baseline CPLs, since they won't
> > know about foo in the DTD and thus the script is immediately rejected.
> > The only way I know of to turn off parsing for subcompnents is via
> > CDATA:
> >
> > <if understand="foo">
> >  <![CDATA[
> >   <foo bar="baz"/>
> >  ]]>
> > </if>
> >
> > Parsers that do understand foo could conceivably extract the content of
> > the CDATA and then re-validate. A bit of a pain, but it would work.
> > Nesting of if tags is a bit annoying, since the XML parser will pick up
> > the first ]] and not the last, as you would want. Not sure what to do
> > about that...
> 
> This seems ugly. Would namespaces help?

I don't think so. Unfortunately, I believe they suffer from the same DTD
validation problems - i.e., I don't know how to do DTD validation on a
document with elements from external namespaces. This may just be my
ignorance. Any XML namespace experts care to comment?

-Jonathan R.
-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 16:50:57 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13595
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 16:50:56 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 493CF44377; Tue,  5 Sep 2000 15:50:32 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14])
	by lists.bell-labs.com (Postfix) with ESMTP id B5BD04435E
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 15:50:28 -0400 (EDT)
Received: from fokus.gmd.de (shaky [193.175.132.94])
	by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id WAA24851;
	Tue, 5 Sep 2000 22:50:08 +0200 (MET DST)
Message-ID: <39B55BBF.1AB822B1@fokus.gmd.de>
Date: Tue, 05 Sep 2000 22:46:55 +0200
From: Jiri Kuthan <kuthan@fokus.gmd.de>
Organization: GMD Fokus
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> <if understand="foo">
>  <foo bar="baz"/>
> </if>
> 
> This little CPL won't be accepted by baseline CPLs, since they won't
> know about foo in the DTD and thus the script is immediately rejected.

Jonathan,

is insisting on DTD conformance so useful if it prohibits extensibility?
How do you plan to deal with extensions?

Jiri


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 18:10:32 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14839
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 18:10:31 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 2AB6F4435F; Tue,  5 Sep 2000 17:10:13 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id E4C874433F
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 17:10:10 -0400 (EDT)
Received: from dynamicsoft.com (1Cust235.tnt1.freehold.nj.da.uu.net [63.17.113.235])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id SAA09322;
	Tue, 5 Sep 2000 18:08:09 -0400 (EDT)
Message-ID: <39B56E21.273F1F30@dynamicsoft.com>
Date: Tue, 05 Sep 2000 18:05:21 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jiri Kuthan <kuthan@fokus.gmd.de>
Cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B55BBF.1AB822B1@fokus.gmd.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Jiri Kuthan wrote:
> 
> Jonathan Rosenberg wrote:
> > <if understand="foo">
> >  <foo bar="baz"/>
> > </if>
> >
> > This little CPL won't be accepted by baseline CPLs, since they won't
> > know about foo in the DTD and thus the script is immediately rejected.
> 
> Jonathan,
> 
> is insisting on DTD conformance so useful if it prohibits extensibility?
> How do you plan to deal with extensions?

IMHO, XML without DTD validation is useless. DTD validation ensures that
all other kinds of things are correct with CPL, things I would have to
check manually without validation, effectively writing my own validating
parser.

-Jonathan R.

-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 19:14:52 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15333
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 19:14:52 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 10C4144375; Tue,  5 Sep 2000 18:14:47 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 14BCC4433F
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 18:14:44 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id TAA06061;
	Tue, 5 Sep 2000 19:10:54 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id TAA39075;
	Tue, 5 Sep 2000 19:10:53 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14773.32125.175514.176575@conrail.cs.columbia.edu>
Date: Tue, 5 Sep 2000 19:10:53 -0400 (EDT)
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Henning Schulzrinne <schulzrinne@opus.cs.columbia.edu>,
        James Undery <jundery@ubiquity.net>, iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
In-Reply-To: <39B50EB0.5B48498B@dynamicsoft.com>
References: <39A4F1A6.87F7A386@indigosw.com>
	<39A4F5B4.BD3E3EE2@ubiquity.net>
	<39A5275C.3AADBE1F@dynamicsoft.com>
	<39A535F1.48928278@ubiquity.net>
	<39A5FC2D.F49020AB@dynamicsoft.com>
	<39A6379C.DCC21EA3@ubiquity.net>
	<39AF5AC2.1016B520@dynamicsoft.com>
	<39AFAB1E.D73D303D@cs.columbia.edu>
	<39B1E044.BF12899D@dynamicsoft.com>
	<39B24D1B.2D64DA2A@cs.columbia.edu>
	<39B3296F.1D28EC17@dynamicsoft.com>
	<39B3D1A5.1812CCAD@cs.columbia.edu>
	<39B50EB0.5B48498B@dynamicsoft.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

On Tuesday, September 5 2000, "Jonathan Rosenberg" wrote to "Henning Schulzrinne, James Undery, iptel@lists.bell-labs.com" saying:

> I don't think so. Unfortunately, I believe they suffer from the same DTD
> validation problems - i.e., I don't know how to do DTD validation on a
> document with elements from external namespaces. This may just be my
> ignorance. Any XML namespace experts care to comment?

The nature of DTD validation is that a DTD defines a fixed content model,
and nothing more.   It doesn't (as far as I can tell) have room for
extensibility within this framework.

As such, I think we have three conflicting goals:

* Extensibility
* Backward compatibility for extensions
* DTD validation

It's not clear all of these can be satisfied at once (at least not without
doing something like the CDATA suggestion, which I think is truly ugly).

With some minor effort, it would be possible, I think, to define a wrapper
around DTDs in order to support only *those namespaces you understand* --
for example, it seems like this would be possible for SAX applications by
using the Namespace SAX Filter <http://home.ccil.org/~cowan/XML/>.  However,
this wouldn't allow us to do, for example:

<extension ns="http://www.example.com/cpl/our-first-weird-extension">
   <supported>
      <color-switch xmlns="http://www.example.com/cpl/our-first-weird-extension">
        <color is="blue">
            ... 
        </color>
        <color is="green">
            ...
        </color>
        <otherwise>
            ...
        </otherwise>
      </color-switch>
   </supported>
   <unsupported>
      <mail url="mailto:admin@example.com?subject=Server%20is%20colorblind!" />
   </unsupported>
</extension>

Is this needed?  Obviously, if this sort of thing is present, no
syntactic-level DTD validation is going to be possible.  You're going to
need to use a non-validating XML parser, and then do your validation
entirely at the semantic level.  It's not entirely clear to me how much this
is useful, though.

As a point of reference, the Sieve people considered this sort of
extensibility mechanism, but decided instead to use a "you must declare all
extensions you are using.  A server rejects all scripts requesting unknown
extensions."  This was the justification given for this (Ned Freed
<Ned.Freed@innosoft.com>, 25 Jan 1998):

        The problem lies in how "support" affects the way the language is
        used. People will use the presence of "support" to justify all sorts
        of extensions. These extensions will then be used willy-nilly, and
        they will be used *without* support tests being made. We will then
        end up with massive interoperability problems.

        You are recreating the PostScript situation here. Nothing more and
        nothing less. 

As such, I would suggest that CPL extensions use XML namespaces, and we
apply the rule "if the script requests an unknown namespace, it must be
rejected".

Given this, I *think* that it would be possible to define a custom DTD given
something like a namespace filter which would allow you to validate all
the CPL extensions you undertand.  I'm almost positive it would be
possible to define an XML schema which would do this, since XML schemas have
been defined post-namespaces.  (Retrofitting namespaces onto DTDs is ugly at
best, and impossible at worst.)

Useful information about XML namespaces is available at:
<http://www.informatik.tu-darmstadt.de/DVS1/staff/bourret/xml/NamespacesFAQ.htm>

-- 
Jonathan Lennox
lennox@cs.columbia.edu


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Tue Sep  5 20:04:25 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15801
	for <iptel-archive@odin.ietf.org>; Tue, 5 Sep 2000 20:04:25 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 47EBA44381; Tue,  5 Sep 2000 19:04:20 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from lotl.clari.net.au (lotl.clari.net.au [203.26.127.210])
	by lists.bell-labs.com (Postfix) with ESMTP id 5128B4435E
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 19:04:16 -0400 (EDT)
Received: from spa.com.au (ppp-195.dialup.clari.net.au [203.57.253.195])
	by lotl.clari.net.au (8.9.3/8.9.1) with SMTP id LAA14913
	for <iptel@lists.bell-labs.com>; Wed, 6 Sep 2000 11:03:18 +1100 (EST)
	(envelope-from gbs@spa.com.au)
Received: from giuseppe [192.168.0.153] by spa.com.au [192.168.0.100] with SMTP (MDaemon.v2.7.SP5.R) for <iptel@lists.bell-labs.com>; Wed, 06 Sep 2000 10:10:09 +1100
From: "Giuseppe B. Scelsi" <gbs@spa.com.au>
To: <iptel@lists.bell-labs.com>
Date: Wed, 6 Sep 2000 10:12:00 +1100
Message-ID: <006301c0178e$b2e1a0e0$9900a8c0@spa.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
X-MDaemon-Deliver-To: iptel@lists.bell-labs.com
X-Return-Path: gbs@spa.com.au
Subject: [IPTEL] DTMF relay standards?
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Hi everyone,

I am trying to find out if there is any existing specification/standard for
the testing of a DTMF "relay" function.  NOT DTMF detection or generation,
but something specific to the problem of reproducing levels and in
particular timings of DTMF signals after packetisation and transport using
for instance RTP.

Any help is welcome.

Cheers,

Giuseppe Scelsi


--
Giuseppe B. Scelsi
Vice President Engineering              phone:  +61 3 9800 2000
Signal Processing Associates Pty Ltd    fax:    +61 3 9800 2111
Unit 3, 97 Lewis Road                   e-mail: gbs@spa.com.au
Wantirna VIC 3152                       www:    http://www.spa.com.au/
AUSTRALIA                               time zone: GMT+10




_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Wed Sep  6 03:40:26 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05247
	for <iptel-archive@odin.ietf.org>; Wed, 6 Sep 2000 03:40:26 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id BB79244362; Wed,  6 Sep 2000 02:40:22 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ubiquity.net (mail.ubiquity.net [194.128.96.72])
	by lists.bell-labs.com (Postfix) with ESMTP id D883E4433F
	for <iptel@lists.bell-labs.com>; Wed,  6 Sep 2000 02:40:18 -0400 (EDT)
Received: from ubiquity.net by ubiquity.net with ESMTP (8.8.8+Sun/25-eef)
	id IAA29670; Wed, 6 Sep 2000 08:38:26 +0100 (BST)
Message-ID: <39B5F475.282DA46D@ubiquity.net>
Date: Wed, 06 Sep 2000 08:38:30 +0100
From: James Undery <jundery@ubiquity.net>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B3D1A5.1812CCAD@cs.columbia.edu> <39B4C7F4.BD4D03FF@ubiquity.net> <39B50D80.DEEF34AE@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Jonathan Rosenberg wrote:

> James Undery wrote:
> >
> > > > I wouldn't even object to adding the byX attributes under the condition
> > > > of "contraction", that is, the unit in the by component is always a
> > > > greater interval than the freq component. These cases are easier to
> >
> > This is a bit late in the day to have a change of heart, but I've just
> > actually thought about implementing this efficiently, and I can't see what the
> > fuss was.
> >
> > Firstly check all the byX's are satisfied.
> > Secondly find if the if the time lies in a repetition of the time period.
>
> This is true for byXs that represent contraction, that is, elimination
> of some of the
> allowed repittion periods. Thats why I am proposing this.
>

Yes I've lost the plot here, I just read what I thought should be there. i.e. the
old cron style definitions.

>
> This, unfortunately, represents the expansion case, and its one of the
> things I can't figure out how to handle. The problem is that you can't
> really use the month repitition any more. The rule specifies the first
> monday of the month, 9am-10am. What confuses me is that the monthly
> repititons on the dtstart may not even fall on Monday; so, in this case,
> do you ignore those repititions? Its like byX is specifying an alternate
> repition mechanism, and I can't figure out how it interacts with the
> regular freq mechanism.

Having actually read the spec rather than getting bored after the parameters are
defined, I have to reassert my previous suggestion of ditching iCalender and
reverting to the previous spec (assuming I read that one too). They were much more
readable, had no less power and didn't have the complexity. Provided a sensible
method for versioning CPL I can see no reason for including iCalendar until a need
and use is demonstrated.

However, the versioning issue really comes from the use of XML rather than defining
a true scripting language. I'd be tempted to retain the syntax, yet not specify the
language as XML specifically, so versioning can be introduced as a more natural
rule.

James Undery





_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Wed Sep  6 03:50:14 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05382
	for <iptel-archive@odin.ietf.org>; Wed, 6 Sep 2000 03:50:13 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 7EAA544396; Wed,  6 Sep 2000 02:49:23 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ubiquity.net (mail.ubiquity.net [194.128.96.72])
	by lists.bell-labs.com (Postfix) with ESMTP id 2ED5F4433F
	for <iptel@lists.bell-labs.com>; Wed,  6 Sep 2000 02:49:12 -0400 (EDT)
Received: from ubiquity.net by ubiquity.net with ESMTP (8.8.8+Sun/25-eef)
	id IAA02724; Wed, 6 Sep 2000 08:46:50 +0100 (BST)
Message-ID: <39B5F66E.A85BF4F2@ubiquity.net>
Date: Wed, 06 Sep 2000 08:46:54 +0100
From: James Undery <jundery@ubiquity.net>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Jiri Kuthan <kuthan@fokus.gmd.de>,
        Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B55BBF.1AB822B1@fokus.gmd.de> <39B56E21.273F1F30@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Jonathan Rosenberg wrote:

> Jiri Kuthan wrote:
> >
> > Jonathan Rosenberg wrote:
> > > <if understand="foo">
> > >  <foo bar="baz"/>
> > > </if>
> > >
> > > This little CPL won't be accepted by baseline CPLs, since they won't
> > > know about foo in the DTD and thus the script is immediately rejected.
> >
> > Jonathan,
> >
> > is insisting on DTD conformance so useful if it prohibits extensibility?
> > How do you plan to deal with extensions?
>
> IMHO, XML without DTD validation is useless. DTD validation ensures that
> all other kinds of things are correct with CPL, things I would have to
> check manually without validation, effectively writing my own validating
> parser.
>

Writting a parser for CPL is a trival problem and most of the checks suggested
and required by the draft mean a fair quantity of checking needs to be done
manually. The real complexity in an XML parser is checking conformity to a
schema, yet with CPL its the semantics of the script that are important not
the syntax of the schema. You can check the script conforms to a schema but
that doesn't mean you can do anything with it or that the script really makes
sense.

James Undery



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Wed Sep  6 07:11:54 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07598
	for <iptel-archive@odin.ietf.org>; Wed, 6 Sep 2000 07:11:53 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 182BB4433E; Wed,  6 Sep 2000 06:11:47 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 29A374433F
	for <iptel@lists.bell-labs.com>; Tue,  5 Sep 2000 19:19:18 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id UAA10052;
	Tue, 5 Sep 2000 20:19:15 -0400 (EDT)
Message-ID: <39B58D83.F2F6794C@cs.columbia.edu>
Date: Tue, 05 Sep 2000 20:19:15 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Lennox <lennox@ober.cs.columbia.edu>
Cc: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com>
		<39A4F5B4.BD3E3EE2@ubiquity.net>
		<39A5275C.3AADBE1F@dynamicsoft.com>
		<39A535F1.48928278@ubiquity.net>
		<39A5FC2D.F49020AB@dynamicsoft.com>
		<39A6379C.DCC21EA3@ubiquity.net>
		<39AF5AC2.1016B520@dynamicsoft.com>
		<39AFAB1E.D73D303D@cs.columbia.edu>
		<39B1E044.BF12899D@dynamicsoft.com>
		<39B24D1B.2D64DA2A@cs.columbia.edu>
		<39B3296F.1D28EC17@dynamicsoft.com>
		<39B3D1A5.1812CCAD@cs.columbia.edu>
		<39B50EB0.5B48498B@dynamicsoft.com> <14773.32125.175514.176575@conrail.cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Jonathan Lennox wrote:
> 

> * Extensibility
> * Backward compatibility for extensions
> * DTD validation
> 
> It's not clear all of these can be satisfied at once (at least not without
> doing something like the CDATA suggestion, which I think is truly ugly).
> 
> With some minor effort, it would be possible, I think, to define a wrapper
> around DTDs in order to support only *those namespaces you understand* --
> for example, it seems like this would be possible for SAX applications by
> using the Namespace SAX Filter <http://home.ccil.org/~cowan/XML/>.  However,
> this wouldn't allow us to do, for example:
> 
> <extension ns="http://www.example.com/cpl/our-first-weird-extension">
>    <supported>
>       <color-switch xmlns="http://www.example.com/cpl/our-first-weird-extension">
>         <color is="blue">
>             ...
>         </color>
>         <color is="green">
>             ...
>         </color>
>         <otherwise>
>             ...
>         </otherwise>
>       </color-switch>
>    </supported>
>    <unsupported>
>       <mail url="mailto:admin@example.com?subject=Server%20is%20colorblind!" />
>    </unsupported>
> </extension>
> 
> Is this needed?  Obviously, if this sort of thing is present, no
> syntactic-level DTD validation is going to be possible.  You're going to
> need to use a non-validating XML parser, and then do your validation
> entirely at the semantic level.  It's not entirely clear to me how much this
> is useful, though.

The problem with not having the "if-supported" switches is that the
client effectively has to keep, in an extreme case, 2^N versions of the
CPL script, if N is the number of extensions it would like to use. This
becomes unmanageable pretty quickly unless the client has some kind of
internal meta-representation that allows it to dynamically create a
version of the script that only uses the desired extensions. This may
not be so bad, as in 

#ifdef feature17
<feature17>
  fancy stuff here
</feature17>
#elseif
basic call handling here
#endif

I suppose one could even let the server do this "preprocessing" if one
were sufficiently aesthetically challenged, by defining a new media type
"CPL-with-C-preprocessor".


> 
> As such, I would suggest that CPL extensions use XML namespaces, and we
> apply the rule "if the script requests an unknown namespace, it must be
> rejected".
> 
> Given this, I *think* that it would be possible to define a custom DTD given
> something like a namespace filter which would allow you to validate all
> the CPL extensions you undertand.  I'm almost positive it would be
> possible to define an XML schema which would do this, since XML schemas have
> been defined post-namespaces.  (Retrofitting namespaces onto DTDs is ugly at
> best, and impossible at worst.)
> 
> Useful information about XML namespaces is available at:
> <http://www.informatik.tu-darmstadt.de/DVS1/staff/bourret/xml/NamespacesFAQ.htm>
> 
> --
> Jonathan Lennox
> lennox@cs.columbia.edu

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Wed Sep  6 13:31:24 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18507
	for <iptel-archive@odin.ietf.org>; Wed, 6 Sep 2000 13:31:24 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id D65C64433D; Wed,  6 Sep 2000 12:31:18 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from east.isi.edu (east.isi.edu [38.245.76.2])
	by lists.bell-labs.com (Postfix) with ESMTP id D6DA54433D
	for <iptel@lists.bell-labs.com>; Wed,  6 Sep 2000 12:28:10 -0400 (EDT)
Received: from hafez.east.isi.edu (hafez.east.isi.edu [38.245.76.121])
	by east.isi.edu (8.9.2/8.9.2) with ESMTP id NAA15462;
	Wed, 6 Sep 2000 13:28:26 -0400 (EDT)
Received: from hafez.east.isi.edu (localhost [127.0.0.1])
	by hafez.east.isi.edu (8.9.3/8.8.7) with ESMTP id WAA05619;
	Wed, 6 Sep 2000 22:28:05 +0500
Message-Id: <200009061728.WAA05619@hafez.east.isi.edu>
To: "Giuseppe B. Scelsi" <gbs@spa.com.au>
Cc: iptel <iptel@lists.bell-labs.com>
Subject: Re: [IPTEL] DTMF relay standards? 
In-Reply-To: Your message of "Wed, 06 Sep 2000 10:12:00 +1100."
             <006301c0178e$b2e1a0e0$9900a8c0@spa.com.au> 
Date: Wed, 06 Sep 2000 13:28:05 -0400
From: Colin Perkins <csp@east.isi.edu>
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

--> "Giuseppe B. Scelsi" writes:
>I am trying to find out if there is any existing specification/standard for
>the testing of a DTMF "relay" function.  NOT DTMF detection or generation,
>but something specific to the problem of reproducing levels and in
>particular timings of DTMF signals after packetisation and transport using
>for instance RTP.

See RFC 2833.

Colin



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep  7 01:53:04 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05754
	for <iptel-archive@odin.ietf.org>; Thu, 7 Sep 2000 01:53:04 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 62BFC443BE; Thu,  7 Sep 2000 00:52:30 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 500D24439A
	for <iptel@lists.bell-labs.com>; Thu,  7 Sep 2000 00:52:27 -0400 (EDT)
Received: from dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA18984;
	Thu, 7 Sep 2000 01:50:23 -0400 (EDT)
Message-ID: <39B72C08.9CA9B403@dynamicsoft.com>
Date: Thu, 07 Sep 2000 01:47:52 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
Cc: Jiri Kuthan <kuthan@fokus.gmd.de>,
        Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B55BBF.1AB822B1@fokus.gmd.de> <39B56E21.273F1F30@dynamicsoft.com> <39B5F66E.A85BF4F2@ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



James Undery wrote:
> 
> > IMHO, XML without DTD validation is useless. DTD validation ensures that
> > all other kinds of things are correct with CPL, things I would have to
> > check manually without validation, effectively writing my own validating
> > parser.
> >
> 
> Writting a parser for CPL is a trival problem and most of the checks suggested
> and required by the draft mean a fair quantity of checking needs to be done
> manually. The real complexity in an XML parser is checking conformity to a
> schema, yet with CPL its the semantics of the script that are important not
> the syntax of the schema. You can check the script conforms to a schema but
> that doesn't mean you can do anything with it or that the script really makes
> sense.

Its not just me not wanting to do the work; there are lots of xml tools
getting written and being distributed, many of which are strongly based
on usage of the DTD. For example, XML SPy is a nice tool for editing
XML. If you have a DTD, it does "tab style" completions of tag names and
attributes as you type in the document. Very nice for quickly building
valid CPL scripts. I'd like to be able to usefully use such tools with
CPL.

-Jonathan R.

-- 
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (732) 741-7244
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep  7 06:40:01 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14662
	for <iptel-archive@odin.ietf.org>; Thu, 7 Sep 2000 06:40:01 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id CF96344377; Thu,  7 Sep 2000 05:39:43 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ubiquity.net (mail.ubiquity.net [194.128.96.72])
	by lists.bell-labs.com (Postfix) with ESMTP id 7FFC94433D
	for <iptel@lists.bell-labs.com>; Thu,  7 Sep 2000 05:39:37 -0400 (EDT)
Received: from ubiquity.net by ubiquity.net with ESMTP (8.8.8+Sun/25-eef)
	id LAA29506; Thu, 7 Sep 2000 11:36:51 +0100 (BST)
Message-ID: <39B76FC1.45357E21@ubiquity.net>
Date: Thu, 07 Sep 2000 11:36:50 +0100
From: James Undery <jundery@ubiquity.net>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Jiri Kuthan <kuthan@fokus.gmd.de>,
        Henning Schulzrinne <schulzrinne@cs.columbia.edu>,
        iptel@lists.bell-labs.com
Subject: Re: [IPTEL] supporting CPL versions
References: <39A4F1A6.87F7A386@indigosw.com> <39A4F5B4.BD3E3EE2@ubiquity.net> <39A5275C.3AADBE1F@dynamicsoft.com> <39A535F1.48928278@ubiquity.net> <39A5FC2D.F49020AB@dynamicsoft.com> <39A6379C.DCC21EA3@ubiquity.net> <39AF5AC2.1016B520@dynamicsoft.com> <39AFAB1E.D73D303D@cs.columbia.edu> <39B1E044.BF12899D@dynamicsoft.com> <39B24D1B.2D64DA2A@cs.columbia.edu> <39B3296F.1D28EC17@dynamicsoft.com> <39B55BBF.1AB822B1@fokus.gmd.de> <39B56E21.273F1F30@dynamicsoft.com> <39B5F66E.A85BF4F2@ubiquity.net> <39B72C08.9CA9B403@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Jonathan Rosenberg wrote:

> James Undery wrote:
> >
> > Writting a parser for CPL is a trival problem and most of the checks suggested
> > and required by the draft mean a fair quantity of checking needs to be done
> > manually. The real complexity in an XML parser is checking conformity to a
> > schema, yet with CPL its the semantics of the script that are important not
> > the syntax of the schema. You can check the script conforms to a schema but
> > that doesn't mean you can do anything with it or that the script really makes
> > sense.
>
> Its not just me not wanting to do the work; there are lots of xml tools
> getting written and being distributed, many of which are strongly based
> on usage of the DTD. For example, XML SPy is a nice tool for editing
> XML. If you have a DTD, it does "tab style" completions of tag names and
> attributes as you type in the document. Very nice for quickly building
> valid CPL scripts. I'd like to be able to usefully use such tools with
> CPL.

If we are going to continue with DTDs (and XML schemas) I'd have a look at this
chapter from "Learning XML" which seems to suggest grim choices when it comes to
conditionals in XML.

Section 5.2.4.4
http://world.std.com/~eray/book/ch05_02.htm

Any I agree whole heartedly writting CPL in emacs using the compeletions is a
pleasure compared to handcoding a script, my testscripts are generated
programatically ready for a nice GUI where drag and drop creation of the scripts
means users will never need to see the syntax of their scripts. Having looked at the
source of loads of webpages, it's obvious few people handcode, the closest they may
get is fine tuning pre-generated scripts. The point I am trying to make is by
limiting ourselves to the strict bounds of XML we are making life difficult for
future expansion. I am not suggesting ditching the current syntax just defining it
using a different method, so we don't require preprocessors or SGML hacks to provide
extensibility.

James Undery



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep 11 07:44:15 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA29525
	for <iptel-archive@odin.ietf.org>; Mon, 11 Sep 2000 07:44:15 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id B5D3844359; Mon, 11 Sep 2000 06:42:45 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from beluga.telepar.com.br (unknown [200.203.207.190])
	by lists.bell-labs.com (Postfix) with ESMTP id 9267544356
	for <iptel@lists.bell-labs.com>; Mon, 11 Sep 2000 06:42:41 -0400 (EDT)
Received: by BELUGA with Internet Mail Service (5.5.2650.21)
	id <RF1QYS3L>; Mon, 11 Sep 2000 08:45:49 -0300
Message-ID: <3D98391A7EA2D31192E5000629385A9601F1DACC@correio.telepar.com.br>
From: Luiz Alberto Pasini Melek <pasini@telepar.com.br>
To: iptel@lists.bell-labs.com
Date: Mon, 11 Sep 2000 08:45:34 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [IPTEL] unsubscribe lapm pasini@telepar.com.br
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

unsubscribe lapm pasini@telepar.com.br


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep 11 22:03:11 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA11660
	for <iptel-archive@odin.ietf.org>; Mon, 11 Sep 2000 22:03:11 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 9F5FD4436F; Mon, 11 Sep 2000 21:02:49 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ldap2.ptt.js.cn (unknown [202.102.24.41])
	by lists.bell-labs.com (Postfix) with ESMTP id D9EF244358
	for <IPTEL@lists.bell-labs.com>; Mon, 11 Sep 2000 21:02:45 -0400 (EDT)
Received: from zsdpre ([202.111.12.84]) by ldap2.ptt.js.cn
          (Netscape Messaging Server 4.05) with SMTP id G0R4MB00.47F for
          <IPTEL@lists.bell-labs.com>; Tue, 12 Sep 2000 10:08:35 +0800 
Message-ID: <002701c01c5d$fbce2020$2d00a8c0@zsdpre>
From: "Yongning Wang" <casper@public1.ptt.js.cn>
To: <IPTEL@lists.bell-labs.com>
Date: Tue, 12 Sep 2000 10:04:33 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0015_01C01CA0.D99F1340"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [IPTEL] [IPTEL]unsubscribe lapm pasini@telepar.com.br
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01C01CA0.D99F1340
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

dW5zdWJzY3JpYmUgbGFwbSBwYXNpbmlAdGVsZXBhci5jb20uYnINCg==

------=_NextPart_000_0015_01C01CA0.D99F1340
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yOTE5LjYzMDciIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNjMGMwYzA+DQo8RElWPjxGT05UIHNpemU9Mj51bnN1YnNjcmliZSBsYXBt
IDxBIA0KaHJlZj0ibWFpbHRvOnBhc2luaUB0ZWxlcGFyLmNvbS5iciI+cGFzaW5pQHRlbGVwYXIu
Y29tLmJyPC9BPjwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0015_01C01CA0.D99F1340--



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 14 21:00:51 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28127
	for <iptel-archive@odin.ietf.org>; Thu, 14 Sep 2000 21:00:50 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 234A24435B; Thu, 14 Sep 2000 20:00:49 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 1114D4433F
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 20:00:46 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id VAA19979
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 21:00:42 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id VAA49193;
	Thu, 14 Sep 2000 21:00:42 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="Fx01ttTi8z"
Content-Transfer-Encoding: 7bit
Message-ID: <14785.29881.783760.422820@conrail.cs.columbia.edu>
Date: Thu, 14 Sep 2000 21:00:41 -0400 (EDT)
To: iptel@lists.bell-labs.com
X-Mailer: VM 6.75 under Emacs 19.34.1
Subject: [IPTEL] Proposed CPL extension mechanism
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com


--Fx01ttTi8z
Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
Content-Transfer-Encoding: 7bit

Here's my proposal for how to handle CPL extensions.  What do people think?

-- 
Jonathan Lennox
lennox@cs.columbia.edu


--Fx01ttTi8z
Content-Type: text/plain
Content-Disposition: inline;
	filename="ext.txt"
Content-Transfer-Encoding: 7bit

N CPL Extensions

   Servers MAY support additional CPL features beyond those listed in
   this document. Some of the extensions which have been suggested are a
   more powerful time-switch mechanism, compatible with the recurrence
   rules of the iCal Core Object Specification [1]; a means of querying
   how a call has been authenticated; richer control over H.323
   addressing; and end-system or administrator-specific features.

   CPL extensions are indicated by XML namespaces [2]. Every extension
   MUST have an appropriate XML namespace assigned to it. All XML tags
   and attributes MUST be appropriately qualified so as to place them
   within that namespace.

   Tags or attributes in a CPL script which are in the global namespace
   (i.e., not associated with any namespace) are equivalent to tags and
   attributes in the CPL namespace "http://www.ietf.org/internet-
   drafts/draft-ietf-iptel-cpl-03.txt".

   A CPL server MUST reject any script which contains a reference to a
   namespace which it does not understand. It MUST reject any script
   which contains an extension tag or attribute which is not qualified
   to be in an appropriate namespace.

   A CPL script SHOULD NOT specify any namespaces it does not use. For
   compatibility with non-namespace-aware parsers, a CPL script SHOULD
   NOT specify the base CPL namespace for a script which does not use
   any extensions.


        A syntax such as

        <extension-switch>
          <extension is="http://www.example.com/foo">
             [extended things]
          </extension>
          <otherwise>
             [non-extended things]
          </otherwise>
        </extension-switch>

        was suggested as an alternate way of handling extensions.
        This would allow scripts to be uploaded to a server without
        requiring a script author to somehow determine which
        extensions a server supports. However, experience
        developing other languages, notably Sieve [3], was that
        this added excessive complexity to languages. The
        extension-switch tag could, of course, itself be defined in
        a CPL extension.


        It is unfortunately true that XML DTDs, such as the CPL DTD
        given in appendix A, are not powerful enough to encompass
        namespaces, since the base XML specification (which defines
        DTDs) predates the XML namespace specification. XML schemas
        [4] are a work in progress to define a namespace-aware
        method for validating XML documents, as well as improving
        upon DTDs' expressive power in many other ways.

N.1 Examples of Extensions

   The example in figure 1 shows a hypothetical extension which
   implements distinctive ringing. The XML namespace
   "http://www.example.com/distinctive-ring" specifies a new node named
   ring.


   <?xml version="1.0" ?>
   <!DOCTYPE cpl PUBLIC "-//IETF//DTD RFCxxxx CPL 1.0//EN" "cpl.dtd">

   <cpl xmlns="http://www.ietf.org/internet-drafts/draft-ietf-iptel-cpl-03.txt"
        xmlns:dr="http://www.example.com/distinctive-ring">
     <incoming>
       <address-switch field="origin">
         <address is="sip:boss@example.com">
            <dr:ring ringstyle="warble" />
         </address>
       </address-switch>
     </incoming>
   </cpl>


   Figure 1: Example Script: Hypothetical Distinctive-Ringing Extension



   The example in figure 2 implements a hypothetical new attribute for
   address switches, to allow regular-expression matches. It defines a
   new attribute regex for the standard address node.


   <?xml version="1.0" ?>
   <!DOCTYPE cpl PUBLIC "-//IETF//DTD RFCxxxx CPL 1.0//EN" "cpl.dtd">

   <cpl>
     <incoming>
       <address-switch field="origin" subfield="user"
           xmlns:re="http://www.example.com/regex">
         <address re:regex="(.*.smith|.*.jones)">
            <reject status="reject"
                    reason="I don't want to talk to Smiths or Joneses" />
         </address>
       </address-switch>
     </incoming>
   </cpl>


   Figure 2: Example Script: Hypothetical Regular-Expression Extension



Bibliography

   [1] F. Dawson and D. Stenerson, "Internet calendaring and scheduling
   core object specification (icalendar)," Request for Comments 2445,
   Internet Engineering Task Force, Nov. 1998.

   [2] T. Bray, D. Hollander, and A. Layman, "Namespaces in XML," W3C
   Recommendation REC-xml-names-19900114, World Wide Web Consortium
   (W3C), Jan. 1999.  Available at http://www.w3.org/TR/REC-xml-names/.

   [3] T. Showalter, "Sieve: A mail filtering language," Internet Draft,
   Internet Engineering Task Force, May 2000.  Work in progress.

   [4] D. C. Fallside, "XML schema part 0: Primer," Working Draft WD-
   xmlschema-0-20000225, World Wide Web Consortium (W3C), Feb. 2000.
   Available at http://www.w3.org/TR/xmlschema-0/.





















Lennox/Schulzrinne                                            [Page 3]


--Fx01ttTi8z--


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 14 21:07:16 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28182
	for <iptel-archive@odin.ietf.org>; Thu, 14 Sep 2000 21:07:16 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 4129744383; Thu, 14 Sep 2000 20:05:59 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id D02CC44370
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 20:05:56 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id VAA20175
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 21:05:51 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id VAA49200;
	Thu, 14 Sep 2000 21:05:50 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14785.30190.532948.355351@conrail.cs.columbia.edu>
Date: Thu, 14 Sep 2000 21:05:50 -0400 (EDT)
To: iptel@lists.bell-labs.com
X-Mailer: VM 6.75 under Emacs 19.34.1
Subject: [IPTEL] Proposed resolution of CPL time-switch issue
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

There was enough dismay over the whole iCal time-switch issue that I've
(semi-reluctantly) agreed that it's too complicated for the base CPL spec.

Accordingly, my propsal is this.  Roll back the syntax of time-switch to the
version in the CPL draft -01 (the crontab-based syntax).  Simultaneously,
though, define a CPL extension which provides an ical-time-switch tag, which
would include the whole of the iCal recurrence spec as it appeared in CPL
draft -02.

Would this generally satisfy everyone?

(You may note that my text describing CPL extensions assumed this solution
in its list of suggested extensions.)

-- 
Jonathan Lennox
lennox@cs.columbia.edu


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 14 22:17:14 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA29842
	for <iptel-archive@odin.ietf.org>; Thu, 14 Sep 2000 22:17:14 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id BC55844370; Thu, 14 Sep 2000 21:17:13 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 8D27C4433F
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 21:17:10 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id WAA22966;
	Thu, 14 Sep 2000 22:17:07 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id WAA52109;
	Thu, 14 Sep 2000 22:17:07 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14785.34466.943108.349764@conrail.cs.columbia.edu>
Date: Thu, 14 Sep 2000 22:17:06 -0400 (EDT)
To: Henning Schulzrinne <schulzrinne@opus.cs.columbia.edu>
Cc: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
In-Reply-To: <39C176C0.3ED75E03@cs.columbia.edu>
References: <14785.30190.532948.355351@conrail.cs.columbia.edu>
	<39C176C0.3ED75E03@cs.columbia.edu>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

On Thursday, September 14 2000, "Henning Schulzrinne" wrote to "Jonathan Lennox, iptel@lists.bell-labs.com" saying:

> Jonathan Lennox wrote:
> > 
> > There was enough dismay over the whole iCal time-switch issue that I've
> > (semi-reluctantly) agreed that it's too complicated for the base CPL spec.
> 
> I disagree strongly. I thought we had agreed that a simplified version
> of the ical syntax, minus some of the by-rules, would be an easier road
> to upgrade later, rather than having two completely different
> specification rules.

One consideration that I think is very important, which held true for the
crontab-based proposal but which (as far as I can tell) doesn't hold true
for iCal, is that it should be possible to write (easily) an O(1) algorithm
that determines whether a given instant in time falls within a given time
range -- i.e., without having to iterate through all the time positions
prior to the current one.

I'm trying to work out what such an O(1) subset of iCal would be.  It's
clear that the "count" rule has to be eliminated, and "bysetpos".  Probably,
expanding by* rules would have to go as well, though I *think* contracting
ones can stay.  "interval" is tricky, but possibly doable; I'm not sure.

I could make the argument, though, that we would actually have an *easier*
time with future upgrades if our two time syntaxes were completely
different, rather than largely the same but with important and subtle
semantic differences.  Given that (it seems) the implementation of
iCal-subset and iCal-complete have to be quite different, and the inevitable
confusion of "okay, '<time freq="daily" byhour="5">' is illegal, but '<time
freq="daily" ical:byhour="5">' is fine"...well, it feels like an
interoperability and documentation nightmare.

Additionally, as JR pointed out earlier in the time-switch discussion, it's
not possible to express "first monday of the month" or using only
contracting rules; that needs an expanding rule.  By contrast, it's trivial
using the crontab syntax.

That said, if consensus is for a subset, we can subset, once we're
algorithmically sure of what that subset should be.

-- 
Jonathan Lennox
lennox@cs.columbia.edu


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 15 00:07:08 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA01878
	for <iptel-archive@odin.ietf.org>; Fri, 15 Sep 2000 00:07:08 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 02E824433F; Thu, 14 Sep 2000 23:06:57 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 2C99644370
	for <iptel@lists.bell-labs.com>; Thu, 14 Sep 2000 20:09:23 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id VAA20296;
	Thu, 14 Sep 2000 21:09:20 -0400 (EDT)
Message-ID: <39C176C0.3ED75E03@cs.columbia.edu>
Date: Thu, 14 Sep 2000 21:09:20 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Lennox <lennox@ober.cs.columbia.edu>
Cc: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
References: <14785.30190.532948.355351@conrail.cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

Jonathan Lennox wrote:
> 
> There was enough dismay over the whole iCal time-switch issue that I've
> (semi-reluctantly) agreed that it's too complicated for the base CPL spec.

I disagree strongly. I thought we had agreed that a simplified version
of the ical syntax, minus some of the by-rules, would be an easier road
to upgrade later, rather than having two completely different
specification rules.

> 
> Accordingly, my propsal is this.  Roll back the syntax of time-switch to the
> version in the CPL draft -01 (the crontab-based syntax).  Simultaneously,
> though, define a CPL extension which provides an ical-time-switch tag, which
> would include the whole of the iCal recurrence spec as it appeared in CPL
> draft -02.
> 
> Would this generally satisfy everyone?
> 
> (You may note that my text describing CPL extensions assumed this solution
> in its list of suggested extensions.)
> 
> --
> Jonathan Lennox
> lennox@cs.columbia.edu
> 
> _______________________________________________
> IPTEL mailing list
> IPTEL@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/iptel

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 15 01:40:31 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07337
	for <iptel-archive@odin.ietf.org>; Fri, 15 Sep 2000 01:40:31 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 554994433D; Fri, 15 Sep 2000 00:40:28 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 26E1844339
	for <iptel@lists.bell-labs.com>; Fri, 15 Sep 2000 00:40:25 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA05639;
	Fri, 15 Sep 2000 01:40:02 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <SY593BL6>; Fri, 15 Sep 2000 01:35:08 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF21FE42@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>
Subject: RE: [IPTEL] Proposed CPL extension mechanism
Date: Fri, 15 Sep 2000 01:34:56 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

This looks fine. I'll buy your arguments on the conditional execution stuff
based on support for extensions; I think KISS is very important and it
clearly simplifies things not to try to do that.

As for the actual extension mechanism, this looks fine. I am still annoyed
about the incompatibility of namespaces and DTDs, but thats a much bigger
problem for someone else to solve. Clearly namespaces are the right way to
handle extensions.

-Jonathan R.

---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com

> -----Original Message-----
> From: Jonathan Lennox [mailto:lennox@cs.columbia.edu]
> Sent: Thursday, September 14, 2000 9:01 PM
> To: iptel@lists.bell-labs.com
> Subject: [IPTEL] Proposed CPL extension mechanism
> 
> 
> Here's my proposal for how to handle CPL extensions.  What do 
> people think?
> 
> -- 
> Jonathan Lennox
> lennox@cs.columbia.edu
> 
> 


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 15 01:48:34 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08503
	for <iptel-archive@odin.ietf.org>; Fri, 15 Sep 2000 01:48:33 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 71FCA44380; Fri, 15 Sep 2000 00:47:26 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 3042F4437A
	for <iptel@lists.bell-labs.com>; Fri, 15 Sep 2000 00:47:23 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA05651;
	Fri, 15 Sep 2000 01:49:02 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <SY593BL9>; Fri, 15 Sep 2000 01:44:08 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF21FE43@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
        "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>
Cc: "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>
Subject: RE: [IPTEL] Proposed resolution of CPL time-switch issue
Date: Fri, 15 Sep 2000 01:44:01 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com




> -----Original Message-----
> From: Jonathan Lennox [mailto:lennox@cs.columbia.edu]
> Sent: Thursday, September 14, 2000 10:17 PM
> To: Henning Schulzrinne
> Cc: iptel@lists.bell-labs.com
> Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
> 
> 
> On Thursday, September 14 2000, "Henning Schulzrinne" wrote 
> to "Jonathan Lennox, iptel@lists.bell-labs.com" saying:
> 
> > Jonathan Lennox wrote:
> > > 
> > > There was enough dismay over the whole iCal time-switch 
> issue that I've
> > > (semi-reluctantly) agreed that it's too complicated for 
> the base CPL spec.
> > 
> > I disagree strongly. I thought we had agreed that a 
> simplified version
> > of the ical syntax, minus some of the by-rules, would be an 
> easier road
> > to upgrade later, rather than having two completely different
> > specification rules.
> 
> One consideration that I think is very important, which held 
> true for the
> crontab-based proposal but which (as far as I can tell) 
> doesn't hold true
> for iCal, is that it should be possible to write (easily) an 
> O(1) algorithm
> that determines whether a given instant in time falls within 
> a given time
> range -- i.e., without having to iterate through all the time 
> positions
> prior to the current one.
> 
> I'm trying to work out what such an O(1) subset of iCal would 
> be.  It's
> clear that the "count" rule has to be eliminated, and 
> "bysetpos".  Probably,
> expanding by* rules would have to go as well, though I 
> *think* contracting
> ones can stay.  "interval" is tricky, but possibly doable; 
> I'm not sure.
> 
> I could make the argument, though, that we would actually 
> have an *easier*
> time with future upgrades if our two time syntaxes were completely
> different, rather than largely the same but with important and subtle
> semantic differences.  Given that (it seems) the implementation of
> iCal-subset and iCal-complete have to be quite different, and 
> the inevitable
> confusion of "okay, '<time freq="daily" byhour="5">' is 
> illegal, but '<time
> freq="daily" ical:byhour="5">' is fine"...well, it feels like an
> interoperability and documentation nightmare.
> 
> Additionally, as JR pointed out earlier in the time-switch 
> discussion, it's
> not possible to express "first monday of the month" or using only
> contracting rules; that needs an expanding rule.  By 
> contrast, it's trivial
> using the crontab syntax.
> 
> That said, if consensus is for a subset, we can subset, once we're
> algorithmically sure of what that subset should be.

We seem to keep rolling around in circles here. This is due, in part, to the
fact that only a few folks have expressed any opinion here (myself, Henning,
Jonathan L., and James U.), and of those, a few of us have waffled quite a
lot, including myself.

We need to make a decision already, and go with it. So, I will employ the
tools at hand for a working group chair - rough consensus and running code.
As for the first, James last spoke in favor of the crontab syntax, I
personally would prefer it, Jonathan seems on the fence, and Henning is
opposed. Rough consensus is for crontab. As for running code, I know of
numerous implementations of the crontab approach and none for iCal. 

SO, given rough consensus and running code speak in favor of the old syntax,
AND using the old syntax will help with compatibility with older CPL
implementations that did the crontab stuff, AND we can add in iCal stuff
later through extensions, AND the crontab stuff is similar to existing time
mechanisms and not something totally new, it seems reasonable to go that
path.

So, I am waving the wg chair wand and declaring this issue resolved. I will
only reconsider if someone (1) says I have misrepresented their opinion,
thus changing rough consensus, or (2) someone can demonstrate running code
for the iCal stuff, and argue that its really a piece of cake after all. 

-Jonathan R.
---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 15 10:08:48 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19837
	for <iptel-archive@odin.ietf.org>; Fri, 15 Sep 2000 10:08:47 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id D24A64433F; Fri, 15 Sep 2000 09:07:57 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 8518A44338
	for <iptel@lists.bell-labs.com>; Fri, 15 Sep 2000 09:07:54 -0400 (EDT)
Received: from ind.cs.columbia.edu (ind.cs.columbia.edu [128.59.19.27])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id KAA24774;
	Fri, 15 Sep 2000 10:07:51 -0400 (EDT)
Received: (from lennox@localhost)
	by ind.cs.columbia.edu (8.9.3/8.9.3) id KAA00056;
	Fri, 15 Sep 2000 10:07:51 -0400 (EDT)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14786.11574.530591.297835@ind.cs.columbia.edu>
Date: Fri, 15 Sep 2000 10:07:50 -0400 (EDT)
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>
Subject: RE: [IPTEL] Proposed resolution of CPL time-switch issue
In-Reply-To: <B65B4F8437968F488A01A940B21982BF21FE43@DYN-EXCH-001.dynamicsoft.com>
References: <B65B4F8437968F488A01A940B21982BF21FE43@DYN-EXCH-001.dynamicsoft.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

On Friday, September 15 2000, "Jonathan Rosenberg" wrote to "'Jonathan Lennox', 'Henning Schulzrinne', 'iptel@lists.bell-labs.com'" saying:

> So, I am waving the wg chair wand and declaring this issue resolved. I will
> only reconsider if someone (1) says I have misrepresented their opinion,
> thus changing rough consensus, or (2) someone can demonstrate running code
> for the iCal stuff, and argue that its really a piece of cake after all. 

Round and round and round we go...I was thinking about this problem last
night after my last mail to the list, and I think I've come up with a useful
iCal subset, and a relatively simple O(1) algorithm for deciding time
switches.

Here are the restrictions I've imposed on iCal:

A. The "secondly", "minutely", and "hourly" recurrences, and the "bysecond",
        "byminute", and "byhour" rules, are eliminated.
B. The "count" and "bysetpos" rules are eliminated.
C. "Expanding" by* rules are eliminated.  Only the following by* rules are
        allowed:
    freq=daily:   byday, bymonthday, byyearday, byweekno, bymonth
    freq=weekly:  byweekno, bymonth
    freq=monthly: bymonth
    freq=yearly:  none
D. The duration of the event ("duration" or "dtend - dtstart") must be
        strictly less than the unit of "freq" times "interval".

Here is the algorithm:
1.  Compute the time of the call, in the timezone of the time switch.
    (No step after this needs to consider time zones -- all calculations
    are done using continuously-running standard Gregorian time.)

2.  If the call time is earlier than dtstart, fail NOMATCH.

3.  Determine the number of occurences of the recurrence frequency (the
    number of days, weeks, months, or years) that have passed between
    dtstart and the call time.  Call this fraction 'Repeats'.

4.  Round Repeats down to the nearest whole-number multiple of "interval".
    Call this rounded value 'WholeRepeats'.

5.  Determine the instant that is WholeRepeats occurences of the recurrence
    frequency from dtstart.  This instant is the 'Candidate Instant'.  If
    the current time falls within a recurrence interval, the Candidate
    Instant must be the starting point of this interval.

6.  If the Candidate Instant is later than the 'until' parameter of the
    recurrence, fail NOMATCH.

7.  If the time between the Candidate Instant and the current time is
    greater than the duration, fail NOMATCH.

8.  For each by* rule which is present in the recurrence and which is
    legal for the frequency, confirm that the Candidate Instant matches to
    the rule.  If any doesn't match, fail NOMATCH.

9.  Succeed MATCH.


Some notes on this algorithm:

The justifications for each of the eliminations above are as follows.

A.  When sub-day-resolution rules are present, issues of daylight-savings
        transitions come into play.  The number of, e.g., "nine hour"
        intervals since a given time isn't easily computable from a
        broken-down local time if a DST transition has occured in between.
        Since sub-day-resolution rules don't seem especially useful for
        recurring events anyway, we can avoid consideration of these
        issues by eliminating them.

B.  Barring very clever (and complex) algorithms that escape me, "count" and
        "bysetpos" rules both require that a set of recurrences be fully
        enumerated for them to be correctly resolved.

C.  Expanding rules add to the set of start times for a recurrence, making it
        impossible to find a unique candidate instant in O(1) time.

D.  Durations longer than a frequency will result in multiple candidate
        instants being possible for a given call time.


The correctness of this algorithm depends on the fact that a) the candidate
instant is unique, and b) we have computed it correctly.  Given these two
facts, the correctness of the rest of the algorithm should be obvious.
I'm reasonably convinced both these facts hold, but more eyeballs are always
good.


It is worth noting that (I believe) the crontab-style entries can be exactly
represented by a freq="daily" recurrence, except that multiple time-of-day
intervals cannot be given in a single rule.  (They can be expressed with
multiple time-switch rules connected by subs, of course.)


I was wrong, incidentally, about the "first monday of the month" rule
requiring expansion rules.  The following rule, which conforms to the
restrictions above, describes it:

<time dtstart="20000904T090000" duration="8H"
      recur="daily" byday="MO" bymonthday="1,2,3,4,5,6,7">

This is slightly clumsier than recur="monthly" byday="1MO", but it's a lot
easier to calculate.


Given the algorithm above, surprising things can happen during a
daylight-savings-time transition.  For instance, given a daily rule which
starts at 2:30 a.m. and lasts for an hour, in US-Eastern on the "fall back"
day a call at 2:45 daylight time will fall under the rule; a call half an
hour later at 2:15 standard time will not; and a call half an hour after
that at 2:45 standard time will.  For the common case of rules that don't
care about early-morning events, though, this model behaves as expected.
(I.e., a rule that starts at 5 pm and has a 16-hour duration will last until
9 am, even on days when there is a DST transition.)


I know this isn't *running* code, but this algorithm should be implementable
without too much work.

Given this, how do people think we should proceed?

-- 
Jonathan Lennox
lennox@cs.columbia.edu


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 15 11:43:06 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA21337
	for <iptel-archive@odin.ietf.org>; Fri, 15 Sep 2000 11:43:06 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 7EBCF4435D; Fri, 15 Sep 2000 10:42:37 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 7947D4433A
	for <iptel@lists.bell-labs.com>; Fri, 15 Sep 2000 10:42:34 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id LAA09066
	for <iptel@lists.bell-labs.com>; Fri, 15 Sep 2000 11:44:28 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <SY593B7H>; Fri, 15 Sep 2000 11:39:32 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF21FE8B@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>
Date: Fri, 15 Sep 2000 11:39:23 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [IPTEL] Slides now available
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

Folks,

My apologies for the delay in getting slides available from the meeting. You
can now download them, along with the minutes, from the iptel home page at:

http://www.bell-labs.com/mailing-lists/iptel/

Thanks,
Jonathan R.

---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep 18 03:43:02 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA29462
	for <iptel-archive@odin.ietf.org>; Mon, 18 Sep 2000 03:43:02 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 2C39D443B2; Mon, 18 Sep 2000 02:40:28 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id E39FA4433B
	for <iptel@lists.bell-labs.com>; Mon, 18 Sep 2000 02:40:25 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id DAA01866;
	Mon, 18 Sep 2000 03:42:19 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <SY593D14>; Mon, 18 Sep 2000 03:37:19 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF21FEF8@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>
Subject: RE: [IPTEL] Proposed resolution of CPL time-switch issue
Date: Mon, 18 Sep 2000 03:37:19 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com

The question is - have we bought ourselves anything?

This won't be compatible with iCal, so you won't be able to drag and drop
your calendar appointments into CPL generators. I suspect its less complete
than the crontab definition, in that there is less you can describe with it.
Its definitely more difficult to use. We have probably made interop with
iCal harder, since if we do the full blown version later, its not clear from
the tag (its still called time-switch) whether it will work on a given
server. 

So, I'm taking a stand here and sticking by my proposal - back to the
crontab definition. If folks want, we can define the ical-switch tag as an
extension right away (and in this case, do the full version). 

Do we still have consensus on that?

-Jonathan R.

---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com

> -----Original Message-----
> From: Jonathan Lennox [mailto:lennox@cs.columbia.edu]
> Sent: Friday, September 15, 2000 10:08 AM
> To: Jonathan Rosenberg
> Cc: 'Henning Schulzrinne'; 'iptel@lists.bell-labs.com'
> Subject: RE: [IPTEL] Proposed resolution of CPL time-switch issue
> 
> 
> On Friday, September 15 2000, "Jonathan Rosenberg" wrote to 
> "'Jonathan Lennox', 'Henning Schulzrinne', 
> 'iptel@lists.bell-labs.com'" saying:
> 
> > So, I am waving the wg chair wand and declaring this issue 
> resolved. I will
> > only reconsider if someone (1) says I have misrepresented 
> their opinion,
> > thus changing rough consensus, or (2) someone can 
> demonstrate running code
> > for the iCal stuff, and argue that its really a piece of 
> cake after all. 
> 
> Round and round and round we go...I was thinking about this 
> problem last
> night after my last mail to the list, and I think I've come 
> up with a useful
> iCal subset, and a relatively simple O(1) algorithm for deciding time
> switches.
> 
> Here are the restrictions I've imposed on iCal:
> 
> A. The "secondly", "minutely", and "hourly" recurrences, and 
> the "bysecond",
>         "byminute", and "byhour" rules, are eliminated.
> B. The "count" and "bysetpos" rules are eliminated.
> C. "Expanding" by* rules are eliminated.  Only the following 
> by* rules are
>         allowed:
>     freq=daily:   byday, bymonthday, byyearday, byweekno, bymonth
>     freq=weekly:  byweekno, bymonth
>     freq=monthly: bymonth
>     freq=yearly:  none
> D. The duration of the event ("duration" or "dtend - dtstart") must be
>         strictly less than the unit of "freq" times "interval".
> 
> Here is the algorithm:
> 1.  Compute the time of the call, in the timezone of the time switch.
>     (No step after this needs to consider time zones -- all 
> calculations
>     are done using continuously-running standard Gregorian time.)
> 
> 2.  If the call time is earlier than dtstart, fail NOMATCH.
> 
> 3.  Determine the number of occurences of the recurrence 
> frequency (the
>     number of days, weeks, months, or years) that have passed between
>     dtstart and the call time.  Call this fraction 'Repeats'.
> 
> 4.  Round Repeats down to the nearest whole-number multiple 
> of "interval".
>     Call this rounded value 'WholeRepeats'.
> 
> 5.  Determine the instant that is WholeRepeats occurences of 
> the recurrence
>     frequency from dtstart.  This instant is the 'Candidate 
> Instant'.  If
>     the current time falls within a recurrence interval, the Candidate
>     Instant must be the starting point of this interval.
> 
> 6.  If the Candidate Instant is later than the 'until' 
> parameter of the
>     recurrence, fail NOMATCH.
> 
> 7.  If the time between the Candidate Instant and the current time is
>     greater than the duration, fail NOMATCH.
> 
> 8.  For each by* rule which is present in the recurrence and which is
>     legal for the frequency, confirm that the Candidate 
> Instant matches to
>     the rule.  If any doesn't match, fail NOMATCH.
> 
> 9.  Succeed MATCH.
> 
> 
> Some notes on this algorithm:
> 
> The justifications for each of the eliminations above are as follows.
> 
> A.  When sub-day-resolution rules are present, issues of 
> daylight-savings
>         transitions come into play.  The number of, e.g., "nine hour"
>         intervals since a given time isn't easily computable from a
>         broken-down local time if a DST transition has 
> occured in between.
>         Since sub-day-resolution rules don't seem especially 
> useful for
>         recurring events anyway, we can avoid consideration of these
>         issues by eliminating them.
> 
> B.  Barring very clever (and complex) algorithms that escape 
> me, "count" and
>         "bysetpos" rules both require that a set of 
> recurrences be fully
>         enumerated for them to be correctly resolved.
> 
> C.  Expanding rules add to the set of start times for a 
> recurrence, making it
>         impossible to find a unique candidate instant in O(1) time.
> 
> D.  Durations longer than a frequency will result in multiple 
> candidate
>         instants being possible for a given call time.
> 
> 
> The correctness of this algorithm depends on the fact that a) 
> the candidate
> instant is unique, and b) we have computed it correctly.  
> Given these two
> facts, the correctness of the rest of the algorithm should be obvious.
> I'm reasonably convinced both these facts hold, but more 
> eyeballs are always
> good.
> 
> 
> It is worth noting that (I believe) the crontab-style entries 
> can be exactly
> represented by a freq="daily" recurrence, except that 
> multiple time-of-day
> intervals cannot be given in a single rule.  (They can be 
> expressed with
> multiple time-switch rules connected by subs, of course.)
> 
> 
> I was wrong, incidentally, about the "first monday of the month" rule
> requiring expansion rules.  The following rule, which conforms to the
> restrictions above, describes it:
> 
> <time dtstart="20000904T090000" duration="8H"
>       recur="daily" byday="MO" bymonthday="1,2,3,4,5,6,7">
> 
> This is slightly clumsier than recur="monthly" byday="1MO", 
> but it's a lot
> easier to calculate.
> 
> 
> Given the algorithm above, surprising things can happen during a
> daylight-savings-time transition.  For instance, given a 
> daily rule which
> starts at 2:30 a.m. and lasts for an hour, in US-Eastern on 
> the "fall back"
> day a call at 2:45 daylight time will fall under the rule; a 
> call half an
> hour later at 2:15 standard time will not; and a call half an 
> hour after
> that at 2:45 standard time will.  For the common case of 
> rules that don't
> care about early-morning events, though, this model behaves 
> as expected.
> (I.e., a rule that starts at 5 pm and has a 16-hour duration 
> will last until
> 9 am, even on days when there is a DST transition.)
> 
> 
> I know this isn't *running* code, but this algorithm should 
> be implementable
> without too much work.
> 
> Given this, how do people think we should proceed?
> 
> -- 
> Jonathan Lennox
> lennox@cs.columbia.edu
> 


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 21 11:24:45 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07719
	for <iptel-archive@odin.ietf.org>; Thu, 21 Sep 2000 11:24:44 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 9A72144380; Thu, 21 Sep 2000 10:24:35 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from ix.netcorps.com (ix.netcorps.com [207.1.125.106])
	by lists.bell-labs.com (Postfix) with ESMTP id 6CC774437A
	for <iptel@lists.bell-labs.com>; Thu, 21 Sep 2000 10:24:32 -0400 (EDT)
Received: from indigosw.com (adsl-1561.turboline.skynet.be [194.78.202.25])
	by ix.netcorps.com (8.9.0/8.9.0) with ESMTP id IAA26102;
	Thu, 21 Sep 2000 08:23:03 -0700 (PDT)
Message-ID: <39C97EB4.16737570@indigosw.com>
Date: Thu, 21 Sep 2000 05:21:24 +0200
From: Emmanuel Bertrand <eb@indigosw.com>
Organization: Indigo Software
X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
        "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>,
        David Bertrand <david@indigosw.com>,
        dENIS Vandersteene <dENIS@indigosw.com>
Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
References: <B65B4F8437968F488A01A940B21982BF21FEF8@DYN-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit



Jonathan Rosenberg wrote:

> The question is - have we bought ourselves anything?
>
> This won't be compatible with iCal, so you won't be able to drag and drop
> your calendar appointments into CPL generators. I suspect its less complete
> than the crontab definition, in that there is less you can describe with it.
> Its definitely more difficult to use. We have probably made interop with
> iCal harder, since if we do the full blown version later, its not clear from
> the tag (its still called time-switch) whether it will work on a given
> server.
>
> So, I'm taking a stand here and sticking by my proposal - back to the
> crontab definition. If folks want, we can define the ical-switch tag as an
> extension right away (and in this case, do the full version).
>
> Do we still have consensus on that?
>
> -Jonathan R.

Hi,

I hope it's not too late to post on this thread.

Here at Indigo we have implemented both crontab and iCal.  Beside finding iCal
more powerful and flexible than crontab, we also found it easier to have it
turned into a GUI and to retrieve calendar information from popular
applications.

In our iCal implementation, on the server side we have used an algorithm quite
similar to Jonathan's (Lennox) one to avoid computing overhead.   The algorithm
is not designed to particular iCal subsets and works pretty well.

We also think that, as far as complexity is concerned, one can expect that, in
general, CPL editors/generators will not offer the full iCal possibilies on the
client side thus generating various subsets of iCal.  With this in mind, the
best way for a CPL server to be able to handle all these variants of
time-switches may be to provide full support of iCal.

In conclusion, why not keep the reference to iCal as it exists in the
time-switch paragraph of the 02 CPL draft ?

Not too sure that we have rough consensus on this one, but at least there is
already some running code.

Our two cents,

Cheers,


--
Emmanuel Bertrand
mailto:eb@indigosw.com
http://www.indigosw.com




_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 22 09:51:47 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14163
	for <iptel-archive@odin.ietf.org>; Fri, 22 Sep 2000 09:51:45 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id BFB7244380; Fri, 22 Sep 2000 08:49:51 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 36A0344338
	for <iptel@lists.bell-labs.com>; Fri, 22 Sep 2000 08:49:48 -0400 (EDT)
Received: from ind.cs.columbia.edu (ind.cs.columbia.edu [128.59.19.27])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id JAA15670;
	Fri, 22 Sep 2000 09:49:28 -0400 (EDT)
Received: (from lennox@localhost)
	by ind.cs.columbia.edu (8.9.3/8.9.3) id JAA25950;
	Fri, 22 Sep 2000 09:49:23 -0400 (EDT)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14795.25371.570285.518704@ind.cs.columbia.edu>
Date: Fri, 22 Sep 2000 09:48:11 -0400 (EDT)
To: Emmanuel Bertrand <eb@indigosw.com>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>,
        David Bertrand <david@indigosw.com>,
        dENIS Vandersteene <dENIS@indigosw.com>
Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
In-Reply-To: <39C97EB4.16737570@indigosw.com>
References: <B65B4F8437968F488A01A940B21982BF21FEF8@DYN-EXCH-001.dynamicsoft.com>
	<39C97EB4.16737570@indigosw.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-Mailman-Version: 1.1
Precedence: bulk
List-Id:  <iptel.lists.bell-labs.com>
X-BeenThere: iptel@lists.bell-labs.com
Content-Transfer-Encoding: 7bit

On Thursday, September 21 2000, "Emmanuel Bertrand" wrote to "Jonathan Rosenberg, 'Jonathan Lennox', 'Henning Schulzrinne', 'iptel@lists.bell-labs.com', David Bertrand, dENIS Vandersteene" saying:

> Hi,
> 
> I hope it's not too late to post on this thread.
> 
> Here at Indigo we have implemented both crontab and iCal.  Beside finding iCal
> more powerful and flexible than crontab, we also found it easier to have it
> turned into a GUI and to retrieve calendar information from popular
> applications.
> 
> In our iCal implementation, on the server side we have used an algorithm quite
> similar to Jonathan's (Lennox) one to avoid computing overhead.   The algorithm
> is not designed to particular iCal subsets and works pretty well.

When you say "not designed to particular iCal subsets", do you mean that it
supports the entire iCal specification -- including expanding by-rules,
'count', 'bysetpos', and arbitrary-length durations -- in such a way that
you can make the decision in constant-time, without enumerating the set?

If so, could you post at least rough pseudocode for this?  That'll make a
big difference to how we end up resolving this issue.

(My current incination: if we can manage the whole of iCal in constant time,
stick with it and add an appendix describing our algorithm; otherwise, go
with JR's suggestion to revert to crontab, and define ical-switch as an
extension.)

-- 
Jonathan Lennox
lennox@cs.columbia.edu


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Mon Sep 25 12:16:55 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07487
	for <iptel-archive@odin.ietf.org>; Mon, 25 Sep 2000 12:16:55 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id A454144371; Mon, 25 Sep 2000 11:01:12 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51])
	by lists.bell-labs.com (Postfix) with ESMTP id 46F9244348
	for <iptel@lists.bell-labs.com>; Mon, 25 Sep 2000 10:32:57 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50])
	by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id KAA04127;
	Mon, 25 Sep 2000 10:36:58 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <SY593K5G>; Mon, 25 Sep 2000 10:31:44 -0400
Message-ID: <B65B4F8437968F488A01A940B21982BF220236@DYN-EXCH-001.dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
To: "'Jonathan Lennox'" <lennox@cs.columbia.edu>,
        "'Emmanuel Bertrand'" <eb@indigosw.com>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        "'Henning Schulzrinne'" <schulzrinne@opus.cs.columbia.edu>,
        "'iptel@lists.bell-labs.com'" <iptel@lists.bell-labs.com>,
        "'David Bertrand'" <david@indigosw.com>,
        "'dENIS Vandersteene'" <dENIS@indigosw.com>
Subject: RE: [IPTEL] Proposed resolution of CPL time-switch issue
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Mon, 25 Sep 2000 10:31:43 -0400




> -----Original Message-----
> From: Jonathan Lennox [mailto:lennox@cs.columbia.edu]
> Sent: Friday, September 22, 2000 9:48 AM
> To: Emmanuel Bertrand
> Cc: Jonathan Rosenberg; 'Henning Schulzrinne';
> 'iptel@lists.bell-labs.com'; David Bertrand; dENIS Vandersteene
> Subject: Re: [IPTEL] Proposed resolution of CPL time-switch issue
> 
> 
> On Thursday, September 21 2000, "Emmanuel Bertrand" wrote to 
> "Jonathan Rosenberg, 'Jonathan Lennox', 'Henning 
> Schulzrinne', 'iptel@lists.bell-labs.com', David Bertrand, 
> dENIS Vandersteene" saying:
> 
> > Hi,
> > 
> > I hope it's not too late to post on this thread.
> > 
> > Here at Indigo we have implemented both crontab and iCal.  
> Beside finding iCal
> > more powerful and flexible than crontab, we also found it 
> easier to have it
> > turned into a GUI and to retrieve calendar information from popular
> > applications.
> > 
> > In our iCal implementation, on the server side we have used 
> an algorithm quite
> > similar to Jonathan's (Lennox) one to avoid computing 
> overhead.   The algorithm
> > is not designed to particular iCal subsets and works pretty well.
> 
> When you say "not designed to particular iCal subsets", do 
> you mean that it
> supports the entire iCal specification -- including expanding 
> by-rules,
> 'count', 'bysetpos', and arbitrary-length durations -- in 
> such a way that
> you can make the decision in constant-time, without 
> enumerating the set?

That would be something, but I doubt its possible.

> 
> If so, could you post at least rough pseudocode for this?  
> That'll make a
> big difference to how we end up resolving this issue.


> 
> (My current incination: if we can manage the whole of iCal in 
> constant time,
> stick with it and add an appendix describing our algorithm; 
> otherwise, go
> with JR's suggestion to revert to crontab, and define 
> ical-switch as an
> extension.)

Agreed.

Time is running short though. I have committed to finished CPL *before* the
next meeting. This is one of the major issues left to resolve. 

If pseudocode demonstrating the feasibility of doing all of ical in O(1)
cannot be demonstrated on the list by THURSDAY, we will proceed with crontab
and consider this issue closed.

-Jonathan R.
---
Jonathan D. Rosenberg                       72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.cs.columbia.edu/~jdrosen         PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 28 13:12:56 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA26902
	for <iptel-archive@odin.ietf.org>; Thu, 28 Sep 2000 13:12:55 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 8EE26443D7; Thu, 28 Sep 2000 12:02:18 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 384A6443D1
	for <iptel@lists.bell-labs.com>; Thu, 28 Sep 2000 12:01:32 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA28116
	for <iptel@lists.bell-labs.com>; Thu, 28 Sep 2000 13:01:27 -0400 (EDT)
Message-ID: <39D37968.8830644A@cs.columbia.edu>
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: iptel@lists.bell-labs.com
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [IPTEL] CPL time ranges
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Thu, 28 Sep 2000 13:01:28 -0400
Content-Transfer-Encoding: 7bit

To help reaching closure by other than default, let me try to summarize
the options and concerns:

(1) Use crontab

My major concern here goes beyond the "import from calendar" issue. I
have a hard time picturing a user interface that is at all
understandable for somebody not steeped in Unix lore. Given that we want
CPL scripts to be portable and creatable by users, this process must be
reversible. I.e., it is not good enough that I can have a user interface
with a button that says "first Tuesday of the month" and then generate
some crontab specification based on that. I must be able to take CPL and
generate a user interface to change it, readily, to the first Wednesday
of the month. Since the way of expressing date is wholly unnatural, for
humans, for anything but trivial time ranges, I effectively force the UI
to have an interface that has a day slider, a month slider, a weekday
slider (or two, with ranges), etc., directly representing the crontab
fields.

No known user input for anything having to do with dates operates that
way (Jonathan L. has been looking at a variety of calendaring-style
programs and services recently and will report on his findings shortly).

Another problem is that even very simple date ranges like "from 5 pm to
7 am" are not directly expressible in crontab - you need two entries to
do this, which again is not exactly ideal when you're trying to build a
user interface that now has to reverse-engineer what the user meant.
Midnight-spanning time ranges are likely going to be very common.

(2) Use a subset of ical

This seems to solve the user input (including CPL-to-UI reversal)
problem, in the sense that this is a more natural representation of
common ways of expressing date ranges. It has been shown to be
implementable in O(1).

The only objection I remember (I'm sure somebody will point out the
other flaws) is that it may make importing full-fledged iCal difficult.
I don't buy this argument - it's even more difficult or impossible to
translate any reasonable subset of iCal to crontab, so this is no net
loss. For import from a calendar for those obscure cases, an enumeration
of date ranges is possible (it would then only have the disadvantage of
making re-import from CPL to a calendar lossy; importing CPL into a
calendar seems somewhat less likely, since this would only work for a
tightly constrained subset of CPL that only used time switches at the
top level). Given that most reasonable and currently used date
specifications are supported by the subset, this loss of information and
need for enumeration would appear to be an unlikely case. 

(3) Use full ical

It wasn't clear to me whether an implementation has been completed, but
unless there is one, it is probably a risky scheme, as Al Gore would
say. (No, he didn't invent ical, as far as I know.)

(4) Use ical later

This still has the same user interface issues as before, just more so,
plus it adds the usual complexity of finding out which version is
supported where.

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs

_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Thu Sep 28 13:56:08 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27968
	for <iptel-archive@odin.ietf.org>; Thu, 28 Sep 2000 13:56:08 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id EF1D24433C; Thu, 28 Sep 2000 12:56:01 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 2726B44339
	for <iptel@lists.bell-labs.com>; Thu, 28 Sep 2000 12:55:21 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA01864;
	Thu, 28 Sep 2000 13:55:16 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id NAA82820;
	Thu, 28 Sep 2000 13:55:16 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1kF3aAq4ud"
Content-Transfer-Encoding: 7bit
Message-ID: <14803.34307.837950.95690@conrail.cs.columbia.edu>
To: Henning Schulzrinne <schulzrinne@opus.cs.columbia.edu>
Cc: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] CPL time ranges
In-Reply-To: <39D37968.8830644A@cs.columbia.edu>
References: <39D37968.8830644A@cs.columbia.edu>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Thu, 28 Sep 2000 13:55:15 -0400 (EDT)


--1kF3aAq4ud
Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
Content-Transfer-Encoding: 7bit

On Thursday, September 28 2000, "Henning Schulzrinne" wrote to "iptel@lists.bell-labs.com" saying:

> No known user input for anything having to do with dates operates that
> way (Jonathan L. has been looking at a variety of calendaring-style
> programs and services recently and will report on his findings shortly).

The attached file lists my study of five user interfaces for calendaring
programs.  If other people have additional interfaces to contribute --
especially if they are substantially different -- I'd be interested to hear
of them.

The iCal-subset is capable of representing all the output of each of these
interfaces, though not necessarily of representing it "naturally" -- i.e. in
a way which (as Henning's mention recommended) can be back-translated to the
same UI.  I believe a somewhat broader iCal subset will be able to represent
all, or almost all, of these attributes naturally, and still be resolvable
in O(1) time with respect to (now - dtstart); more information will be
forthcoming soon.

-- 
Jonathan Lennox
lennox@cs.columbia.edu


--1kF3aAq4ud
Content-Type: text/plain
Content-Disposition: inline;
	filename="calendar.notes.txt"
Content-Transfer-Encoding: 7bit

Sun cm

Appointment recurrence parameters:
Date
Start time
Stop time
Repeat:
        One Time
        Daily
        Weekly
        Every Two Weeks
        Monthly By Date
        Monthly By Weekday
        Yearly
        Monday through Friday
        Mon, Wed, Fri
        Tue, Thu
        Repeat Every...
                N (days | weeks | months)
For: N (days | weeks | biweeks | months | years)

The stop time can be earlier than the start time -- it asks you if
you want it to continue to the next day.

Time Zone: from /usr/share/lib/zoneinfo/.  In "View" menu, not appointment
setting.


Netcenter WebCalendar

Date
Time (5-minute intervals, 12:00 AM to 11:55 PM)
Duration (5-minute intervals, 0:05 - 12:55)
Repeat:
        * Does not Repeat
        * Repeats (every | every other | every third | every fourth)
                (day | week | month | year | MWF | TuTh | MW | M-F | SaSu)
        * Repeats on the (first | second | third | fourth | last)
                (Su | Mo | Tu | We | Th | Fr | Sa) every month
* No End date, or * End by [date]

Appointments do not carry past midnight -- duration is truncated.

Time Zone: GMT offset only.  In "Calendar Preferences".  Does not seem
to take DST into account?


SDR
How often it takes place: (Once | Daily | Weekly | Every Two Weeks |
        [Monthly By Date] | [Monday through Friday])
        from [Date] at [Time] for (30 minutes | 1 - 12 hours | 1 - 6 days)
Length of this series of sessions:
        (2 - 6 days | 1 week | 8 - 13 days | (2 - 4) weeks)
        [ "Week" parameters only for weekly; "4 weeks" only for biweekly ]

"Monthly by date" and "Monday through Friday" selections are disabled.
Bug list says 'Doesn't handle SDPv2 repeat times with units "M" and "Y"'


Microsoft Outlook

Start time: (Date) (Time) [X] All day event
ENd time: (Date) (Time)
Start - End can be arbitrarily long

Appointment Recurrence
Start:  [Time]    End:  [Time]    Duration: [Interval]
(Remebers dates of parent window, though they cannot be set here)

Recurrence pattern:
* Daily:    * Every [N] day(s)
	    * Every weekday

* Weekly:   Recur every [N] week(s) on:
            [] Su [] Mo [] Tu [] We [] Thu [] Fri [] Sa [] Su

* Monthly:  * Day [N] of every [N] month(s)
            * The (first | second | third | fourth | last) 
               (day | weekday | weekend day | Su - Sa)
               of every [N] month(s)

* Yearly:   * Every (Month) [day]
            * The (first | second | third | fourth | last) (day...) of (month)

Range of recurrence:
Start: [Date]      * No end date
		   * End after: [N] occurences
                   * End by: [Date]


Netscape Calendar

Main tab:
Date, Start Time, end time, duration.  (Duration cannot exceed 24h)

"Repeating..." tab:

Start: [date]
        * Until [date]
        * For [N] (Day(s) | Week(s) | Month(s) | Year(s)

Include: [X] Saturdays [X] Sundays [X] Holidays

Frequency: Daily:
	* Every day
	* Every [N] day(s)

Weekly:
        * Every week
        * Every [N] week(s)
        [Mo] [Tu] [We] [Th] [Fr] [Sa] [Su]

Monthly on date(s):
        * On the [N] of every month
        * On the [1st .. 31st] of every [N] months
                   ^ multi-choice

Monthly on day(s):
* On the (1st, 2nd, 3rd, 4th, last) (Su - Sa) of every [N] month(s)
         ^ multi-choice


Yearly:
* Every year
* Every [N] year(s)

--1kF3aAq4ud--

_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 29 00:54:02 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA11081
	for <iptel-archive@odin.ietf.org>; Fri, 29 Sep 2000 00:54:02 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id DE9B0443CA; Thu, 28 Sep 2000 23:54:02 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from mail.pingtel.com (mail.pingtel.com [216.91.1.131])
	by lists.bell-labs.com (Postfix) with ESMTP id 904C44438C
	for <iptel@lists.bell-labs.com>; Thu, 28 Sep 2000 23:53:35 -0400 (EDT)
Received: from bbk.pingtel.com (h080046055682.ne.mediaone.net [24.218.19.140])
	by mail.pingtel.com (8.9.3/8.9.3) with ESMTP id AAA29170
	for <iptel@lists.bell-labs.com>; Fri, 29 Sep 2000 00:50:40 -0400
Message-Id: <4.3.2.7.2.20000929001743.00b67b70@mail.pingtel.com>
X-Sender: jbatson@mail.pingtel.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: iptel@lists.bell-labs.com
From: Jay Batson <jbatson@pingtel.com>
Subject: Re: [IPTEL] CPL time ranges
In-Reply-To: <14803.34307.837950.95690@conrail.cs.columbia.edu>
References: <39D37968.8830644A@cs.columbia.edu>
 <39D37968.8830644A@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Fri, 29 Sep 2000 00:56:31 -0400

I can speak to one other, very mature calendaring 
system:  MeetingMaker.  For reference, I was VP of Engineering of the team 
that built this client/server group calendaring product, which is still in 
wide use.  (E.g it is the group meeting scheduler at Cisco.)  I am proud to 
brag that MM a very sophisticated product that is targeted at high-end, 
very large, geographically diverse enterprises.

Following Jonathan L.'s outline, Meeting Maker provides:

Start time
Duration (from which stop time is calculated)
Frequency:
	Daily
	  - options: every day, every 'n' days, on specified days of the week
	Weekly
	  - options: on specified day of week, every week; every 'n' weeks; on 
specified week of month (e.g. 1st, 2nd, 3rd, 4th, last)
	Monthly
	  - options: Every month on this date, every other month on this date, 
29th day of every month, 29th day of every other month, and what to do if 
activity falls on weekend (don't move, move to previous weekday, move to 
next weekday, move to closest weekday)
	Quarterly
	  - options: What to do if activity falls on weekend (see previous choices)
	Annually
	  - options: What to do if activity falls on weekend (see previous choices)

Exception vector:
	(Not an explicit choice.  However, when a user sees a recurring meeting in 
their calendar, and they select the meeting and hit "delete," the program 
asks them if they want to cancel "the meeting on this (selected) date," 
"the meetings after this (selected) date," or "all occurrences of this 
meeting."  Note that the Palm desktop provides the same options.)

Time zone is attached to the meeting object by the server involved.  (Users 
are "associated" with a server within their time zone, and the server is 
told its time zone.  In MeetingMaker, when a meeting proposal is sent to a 
user on another server, the remote server adjusts for time zone 
differences, so that the proposal ends up being presented to the user in 
their "local" time.)  The meeting is stored in Zulu (GMT) time, along with 
storing the meeting proposer's time zone.  On servers, time zones are set 
in +/- GMT, and they know their local time zone rules (e.g. Arizona.)

Meetings/activities can span midnight, but for reasons I can't remember 
cannot exceed 24 hours.

For the record, I will claim substantial credit for getting the IETF iCal 
working group started.  I wanted to get calendaring products to provide the 
ability to propose meetings between companies, so I harangued other 
calendar vendors into getting the IETF to let us start the group.

As a non-technical contributor, I didn't chair the group, etc., but 
employees from my team contributed to the (never-completed) portion of iCal 
that was creating the "live" calendaring *protocol* for interactions 
between systems.  (Never completed because we couldn't solve some 
fundamental problems, e.g. information protection/security.)

The data representation portions of iCal -- which this group is mostly 
looking at -- is made up primarily of work done by Microsoft, and by 
Qualcomm (who was expecting to build a calendaring product, but never 
did.)  Much of the data representation decisions were made to suit 
Microsoft's then-current-product needs.

Note that there are various *calendaring* products out today which support 
parsing of iCal data, e.g. Outlook and Organizer.

For the record (again), I'm an old unix hack.  crontab was *maybe* okay in 
1986, but was and is maddening obtuse.  I always had the opinion that the 
crontab format was the bad idea of a junior programmer who hadn't thought 
through all the issues, and that we were all stuck with his/her bad 
ideas.  I even wrote a replacement for it when I was at BBN that we toyed 
with distributing as part of the OS release for our Mach-based massively 
parallel processor computers.  (It was a *tad* better, though not much.... ;-)

IMHO, I think the work done by the iCal WG was pretty good.  There are 
*many* subtleties that arise when you have to think about representing 
events and times, and you don't always know what they are till you've been 
there.  People who had "been there" built the iCal data representation, and 
did good work.

So I'm sad (nah -- happy!) to say that I can't provide "running code," I 
would place myself on the side of using iCal in some manner -- abbreviated 
or not -- when it comes to the "rough consensus" part.  Now if Jonathan L. 
can provide the running code.... ;-)

-jb
----------
Jay Batson
Pingtel Corp.
jbatson@pingtel.com

781-938-5306 (office)
781-938-9650 (fax)


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 29 10:43:07 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00839
	for <iptel-archive@odin.ietf.org>; Fri, 29 Sep 2000 10:43:06 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 5A90144403; Fri, 29 Sep 2000 09:43:02 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from Mitel.COM (unknown [198.53.180.100])
	by lists.bell-labs.com (Postfix) with ESMTP id 60AF044401
	for <iptel@lists.bell-labs.com>; Fri, 29 Sep 2000 09:42:57 -0400 (EDT)
Received: from kanmta01.software.mitel.com (kanmta01.kanata.mitel.com [134.199.37.58]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with SMTP id KAA10737;
	Fri, 29 Sep 2000 10:42:12 -0400 (EDT)
Received: by kanmta01.software.mitel.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 85256969.0050BFFF ; Fri, 29 Sep 2000 10:42:00 -0400
X-Lotus-FromDomain: MITEL
From: Tom_Gray@Mitel.COM
To: Jay Batson <jbatson@pingtel.com>
Cc: iptel@lists.bell-labs.com
Message-ID: <85256969.0050BF6E.00@kanmta01.software.mitel.com>
Subject: Re: [IPTEL] CPL time ranges
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Fri, 29 Sep 2000 10:41:59 -0400



From:  Tom Gray@MITEL on 09/29/2000 10:41 AM

In the description below, there is an account of exception handling when
monthly, quarterly, annual events fall on weekends. Is there similar handling
for statutory holidays which are distinct on the local, regional and national
levels. Similarly are there means for handling events of purely local
significance such as plant shut downs, organisational celebrations, no meeting
days and so on. The need to handle such execptions would seem to me to have
signficance in the allocation of responsibilities between the client and server.








Jay Batson <jbatson@pingtel.com> on 09/29/2000 12:56:31 AM

To:   iptel@lists.bell-labs.com
cc:    (bcc: Tom Gray/Kan/Mitel)

Subject:  Re: [IPTEL] CPL time ranges



I can speak to one other, very mature calendaring
system:  MeetingMaker.  For reference, I was VP of Engineering of the team
that built this client/server group calendaring product, which is still in
wide use.  (E.g it is the group meeting scheduler at Cisco.)  I am proud to
brag that MM a very sophisticated product that is targeted at high-end,
very large, geographically diverse enterprises.

Following Jonathan L.'s outline, Meeting Maker provides:

Start time
Duration (from which stop time is calculated)
Frequency:
     Daily
       - options: every day, every 'n' days, on specified days of the week
     Weekly
       - options: on specified day of week, every week; every 'n' weeks; on
specified week of month (e.g. 1st, 2nd, 3rd, 4th, last)
     Monthly
       - options: Every month on this date, every other month on this date,
29th day of every month, 29th day of every other month, and what to do if
activity falls on weekend (don't move, move to previous weekday, move to
next weekday, move to closest weekday)
     Quarterly
       - options: What to do if activity falls on weekend (see previous choices)
     Annually
       - options: What to do if activity falls on weekend (see previous choices)

Exception vector:
     (Not an explicit choice.  However, when a user sees a recurring meeting in
their calendar, and they select the meeting and hit "delete," the program
asks them if they want to cancel "the meeting on this (selected) date,"
"the meetings after this (selected) date," or "all occurrences of this
meeting."  Note that the Palm desktop provides the same options.)

Time zone is attached to the meeting object by the server involved.  (Users
are "associated" with a server within their time zone, and the server is
told its time zone.  In MeetingMaker, when a meeting proposal is sent to a
user on another server, the remote server adjusts for time zone
differences, so that the proposal ends up being presented to the user in
their "local" time.)  The meeting is stored in Zulu (GMT) time, along with
storing the meeting proposer's time zone.  On servers, time zones are set
in +/- GMT, and they know their local time zone rules (e.g. Arizona.)

Meetings/activities can span midnight, but for reasons I can't remember
cannot exceed 24 hours.

For the record, I will claim substantial credit for getting the IETF iCal
working group started.  I wanted to get calendaring products to provide the
ability to propose meetings between companies, so I harangued other
calendar vendors into getting the IETF to let us start the group.

As a non-technical contributor, I didn't chair the group, etc., but
employees from my team contributed to the (never-completed) portion of iCal
that was creating the "live" calendaring *protocol* for interactions
between systems.  (Never completed because we couldn't solve some
fundamental problems, e.g. information protection/security.)

The data representation portions of iCal -- which this group is mostly
looking at -- is made up primarily of work done by Microsoft, and by
Qualcomm (who was expecting to build a calendaring product, but never
did.)  Much of the data representation decisions were made to suit
Microsoft's then-current-product needs.

Note that there are various *calendaring* products out today which support
parsing of iCal data, e.g. Outlook and Organizer.

For the record (again), I'm an old unix hack.  crontab was *maybe* okay in
1986, but was and is maddening obtuse.  I always had the opinion that the
crontab format was the bad idea of a junior programmer who hadn't thought
through all the issues, and that we were all stuck with his/her bad
ideas.  I even wrote a replacement for it when I was at BBN that we toyed
with distributing as part of the OS release for our Mach-based massively
parallel processor computers.  (It was a *tad* better, though not much.... ;-)

IMHO, I think the work done by the iCal WG was pretty good.  There are
*many* subtleties that arise when you have to think about representing
events and times, and you don't always know what they are till you've been
there.  People who had "been there" built the iCal data representation, and
did good work.

So I'm sad (nah -- happy!) to say that I can't provide "running code," I
would place myself on the side of using iCal in some manner -- abbreviated
or not -- when it comes to the "rough consensus" part.  Now if Jonathan L.
can provide the running code.... ;-)

-jb
----------
Jay Batson
Pingtel Corp.
jbatson@pingtel.com

781-938-5306 (office)
781-938-9650 (fax)


_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel





_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


From iptel-admin@lists.bell-labs.com  Fri Sep 29 19:49:03 2000
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA08339
	for <iptel-archive@odin.ietf.org>; Fri, 29 Sep 2000 19:49:03 -0400 (EDT)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 12EB84433A; Fri, 29 Sep 2000 18:49:03 -0400 (EDT)
Delivered-To: iptel@lists.bell-labs.com
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by lists.bell-labs.com (Postfix) with ESMTP id 8F5AD44339
	for <iptel@lists.bell-labs.com>; Fri, 29 Sep 2000 18:48:17 -0400 (EDT)
Received: from conrail.cs.columbia.edu (conrail.cs.columbia.edu [128.59.19.147])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id TAA20514
	for <iptel@lists.bell-labs.com>; Fri, 29 Sep 2000 19:48:12 -0400 (EDT)
Received: (from lennox@localhost)
	by conrail.cs.columbia.edu (8.9.3/8.9.1) id TAA84968;
	Fri, 29 Sep 2000 19:48:13 -0400 (EDT)
	(envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="QJEv+9CBOt"
Content-Transfer-Encoding: 7bit
Message-ID: <14805.10812.864120.484144@conrail.cs.columbia.edu>
To: iptel@lists.bell-labs.com
Subject: Re: [IPTEL] CPL time ranges
In-Reply-To: <14803.34307.837950.95690@conrail.cs.columbia.edu>
References: <39D37968.8830644A@cs.columbia.edu>
	<14803.34307.837950.95690@conrail.cs.columbia.edu>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: iptel-admin@lists.bell-labs.com
Errors-To: iptel-admin@lists.bell-labs.com
X-BeenThere: iptel@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:iptel-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:iptel@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=subscribe>
List-Id: <iptel.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/iptel>, <mailto:iptel-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/iptel/
Date: Fri, 29 Sep 2000 19:48:12 -0400 (EDT)


--QJEv+9CBOt
Content-Type: text/plain; charset=us-ascii
Content-Description: message body and .signature
Content-Transfer-Encoding: 7bit

On Thursday, September 28 2000, "Jonathan Lennox" wrote to "Henning Schulzrinne, iptel@lists.bell-labs.com" saying:

> I believe a somewhat broader iCal subset will be able to represent
> all, or almost all, of these attributes naturally, and still be resolvable
> in O(1) time with respect to (now - dtstart); more information will be
> forthcoming soon.

Here it is.  This handles almost all of iCal -- and, I believe, all its
*useful* parts -- in O(1) time.

No running code yet, though implementation of this algorithm should be
straightforward.  

"Beware of bugs in the above code.  I have only proven it correct; I haven't
tried it yet." -- Donald Knuth

Comments *very* welcome.

-- 
Jonathan Lennox
lennox@cs.columbia.edu


--QJEv+9CBOt
Content-Type: text/plain
Content-Description: iCal resolution algorithm
Content-Disposition: inline;
	filename="algorithm.txt"
Content-Transfer-Encoding: 7bit


A. The "secondly", "minutely", and "hourly" recurrences, and the "bysecond",
        "byminute", and "byhour" rules, are eliminated.
B. The "count" and "bysetpos" rules are eliminated.
C. The duration of the event ("duration" or "dtend - dtstart") must be
        less than 24 hours.

Here is the algorithm:
1.  Compute the time of the call, in the timezone of the time switch.
    (No step after this needs to consider time zones -- all calculations
    are done using continuously-running standard Gregorian time.)

2.  If the call time is earlier than dtstart, fail NOMATCH.

3.  If the call time is less than 'duration' after dtstart, succeed MATCH.

4.  Determine the smallest unit specified in a "by*" rule or by the "freq".
    Call this the Minimum Unit.  Determine the previous instant (before
    the call time) when all the time units smaller than the minimum unit
    are the same as those of DTStart.  (For all minimum units, the
    time-of-day must be the same as dtstart.  If the minimum unit is a week,
    the day-of-the-week must be the same as dtstart.  If the minimum unit is
    a month, the day-of-the-month must be the same as dtstart.  If the
    minimum unit is a year, the month and day-of-month must both be the same
    as dtstart (unless the dtstart is February 29 in a leap year, in which
    case the month and day-of-month can also be March 1 in a non-leap year).

    Call this instant the Candidate Start Time.

5.  If the time between the candidate start time and the call time is more
    than the duration, fail NOMATCH.

6.  If the candidate start time is later than the 'until' parameter of the
    recurrence, fail NOMATCH.

7.  Call the unit of the 'freq' parameter of the recurrence the Frequency
    Unit.  Determine the frequency unit enclosing the Candidate Start Time,
    and that enclosing DTStart.  Calculate the number of frequency units
    that have passed between these two times.  If this is not a multiple
    of the "interval" parameter, fail NOMATCH.

8.  For every by* rule, confirm that the candidate start time matches one
    of the options specified by that by* rule.  If not, fail NOMATCH.

9. Succeed MATCH.


Some notes on this algorithm:

The justifications for each of the eliminations above are as follows.

A.  When sub-day-resolution rules are present, issues of daylight-savings
        transitions come into play.  The number of, e.g., "nine hour"
        intervals since a given time isn't easily computable from a
        broken-down local time if a DST transition has occured in between.
        Since sub-day-resolution rules don't seem especially useful for
        recurring events anyway, we can avoid consideration of these
        issues by eliminating them.

B.  Barring very clever (and complex) algorithms that escape me, "count" and
        "bysetpos" rules both require that a set of recurrences be fully
        enumerated for them to be correctly resolved.

C.  Durations longer than the minimum unit can result in multiple candidate
        start times being possible for a given call time.  The simplest way
        to resolve this is by forcing durations to be less than 24
        hours, while eliminating the sub-day frequencies and rules.  The
        algorithm would still work with just the weaker condition (duration
        < min unit), though this would be much harder to explain.


Notes on importing from full iCal:

In my experience, no actual calendaring implementations present a user
interface for creating sub-day-resolution recurrences.  Very few allow
appointments longer than 24 hours.

Converting from 'count' to 'until' parameters, for a client which must
enumerate the event listings anyway, is trivial.

'bysetpos', 'rdate', 'exrule', and 'exdate' can all be handled by
converting a single full iCal RRULE into multiple time-switches, linked
with sub's to the same output.

--QJEv+9CBOt--

_______________________________________________
IPTEL mailing list
IPTEL@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/iptel


