From exim@www1.ietf.org  Wed Nov  5 08:01:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03885
	for <sipping-archive@odin.ietf.org>; Wed, 5 Nov 2003 08:01:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHNHY-00076y-4H
	for sipping-archive@odin.ietf.org; Wed, 05 Nov 2003 08:01:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5D18iq027330
	for sipping-archive@odin.ietf.org; Wed, 5 Nov 2003 08:01:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHNHX-00076j-W7
	for sipping-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 08:01:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03854
	for <sipping-web-archive@ietf.org>; Wed, 5 Nov 2003 08:00:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHNHX-0003Vm-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 08:01:07 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHNHW-0003Vi-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 08:01:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHNHS-00075a-Dd; Wed, 05 Nov 2003 08:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHNGz-00074Z-KW
	for sipping@optimus.ietf.org; Wed, 05 Nov 2003 08:00:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03839
	for <sipping@ietf.org>; Wed, 5 Nov 2003 08:00:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHNGy-0003VK-00
	for sipping@ietf.org; Wed, 05 Nov 2003 08:00:32 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHNGy-0003VG-00
	for sipping@ietf.org; Wed, 05 Nov 2003 08:00:32 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hA5D0UI2018960
	for <sipping@ietf.org>; Wed, 5 Nov 2003 14:00:30 +0100 (MET)
Received: from ericsson.com (EFO9N000L5C7100 [153.88.94.128]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WHXBF1JW; Wed, 5 Nov 2003 14:00:33 +0100
Message-ID: <3FA8F468.2060006@ericsson.com>
Date: Wed, 05 Nov 2003 15:00:24 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] TEST please ignore
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov  5 15:07:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21273
	for <sipping-archive@odin.ietf.org>; Wed, 5 Nov 2003 15:07:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHTvn-00027o-2Q
	for sipping-archive@odin.ietf.org; Wed, 05 Nov 2003 15:07:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5K76Ha008162
	for sipping-archive@odin.ietf.org; Wed, 5 Nov 2003 15:07:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHTvm-00027R-Gg
	for sipping-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 15:07:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21214
	for <sipping-web-archive@ietf.org>; Wed, 5 Nov 2003 15:06:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHTvj-0002JS-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 15:07:03 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHTvj-0002JP-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 15:07:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHTvh-00025B-Eb; Wed, 05 Nov 2003 15:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHTvH-00024F-Cu
	for sipping@optimus.ietf.org; Wed, 05 Nov 2003 15:06:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21139
	for <sipping@ietf.org>; Wed, 5 Nov 2003 15:06:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHTvD-0002Is-00
	for sipping@ietf.org; Wed, 05 Nov 2003 15:06:31 -0500
Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHTvD-0002Hl-00
	for sipping@ietf.org; Wed, 05 Nov 2003 15:06:31 -0500
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by ihemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA5K4c924916
	for <sipping@ietf.org>; Wed, 5 Nov 2003 14:05:18 -0600 (CST)
Received: by il0015exch001h.ih.lucent.com with Internet Mail Service (5.5.2656.59)
	id <TFQPK5HR>; Wed, 5 Nov 2003 14:03:55 -0600
Message-ID: <DBC3D7D0A071F743AE0767C9C6071EDA0482BE6B@il0015exch010u.ih.lucent.com>
From: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Wed, 5 Nov 2003 14:03:53 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [Sipping] Early Media draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo,
For completeness, I suggest you incorporate into the early media draft some discussion of early media handling in ITU-T Q.1912.5.  Q.1912.5 uses the presence of encapsulated ISUP in a 180 response to determine that the terminating end is associated with an ISUP endpoint that has in-band call progress information, so that it is not necessary to generate local ringing.  Conversely, the lack of encapsulated ISUP in a 180 response may cause the originating side to generate local ringing.  This effectively provides the functionality I requested in previous correspondence without the need for any SIP extensions.

Richard Ejzak
Lucent Technologies

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov  5 17:44:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27956
	for <sipping-archive@odin.ietf.org>; Wed, 5 Nov 2003 17:44:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHWNr-0003hM-3E
	for sipping-archive@odin.ietf.org; Wed, 05 Nov 2003 17:44:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA5MiFuF014210
	for sipping-archive@odin.ietf.org; Wed, 5 Nov 2003 17:44:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHWNq-0003h7-VJ
	for sipping-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 17:44:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27951
	for <sipping-web-archive@ietf.org>; Wed, 5 Nov 2003 17:44:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHWNo-00050X-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 17:44:12 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHWNn-00050U-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 17:44:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHWNd-0003fk-Ns; Wed, 05 Nov 2003 17:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHWNZ-0003fN-Ms
	for sipping@optimus.ietf.org; Wed, 05 Nov 2003 17:43:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27938
	for <sipping@ietf.org>; Wed, 5 Nov 2003 17:43:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHWNW-00050D-00
	for sipping@ietf.org; Wed, 05 Nov 2003 17:43:54 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHWNV-0004zl-00
	for sipping@ietf.org; Wed, 05 Nov 2003 17:43:54 -0500
Received: from cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 05 Nov 2003 14:47:54 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA5MhIAt002912;
	Wed, 5 Nov 2003 14:43:19 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA08699; Wed, 5 Nov 2003 14:43:18 -0800 (PST)
Message-Id: <4.3.2.7.2.20031105164041.025f1b38@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 05 Nov 2003 16:43:18 -0600
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping] TEST please ignore
Cc: sipping <sipping@ietf.org>
In-Reply-To: <3FA8F468.2060006@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Gonzalo

Is there a sipping draft agenda available yet anywhere? It hasn't been 
posted, and I cannot find one on softarmor

just curious

cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov  5 20:48:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05181
	for <sipping-archive@odin.ietf.org>; Wed, 5 Nov 2003 20:48:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZFp-0006sl-Ov
	for sipping-archive@odin.ietf.org; Wed, 05 Nov 2003 20:48:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA61m9Ap026451
	for sipping-archive@odin.ietf.org; Wed, 5 Nov 2003 20:48:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZFp-0006sY-Ex
	for sipping-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 20:48:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05152
	for <sipping-web-archive@ietf.org>; Wed, 5 Nov 2003 20:47:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZFm-0007VV-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 20:48:06 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZFm-0007VS-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 20:48:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZFi-0006rH-4V; Wed, 05 Nov 2003 20:48:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZEw-0006nQ-Ry
	for sipping@optimus.ietf.org; Wed, 05 Nov 2003 20:47:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05121
	for <sipping@ietf.org>; Wed, 5 Nov 2003 20:47:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZEu-0007Uq-00
	for sipping@ietf.org; Wed, 05 Nov 2003 20:47:12 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZEt-0007UN-00
	for sipping@ietf.org; Wed, 05 Nov 2003 20:47:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA61kSP13399;
	Wed, 5 Nov 2003 20:46:28 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <VRTPG3R2>; Wed, 5 Nov 2003 20:46:29 -0500
Message-ID: <0D7FC1D8D861D511AEA70002A52CE5E6082C0218@zcard0ke.ca.nortel.com>
From: "Joe Zebarth" <zebarth@nortelnetworks.com>
To: Eric Burger <eburger@snowshore.com>
Cc: Dean Willis <dean.willis@softarmor.com>, sipping@ietf.org, t1s17@t1.org,
        bhall@labs.sbc.com
Subject: RE: [Sipping] Please Read Committee T1 Draft on DTMF Notification
Date: Wed, 5 Nov 2003 20:46:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3A407.CAFE4094"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3A407.CAFE4094
Content-Type: text/plain;
	charset="iso-8859-1"

Eric

Thank you for taking the time to review this document which was developed to
support the IANA registration of this event package.  

This event package was intended to support the use scenario as identified
within the document, viz. "This event package MAY be used to allow an
application server (subscriber) to request DTMF monitoring and notification
of detection from a receiving agent (notifier) in order to enable a
caller-initiated re-origination request while a call is in progress."  It is
important to understand that this usage scenario assumes that the DTMF
signal comes from the portion of the PSTN that uses TDM technology and that
the application server supports SIP and also forms part of the PSTN.

This is a reponse to your email, please see the comments in line.



Kindest regards,

Joe Zebarth
T1S1.7 Vice Chair

Dept. 1A12
ATI Strategic Standards
Nortel Networks (Canada)
Phone: +1 613 765 8481
ESN:    6+395 8481
Fax:     +1 613 763 2697
ESN:    6+393 2697
http://www.nortelnetworks.com
 



-----Original Message-----
From: Eric Burger [mailto:eburger@snowshore.com]
Sent: Wednesday, October 29, 2003 10:03 PM
To: Dean Willis; sipping@ietf.org
Cc: Zebarth, Joe [CAR:1A12:EXCH]
Subject: RE: [Sipping] Please Read Committee T1 Draft on DTMF
Notification

Things I like in dtmfad:
 
1. Explicit maxrate (but see below)
2. "Handshook" throttling (although isn't that normal SIP: no overlapping
transactions?)
3. Very simple and compact
4. Described forking and state agent behavior (I forgot!)
 
 
Things I don't like:
1. The model is worse than MGCP.  An event for every key press?  If you are
interested in such low-level control, use H.248.
 
	Comment: JAZ
	This document is not discussing control.  Rather it is addressing
the subject of capturing the DTMF digits that originated in the portion of
the PSTN that uses TDM technology and which subsequently enter the portion
of the PSTN that uses IP technology.  The application server already
supports SIP.  The implementation of the event package is a modest extension
to support this capability.
 
2. The model only works for a B2BUA or machine end point.  The far end is
the only entity that can request digit monitoring.  OK for a "softswitch",
but not necessarily desirable in an Applications and Services
Infrastructure.

	Comment: JAZ
	I believe that your observation is correct that the far end is the
only entity that can request digit monitoring in this usage scenario.  The
usage scenario calls for the far end to request digit monitoring. 
 
3. Duration: On the one hand, it is handy to be able to define what "long"
is.  However, this is a disaster.  What if I set "duration=50" and I hold
the octothorpe key down for 6 seconds?  I will get 120 NOTIFY messages in
that time.  That isn't helpful for traffic shaping.  What does the
application do with all of those messages?  The model is taken directly from
RFC2833 (keep emitting tone and mark the end-of-tone) -- why not just use
RFC2833 and be done with it?  Eating a low-rate RTP stream has GOT to be
easier than implementing a RFC3261 stack!
 
	Comment: JAZ
	The usage scenario assumes that SIP is implemented.  Thus, the
proposed implementation is as you suggest "simple and compact" to add this
capability.
	 
	The following guidance is contained in the document to prevent
operators from setting the optional duration parameter to some number like
50 ms. (If this optional parameter is not present, then event notification
occurs only when the end of the DTMF tone is detected.), viz.
	 
		'Note: for long key presses, combined with short values of
"duration", a single DTMF digit can result in many NOTIFY requests.  With
calling card re-origination requests, in particular, the Application Server
(AS) cannot provide a prompt for a new destination number or begin
collecting digits if the caller is still pressing a DTMF key, so the AS must
wait for completion of the tone.  Therefore, it is likely that sending
NOTIFY requests at the termination of each detected DTMF digit is preferable
to sending many NOTIFY requests for each digit.  As a result, it is
RECOMMENDED that the AS not include the "duration" parameter.'
	 
	Additional guidance is also given in this regard, viz.
	 
		'maxrate
		"maxrate" is an optional parameter defining a maximum number
of NOTIFY transactions per minute initiated to report DTMF events.  The
notifier MUST NOT exceed this limit in any one minute period, but MAY send
notifications in more rapid bursts over shorter periods.  If "maxrate" is
omitted, the notifier MUST limit reporting to forty (40) NOTIFY transactions
per minute.  "maxrate" SHOULD NOT exceed 60. 
		 
		If the reporting rate limit causes a queue of unreported
events to build up, the notifier MAY discard some or all of the excess
events.  If the notifier can choose which events to discard, the notifier
SHOULD discard notifications of uncompleted DTMF events resulting from the
presence of the "duration" parameter before discarding notifications of
completed DTMF events.'
	 
	Should the optional duration parameter be set, the text allows the
notifier to delete/discard notifications of uncompleted DTMF events.
 
4. Hex codes don't really fit into the SIP gestalt.  Why not encode the
information in a straightforward manner?  One cannot argue for compactness
-- if one is going to live with 600+ bytes of SIP headers (see the example
in the document), one can have a 35-byte text message that means something
instead of a 12-byte "binary" message that is indecipherable.
 
	Comment:JAZ
	As the event package is intended to carry dtmf digits and as they
are transparent to SIP processing, we believe that the defined event package
is consistent with normal IETF style.
  
Things I am open to:
1. Volume: Does anyone need this?  What for?  How would you know?  What
would you do with it?  Not for falsing detection: that is what the detection
device should be doing.  If there is a good use case, I could see
implementing it.  Then again, what do you do for RFC2833 digit detection (no
volume)?
 
	Comment JAZ
	The DTMF tone originates in the TDM portion of the PSTN and thus
depending on the PSTN transmission plan the DTMF tone levels may vary.
 
2. Maxrate: I'm leaning towards not liking it, but I'm open to it.
First, the SUBSCRIBER here only specifies its own ability to process NOTIFY
requests.  Using this as a network-saving device isn't going to work: how
does the subscriber have any idea what to set this to? 
Second, the default maxrate is one message every 16ms, or faster than G.711.
What could this be possibly useful for?
Third (and the big one), the whole point of transporting digits in the
signaling path is because the digits *are* signaling.  Said differently, the
application needs reliable delivery of signaling (digits).  If the use case
for this package allows unreliable delivery, then I would be very interested
in understanding why one is not using RFC2833, which has EVERYTHING
discussed in this draft, available today?
 
	Comment JAZ
	The usage scenario only calls for the far end to request digit
monitoring.  The subscriber is typically using a PTSN phone to originate
calls and subsequent in band dtmf tones.  Maxrate provides additional
security against people who do insist upon holding down a DTMF digit when
the carrier has set the duration parameter to a short duration.

	As you indicated earlier, this is a "very simple and compact" way of
implementing this feature.

	In summary, based on your comments, I do not see any technical
issues with the proposed event package.

	I would look forward to your support in having this work progress so
that the event package can be registered with IANA in a timely fashion.

	Again I would like to thank you for taking the time to comment on
this document.
 

	Kindest regards, 
	Joe Zebarth

	T1S1.7 Vice Chair

 




> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Tue, October 28, 2003 2:27 AM
> To: sipping@ietf.org
> Cc: Joe Zebarth
> Subject: [Sipping] Please Read Committee T1 Draft on DTMF Notification
> 
> 
> While we were arguing about how to handle keypresses, 
> somebody went out
> and wrote a draft for an event package for DTMF events.
> 
> Please review the draft:
> 
> http://www.softarmor.com/wgdb/docs/draft-zebarth-sipping-dtmfad-00.txt
> 
> As I understand it, the mechanism that this draft is meant to 
> support is
> defined in Committee T1 Technical Report T1.TR.82-2003. 
> Unfortunately, I
> wasn't able to find said document on the T1 site, but that 
> could just be
> me -- perhaps the author can give us a link?
> 
> Questions to consider: Does this approach complement or conflict with
> the KPML work? Is there danger of fragmenting, or is this work clearly
> seperate? Would the world (or at least the Internet) be a better place
> with, or without, this event package?
> 
> Please copy the author, as well as the list, on any 
> responses. I expect
> that discussion on this topic will come up during the Minneapolis
> meeting.
> 
> Thanks,
> 
> --
> Dean Willis
> SIPPING co-chair
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 


------_=_NextPart_001_01C3A407.CAFE4094
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] Please Read Committee T1 Draft on DTMF =
Notification</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Eric</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thank you for taking the time to =
review this document which was developed to support the IANA =
registration of this event package.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This event package was intended to =
support the use scenario as identified within the document, viz. =
&quot;This event package MAY be used to allow an application server =
(subscriber) to request DTMF monitoring and notification of detection =
from a receiving agent (notifier) in order to enable a caller-initiated =
re-origination request while a call is in progress.&quot;&nbsp; It is =
important to understand that this usage scenario assumes that the DTMF =
signal comes from the portion of the PSTN that uses TDM technology and =
that the application server supports SIP and also forms part of the =
PSTN.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is a reponse to your email, =
please see the comments in line.</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Kindest regards,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Joe Zebarth</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">T1S1.7 Vice Chair</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dept. 1A12</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ATI Strategic Standards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Nortel Networks (Canada)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Phone: +1 613 765 8481</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+395 =
8481</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Fax:&nbsp;&nbsp;&nbsp;&nbsp; +1 613 =
763 2697</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+393 =
2697</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.nortelnetworks.com" =
TARGET=3D"_blank">http://www.nortelnetworks.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Eric Burger [<A =
HREF=3D"mailto:eburger@snowshore.com">mailto:eburger@snowshore.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: Wednesday, October 29, 2003 =
10:03 PM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: Dean Willis; =
sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cc: Zebarth, Joe =
[CAR:1A12:EXCH]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: RE: [Sipping] Please Read =
Committee T1 Draft on DTMF</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Notification</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Things I like in dtmfad:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">1. Explicit maxrate (but see =
below)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2. &quot;Handshook&quot; throttling =
(although isn't that normal SIP: no overlapping transactions?)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">3. Very simple and compact</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">4. Described forking and state agent =
behavior (I forgot!)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Things I don't like:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">1. The model is worse than =
MGCP.&nbsp; An event for every key press?&nbsp; If you are interested =
in such low-level control, use H.248.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">This document is not discussing =
control.&nbsp; Rather it is addressing the subject of capturing the =
DTMF digits that originated in the portion of the PSTN that uses TDM =
technology and which subsequently enter the portion of the PSTN that =
uses IP technology.&nbsp; The application server already supports =
SIP.&nbsp; The implementation of the event package is a modest =
extension to support this capability.</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2. The model only works for a B2BUA =
or machine end point.&nbsp; The far end is the only entity that can =
request digit monitoring.&nbsp; OK for a "softswitch", but not =
necessarily desirable in an Applications and Services =
Infrastructure.</FONT></P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I believe that your observation is =
correct that the far end is the only entity that can request digit =
monitoring in this usage scenario.&nbsp; The usage scenario calls for =
the far end to request digit monitoring. </FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">3. Duration: On the one hand, it is =
handy to be able to define what &quot;long&quot; is.&nbsp; However, =
this is a disaster.&nbsp; What if I set &quot;duration=3D50&quot; and I =
hold the octothorpe key down for 6 seconds?&nbsp; I will get 120 NOTIFY =
messages in that time.&nbsp; That isn't helpful for traffic =
shaping.&nbsp; What does the application do with all of those =
messages?&nbsp; The model is taken directly from RFC2833 (keep emitting =
tone and mark the end-of-tone) -- why not just use RFC2833 and be done =
with it?&nbsp; Eating a low-rate RTP stream has GOT to be easier than =
implementing a RFC3261 stack!</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">The usage scenario assumes that SIP =
is implemented.&nbsp; Thus, the proposed implementation is as you =
suggest &quot;simple and compact&quot; to add this =
capability.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">The following guidance is contained =
in the document to prevent operators from setting the optional duration =
parameter to some number like 50 ms. (If this optional parameter is not =
present, then event notification occurs only when the end of the DTMF =
tone is detected.), viz.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">'Note: for long key presses, combined =
with short values of &quot;duration&quot;, a single DTMF digit can =
result in many NOTIFY requests.&nbsp; With calling card re-origination =
requests, in particular, the Application Server (AS) cannot provide a =
prompt for a new destination number or begin collecting digits if the =
caller is still pressing a DTMF key, so the AS must wait for completion =
of the tone.&nbsp; Therefore, it is likely that sending NOTIFY requests =
at the termination of each detected DTMF digit is preferable to sending =
many NOTIFY requests for each digit.&nbsp; As a result, it is =
RECOMMENDED that the AS not include the &quot;duration&quot; =
parameter.'</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Additional guidance is also given in =
this regard, viz.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">'maxrate</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;maxrate&quot; is an optional =
parameter defining a maximum number of NOTIFY transactions per minute =
initiated to report DTMF events.&nbsp; The notifier MUST NOT exceed =
this limit in any one minute period, but MAY send notifications in more =
rapid bursts over shorter periods.&nbsp; If &quot;maxrate&quot; is =
omitted, the notifier MUST limit reporting to forty (40) NOTIFY =
transactions per minute.&nbsp; &quot;maxrate&quot; SHOULD NOT exceed =
60. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">If the reporting rate limit causes a =
queue of unreported events to build up, the notifier MAY discard some =
or all of the excess events.&nbsp; If the notifier can choose which =
events to discard, the notifier SHOULD discard notifications of =
uncompleted DTMF events resulting from the presence of the &quot;duratio=
n&quot; parameter before discarding notifications of completed DTMF =
events.'</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Should the optional duration =
parameter be set, the text allows the notifier to delete/discard =
notifications of uncompleted DTMF events.</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">4. Hex codes don't really fit into =
the SIP gestalt.&nbsp; Why not encode the information in a =
straightforward manner?&nbsp; One cannot argue for compactness -- if =
one is going to live with 600+ bytes of SIP headers (see the example in =
the document), one can have a 35-byte text message that means something =
instead of a 12-byte &quot;binary&quot; message that is =
indecipherable.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment:JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">As the event package is intended to =
carry dtmf digits and as they are transparent to SIP processing, we =
believe that the defined event package is consistent with normal IETF =
style.</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Things I am open to:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">1. Volume: Does anyone need =
this?&nbsp; What for?&nbsp; How would you know?&nbsp; What would you do =
with it?&nbsp; Not for falsing detection: that is what the detection =
device should be doing.&nbsp; If there is a good use case, I could see =
implementing it.&nbsp; Then again, what do you do for RFC2833 digit =
detection (no volume)?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">The DTMF tone originates in the TDM =
portion of the PSTN and thus depending on the PSTN transmission plan =
the DTMF tone levels may vary.</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2. Maxrate: I'm leaning towards not =
liking it, but I'm open to it.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">First, the SUBSCRIBER here only =
specifies its own ability to process NOTIFY requests.&nbsp; Using this =
as a network-saving device isn't going to work: how does the subscriber =
have any idea what to set this to? </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Second, the default maxrate is one =
message every 16ms, or faster than G.711.&nbsp; What could this be =
possibly useful for?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Third (and the big one), the whole =
point of transporting digits in the signaling path is because the =
digits *are* signaling.&nbsp; Said differently, the application needs =
reliable delivery of signaling (digits).&nbsp; If the use case for this =
package allows unreliable delivery, then I would be very interested in =
understanding why one is not using RFC2833, which has EVERYTHING =
discussed in this draft, available today?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">The usage scenario only calls for the =
far end to request digit monitoring.&nbsp; The subscriber is typically =
using a PTSN phone to originate calls and subsequent in band dtmf =
tones.&nbsp; Maxrate provides additional security against people who do =
insist upon holding down a DTMF digit when the carrier has set the =
duration parameter to a short duration.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As you indicated earlier, this is a =
&quot;very simple and compact&quot; way of implementing this =
feature.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In summary, based on your comments, I =
do not see any technical issues with the proposed event package.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would look forward to your support =
in having this work progress so that the event package can be =
registered with IANA in a timely fashion.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Again I would like to thank you for =
taking the time to comment on this document.</FONT>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Kindest regards, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Joe Zebarth</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">T1S1.7 Vice Chair</FONT>
</P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; From: Dean Willis [<A =
HREF=3D"mailto:dean.willis@softarmor.com">mailto:dean.willis@softarmor.c=
om</A>]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Sent: Tue, October 28, 2003 2:27 =
AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; To: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Cc: Joe Zebarth</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Subject: [Sipping] Please Read =
Committee T1 Draft on DTMF Notification</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; While we were arguing about how =
to handle keypresses, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; somebody went out</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; and wrote a draft for an event =
package for DTMF events.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Please review the draft:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; <A =
HREF=3D"http://www.softarmor.com/wgdb/docs/draft-zebarth-sipping-dtmfad-=
00.txt" =
TARGET=3D"_blank">http://www.softarmor.com/wgdb/docs/draft-zebarth-sippi=
ng-dtmfad-00.txt</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; As I understand it, the =
mechanism that this draft is meant to </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; support is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; defined in Committee T1 =
Technical Report T1.TR.82-2003. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Unfortunately, I</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; wasn't able to find said =
document on the T1 site, but that </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; could just be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; me -- perhaps the author can =
give us a link?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Questions to consider: Does this =
approach complement or conflict with</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; the KPML work? Is there danger =
of fragmenting, or is this work clearly</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; seperate? Would the world (or at =
least the Internet) be a better place</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; with, or without, this event =
package?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Please copy the author, as well =
as the list, on any </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; responses. I expect</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; that discussion on this topic =
will come up during the Minneapolis</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; meeting.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; --</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Dean Willis</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; SIPPING co-chair</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; This list is for NEW development =
of the application of SIP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Use =
sip-implementors@cs.columbia.edu for questions on current sip</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Use sip@ietf.org for new =
developments of core SIP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3A407.CAFE4094--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov  5 21:29:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06426
	for <sipping-archive@odin.ietf.org>; Wed, 5 Nov 2003 21:29:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZtT-0001Jw-3p
	for sipping-archive@odin.ietf.org; Wed, 05 Nov 2003 21:29:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA62T7XZ005070
	for sipping-archive@odin.ietf.org; Wed, 5 Nov 2003 21:29:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZtT-0001Jh-05
	for sipping-web-archive@optimus.ietf.org; Wed, 05 Nov 2003 21:29:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06411
	for <sipping-web-archive@ietf.org>; Wed, 5 Nov 2003 21:28:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZtQ-0000Df-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 21:29:04 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZtP-0000Dc-00
	for sipping-web-archive@ietf.org; Wed, 05 Nov 2003 21:29:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZtN-0001IP-QC; Wed, 05 Nov 2003 21:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHZso-0001GR-12
	for sipping@optimus.ietf.org; Wed, 05 Nov 2003 21:28:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06386
	for <sipping@ietf.org>; Wed, 5 Nov 2003 21:28:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZsl-0000Cs-00
	for sipping@ietf.org; Wed, 05 Nov 2003 21:28:23 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHZsk-0000CP-00
	for sipping@ietf.org; Wed, 05 Nov 2003 21:28:22 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hA62RdC16599;
	Wed, 5 Nov 2003 21:27:39 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <VRTPG3X2>; Wed, 5 Nov 2003 21:27:40 -0500
Message-ID: <0D7FC1D8D861D511AEA70002A52CE5E6082C0229@zcard0ke.ca.nortel.com>
From: "Joe Zebarth" <zebarth@nortelnetworks.com>
To: Eric Burger <eburger@snowshore.com>
Cc: Dean Willis <dean.willis@softarmor.com>, sipping@ietf.org, t1s17@t1.org,
        bhall@labs.sbc.com
Subject: RE: [Sipping] RE: Please Read Committee T1 Draft on DTMF Notifica
	tion
Date: Wed, 5 Nov 2003 21:27:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3A40D.8B902C3C"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3A40D.8B902C3C
Content-Type: text/plain;
	charset="iso-8859-1"

Eric

Again I would like to thank you for taking the time to provide additional
comment.

While the KPML is an interesting approach and provides extended
capablilities it inherently is not a "simple and compact" solution for the
identified use scenario, as I understand it.  

	For the usage scenario discussed in the ID defining the event
package, the KPML solution is more processing intensive at the "Notifier"
while the proposed event package is more processing intensive at the
"Application Server".  Obviously each solution has its particular strengths.
However, as these strengths are use scenario dependent, it is felt that they
should be considered complementary, not competative, solutions.


T1S1 is populated with people who have dealt with protocol for many years.
It was based on their experience that this event package was developed for
this usage scenario.

I have provided in line comments below.

As per my previous message, again I do not see any technical issues with
this new event package based on your comments.  I would look forward to your
support in having this work progress so that the event package can be
registered with IANA in a timely fashion.



Kindest regards,

Joe Zebarth
T1S1.7 Vice Chair

Dept. 1A12
ATI Strategic Standards
Nortel Networks (Canada)
Phone: +1 613 765 8481
ESN:    6+395 8481
Fax:     +1 613 763 2697
ESN:    6+393 2697
http://www.nortelnetworks.com
 



-----Original Message-----
From: Eric Burger [mailto:eburger@snowshore.com]
Sent: Thursday, October 30, 2003 10:34 PM
To: Zebarth, Joe [CAR:1A12:EXCH]
Cc: sipping@ietf.org
Subject: RE: [Sipping] RE: Please Read Committee T1 Draft on DTMF
Notification


Thanks for the posting.

Reviewing the document, I think the T1 community may be better served by
KPML.  

	Comment: JAZ

	See comments above. Each method has its strengths and should be
considered complementary, not competative solutions.

It handles the long # issue, 

	Comment: JAZ
	A methodology is provided to deal with the long # issue in the
defined event package.  Thus it is not a technical issue.

as well as directly handles the #9# example given.  

	Comment: JAZ

	The #9# is a timing issue, not a technical issue.


Moreover, it is a general solution, while the T1 suggestion does not really
work even for the pre-paid scenario (the NOTIFY flooding and ignoring
expires on SUBSCRIBE).

	Comment: JAZ

	In the usage scenario there need be no NOTIFY flooding occurences.  
	If the devices comply with the IETF version of SIP, the devices will
handle SUBSCRIBE correctly.  This event package was produced to foster
ongoing compliance with SIP by IP technology.  It is for this reason that
IANA registration of this event package is being sought.  
	I would look forward to your support in having this work progress so
that the event package can be registered with IANA in a timely fashion.



-----Original Message-----
From: Joe Zebarth [mailto:zebarth@nortelnetworks.com]
Sent: Tue, October 28, 2003 9:05 AM
To: sipping@ietf.org
Cc: Dean Willis
Subject: [Sipping] RE: Please Read Committee T1 Draft on DTMF Notification


Colleagues 
The T1 prepublished document can be found at: 
http://www.t1.org/filemgr/filesearch.taf?_function=detail&T1_Files_uid1=3S17
0632 
Note that the zip file is 251 k and the uncompressed is 1.4 M 
Kindest regards, 
Joe Zebarth 
Dept. 1A12 
ATI Strategic Standards 
Nortel Networks (Canada) 
Phone: +1 613 765 8481 
ESN:    6+395 8481 
Fax:     +1 613 763 2697 
ESN:    6+393 2697 
http://www.nortelnetworks.com 
  



-----Original Message----- 
From: Dean Willis [mailto:dean.willis@softarmor.com] 
Sent: Tuesday, October 28, 2003 2:27 AM 
To: sipping@ietf.org 
Cc: Zebarth, Joe [CAR:1A12:EXCH] 
Subject: Please Read Committee T1 Draft on DTMF Notification 


While we were arguing about how to handle keypresses, somebody went out 
and wrote a draft for an event package for DTMF events. 
Please review the draft: 
http://www.softarmor.com/wgdb/docs/draft-zebarth-sipping-dtmfad-00.txt 
As I understand it, the mechanism that this draft is meant to support is 
defined in Committee T1 Technical Report T1.TR.82-2003. Unfortunately, I 
wasn't able to find said document on the T1 site, but that could just be 
me -- perhaps the author can give us a link? 
Questions to consider: Does this approach complement or conflict with 
the KPML work? Is there danger of fragmenting, or is this work clearly 
seperate? Would the world (or at least the Internet) be a better place 
with, or without, this event package? 
Please copy the author, as well as the list, on any responses. I expect 
that discussion on this topic will come up during the Minneapolis 
meeting. 
Thanks, 
-- 
Dean Willis 
SIPPING co-chair 


------_=_NextPart_001_01C3A40D.8B902C3C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Sipping] RE: Please Read Committee T1 Draft on DTMF =
Notification</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Eric</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Again I would like to thank you for =
taking the time to provide additional comment.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">While the KPML is an interesting =
approach and provides extended capablilit</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">ies</FONT><FONT SIZE=3D2 FACE=3D"Arial"> it inherently =
is not a &quot;simple and compact&quot; solution for the identified use =
scenario</FONT><FONT SIZE=3D2 FACE=3D"Arial">, as I understand =
it</FONT><FONT SIZE=3D2 FACE=3D"Arial">.&nbsp; </FONT></P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">For the usage scenario discussed in =
the ID defining the event package</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">,</FONT><FONT SIZE=3D2 FACE=3D"Arial"> the KPML solution =
is more processing intensive at the &quot;Notifier&quot; while the =
proposed event package is more processing intensive at the =
&quot;Application Server&quot;.</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; Obviously each solution has its particular =
strengths.&nbsp; However, as these strengths are use scenario =
dependent, it is felt that they should be considered complementary, not =
competative, solutions.</FONT></P>
<BR>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">T1S1 is populated with people who have =
deal</FONT><FONT SIZE=3D2 FACE=3D"Arial">t</FONT><FONT SIZE=3D2 =
FACE=3D"Arial"> with protocol for many years.&nbsp; It was based on =
their experience that this event package was developed for this usage =
scenario.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have provided in line comments =
below.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As per my previous message, again =
I</FONT> <FONT SIZE=3D2 FACE=3D"Arial">do not</FONT> <FONT SIZE=3D2 =
FACE=3D"Arial">see</FONT> <FONT SIZE=3D2 FACE=3D"Arial">any</FONT><FONT =
SIZE=3D2 FACE=3D"Arial"> technical issues with this new event package =
based on your comments.&nbsp; I would look forward to your support in =
having this work progress so that the event package can be registered =
with IANA in a timely fashion.</FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Kindest regards,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Joe Zebarth</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">T1S1.7 Vice Chair</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dept. 1A12</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ATI Strategic Standards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Nortel Networks (Canada)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Phone: +1 613 765 8481</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+395 =
8481</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Fax:&nbsp;&nbsp;&nbsp;&nbsp; +1 613 =
763 2697</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+393 =
2697</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.nortelnetworks.com" =
TARGET=3D"_blank">http://www.nortelnetworks.com</A></FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Eric Burger [<A =
HREF=3D"mailto:eburger@snowshore.com">mailto:eburger@snowshore.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: Thursday, October 30, 2003 =
10:34 PM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: Zebarth, Joe =
[CAR:1A12:EXCH]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cc: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: RE: [Sipping] RE: Please =
Read Committee T1 Draft on DTMF</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Notification</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for the posting.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Reviewing the document, I think the T1 =
community may be better served by KPML.&nbsp; </FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">See co</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">mments above. Each method has its strengths and should =
be considered complementary, not competative solutions.</FONT>
</P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">It handles the long # issue, </FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">A methodology is provided to deal =
with the long # issue in the defined event package.&nbsp; Thus it is =
not a technical issue.</FONT></P>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">as well as directly handles the #9# =
example given.&nbsp; </FONT>
</P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The #9# is a timing issue, not a =
technical issue.</FONT>
</P>
<BR>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Moreover, it is a general solution, =
while the T1 suggestion does not really work even for the pre-paid =
scenario (the NOTIFY flooding and ignoring expires on =
SUBSCRIBE).</FONT></P>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">Comment: JAZ</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the usage scenario there need be no =
NOTIFY flooding occurences.&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">If the devices comply with the IETF =
version of SIP, the devices will handle SUBSCRIBE correctly.&nbsp; This =
event package was produced to foster ongoing compliance with SIP by IP =
technology.&nbsp; It is for this reason that IANA registration of this =
event package is being sought.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would look forward to your support =
in having this work progress so that the event package can be =
registered with IANA in a timely fashion.</FONT></P>
<BR>
<BR>
</UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Joe Zebarth [<A =
HREF=3D"mailto:zebarth@nortelnetworks.com">mailto:zebarth@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: Tue, October 28, 2003 9:05 =
AM</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cc: Dean Willis</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: [Sipping] RE: Please Read =
Committee T1 Draft on DTMF Notification</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Colleagues </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">The T1 prepublished document can be =
found at: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.t1.org/filemgr/filesearch.taf?_function=3Ddetail&T1_F=
iles_uid1=3D3S170632" =
TARGET=3D"_blank">http://www.t1.org/filemgr/filesearch.taf?_function=3Dd=
etail&T1_Files_uid1=3D3S170632</A> </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Note that the zip file is 251 k and =
the uncompressed is 1.4 M </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Kindest regards, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Joe Zebarth </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Dept. 1A12 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ATI Strategic Standards </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Nortel Networks (Canada) </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Phone: +1 613 765 8481 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+395 8481 =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Fax:&nbsp;&nbsp;&nbsp;&nbsp; +1 613 =
763 2697 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ESN:&nbsp;&nbsp;&nbsp; 6+393 2697 =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.nortelnetworks.com" =
TARGET=3D"_blank">http://www.nortelnetworks.com</A> </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">-----Original Message----- </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Dean Willis [<A =
HREF=3D"mailto:dean.willis@softarmor.com">mailto:dean.willis@softarmor.c=
om</A>] </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Sent: Tuesday, October 28, 2003 2:27 =
AM </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: sipping@ietf.org </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Cc: Zebarth, Joe [CAR:1A12:EXCH] =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Subject: Please Read Committee T1 =
Draft on DTMF Notification </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">While we were arguing about how to =
handle keypresses, somebody went out </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">and wrote a draft for an event =
package for DTMF events. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Please review the draft: </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial"><A =
HREF=3D"http://www.softarmor.com/wgdb/docs/draft-zebarth-sipping-dtmfad-=
00.txt" =
TARGET=3D"_blank">http://www.softarmor.com/wgdb/docs/draft-zebarth-sippi=
ng-dtmfad-00.txt</A> </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">As I understand it, the mechanism =
that this draft is meant to support is </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">defined in Committee T1 Technical =
Report T1.TR.82-2003. Unfortunately, I </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">wasn't able to find said document on =
the T1 site, but that could just be </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">me -- perhaps the author can give us =
a link? </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Questions to consider: Does this =
approach complement or conflict with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">the KPML work? Is there danger of =
fragmenting, or is this work clearly </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">seperate? Would the world (or at =
least the Internet) be a better place </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">with, or without, this event package? =
</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Please copy the author, as well as =
the list, on any responses. I expect </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">that discussion on this topic will =
come up during the Minneapolis </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">meeting. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Thanks, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">-- </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Dean Willis </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">SIPPING co-chair </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3A40D.8B902C3C--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 00:05:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10719
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 00:05:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHcKS-0001Ak-Pt
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 00:05:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6558GM004500
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 00:05:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHcKS-0001AV-Lp
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 00:05:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10661
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 00:04:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHcKQ-0002Bd-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 00:05:06 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHcKP-0002Ba-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 00:05:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHcKN-00018P-GM; Thu, 06 Nov 2003 00:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHcJX-00017M-7Y
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 00:04:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10631
	for <sipping@ietf.org>; Thu, 6 Nov 2003 00:03:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHcJU-0002B9-00
	for sipping@ietf.org; Thu, 06 Nov 2003 00:04:08 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHcJU-00029h-00
	for sipping@ietf.org; Thu, 06 Nov 2003 00:04:08 -0500
Received: from pingtel.com (h00d01e004cd0.ne.client2.attbi.com[66.30.203.15])
          by comcast.net (rwcrmhc11) with SMTP
          id <2003110605033701300rndl7e>
          (Authid: dgpetrie);
          Thu, 6 Nov 2003 05:03:38 +0000
Message-ID: <3FA9D646.9AE19164@pingtel.com>
Date: Thu, 06 Nov 2003 00:04:06 -0500
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: sipping <sipping@ietf.org>, Rohan Mahy <rohan@cisco.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] Agenda requests
References: <3F939657.6050801@ericsson.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gonzalo:
I would like to request two time slots for the SIPPING WG.
Let me know if you need more information or if I can help to
get this on the agenda in anyway.
Cheers,
Dan

Topic 1:
Dan Petrie
Event Package for User Configuration Profiles
15 minutes
http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-01.txt

Topic 2:
Dan Petrie
Transfer Issues
10 minutes
http://www.ietf.org/internet-drafts/draft-petrie-sipping-xfer-issues-00.txt



Gonzalo Camarillo wrote:

> Folks,
>
> I will be taking care of registering agenda requests for the Minneapolis
> meeting at:
> http://www.softarmor.com/sipping/meets/ietf58/requests.html
>
> Send your requests to me including:
> o Your name
> o Topic you would like to present
> o Lenght of the slot
> o List of related drafts that people should read
>
> If you use the following template to send me your request, you would
> make this task much easier for me:
>
> <tr>
> <td><a href="mailto:Gonzalo.Camarillo@ericsson.com">
> Gonzalo Camarillo</a></td>
> <td>Exploder requirements</td>
> <td><center>5</center></td>
> <td>
> <a
> href="http://www.ietf.org/internet-drafts/draft-camarillo-sipping-exploders-00.txt">
> draft-camarillo-sipping-exploders-00.txt</a>
> </td>
> </tr>
>
> Thanks,
>
> Gonzalo
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 02:24:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26719
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 02:24:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHeV7-0000h8-QH
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 02:24:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA67OHmb002667
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 02:24:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHeV6-0000gw-P3
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 02:24:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26710
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 02:24:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHeV2-0003ov-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 02:24:12 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHeV2-0003os-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 02:24:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHeUt-0000eW-EU; Thu, 06 Nov 2003 02:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHeUB-0000bA-3H
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 02:23:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26695
	for <sipping@ietf.org>; Thu, 6 Nov 2003 02:23:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHeU7-0003oa-00
	for sipping@ietf.org; Thu, 06 Nov 2003 02:23:15 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHeU6-0003oX-00
	for sipping@ietf.org; Thu, 06 Nov 2003 02:23:14 -0500
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hA67NESs019065;
	Thu, 6 Nov 2003 08:23:14 +0100 (MET)
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.31.125]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id V6M28WQQ; Thu, 6 Nov 2003 08:23:14 +0100
Message-ID: <3FA9F6E2.9040206@ericsson.com>
Date: Thu, 06 Nov 2003 09:23:14 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ejzak, Richard P (Richard)" <ejzak@lucent.com>
CC: "'sipping@ietf.org'" <sipping@ietf.org>
References: <DBC3D7D0A071F743AE0767C9C6071EDA0482BE6B@il0015exch010u.ih.lucent.com>
In-Reply-To: <DBC3D7D0A071F743AE0767C9C6071EDA0482BE6B@il0015exch010u.ih.lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: Early Media draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Richard,

this draft is supposed to focus on SIP procedures, not on interworking
with other protocols. RFC 3398 handles interworking with ISUP.

In any case, what you are proposing is an example of a local policy, as 
defined in the draft. So, you are free to implement such a local policy 
(do not generate local ringing tone if an encapsulated ISUP message is 
received) in all the user agents you want.

Thanks,

Gonzalo

Ejzak, Richard P (Richard) wrote:
> Gonzalo, For completeness, I suggest you incorporate into the early
> media draft some discussion of early media handling in ITU-T
> Q.1912.5.  Q.1912.5 uses the presence of encapsulated ISUP in a 180
> response to determine that the terminating end is associated with an
> ISUP endpoint that has in-band call progress information, so that it
> is not necessary to generate local ringing.  Conversely, the lack of
> encapsulated ISUP in a 180 response may cause the originating side to
> generate local ringing.  This effectively provides the functionality
> I requested in previous correspondence without the need for any SIP
> extensions.
> 
> Richard Ejzak Lucent Technologies


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 04:46:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01700
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 04:46:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiU-0002Ai-SU
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 04:46:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69kD3T008326
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 04:46:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiR-00029J-OU
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 04:46:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01628
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 04:45:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiO-00060d-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:08 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiN-00060Z-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiJ-00026b-T9; Thu, 06 Nov 2003 04:46:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHghW-0001xr-9g
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 04:45:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01304
	for <sipping@ietf.org>; Thu, 6 Nov 2003 04:45:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHghT-0005qa-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:11 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AHghS-0005qQ-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:10 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 29265; Thu, 06 Nov 2003 04:51:54 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Nov 2003 04:44:02 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F6919@zoe.office.snowshore.com>
Thread-Topic: Comment on 3pcc-05
Thread-Index: AcOkCxq/nJ9nYMMQSXerq1W1r6XNgg==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Comment on 3pcc-05
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

The draft highlights that the message exchange with the UAS (B) happens =
on human terms, e.g., waiting for a person to answer before issuing an =
OK.

I think it is worth pointing that for all the flows not only does A's =
phone ring first, but they hear digital silence during the sequences =
with B's UAS.

Of course, this could be a pitch for music on hold :-)


Also, Normative Reference [6] has a bizarre citation format.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 04:46:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01702
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 04:46:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiU-0002Ag-I2
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 04:46:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69kDX9008327
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 04:46:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiR-00029Q-Ss
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 04:46:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01631
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 04:45:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiO-00060g-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:08 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiO-00060b-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiO-00027A-Fm; Thu, 06 Nov 2003 04:46:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHghW-0001xt-T5
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 04:45:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01310
	for <sipping@ietf.org>; Thu, 6 Nov 2003 04:45:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHghT-0005qk-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:11 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AHghT-0005qQ-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:11 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 29265; Thu, 06 Nov 2003 04:51:54 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Nov 2003 04:44:10 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F691B@zoe.office.snowshore.com>
Thread-Topic: Comments on app-interaction-framework-00
Thread-Index: AcOkDOmcbVadB545QKiRfg/On0NjiA==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Comments on app-interaction-framework-00
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

First Section 5.2 Open issue (does normative stuff belong?):
I don't think so.  Going back to the original format, this section is =
really our current understanding of the former App-Info header.  I can =
go either way: we can separate it, as it was separate before.  Or, we =
can fold it in, to keep it all in a single document.

Second Section 5.2 Open issue (GRUU requirement):
If a SUBSCRIBE gets sent on an INVITE-initiated dialog (e.g., same =
CallId, To, From, and presumably, route set), won't the SUBSCRIBE end up =
at the same end point?  If so, why do we need the GRUU?  I can see =
needing a GRUU for third-party requests (e.g., not on a dialog), but =
that would be an option, not a MUST.

Section 7.1 refers to the old digit suppression scheme (Q's).  We can =
update this w/ consensus on the new pre=3D method.


Nits:

Section 3.2: "application operation in asynchonously" should probably be =
worded as "Non-real-time interaction allows the user to asynchronously =
enter information about application operation with its invocation."

Section 4, 4th paragraph
instantiate one of more
instantiate one or more
                 ^

Section 4, page 14 (text version), last full paragraph on page, 3rd =
line:
Extra space before "HTML"

Section 5.3, second paragraph:
This allows the UI to updated in response
This allows the UI to update in response
                            ^

Section 5.4, third paragraph
The applciatio needs to be prepared
The applciation needs to be prepared
              ^


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 04:46:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01730
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 04:46:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiW-0002Ay-E5
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 04:46:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69kEOa008348
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 04:46:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiT-0002AA-DA
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 04:46:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01634
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 04:46:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiP-00060o-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:09 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiP-00060l-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiR-000291-74; Thu, 06 Nov 2003 04:46:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHghX-0001yC-Uy
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 04:45:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01316
	for <sipping@ietf.org>; Thu, 6 Nov 2003 04:45:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHghU-0005qu-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:12 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AHghT-0005qQ-01
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:11 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 29265; Thu, 06 Nov 2003 04:51:55 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Nov 2003 04:44:11 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F691C@zoe.office.snowshore.com>
Thread-Topic: Comments on dialog-package-03
Thread-Index: AcOkDnuJ+JKAwioZTuKAa7/rxLh9Eg==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Comments on dialog-package-03
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Section 3.3, last bullet:
I don't like the "or" in the explicitly requested and / or explicitly =
authorized.  Even if I am authorized, I don't want the information =
unless I explicitly request it (making it an "and" only).

How about, "The notifier MUST NOT include additional information unless =
explicitly requested.  The notifier SHOULD authorize the request before =
honoring the request."


Section 3.10 on notification rate:
I think the granularity is too small.  I would expect a flurry of =
interesting activity during call state change, and then relative quiet =
during conversations.  Given a conversation of 1 minute (efficient call =
center), how about having a suggested limit of 10 messages (or some =
other appropriate number) in one minute?  That way, you can have a =
message per second (as people answer calls, etc.), without flooding the =
network (as the dialog will be relatively quiet after the flurry).

Section 4.1.1 open issue (escaped quotes):
Don't forget, you get to chose between ' and ".  We could suggest using =
single tics.

Example in 4.1.1 is not consistent with the draft.  The version =
indicates which message number this is.  In the example, version=3D0, =
which implies this is the first message.  However, state=3D"partial", =
which is wrong: the first message always conveys state=3D"full".

Open issue 4.1.6 (reporting route set): Is there a use case for this?

Open issue 4.1.6.1.4 (reporting CSeq): What could anyone possibly do =
with this information?



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 04:46:41 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01748
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 04:46:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgic-0002Lg-1H
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 04:46:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69kLGa009006
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 04:46:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiZ-0002GL-HF
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 04:46:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01685
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 04:46:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiU-00060u-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:14 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgiU-00060r-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 04:46:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgiV-0002Ax-R1; Thu, 06 Nov 2003 04:46:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHghZ-0001yN-2J
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 04:45:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01331
	for <sipping@ietf.org>; Thu, 6 Nov 2003 04:45:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHghV-0005rL-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:13 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AHghV-0005qQ-00
	for sipping@ietf.org; Thu, 06 Nov 2003 04:45:13 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 29265; Thu, 06 Nov 2003 04:51:56 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Nov 2003 04:44:14 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F6920@zoe.office.snowshore.com>
Thread-Topic: Comments on cc-conferencing-02
Thread-Index: AcOkHiGdUqc+Dq8vR/mbiGDvvz+yBA==
From: "Eric Burger" <eburger@snowshore.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Comments on cc-conferencing-02
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Section 3.4:
I still don't understand why there is any normative stricture on a =
conference-aware UA to subscribe to the conference package.  If =
anything, the DEFINITION of a conference-aware UA is a UA that knows to =
subscribe to the conference package.  Thus the statement is rather =
self-referential and doesn't add any value.

Section 4:
I would offer that keeping the goal of small primitives, put together in =
novel ways by user agents, means that the call flows in this section =
are, by definition, informative and NOT normative.  That is, there is no =
"right way" to implement the primitives.  If the UA's are 3261 =
compliant, any combination of 3261 commands will work.

Section 4.1:
Why must the conference URI be reserved?  True, it doesn't say MUST, but =
it reads like it says "must."


Nits:
Section 3.2, third paragraph, first sentence:
the automatic creation a new conference
the automatic creation of a new conference
                       ^^^


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 08:03:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06963
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 08:03:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHjn3-0004qA-4k
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 08:03:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6D39PD018600
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 08:03:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHjn3-0004pv-1a
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 08:03:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06945
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 08:02:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHjn2-0000Z4-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 08:03:08 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHjn1-0000Z0-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 08:03:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHjmv-0004oB-1R; Thu, 06 Nov 2003 08:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHjmD-0004nH-D1
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 08:02:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06892
	for <sipping@ietf.org>; Thu, 6 Nov 2003 08:02:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHjmC-0000XZ-00
	for sipping@ietf.org; Thu, 06 Nov 2003 08:02:16 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHjmB-0000XT-00
	for sipping@ietf.org; Thu, 06 Nov 2003 08:02:15 -0500
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hA6D2CUC014165
	for <sipping@ietf.org>; Thu, 6 Nov 2003 22:02:12 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hA6D2Bpo004332
	for <sipping@ietf.org>; Thu, 6 Nov 2003 22:02:11 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hA6D2B8H004460
	for <sipping@ietf.org>; Thu, 6 Nov 2003 22:02:11 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id WAA20488
	for <sipping@ietf.org>; Thu, 6 Nov 2003 22:02:10 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id WAA22600
	for <sipping@ietf.org>; Thu, 6 Nov 2003 22:02:10 +0900 (JST)
Date: Thu, 06 Nov 2003 22:02:04 +0900
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
Subject: Re:[Sipping] I-D ACTION:draft-ietf-sipping-e2m-sec-reqs-00.txt
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.07beta6 (WinNT,501)
Message-Id: <BBC3A4662D27EEono.kumiko@lab.ntt.co.jp>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear SIPPING folk,

I have recently updated my end-to-middle security draft to a version 00 
of the requirements draft, draft-ietf-sipping-e2m-sec-reqs-00.txt, (the 
mechanism draft will follow). I wanted to point out some major changes 
since the last individual submission:
	- Organized the requirements better
	- Added requirements for discovery
	
I also have some open issues that I wanted to share and get your 
feedback on. 

First, some background on my thinking: I think that in the real world 
there is sometimes a need for proxy servers to inspect the contents of 
SIP message bodies.  In addition, proxy servers sometimes need to  
delete a message body in a request in order to delete a user 
authentication data (ex. Proxy-Authorization) that is protected with S/
MIME.  Or, proxy servers sometimes need to even append a message body in 
a request in order to indicate some requirements for a response, such as 
recommended SDP for 200 OK response.  There is also a great need for 
security end to end. 

There are currently many proxy servers that add, modify and/or delete 
message bodies as proscribed in RFC 3261. We want to enable an end-point 
to communicate with a proxy somewhere in the chain of proxy servers. 

There needs to be a way to balance the desire allow features (ex. 
logging, firewall traversal) and preserve end-to-end integrity and 
confidentiality. In order to balance them and improve usability of end-
to-end security, it is important to define a means of e2m security.

There is no way at the end-points to determine whether or not the 
message body has been appended if network services are only available to 
end-points that do not use end-to-end security (S/MIME). 

Open Issues:
*** Should RFC3261 be amended to allow proxies to append SIP message 
bodies or fragments that are addressed to it? (they$B!!(Bwould still  be 
forbidden from adding, modifying or deleting SIP message$B!!(Bbodies that 
are not addressed to them.)

*** Is this important enough to support the creation of a new SIP 
header? (I feel that it is, but I want to hear any arguments to the 
contrary.)

--
Kumiko Ono
NTT Network Service Systems Labs.
Tel +81 422 59 4508/Fax +81 422 60 4012

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 11:38:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17231
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 11:38:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHn9A-0001zd-RH
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 11:38:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6GcCcq007654
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 11:38:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHn9A-0001zF-Gq
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 11:38:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17181
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 11:37:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHn98-0003o0-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 11:38:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHn98-0003nx-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 11:38:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHn91-0001tq-Bp; Thu, 06 Nov 2003 11:38:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHn8V-0001mj-EC
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 11:37:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17136
	for <sipping@ietf.org>; Thu, 6 Nov 2003 11:37:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHn8U-0003mv-00
	for sipping@ietf.org; Thu, 06 Nov 2003 11:37:30 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHn8T-0003ms-00
	for sipping@ietf.org; Thu, 06 Nov 2003 11:37:29 -0500
Received: from ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id LAA28547
	for <sipping@ietf.org>; Thu, 6 Nov 2003 11:37:29 -0500 (EST)
Message-ID: <3FAA7B11.7070105@ulticom.com>
Date: Thu, 06 Nov 2003 11:47:13 -0500
From: Vijaya Venkatachalam <vijaya@ulticom.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-torture-tests-01 question
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I need clarification for the following test given in Torture tests document.

Section 3.1.2.11 Escaped headers in SIP Request-URI

The Request-URI seems valid as per BNF

Request-URI    =  SIP-URI / SIPS-URI / absoluteURI
SIP-URI          =  "sip:" [ userinfo ] hostport
                    uri-parameters [ headers ]
headers         =  "?" header *( "&" header )
header          =  hname "=" hvalue
hname           =  1*( hnv-unreserved / unreserved / escaped )
hvalue          =  *( hnv-unreserved / unreserved / escaped )

And the "escaped" hvalue allows %. So is this an invalid Request-URI.

      INVITE sip:user@example.com?Route=%3Csip:example.com%3E SIP/2.0
      To: sip:user@example.com
      From: sip:caller@example.net;tag=341518
      Max-Forwards: 7
      Contact: <sip:caller@host39923.example.net>
      Call-ID: 23940-asdfhj-aje3br-234q098w-fawerh2q-h4n5
      CSeq: 149209342 INVITE
      Via: SIP/2.0/UDP host-of-the-hour.example.com;branch=z9hG4bKkdjuw
      Content-Type: application/sdp
      Content-Length: 151

      v=0
      o=mhandley 29739 7272939 IN IP4 192.0.2.1
      s=-
      c=IN IP4 192.0.2.1
      t=0 0
      m=audio 492170 RTP/AVP 0 12
      m=video 3227 RTP/AVP 31
      a=rtpmap:31 LPC








_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 12:06:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18623
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 12:06:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHna5-0003lb-85
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 12:06:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6H61ME014473
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 12:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHna5-0003lM-4k
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 12:06:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18587
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 12:05:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHna2-0004Df-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 12:05:58 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHna2-0004Dc-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 12:05:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHnZ9-0003hU-MF; Thu, 06 Nov 2003 12:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHnYK-0003Yp-9b
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 12:04:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18489
	for <sipping@ietf.org>; Thu, 6 Nov 2003 12:03:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHnYI-0004Bu-00
	for sipping@ietf.org; Thu, 06 Nov 2003 12:04:11 -0500
Received: from zephir.uk.clara.net ([195.8.69.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHnYI-0004Br-00
	for sipping@ietf.org; Thu, 06 Nov 2003 12:04:10 -0500
Received: from [80.168.137.82] (helo=ictgateway.ictrnid.org.uk)
	by zephir.uk.clara.net with smtp (Exim 4.22)
	id 1AHnY3-000G2f-Ua
	for sipping@ietf.org; Thu, 06 Nov 2003 17:03:56 +0000
Received: from 192.168.1.43 ([192.168.1.43]) by ictgateway.ictrnid.org.uk (WinRoute Pro 4.1.29) with SMTP; Thu, 6 Nov 2003 17:10:16 +0000
From: "Frank Shearar" <frank.shearar@rnid.org.uk>
To: <sipping@ietf.org>
Subject: RE: [Sipping] draft-ietf-sipping-torture-tests-01 question
Date: Thu, 6 Nov 2003 17:03:53 -0000
Message-ID: <000c01c3a487$f5e4d220$2b01a8c0@wsfrank>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <3FAA7B11.7070105@ulticom.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> >>> "vijaya@ulticom.com" 11/06/03 16:47 >>>
> 
> Hi,
> 
> I need clarification for the following test given in Torture 
> tests document.
> 
> Section 3.1.2.11 Escaped headers in SIP Request-URI
> 
> The Request-URI seems valid as per BNF
> 
> Request-URI    =  SIP-URI / SIPS-URI / absoluteURI
> SIP-URI          =  "sip:" [ userinfo ] hostport
>                     uri-parameters [ headers ]
> headers         =  "?" header *( "&" header )
> header          =  hname "=" hvalue
> hname           =  1*( hnv-unreserved / unreserved / escaped )
> hvalue          =  *( hnv-unreserved / unreserved / escaped )
> 
> And the "escaped" hvalue allows %. So is this an invalid Request-URI.
> 
>       INVITE sip:user@example.com?Route=%3Csip:example.com%3E SIP/2.0
<snip>

As you say, it's valid according to the BNF, but RFC 3261 section 19.1.2
says that escaped headers are not permitted in the Request-URI.

frank


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov  6 18:28:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08308
	for <sipping-archive@odin.ietf.org>; Thu, 6 Nov 2003 18:28:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHtXt-000509-0D
	for sipping-archive@odin.ietf.org; Thu, 06 Nov 2003 18:28:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6NS8Og019223
	for sipping-archive@odin.ietf.org; Thu, 6 Nov 2003 18:28:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHtXs-0004zy-RB
	for sipping-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 18:28:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08296
	for <sipping-web-archive@ietf.org>; Thu, 6 Nov 2003 18:27:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHtXp-0002kg-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 18:28:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHtXp-0002kd-00
	for sipping-web-archive@ietf.org; Thu, 06 Nov 2003 18:28:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHtXl-0004yt-0q; Thu, 06 Nov 2003 18:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHtXL-0004yH-5q
	for sipping@optimus.ietf.org; Thu, 06 Nov 2003 18:27:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08293
	for <sipping@ietf.org>; Thu, 6 Nov 2003 18:27:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHtXI-0002kY-00
	for sipping@ietf.org; Thu, 06 Nov 2003 18:27:32 -0500
Received: from dsl-dt-207-34-112-i195-cgy.nucleus.com ([207.34.112.195] helo=yyc.jasomi.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHtXH-0002kU-00
	for sipping@ietf.org; Thu, 06 Nov 2003 18:27:31 -0500
Received: from [192.168.16.61] (aluminum.jasomi.com [192.168.16.61])
	(authenticated bits=0)
	by yyc.jasomi.com (8.12.9/8.12.6) with ESMTP id hA6N0xiT017832
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 6 Nov 2003 16:00:59 -0700 (MST)
In-Reply-To: <3FAA7B11.7070105@ulticom.com>
References: <3FAA7B11.7070105@ulticom.com>
Mime-Version: 1.0 (Apple Message framework v606)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C6FDA1A6-10B0-11D8-8A39-000A956A5F38@jasomi.com>
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
From: Alan Hawrylyshen <alan@jasomi.com>
Subject: Re: [Sipping] draft-ietf-sipping-torture-tests-01 question
Date: Thu, 6 Nov 2003 16:27:24 -0700
To: Vijaya Venkatachalam <vijaya@ulticom.com>
X-Mailer: Apple Mail (2.606)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On 6 Nov 2003, at 09:47, Vijaya Venkatachalam wrote:

>
> And the "escaped" hvalue allows %. So is this an invalid Request-URI. 
> [?]
>
>      INVITE sip:user@example.com?Route=%3Csip:example.com%3E SIP/2.0
>


As per the draft (emphasis mine):

3.1.2.11 Escaped headers in SIP Request-URI

    This INVITE is *malformed* as the SIP Request-URI contains escaped
    headers.

    It is acceptable for an element to reject this request with a 400 Bad
    Request. An element could choose to be liberal in what it accepts and
    ignore the escaped headers. If the element is a proxy, the escaped
    headers must not appear in the Request-URI of forwarded request (and
    most certainly must not be translated into the actual header of the
    forwarded request).

The RURI about which you ask is invalid. (Semantically).
Your implementation decisions will determine how you deal with this 
request.

Cheers,

Alan Hawrylyshen
Jasomi Networks Inc


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov  7 04:47:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07966
	for <sipping-archive@odin.ietf.org>; Fri, 7 Nov 2003 04:47:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI3Cv-00044A-FM
	for sipping-archive@odin.ietf.org; Fri, 07 Nov 2003 04:47:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA79l7bU015605
	for sipping-archive@odin.ietf.org; Fri, 7 Nov 2003 04:47:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI3Cs-00043Q-GY
	for sipping-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 04:47:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07933
	for <sipping-web-archive@ietf.org>; Fri, 7 Nov 2003 04:46:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI3Cp-0002BN-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 04:47:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI3Co-0002BH-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 04:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI3Cn-00041p-M5; Fri, 07 Nov 2003 04:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI3CW-00041Q-1b
	for sipping@optimus.ietf.org; Fri, 07 Nov 2003 04:46:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07921
	for <sipping@ietf.org>; Fri, 7 Nov 2003 04:46:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI3CS-0002B0-00
	for sipping@ietf.org; Fri, 07 Nov 2003 04:46:40 -0500
Received: from smtp2.clb.oleane.net ([213.56.31.18])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI3CR-0002At-00
	for sipping@ietf.org; Fri, 07 Nov 2003 04:46:40 -0500
Received: from oleane ([194.250.212.114]) 
	by smtp2.clb.oleane.net with SMTP id hA79kAfo016717
	for <sipping@ietf.org>; Fri, 7 Nov 2003 10:46:10 +0100
Message-ID: <02b401c3a514$7f1027c0$0601a8c0@www.oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <sipping@ietf.org>
Date: Fri, 7 Nov 2003 10:49:54 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02B1_01C3A51C.E080A360"
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: [Sipping] WiMAX Summit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

C'est un message de format MIME en plusieurs parties.

------=_NextPart_000_02B1_01C3A51C.E080A360
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Are WiMAX and WiFi complementary (local vs. metropolitan area =
networking)?=20
When and how will WiMAX evolve towards mobility?=20
Can WiMAX be considered as a migration path to 4G?=20
How is addressed the interoperability challenge?=20

These questions, among others, will be addressed during the WiMAX =
Summit, to be held in Paris on May 25 to 28, 2004.=20

A call for papers has been launched on-line at:
http://www.upperside.fr/wimax04/wimax04intro.htm

------=_NextPart_000_02B1_01C3A51C.E080A360
Content-Type: text/html;
	charset="Windows-1252"
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>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Are WiMAX and WiFi complementary (local vs. =
metropolitan=20
area&nbsp;networking)? <BR>When and how will WiMAX evolve towards =
mobility?=20
<BR>Can WiMAX be considered as a migration path to 4G? <BR>How is =
addressed the=20
interoperability challenge? <BR><BR>These questions, among others, will =
be=20
addressed during the <FONT class=3Dtextebold color=3D#2d795f>WiMAX =
Summit</FONT>, to=20
be held in <SPAN class=3Dunderline>Paris on May 25 to 28, </SPAN>2004. =
<BR><BR>A=20
call for papers has been launched on-line at:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/wimax04/wimax04intro.htm">http://www.uppe=
rside.fr/wimax04/wimax04intro.htm</A></FONT></DIV></BODY></HTML>

------=_NextPart_000_02B1_01C3A51C.E080A360--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov  7 06:55:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11416
	for <sipping-archive@odin.ietf.org>; Fri, 7 Nov 2003 06:55:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI5Ck-0001oo-VX
	for sipping-archive@odin.ietf.org; Fri, 07 Nov 2003 06:55:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7Bt6be006984
	for sipping-archive@odin.ietf.org; Fri, 7 Nov 2003 06:55:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI5Ck-0001oZ-S0
	for sipping-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 06:55:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11403
	for <sipping-web-archive@ietf.org>; Fri, 7 Nov 2003 06:54:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI5Cg-0003im-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 06:55:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI5Cg-0003ii-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 06:55:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI5Cg-0001nV-Pm; Fri, 07 Nov 2003 06:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI5Bj-0001mj-9n
	for sipping@optimus.ietf.org; Fri, 07 Nov 2003 06:54:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11396
	for <sipping@ietf.org>; Fri, 7 Nov 2003 06:53:49 -0500 (EST)
From: aki.niemi@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI5Be-0003iA-00
	for sipping@ietf.org; Fri, 07 Nov 2003 06:53:58 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI5Be-0003i3-00
	for sipping@ietf.org; Fri, 07 Nov 2003 06:53:58 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hA7BrtA25597
	for <sipping@ietf.org>; Fri, 7 Nov 2003 13:53:55 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65c2e1124dac158f21082@esvir01nok.ntc.nokia.com> for <sipping@ietf.org>;
 Fri, 7 Nov 2003 13:53:47 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Fri, 7 Nov 2003 13:53:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C3A525.CE525682"
Date: Fri, 7 Nov 2003 13:53:49 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9027D9125@esebe013.ntc.nokia.com>
X-MS-Has-Attach: yes
Thread-Topic: I-D ACTION:draft-niemi-sipping-event-throttle-00.txt
Thread-Index: AcOkpjFS8GEarwVLSSiddjgvAI9DHQAfrckQ
To: <sipping@ietf.org>
X-OriginalArrivalTime: 07 Nov 2003 11:53:49.0513 (UTC) FILETIME=[CE9ACB90:01C3A525]
Subject: [Sipping] FW: I-D ACTION:draft-niemi-sipping-event-throttle-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3A525.CE525682
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

This draft proposes a mechanism to fulfill the requirements set out in =
the event throttle requirements:

	=
http://www.ietf.org/internet-drafts/draft-ietf-sipping-event-throttle-req=
s-00.txt

Basically, we introduce a simple Event header parameter to carry the =
throttle value, which is taken by the notifier as the client-configured =
minimum time between two notifications. There is also a new option-tag =
to be used by the client in requiring support of this extension.

I'm planning to present this at the meeting next week, but comments and =
suggestions are appreciated even before that.

Cheers,
Aki

 > -----Original Message-----
 > From: owner-ietf-announce@ietf.org
 > [mailto:owner-ietf-announce@ietf.org]On Behalf Of ext
 > Internet-Drafts@ietf.org
 > Sent: 06 November, 2003 22:11
 > Subject: I-D ACTION:draft-niemi-sipping-event-throttle-00.txt
 >=20
 >=20
 > A New Internet-Draft is available from the on-line=20
 > Internet-Drafts directories.
 >=20
 >=20
 > 	Title		: Session Initiation Protocol (SIP)=20
 > Event Notification Throttles
 > 	Author(s)	: A. Niemi
 > 	Filename	: draft-niemi-sipping-event-throttle-00.txt
 > 	Pages		: 11
 > 	Date		: 2003-11-6
 > =09
 > This memo specifies a throttle mechanism for limiting the rate of
 > Session Initiation Protocol (SIP) event notifications. This mechanism
 > can be applied in subscriptions to all SIP event packages.
 >=20
 > A URL for this Internet-Draft is:
 > http://www.ietf.org/internet-drafts/draft-niemi-sipping-event
 > -throttle-00.txt
 >=20
 > To remove yourself from the IETF Announcement list, send a=20
 > message to=20
 > ietf-announce-request with the word unsubscribe in the body=20
 > of the message.
 >=20
 > Internet-Drafts are also available by anonymous FTP. Login=20
 > with the username
 > "anonymous" and a password of your e-mail address. After logging in,
 > type "cd internet-drafts" and then
 > 	"get draft-niemi-sipping-event-throttle-00.txt".
 >=20
 > A list of Internet-Drafts directories can be found in
 > http://www.ietf.org/shadow.html=20
 > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
 >=20
 >=20
 > Internet-Drafts can also be obtained by e-mail.
 >=20
 > Send a message to:
 > 	mailserv@ietf.org.
 > In the body type:
 > 	"FILE=20
 > /internet-drafts/draft-niemi-sipping-event-throttle-00.txt".
 > =09
 > NOTE:	The mail server at ietf.org can return the document in
 > 	MIME-encoded form by using the "mpack" utility.  To use this
 > 	feature, insert the command "ENCODING mime" before the "FILE"
 > 	command.  To decode the response(s), you will need "munpack" or
 > 	a MIME-compliant mail reader.  Different MIME-compliant=20
 > mail readers
 > 	exhibit different behavior, especially when dealing with
 > 	"multipart" MIME messages (i.e. documents which have been split
 > 	up into multiple messages), so check your local documentation on
 > 	how to manipulate these messages.
 > 	=09
 > 	=09
 > Below is the data which will enable a MIME compliant mail reader
 > implementation to automatically retrieve the ASCII version of the
 > Internet-Draft.
 >=20

------_=_NextPart_001_01C3A525.CE525682
Content-Type: application/octet-stream;
	name="ATT316061.TXT"
Content-Description: ATT316061.TXT
Content-Disposition: attachment;
	filename="ATT316061.TXT"
Content-Transfer-Encoding: base64

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJYWNjZXNzLXR5cGU9Im1haWwt
c2VydmVyIjsNCglzZXJ2ZXI9Im1haWxzZXJ2QGlldGYub3JnIg0KDQpDb250ZW50LVR5cGU6IHRl
eHQvcGxhaW4NCkNvbnRlbnQtSUQ6CTwyMDAzLTExLTYxMzExMTcuSS1EQGlldGYub3JnPg0KDQpF
TkNPRElORyBtaW1lDQpGSUxFIC9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbmllbWktc2lwcGluZy1l
dmVudC10aHJvdHRsZS0wMC50eHQNCg==

------_=_NextPart_001_01C3A525.CE525682
Content-Type: application/octet-stream;
	name="draft-niemi-sipping-event-throttle-00.URL"
Content-Description: draft-niemi-sipping-event-throttle-00.URL
Content-Disposition: attachment;
	filename="draft-niemi-sipping-event-throttle-00.URL"
Content-Transfer-Encoding: base64

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1uaWVtaS1zaXBwaW5nLWV2ZW50LXRocm90dGxlLTAwLnR4dA0K

------_=_NextPart_001_01C3A525.CE525682--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov  7 16:38:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08990
	for <sipping-archive@odin.ietf.org>; Fri, 7 Nov 2003 16:38:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEIy-00032A-AV
	for sipping-archive@odin.ietf.org; Fri, 07 Nov 2003 16:38:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7Lc8cd011658
	for sipping-archive@odin.ietf.org; Fri, 7 Nov 2003 16:38:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEIx-00031t-DL
	for sipping-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 16:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08979
	for <sipping-web-archive@ietf.org>; Fri, 7 Nov 2003 16:37:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEIv-0003OF-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 16:38:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEIv-0003OB-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 16:38:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEIs-00030b-BY; Fri, 07 Nov 2003 16:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEI2-0002qH-UN
	for sipping@optimus.ietf.org; Fri, 07 Nov 2003 16:37:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08942;
	Fri, 7 Nov 2003 16:36:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEI0-0003NU-00; Fri, 07 Nov 2003 16:37:08 -0500
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEHz-0003NR-00; Fri, 07 Nov 2003 16:37:07 -0500
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id hA7LbXv3014632
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Fri, 7 Nov 2003 15:37:33 -0600
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: <sipping@ietf.org>, <agenda@ietf.org>
Cc: <rohan@cisco.com>, "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Date: Fri, 7 Nov 2003 15:36:40 -0600
Message-ID: <00b101c3a577$3ba4e760$e1036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Agenda, SIPPING WG, IETF 58
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Agenda, SIPPING WG, IETF 59

TUESDAY, November 11, 2003, 0900-1130, Salon C
0900 Angenda Bash
            Chairs
0905 Status of Work
            Chairs
0920 Application Interaction
          Jonathan Rosenberg
          draft-ietf-sipping-app-interaction-framework-00.txt
0935 Key Press Stimulus Protocol
          Eric Burger
          draft-ietf-sipping-kpml-01.txt
0945 Event Package for DTMF Signals
          Joe Zebarth
          draft-zebarth-sipping-dtmfad-00.txt
1000 Conferencing Design Team Report
          Orit Levin
          draft-ietf-sipping-conference-package-02.txt
          draft-ietf-sipping-cc-conferencing-02.txt
1015 Transcoding Design Team
          Gonzalo Camarillo
          draft-camarillo-sipping-transc-3pcc-00.txt
          draft-camarillo-sipping-transc-framework-00.txt
          draft-camarillo-sipping-transc-b2bua-00.txt
          draft-camarillo-mmusic-source-sink-01.txt
1030 Emergency Calls Design Team
 
1040 Event Package for User Configuration Profiles
          Dan Petrie
          draft-ietf-sipping-config-framework-01.txt
1050 Intermediary Session Policies in SIP
          Volker Hilt
          draft-ietf-sipping-session-policy-req-00.txt
          draft-hilt-sipping-session-indep-policy-00.txt
          draft-hilt-sipping-session-spec-policy-00.txt
1100 Location Conveyance Requirements
          James Polk
          draft-polk-sipping-location-requirements-01.txt
          draft-ietf-geopriv-reqs-04.txt
          draft-schulzrinne-sipping-sos-04.txt
          draft-ietf-sipping-session-policy-req-00
          draft-jennings-sipping-certs-01.txt
1110 Reason Header for Preemption
          James Polk
          draft-polk-sipping-reason-header-for-preemption-00.txt
          draft-ietf-sip-resource-priority-01.txt
          RFC3326

THURSDAY, November 13, 2003, 1530-1730, Salon A
1530 Agenda Bash
          Chairs
1535 End-to-middle security requirements
          Kumiko Ono
          draft-ietf-sipping-end2middle-security-reqs-00
1545 Mechanism to Secure Information Inserted by Intermediaries
          Mary Barnes
          draft-barnes-sipping-sec-inserted-info-01.txt
1555 Role-Based Authentication
          Jon Peterson
          draft-peterson-sipping-role-authz-01.txt
1600 On-demand access authorization for SIP event subscriptions
          Dirk Trossen
          draft-trossen-sipping-ondemand-00.txt
1610 Early Media
          Gonzalo Camarillo
          draft-ietf-sipping-early-media-00.txt
          draft-camarillo-sipping-early-disposition-00.txt
1615 NAT Scenarios
          Jonathan Rosenberg
          draft-rosenberg-sipping-nat-scenarios-01 [.txt][.html]
1630 IPv4/IPv6 Translators in 3GPP Networks
          Gonzalo Camarillo
          draft-elmalki-sipping-3gpp-translator-00.txt
1635 Dialog package
          Rohan Mahy
          draft-ietf-sipping.dialog-package-03.txt
1650 Exploder requirements
          Gonzalo Camarillo
          draft-camarillo-sipping-exploders-00.txt
1655 Torture Tests
          Robert Sparks
          draft-ietf-sipping-torture-tests-01.txt
1700 SIP Load Management
          Robert Sparks
          draft-sparks-sipping-load-00.txt
1710 Event throttles
          Aki Niemi
          draft-niemi-sipping-event-throttle-00.txt
1720 RTCP Summary
          Alan Clark
          draft-sipping-johnston-rtcp-summary-01.txt

Additional requests will be accomodated if time allows


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov  7 16:42:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09174
	for <sipping-archive@odin.ietf.org>; Fri, 7 Nov 2003 16:42:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEMl-0003ar-GQ
	for sipping-archive@odin.ietf.org; Fri, 07 Nov 2003 16:42:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7Lg3Yj013807
	for sipping-archive@odin.ietf.org; Fri, 7 Nov 2003 16:42:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEMl-0003ac-B1
	for sipping-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 16:42:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09102
	for <sipping-web-archive@ietf.org>; Fri, 7 Nov 2003 16:41:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEMj-0003Qm-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 16:42:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEMi-0003Qi-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 16:42:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEMi-0003ZF-VX; Fri, 07 Nov 2003 16:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIEMD-0003Q6-Ko
	for sipping@optimus.ietf.org; Fri, 07 Nov 2003 16:41:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09076;
	Fri, 7 Nov 2003 16:41:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEMB-0003Q3-00; Fri, 07 Nov 2003 16:41:27 -0500
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIEM9-0003Q0-00; Fri, 07 Nov 2003 16:41:26 -0500
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id hA7Lfsv3014659
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Fri, 7 Nov 2003 15:41:54 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Dean Willis'" <dwillis@dynamicsoft.com>, <sipping@ietf.org>,
        <agenda@ietf.org>
Cc: <rohan@cisco.com>, "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Subject: RE: [Sipping] Agenda, SIPPING WG, IETF 58
Date: Fri, 7 Nov 2003 15:41:02 -0600
Message-ID: <00b701c3a577$d73127c0$e1036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <00b101c3a577$3ba4e760$e1036e3f@txdwillis>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Whoops, that should say "IETF 58", not "59".

And a nice hyper-linked version for the drafts is posted at:

http://www.softarmor.com/sipping/meets/ietf58/agenda.html

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Dean Willis
> Sent: Friday, November 07, 2003 3:37 PM
> To: sipping@ietf.org; agenda@ietf.org
> Cc: rohan@cisco.com; 'Gonzalo Camarillo'
> Subject: [Sipping] Agenda, SIPPING WG, IETF 58
> 
> 
> Agenda, SIPPING WG, IETF 59
> 
> TUESDAY, November 11, 2003, 0900-1130, Salon C
> 0900 Angenda Bash
>             Chairs
> 0905 Status of Work
>             Chairs
> 0920 Application Interaction
>           Jonathan Rosenberg
>           draft-ietf-sipping-app-interaction-framework-00.txt
> 0935 Key Press Stimulus Protocol
>           Eric Burger
>           draft-ietf-sipping-kpml-01.txt
> 0945 Event Package for DTMF Signals
>           Joe Zebarth
>           draft-zebarth-sipping-dtmfad-00.txt
> 1000 Conferencing Design Team Report
>           Orit Levin
>           draft-ietf-sipping-conference-package-02.txt
>           draft-ietf-sipping-cc-conferencing-02.txt
> 1015 Transcoding Design Team
>           Gonzalo Camarillo
>           draft-camarillo-sipping-transc-3pcc-00.txt
>           draft-camarillo-sipping-transc-framework-00.txt
>           draft-camarillo-sipping-transc-b2bua-00.txt
>           draft-camarillo-mmusic-source-sink-01.txt
> 1030 Emergency Calls Design Team
>  
> 1040 Event Package for User Configuration Profiles
>           Dan Petrie
>           draft-ietf-sipping-config-framework-01.txt
> 1050 Intermediary Session Policies in SIP
>           Volker Hilt
>           draft-ietf-sipping-session-policy-req-00.txt
>           draft-hilt-sipping-session-indep-policy-00.txt
>           draft-hilt-sipping-session-spec-policy-00.txt
> 1100 Location Conveyance Requirements
>           James Polk
>           draft-polk-sipping-location-requirements-01.txt
>           draft-ietf-geopriv-reqs-04.txt
>           draft-schulzrinne-sipping-sos-04.txt
>           draft-ietf-sipping-session-policy-req-00
>           draft-jennings-sipping-certs-01.txt
> 1110 Reason Header for Preemption
>           James Polk
>           draft-polk-sipping-reason-header-for-preemption-00.txt
>           draft-ietf-sip-resource-priority-01.txt
>           RFC3326
> 
> THURSDAY, November 13, 2003, 1530-1730, Salon A
> 1530 Agenda Bash
>           Chairs
> 1535 End-to-middle security requirements
>           Kumiko Ono
>           draft-ietf-sipping-end2middle-security-reqs-00
> 1545 Mechanism to Secure Information Inserted by Intermediaries
>           Mary Barnes
>           draft-barnes-sipping-sec-inserted-info-01.txt
> 1555 Role-Based Authentication
>           Jon Peterson
>           draft-peterson-sipping-role-authz-01.txt
> 1600 On-demand access authorization for SIP event subscriptions
>           Dirk Trossen
>           draft-trossen-sipping-ondemand-00.txt
> 1610 Early Media
>           Gonzalo Camarillo
>           draft-ietf-sipping-early-media-00.txt
>           draft-camarillo-sipping-early-disposition-00.txt
> 1615 NAT Scenarios
>           Jonathan Rosenberg
>           draft-rosenberg-sipping-nat-scenarios-01 
> [.txt][.html] 1630 IPv4/IPv6 Translators in 3GPP Networks
>           Gonzalo Camarillo
>           draft-elmalki-sipping-3gpp-translator-00.txt
> 1635 Dialog package
>           Rohan Mahy
>           draft-ietf-sipping.dialog-package-03.txt
> 1650 Exploder requirements
>           Gonzalo Camarillo
>           draft-camarillo-sipping-exploders-00.txt
> 1655 Torture Tests
>           Robert Sparks
>           draft-ietf-sipping-torture-tests-01.txt
> 1700 SIP Load Management
>           Robert Sparks
>           draft-sparks-sipping-load-00.txt
> 1710 Event throttles
>           Aki Niemi
>           draft-niemi-sipping-event-throttle-00.txt
> 1720 RTCP Summary
>           Alan Clark
>           draft-sipping-johnston-rtcp-summary-01.txt
> 
> Additional requests will be accomodated if time allows
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov  7 17:31:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11308
	for <sipping-archive@odin.ietf.org>; Fri, 7 Nov 2003 17:31:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIF8H-00074r-BE
	for sipping-archive@odin.ietf.org; Fri, 07 Nov 2003 17:31:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7MV9A0027199
	for sipping-archive@odin.ietf.org; Fri, 7 Nov 2003 17:31:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIF8H-00074c-7z
	for sipping-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 17:31:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11286
	for <sipping-web-archive@ietf.org>; Fri, 7 Nov 2003 17:30:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIF8E-0004E0-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 17:31:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIF8E-0004Dx-00
	for sipping-web-archive@ietf.org; Fri, 07 Nov 2003 17:31:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIF8A-000733-CD; Fri, 07 Nov 2003 17:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIF7a-0006zv-Jh
	for sipping@optimus.ietf.org; Fri, 07 Nov 2003 17:30:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11246;
	Fri, 7 Nov 2003 17:30:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIF7X-0004DO-00; Fri, 07 Nov 2003 17:30:23 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIF7X-0004BT-00; Fri, 07 Nov 2003 17:30:23 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id hA7MTbGd000369;
	Fri, 7 Nov 2003 16:29:37 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <WGQ5L9CG>; Fri, 7 Nov 2003 16:29:36 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E865D3@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: Dean Willis <dwillis@dynamicsoft.com>, sipping@ietf.org, agenda@ietf.org
Cc: rohan@cisco.com, "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Subject: RE: [Sipping] Agenda, SIPPING WG, IETF 58
Date: Fri, 7 Nov 2003 16:29:35 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Minor errata...

draft-schulzrinne-sipping-sos-04.txt

  Draft has expired and is no longer available

draft-ietf-sipping-end2middle-security-reqs-00

  Should be draft-ietf-sipping-e2m-sec-reqs-00.txt

draft-elmalki-sipping-3gpp-translator-00.txt

  Should be draft-elmalki-v6ops-3gpp-translator-00.txt

draft-sipping-johnston-rtcp-summary-01.txt

  Should be draft-johnston-sipping-rtcp-summary-01.txt

/a


> -----Original Message-----
> From: Dean Willis [mailto:dwillis@dynamicsoft.com]
> Sent: Friday, November 07, 2003 15:37
> To: sipping@ietf.org; agenda@ietf.org
> Cc: rohan@cisco.com; 'Gonzalo Camarillo'
> Subject: [Sipping] Agenda, SIPPING WG, IETF 58
> 
> 
> Agenda, SIPPING WG, IETF 59
> 
> TUESDAY, November 11, 2003, 0900-1130, Salon C
> 0900 Angenda Bash
>             Chairs
> 0905 Status of Work
>             Chairs
> 0920 Application Interaction
>           Jonathan Rosenberg
>           draft-ietf-sipping-app-interaction-framework-00.txt
> 0935 Key Press Stimulus Protocol
>           Eric Burger
>           draft-ietf-sipping-kpml-01.txt
> 0945 Event Package for DTMF Signals
>           Joe Zebarth
>           draft-zebarth-sipping-dtmfad-00.txt
> 1000 Conferencing Design Team Report
>           Orit Levin
>           draft-ietf-sipping-conference-package-02.txt
>           draft-ietf-sipping-cc-conferencing-02.txt
> 1015 Transcoding Design Team
>           Gonzalo Camarillo
>           draft-camarillo-sipping-transc-3pcc-00.txt
>           draft-camarillo-sipping-transc-framework-00.txt
>           draft-camarillo-sipping-transc-b2bua-00.txt
>           draft-camarillo-mmusic-source-sink-01.txt
> 1030 Emergency Calls Design Team
>  
> 1040 Event Package for User Configuration Profiles
>           Dan Petrie
>           draft-ietf-sipping-config-framework-01.txt
> 1050 Intermediary Session Policies in SIP
>           Volker Hilt
>           draft-ietf-sipping-session-policy-req-00.txt
>           draft-hilt-sipping-session-indep-policy-00.txt
>           draft-hilt-sipping-session-spec-policy-00.txt
> 1100 Location Conveyance Requirements
>           James Polk
>           draft-polk-sipping-location-requirements-01.txt
>           draft-ietf-geopriv-reqs-04.txt
>           draft-schulzrinne-sipping-sos-04.txt
>           draft-ietf-sipping-session-policy-req-00
>           draft-jennings-sipping-certs-01.txt
> 1110 Reason Header for Preemption
>           James Polk
>           draft-polk-sipping-reason-header-for-preemption-00.txt
>           draft-ietf-sip-resource-priority-01.txt
>           RFC3326
> 
> THURSDAY, November 13, 2003, 1530-1730, Salon A
> 1530 Agenda Bash
>           Chairs
> 1535 End-to-middle security requirements
>           Kumiko Ono
>           draft-ietf-sipping-end2middle-security-reqs-00
> 1545 Mechanism to Secure Information Inserted by Intermediaries
>           Mary Barnes
>           draft-barnes-sipping-sec-inserted-info-01.txt
> 1555 Role-Based Authentication
>           Jon Peterson
>           draft-peterson-sipping-role-authz-01.txt
> 1600 On-demand access authorization for SIP event subscriptions
>           Dirk Trossen
>           draft-trossen-sipping-ondemand-00.txt
> 1610 Early Media
>           Gonzalo Camarillo
>           draft-ietf-sipping-early-media-00.txt
>           draft-camarillo-sipping-early-disposition-00.txt
> 1615 NAT Scenarios
>           Jonathan Rosenberg
>           draft-rosenberg-sipping-nat-scenarios-01 [.txt][.html]
> 1630 IPv4/IPv6 Translators in 3GPP Networks
>           Gonzalo Camarillo
>           draft-elmalki-sipping-3gpp-translator-00.txt
> 1635 Dialog package
>           Rohan Mahy
>           draft-ietf-sipping.dialog-package-03.txt
> 1650 Exploder requirements
>           Gonzalo Camarillo
>           draft-camarillo-sipping-exploders-00.txt
> 1655 Torture Tests
>           Robert Sparks
>           draft-ietf-sipping-torture-tests-01.txt
> 1700 SIP Load Management
>           Robert Sparks
>           draft-sparks-sipping-load-00.txt
> 1710 Event throttles
>           Aki Niemi
>           draft-niemi-sipping-event-throttle-00.txt
> 1720 RTCP Summary
>           Alan Clark
>           draft-sipping-johnston-rtcp-summary-01.txt
> 
> Additional requests will be accomodated if time allows
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov  8 02:08:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02463
	for <sipping-archive@odin.ietf.org>; Sat, 8 Nov 2003 02:08:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AINCh-0005zs-Lj
	for sipping-archive@odin.ietf.org; Sat, 08 Nov 2003 02:08:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA878F6s022868
	for sipping-archive@odin.ietf.org; Sat, 8 Nov 2003 02:08:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AINCd-0005wW-7u
	for sipping-web-archive@optimus.ietf.org; Sat, 08 Nov 2003 02:08:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01970
	for <sipping-web-archive@ietf.org>; Sat, 8 Nov 2003 02:07:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AINCZ-0002dH-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 02:08:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AINCZ-0002dE-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 02:08:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AINCU-0005tK-4c; Sat, 08 Nov 2003 02:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AINBg-0005cM-SR
	for sipping@optimus.ietf.org; Sat, 08 Nov 2003 02:07:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01286
	for <sipping@ietf.org>; Sat, 8 Nov 2003 02:07:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AINBd-0002cl-00
	for sipping@ietf.org; Sat, 08 Nov 2003 02:07:09 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AINBc-0002cc-00
	for sipping@ietf.org; Sat, 08 Nov 2003 02:07:08 -0500
Received: from dynamicsoft.com ([63.113.46.71])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hA876fca013919
	for <sipping@ietf.org>; Sat, 8 Nov 2003 02:06:41 -0500 (EST)
Message-ID: <3FAC9600.6020705@dynamicsoft.com>
Date: Sat, 08 Nov 2003 02:06:40 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Questions and comments on on-demand authorization draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Some questions and comments on:
http://www.ietf.org/internet-drafts/draft-trossen-sipping-ondemand-00.txt

Firstly, to reiterate a question Aki had asked earlier - in what way 
is this not reactive authorization? As far as I can tell it is, 
combined with the desire to provide time limits on the authorization, 
and to try and provide some kind of package-independent authorization 
mechanism. Is that right?

If so, its not clear to me that it really is a good idea to have 
authorization policies and access controls that are independent of the 
package. For almost anything beyond the basic black/white list, the 
details of the authorization policies are one of the main things that 
really varies from package to package.

If the aim is to provide a common mechanism for a basic black/white 
policy independent of the package - I think we can accomodate that 
with a bit of extra text and some hooks in the current xcap-auth spec. 
  In particular, the spec can state that the general structure is 
package independent, and then the <accept> permission has an attribute 
called package that defines the package for which the acceptance is 
granted. The default would be presence.

To provide time limitations to access, you can either remove the 
permission at the appropriate time, or else one can define an xcap 
authorization extension that defines time windows. That has already 
been done in geopriv, btw.

I am not sure that I see what is gained from trying to move towards a 
ticket based system, which appears to be (at least by my reading) the 
preference of the authors. There are a lot of holes that would need to 
be filled in for that to work - much more than getting the 
functionality into xcap.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov  8 11:45:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20399
	for <sipping-archive@odin.ietf.org>; Sat, 8 Nov 2003 11:45:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWCy-0004zb-SO
	for sipping-archive@odin.ietf.org; Sat, 08 Nov 2003 11:45:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA8Gj8KV019187
	for sipping-archive@odin.ietf.org; Sat, 8 Nov 2003 11:45:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWCy-0004zO-OI
	for sipping-web-archive@optimus.ietf.org; Sat, 08 Nov 2003 11:45:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20369
	for <sipping-web-archive@ietf.org>; Sat, 8 Nov 2003 11:44:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWCx-0001Jh-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 11:45:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWCw-0001Je-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 11:45:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWCt-0004yI-6Q; Sat, 08 Nov 2003 11:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWCK-0004xc-GN
	for sipping@optimus.ietf.org; Sat, 08 Nov 2003 11:44:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20358;
	Sat, 8 Nov 2003 11:44:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWCI-0001Ip-00; Sat, 08 Nov 2003 11:44:26 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWCI-0001I5-00; Sat, 08 Nov 2003 11:44:26 -0500
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 08 Nov 2003 08:45:10 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hA8GhrAt007571;
	Sat, 8 Nov 2003 08:43:53 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA19807; Sat, 8 Nov 2003 08:43:51 -0800 (PST)
Message-Id: <4.3.2.7.2.20031108103721.061cf078@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 08 Nov 2003 10:43:51 -0600
To: Adam Roach <adam@dynamicsoft.com>, Dean Willis <dwillis@dynamicsoft.com>,
        sipping@ietf.org, agenda@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Sipping] Agenda, SIPPING WG, IETF 58
Cc: rohan@cisco.com, "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E865D3@dyn-tx-exch-001.dyn
 amicsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Folks

With regard to the two time slots I am presenting in - I am only presenting 
the first ID on each list, namely:

   1100 Location Conveyance Requirements
            James Polk
            draft-polk-sipping-location-requirements-01.txt

and

  1110 Reason Header for Preemption
            James Polk
            draft-polk-sipping-reason-header-for-preemption-00.txt

All the other listed documents in each time slot were given to the Chairs 
as collateral material directly related to the above two IDs.

Sorry for any confusion


At 04:29 PM 11/7/2003 -0600, Adam Roach wrote:
>Minor errata...
>
>draft-schulzrinne-sipping-sos-04.txt
>
>   Draft has expired and is no longer available
>
>draft-ietf-sipping-end2middle-security-reqs-00
>
>   Should be draft-ietf-sipping-e2m-sec-reqs-00.txt
>
>draft-elmalki-sipping-3gpp-translator-00.txt
>
>   Should be draft-elmalki-v6ops-3gpp-translator-00.txt
>
>draft-sipping-johnston-rtcp-summary-01.txt
>
>   Should be draft-johnston-sipping-rtcp-summary-01.txt
>
>/a
>
>
> > -----Original Message-----
> > From: Dean Willis [mailto:dwillis@dynamicsoft.com]
> > Sent: Friday, November 07, 2003 15:37
> > To: sipping@ietf.org; agenda@ietf.org
> > Cc: rohan@cisco.com; 'Gonzalo Camarillo'
> > Subject: [Sipping] Agenda, SIPPING WG, IETF 58
> >
> >
> > Agenda, SIPPING WG, IETF 59
> >
> > TUESDAY, November 11, 2003, 0900-1130, Salon C
> > 0900 Angenda Bash
> >             Chairs
> > 0905 Status of Work
> >             Chairs
> > 0920 Application Interaction
> >           Jonathan Rosenberg
> >           draft-ietf-sipping-app-interaction-framework-00.txt
> > 0935 Key Press Stimulus Protocol
> >           Eric Burger
> >           draft-ietf-sipping-kpml-01.txt
> > 0945 Event Package for DTMF Signals
> >           Joe Zebarth
> >           draft-zebarth-sipping-dtmfad-00.txt
> > 1000 Conferencing Design Team Report
> >           Orit Levin
> >           draft-ietf-sipping-conference-package-02.txt
> >           draft-ietf-sipping-cc-conferencing-02.txt
> > 1015 Transcoding Design Team
> >           Gonzalo Camarillo
> >           draft-camarillo-sipping-transc-3pcc-00.txt
> >           draft-camarillo-sipping-transc-framework-00.txt
> >           draft-camarillo-sipping-transc-b2bua-00.txt
> >           draft-camarillo-mmusic-source-sink-01.txt
> > 1030 Emergency Calls Design Team
> >
> > 1040 Event Package for User Configuration Profiles
> >           Dan Petrie
> >           draft-ietf-sipping-config-framework-01.txt
> > 1050 Intermediary Session Policies in SIP
> >           Volker Hilt
> >           draft-ietf-sipping-session-policy-req-00.txt
> >           draft-hilt-sipping-session-indep-policy-00.txt
> >           draft-hilt-sipping-session-spec-policy-00.txt
> > 1100 Location Conveyance Requirements
> >           James Polk
> >           draft-polk-sipping-location-requirements-01.txt
> >           draft-ietf-geopriv-reqs-04.txt
> >           draft-schulzrinne-sipping-sos-04.txt
> >           draft-ietf-sipping-session-policy-req-00
> >           draft-jennings-sipping-certs-01.txt
> > 1110 Reason Header for Preemption
> >           James Polk
> >           draft-polk-sipping-reason-header-for-preemption-00.txt
> >           draft-ietf-sip-resource-priority-01.txt
> >           RFC3326
> >
> > THURSDAY, November 13, 2003, 1530-1730, Salon A
> > 1530 Agenda Bash
> >           Chairs
> > 1535 End-to-middle security requirements
> >           Kumiko Ono
> >           draft-ietf-sipping-end2middle-security-reqs-00
> > 1545 Mechanism to Secure Information Inserted by Intermediaries
> >           Mary Barnes
> >           draft-barnes-sipping-sec-inserted-info-01.txt
> > 1555 Role-Based Authentication
> >           Jon Peterson
> >           draft-peterson-sipping-role-authz-01.txt
> > 1600 On-demand access authorization for SIP event subscriptions
> >           Dirk Trossen
> >           draft-trossen-sipping-ondemand-00.txt
> > 1610 Early Media
> >           Gonzalo Camarillo
> >           draft-ietf-sipping-early-media-00.txt
> >           draft-camarillo-sipping-early-disposition-00.txt
> > 1615 NAT Scenarios
> >           Jonathan Rosenberg
> >           draft-rosenberg-sipping-nat-scenarios-01 [.txt][.html]
> > 1630 IPv4/IPv6 Translators in 3GPP Networks
> >           Gonzalo Camarillo
> >           draft-elmalki-sipping-3gpp-translator-00.txt
> > 1635 Dialog package
> >           Rohan Mahy
> >           draft-ietf-sipping.dialog-package-03.txt
> > 1650 Exploder requirements
> >           Gonzalo Camarillo
> >           draft-camarillo-sipping-exploders-00.txt
> > 1655 Torture Tests
> >           Robert Sparks
> >           draft-ietf-sipping-torture-tests-01.txt
> > 1700 SIP Load Management
> >           Robert Sparks
> >           draft-sparks-sipping-load-00.txt
> > 1710 Event throttles
> >           Aki Niemi
> >           draft-niemi-sipping-event-throttle-00.txt
> > 1720 RTCP Summary
> >           Alan Clark
> >           draft-sipping-johnston-rtcp-summary-01.txt
> >
> > Additional requests will be accomodated if time allows
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov  8 11:56:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20725
	for <sipping-archive@odin.ietf.org>; Sat, 8 Nov 2003 11:56:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWNZ-0005XM-Jk
	for sipping-archive@odin.ietf.org; Sat, 08 Nov 2003 11:56:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA8Gu5q6021281
	for sipping-archive@odin.ietf.org; Sat, 8 Nov 2003 11:56:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWNZ-0005XA-Gm
	for sipping-web-archive@optimus.ietf.org; Sat, 08 Nov 2003 11:56:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20706
	for <sipping-web-archive@ietf.org>; Sat, 8 Nov 2003 11:55:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWNY-0001VB-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 11:56:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWNX-0001V8-00
	for sipping-web-archive@ietf.org; Sat, 08 Nov 2003 11:56:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWNX-0005W1-6e; Sat, 08 Nov 2003 11:56:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIWMn-0005VL-9s
	for sipping@optimus.ietf.org; Sat, 08 Nov 2003 11:55:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20693
	for <sipping@ietf.org>; Sat, 8 Nov 2003 11:55:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWMm-0001Ug-00
	for sipping@ietf.org; Sat, 08 Nov 2003 11:55:16 -0500
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIWMl-0001UY-00
	for sipping@ietf.org; Sat, 08 Nov 2003 11:55:15 -0500
Received: from magnum.cs.columbia.edu (IDENT:root@magnum.cs.columbia.edu [128.59.16.117])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hA8GrdhL029826;
	Sat, 8 Nov 2003 11:54:14 -0500 (EST)
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	by magnum.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id hA8Grdg15863;
	Sat, 8 Nov 2003 11:53:39 -0500
Message-ID: <3FAD1F92.8000903@cs.columbia.edu>
Date: Sat, 08 Nov 2003 11:53:38 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Questions and comments on on-demand authorization draft
References: <3FAC9600.6020705@dynamicsoft.com>
In-Reply-To: <3FAC9600.6020705@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This is clearly a very early discussion document, rather than 
necessarily a way forward. The principal issue, I believe, is one of 
getting the timing right. If I hand you a token, you can immediately 
access the resource as soon as you have the token. If I need to update a 
permissions file (e.g., XCAP), I need to tell you "please wait some time 
before you try accessing the resource, to make sure you don't get 
rejected" or you would have to have a feedback mechanism that says "ok, 
please try now, you're in the list".

I'm not sure whether this synchronization problem is sufficiently large 
in practice to warrant a new mechanism. The document tries to raise that 
discussion.

Jonathan Rosenberg wrote:

> Some questions and comments on:
> http://www.ietf.org/internet-drafts/draft-trossen-sipping-ondemand-00.txt
> 
> Firstly, to reiterate a question Aki had asked earlier - in what way is 
> this not reactive authorization? As far as I can tell it is, combined 
> with the desire to provide time limits on the authorization, and to try 
> and provide some kind of package-independent authorization mechanism. Is 
> that right?
> 
> If so, its not clear to me that it really is a good idea to have 
> authorization policies and access controls that are independent of the 
> package. For almost anything beyond the basic black/white list, the 
> details of the authorization policies are one of the main things that 
> really varies from package to package.
> 
> If the aim is to provide a common mechanism for a basic black/white 
> policy independent of the package - I think we can accomodate that with 
> a bit of extra text and some hooks in the current xcap-auth spec.  In 
> particular, the spec can state that the general structure is package 
> independent, and then the <accept> permission has an attribute called 
> package that defines the package for which the acceptance is granted. 
> The default would be presence.
> 
> To provide time limitations to access, you can either remove the 
> permission at the appropriate time, or else one can define an xcap 
> authorization extension that defines time windows. That has already been 
> done in geopriv, btw.
> 
> I am not sure that I see what is gained from trying to move towards a 
> ticket based system, which appears to be (at least by my reading) the 
> preference of the authors. There are a lot of holes that would need to 
> be filled in for that to work - much more than getting the functionality 
> into xcap.
> 
> Thanks,
> Jonathan R.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov  9 15:24:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09467
	for <sipping-archive@odin.ietf.org>; Sun, 9 Nov 2003 15:24:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIw6b-0002q2-AP
	for sipping-archive@odin.ietf.org; Sun, 09 Nov 2003 15:24:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA9KOHSm010909
	for sipping-archive@odin.ietf.org; Sun, 9 Nov 2003 15:24:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIw6b-0002ps-6L
	for sipping-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 15:24:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09461
	for <sipping-web-archive@ietf.org>; Sun, 9 Nov 2003 15:24:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIw6Z-0006Yp-00
	for sipping-web-archive@ietf.org; Sun, 09 Nov 2003 15:24:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIw6Z-0006Yl-00
	for sipping-web-archive@ietf.org; Sun, 09 Nov 2003 15:24:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIw6L-0002oc-JW; Sun, 09 Nov 2003 15:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIw6D-0002oP-4D
	for sipping@optimus.ietf.org; Sun, 09 Nov 2003 15:23:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09443;
	Sun, 9 Nov 2003 15:23:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIw6A-0006Yb-00; Sun, 09 Nov 2003 15:23:50 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIw69-0006YY-00; Sun, 09 Nov 2003 15:23:49 -0500
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hA9KNfI2020552;
	Sun, 9 Nov 2003 21:23:41 +0100 (MET)
Received: from ericsson.com (EFO9N000L5C7100 [153.88.94.55]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id V6N3CX2L; Sun, 9 Nov 2003 21:23:40 +0100
Message-ID: <3FAEA249.7060306@ericsson.com>
Date: Sun, 09 Nov 2003 14:23:37 -0600
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@dynamicsoft.com>
CC: Dean Willis <dwillis@dynamicsoft.com>, sipping@ietf.org, agenda@ietf.org,
        rohan@cisco.com
Subject: Re: [Sipping] Agenda, SIPPING WG, IETF 58
References: <9BF66EBF6BEFD942915B4D4D45C051F3E865D3@dyn-tx-exch-001.dynamicsoft.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E865D3@dyn-tx-exch-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fixed.

http://www.softarmor.com/sipping/meets/ietf58/agenda.html

Thanks,

Gonzalo

Adam Roach wrote:

> Minor errata...
> 
> draft-schulzrinne-sipping-sos-04.txt
> 
>   Draft has expired and is no longer available
> 
> draft-ietf-sipping-end2middle-security-reqs-00
> 
>   Should be draft-ietf-sipping-e2m-sec-reqs-00.txt
> 
> draft-elmalki-sipping-3gpp-translator-00.txt
> 
>   Should be draft-elmalki-v6ops-3gpp-translator-00.txt
> 
> draft-sipping-johnston-rtcp-summary-01.txt
> 
>   Should be draft-johnston-sipping-rtcp-summary-01.txt
> 
> /a
> 
> 
> 
>>-----Original Message-----
>>From: Dean Willis [mailto:dwillis@dynamicsoft.com]
>>Sent: Friday, November 07, 2003 15:37
>>To: sipping@ietf.org; agenda@ietf.org
>>Cc: rohan@cisco.com; 'Gonzalo Camarillo'
>>Subject: [Sipping] Agenda, SIPPING WG, IETF 58
>>
>>
>>Agenda, SIPPING WG, IETF 59
>>
>>TUESDAY, November 11, 2003, 0900-1130, Salon C
>>0900 Angenda Bash
>>            Chairs
>>0905 Status of Work
>>            Chairs
>>0920 Application Interaction
>>          Jonathan Rosenberg
>>          draft-ietf-sipping-app-interaction-framework-00.txt
>>0935 Key Press Stimulus Protocol
>>          Eric Burger
>>          draft-ietf-sipping-kpml-01.txt
>>0945 Event Package for DTMF Signals
>>          Joe Zebarth
>>          draft-zebarth-sipping-dtmfad-00.txt
>>1000 Conferencing Design Team Report
>>          Orit Levin
>>          draft-ietf-sipping-conference-package-02.txt
>>          draft-ietf-sipping-cc-conferencing-02.txt
>>1015 Transcoding Design Team
>>          Gonzalo Camarillo
>>          draft-camarillo-sipping-transc-3pcc-00.txt
>>          draft-camarillo-sipping-transc-framework-00.txt
>>          draft-camarillo-sipping-transc-b2bua-00.txt
>>          draft-camarillo-mmusic-source-sink-01.txt
>>1030 Emergency Calls Design Team
>> 
>>1040 Event Package for User Configuration Profiles
>>          Dan Petrie
>>          draft-ietf-sipping-config-framework-01.txt
>>1050 Intermediary Session Policies in SIP
>>          Volker Hilt
>>          draft-ietf-sipping-session-policy-req-00.txt
>>          draft-hilt-sipping-session-indep-policy-00.txt
>>          draft-hilt-sipping-session-spec-policy-00.txt
>>1100 Location Conveyance Requirements
>>          James Polk
>>          draft-polk-sipping-location-requirements-01.txt
>>          draft-ietf-geopriv-reqs-04.txt
>>          draft-schulzrinne-sipping-sos-04.txt
>>          draft-ietf-sipping-session-policy-req-00
>>          draft-jennings-sipping-certs-01.txt
>>1110 Reason Header for Preemption
>>          James Polk
>>          draft-polk-sipping-reason-header-for-preemption-00.txt
>>          draft-ietf-sip-resource-priority-01.txt
>>          RFC3326
>>
>>THURSDAY, November 13, 2003, 1530-1730, Salon A
>>1530 Agenda Bash
>>          Chairs
>>1535 End-to-middle security requirements
>>          Kumiko Ono
>>          draft-ietf-sipping-end2middle-security-reqs-00
>>1545 Mechanism to Secure Information Inserted by Intermediaries
>>          Mary Barnes
>>          draft-barnes-sipping-sec-inserted-info-01.txt
>>1555 Role-Based Authentication
>>          Jon Peterson
>>          draft-peterson-sipping-role-authz-01.txt
>>1600 On-demand access authorization for SIP event subscriptions
>>          Dirk Trossen
>>          draft-trossen-sipping-ondemand-00.txt
>>1610 Early Media
>>          Gonzalo Camarillo
>>          draft-ietf-sipping-early-media-00.txt
>>          draft-camarillo-sipping-early-disposition-00.txt
>>1615 NAT Scenarios
>>          Jonathan Rosenberg
>>          draft-rosenberg-sipping-nat-scenarios-01 [.txt][.html]
>>1630 IPv4/IPv6 Translators in 3GPP Networks
>>          Gonzalo Camarillo
>>          draft-elmalki-sipping-3gpp-translator-00.txt
>>1635 Dialog package
>>          Rohan Mahy
>>          draft-ietf-sipping.dialog-package-03.txt
>>1650 Exploder requirements
>>          Gonzalo Camarillo
>>          draft-camarillo-sipping-exploders-00.txt
>>1655 Torture Tests
>>          Robert Sparks
>>          draft-ietf-sipping-torture-tests-01.txt
>>1700 SIP Load Management
>>          Robert Sparks
>>          draft-sparks-sipping-load-00.txt
>>1710 Event throttles
>>          Aki Niemi
>>          draft-niemi-sipping-event-throttle-00.txt
>>1720 RTCP Summary
>>          Alan Clark
>>          draft-sipping-johnston-rtcp-summary-01.txt
>>
>>Additional requests will be accomodated if time allows
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

-- 
Gonzalo Camarillo         Phone :  +358  9 299 33 71
Oy L M Ericsson Ab        Mobile:  +358 40 702 35 35
Telecom R&D               Fax   :  +358  9 299 30 52
FIN-02420 Jorvas          Email :  Gonzalo.Camarillo@ericsson.com
Finland                   http://www.hut.fi/~gonzalo


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov  9 15:49:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10049
	for <sipping-archive@odin.ietf.org>; Sun, 9 Nov 2003 15:49:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIwUb-0004F5-1F
	for sipping-archive@odin.ietf.org; Sun, 09 Nov 2003 15:49:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA9Kn5Rx016301
	for sipping-archive@odin.ietf.org; Sun, 9 Nov 2003 15:49:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIwUa-0004Eq-Sr
	for sipping-web-archive@optimus.ietf.org; Sun, 09 Nov 2003 15:49:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10040
	for <sipping-web-archive@ietf.org>; Sun, 9 Nov 2003 15:48:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIwUZ-0006t1-00
	for sipping-web-archive@ietf.org; Sun, 09 Nov 2003 15:49:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIwUY-0006sy-00
	for sipping-web-archive@ietf.org; Sun, 09 Nov 2003 15:49:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIwUX-0004Df-LF; Sun, 09 Nov 2003 15:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AIwUB-0004Bu-68
	for sipping@optimus.ietf.org; Sun, 09 Nov 2003 15:48:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10027
	for <sipping@ietf.org>; Sun, 9 Nov 2003 15:48:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIwU9-0006se-00
	for sipping@ietf.org; Sun, 09 Nov 2003 15:48:37 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AIwU9-0006sb-00
	for sipping@ietf.org; Sun, 09 Nov 2003 15:48:37 -0500
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hA9KjlI2022062;
	Sun, 9 Nov 2003 21:45:47 +0100 (MET)
Received: from ericsson.com (EFO9N000L5C7100 [153.88.94.55]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id V63FXW8P; Sun, 9 Nov 2003 21:46:19 +0100
Message-ID: <3FAEA779.7060004@ericsson.com>
Date: Sun, 09 Nov 2003 14:45:45 -0600
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Rohan Mahy <rohan@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Slides
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

we have already started receiving slides. They are available at:
http://www.softarmor.com/sipping/meets/ietf58/slides/

We encourage all the presenters to send them to the chairs before the 
meeting so that we can upload them to our supplementary site.

Thanks,

Gonzalo


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 02:20:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10857
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 02:20:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJ6LY-0004u2-T3
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 02:20:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAA7KOC3018847
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 02:20:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJ6LY-0004tu-Hc
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 02:20:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10808
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 02:20:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJ6LU-0000LJ-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 02:20:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJ6LU-0000LG-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 02:20:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJ6LD-0004s9-Cb; Mon, 10 Nov 2003 02:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJ6KM-0004qc-TG
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 02:19:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10702
	for <sipping@ietf.org>; Mon, 10 Nov 2003 02:18:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJ6KI-0000LB-00
	for sipping@ietf.org; Mon, 10 Nov 2003 02:19:06 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJ6KI-0000L5-00
	for sipping@ietf.org; Mon, 10 Nov 2003 02:19:06 -0500
Received: from dynamicsoft.com ([63.113.46.126])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hAA7IWca014510;
	Mon, 10 Nov 2003 02:18:33 -0500 (EST)
Message-ID: <3FAF3BC6.9030409@dynamicsoft.com>
Date: Mon, 10 Nov 2003 02:18:30 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Questions and comments on on-demand authorization draft
References: <3FAC9600.6020705@dynamicsoft.com> <3FAD1F92.8000903@cs.columbia.edu>
In-Reply-To: <3FAD1F92.8000903@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:

> This is clearly a very early discussion document, rather than 
> necessarily a way forward. The principal issue, I believe, is one of 
> getting the timing right. If I hand you a token, you can immediately 
> access the resource as soon as you have the token. If I need to update a 
> permissions file (e.g., XCAP), I need to tell you "please wait some time 
> before you try accessing the resource, to make sure you don't get 
> rejected" or you would have to have a feedback mechanism that says "ok, 
> please try now, you're in the list".

With rfc3265, we have exactly this capability. The NOTIFY can indicate 
that the subscription state has moved from active to pending.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 08:54:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19442
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUe-0004Wv-BQ
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsCDm017360
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUd-0004Ve-Ky
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19414
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:53:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004if-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004iU-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUZ-0004QZ-7z; Mon, 10 Nov 2003 08:54:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTk-0004Nf-T5
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19365
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:53:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTj-0004hX-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:15 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTj-0004gt-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:15 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqcmW028177
	for <sipping@ietf.org>; Mon, 10 Nov 2003 05:52:39 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61059;
	Mon, 10 Nov 2003 05:52:37 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 21:41:35 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BBD4650F.2407B%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Why draft-zebarth-sipping-dtmfad?
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Seems there have been several other drafts on this problem including one
that is remarkably similar.  Any particular problems this solves that KPML
does not?


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 08:54:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19446
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUe-0004XK-E5
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsCek017346
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUd-0004VW-D4
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19409
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:53:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004ic-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004iT-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUW-0004PH-EK; Mon, 10 Nov 2003 08:54:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTi-0004NQ-Lz
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19356
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:53:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTf-0004hJ-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:11 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTf-0004gs-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:11 -0500
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 10 Nov 2003 05:58:53 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqew5021070;
	Mon, 10 Nov 2003 05:52:40 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61062;
	Mon, 10 Nov 2003 05:52:38 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 21:56:08 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>, Dan Petrie <dpetrie@pingtel.com>
Message-ID: <BBD46878.2407F%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-config-framework
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Like it - one little NIT in discover stage...

The manual configuration needs to override the DHCP or well known DNS name
approach. 
 
Cullen


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 08:54:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19450
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUe-0004X6-CC
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsCE0017371
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUd-0004Vd-Kl
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19403
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:53:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004iZ-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004iR-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUX-0004Q5-JK; Mon, 10 Nov 2003 08:54:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTk-0004Na-PN
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19362
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:53:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTj-0004hT-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:15 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTi-0004gt-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:14 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqdAt007549;
	Mon, 10 Nov 2003 05:52:39 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61060;
	Mon, 10 Nov 2003 05:52:37 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 21:52:11 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>, Robert Sparks <rsparks@dynamicsoft.com>
Message-ID: <BBD4678B.2407D%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-sparks-sipping-load
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I think the user experience of a GW shedding load with a REFER would be
awful. 

DNS works for many of these problems without adding SIP redirects. I don't
think I am sold yet on the redirect, refer or modify route sets. I find GAP
an interesting way to send backpressure up the chain of hops. If a proxy
throttles to only read x messages per second from a given previous hop, does
it result in more or less the same thing in the long run.

Cullen



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 08:54:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19485
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUf-0004Yw-QI
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsDWd017496
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUf-0004Y1-CT
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19429
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:54:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUd-0004is-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUd-0004ip-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUd-0004Vk-Rj; Mon, 10 Nov 2003 08:54:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTn-0004Nq-8f
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19375
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:53:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTl-0004hp-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:17 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTl-0004gt-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:17 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqgAt007599;
	Mon, 10 Nov 2003 05:52:42 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61066;
	Mon, 10 Nov 2003 05:52:41 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 22:38:46 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: Scott Lawrence <slawrence@pingtel.com>,
        Dean Willis <dean.willis@softarmor.com>, sipping <sipping@ietf.org>
Message-ID: <BBD47276.2408A%fluffy@cisco.com>
In-Reply-To: <m31xsl88kx.fsf@kathmandu.pingtel.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: [Sip] Re: Consensus on direction needed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On 11/6/03 1:56 PM, "Scott Lawrence" <slawrence@pingtel.com> wrote:

> Dean Willis <dean.willis@softarmor.com> writes:
> 
>> The security people aren't going to give up on e2e.
> 
> Which is not the same thing as saying that users will use it... but
> that's a different discussion.
> 

What would be the requirements such that users will use it?



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 09:48:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19443
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUe-0004Xe-HL
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsCPZ017345
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUd-0004VP-7s
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19399
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:53:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUb-0004iN-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUa-0004iJ-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUU-0004Og-0I; Mon, 10 Nov 2003 08:54:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTg-0004NL-KF
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19353
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:52:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTf-0004hD-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:11 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTe-0004gs-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:10 -0500
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 10 Nov 2003 05:58:51 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqcmU028177
	for <sipping@ietf.org>; Mon, 10 Nov 2003 05:52:38 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61058;
	Mon, 10 Nov 2003 05:52:36 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 21:38:31 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BBD46457.24079%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] olson-sipping-refer-extensions  tail wagging the dog?
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

   
Mostly like this stuff but one thing I think *might* cause some problems...

Signaling (such as the phone sending a 200) is an artifact of something that
happened on the phone - such as it got answered. By telling the phone to do
the artifact, the phone might have to guess what the root cause operation to
cause that artifact is.

For example, my phone might send a 200 in two different cases. One is where
it some goes hits the speaker phone button when it is ringing. The other is
when it has rung for 10 seconds and it answers, plays a prompt and records a
message and emails it to me. If the phone gets a refer telling it to send a
200 to some ringing call - the phone will need to guess if it should go off
hook in speaker phone mode or use voice mail mode. I know this is a somewhat
contrived example but I think you get the idea that refer is using a
signaling artifact to request a basic operation and that might lead to
ambiguous cases. I see the 200 as the tail and the speaker phone button as
the dog.

Cullen




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 09:48:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19513
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 08:54:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUh-0004a4-59
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAADsFwW017581
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 08:54:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUh-0004ZU-05
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 08:54:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19435
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 08:54:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUf-0004iy-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCUf-0004iv-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 08:54:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCUf-0004Y7-Il; Mon, 10 Nov 2003 08:54:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJCTm-0004Nl-QQ
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 08:53:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19371
	for <sipping@ietf.org>; Mon, 10 Nov 2003 08:53:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTl-0004hi-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:17 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJCTk-0004gt-00
	for sipping@ietf.org; Mon, 10 Nov 2003 08:53:17 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAADqew7021070;
	Mon, 10 Nov 2003 05:52:42 -0800 (PST)
Received: from [130.129.142.157] (sjc-vpn1-121.cisco.com [10.21.96.121])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJU61063;
	Mon, 10 Nov 2003 05:52:39 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sun, 09 Nov 2003 22:13:45 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>,
        Rohan Mahy <rmahy@cisco.com>
Message-ID: <BBD46C99.24081%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] State machine in draft-ietf-sipping-dialog-package
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I think the state machine is confusing and not very accurate from the point
of view of this draft. When I look at the state machines for real UA, I seem
some more states.

Starting -> in this state, the UA has not sent and INVITE yet but is doing
something like collecting digits and getting ready to send an INVITE. The
line is busy from an incoming call point of view.

Terminating-Local -> The UA has sent a BYE but not yet received a 200 for
it. 

Some additional states that might clarify things (and remove some strange
things in the package are )

Terminated-Remote -> The UA received a BYE and has sent a 200 but still has
state around for retransmissions and such.

Terminated-Error -> This includes the timeout error

Terminated-Replaced

We have to figure out how to deal with the state transition between
Terminated and Gone.

Gone -> This is not a state. At this point the UA has erased all state about
the dialog including the fact that the dialog ever existed.

State machines that support preconditions are more complex.


Should think about the structure of the scheme from a extension point of
view - can we subclass the right things? extend the right things?

I am confused on how to form the dialog-id

How refer-by works is not real clear

The identity with the display name parameter and URI separate is goofy.
Contrast this the Target definition which I like.

Agree that CSEQ sound scary.

Not sure how I request SDP or not.

typo in schema - identity type missing tns namespace


Sorry for the disconnected email but I think sorting out the state machine
would help sort out everything else in this draft.

Cullen





_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 10:34:15 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24740
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 10:34:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJE3D-0002MR-9Y
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 10:33:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAFXxJZ009069
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 10:33:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJE3D-0002MC-5Z
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 10:33:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24700
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 10:33:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJE37-000674-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 10:33:53 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJE37-000668-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 10:33:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJE2H-00023W-CV; Mon, 10 Nov 2003 10:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJE1a-0001xH-Nn
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 10:32:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24588
	for <sipping@ietf.org>; Mon, 10 Nov 2003 10:32:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJE1Y-00065o-00
	for sipping@ietf.org; Mon, 10 Nov 2003 10:32:16 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJE1X-00065Q-00
	for sipping@ietf.org; Mon, 10 Nov 2003 10:32:15 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAAFVfAt024363;
	Mon, 10 Nov 2003 07:31:41 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-1-66.cisco.com [10.86.240.66])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ADW03732;
	Mon, 10 Nov 2003 10:31:39 -0500 (EST)
Message-ID: <3FAFAF5B.30504@cisco.com>
Date: Mon, 10 Nov 2003 10:31:39 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] olson-sipping-refer-extensions  tail wagging the dog?
References: <BBD46457.24079%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Cullen,

I agree with you. This isn't just restricted to referring responses. 
There is a general issue that the semantics of REFER are underspecified.

- when I send a REFER of an INVITE *in* an existing call dialog,
   I believe there is an assumption in the published call flows
   that the resulting new call will supercede the old one, taking
   over the media resources of that call. But AFAIK that assumption
   isn't written down, much less normative.

- when a REFER is sent to a phone, independently of any existing dialog,
   a lot of different things could happen, similar to what you mention
   blow for sending a 200:
   . the phone could alert, await acceptance by a local user,
     and then send the INVITE;
   . the phone could alert the local user and send the INVITE in
     parallel. If the Refer-To user answers first, that call could
     then hear ringback until the local user answers;
   . a speakerphone could be enabled, and then the INVITE sent;
   . ...
   It is hard to know how the feature can be used without knowing
   something of the semantics it will yield.

- there have been proposals for more exotic REFER uses, such as
   REFER of a GET method with an http url. While one can imagine some
   plausible semantics for this, it is again in general difficult to
   imagine how to use this capability without additional normative
   behavior.

So, I think there is a general issue of the semantics of REFER that 
needs to be beefed up.

	Paul

Cullen Jennings wrote:
>    
> Mostly like this stuff but one thing I think *might* cause some problems...
> 
> Signaling (such as the phone sending a 200) is an artifact of something that
> happened on the phone - such as it got answered. By telling the phone to do
> the artifact, the phone might have to guess what the root cause operation to
> cause that artifact is.
> 
> For example, my phone might send a 200 in two different cases. One is where
> it some goes hits the speaker phone button when it is ringing. The other is
> when it has rung for 10 seconds and it answers, plays a prompt and records a
> message and emails it to me. If the phone gets a refer telling it to send a
> 200 to some ringing call - the phone will need to guess if it should go off
> hook in speaker phone mode or use voice mail mode. I know this is a somewhat
> contrived example but I think you get the idea that refer is using a
> signaling artifact to request a basic operation and that might lead to
> ambiguous cases. I see the 200 as the tail and the speaker phone button as
> the dog.
> 
> Cullen
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 11:10:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27204
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 11:10:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJEcE-0005ZI-P6
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:10:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAGAAjH021398
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:10:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJEcE-0005Z3-Ln
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 11:10:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27174
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 11:09:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJEcC-0006yA-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:10:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJEcB-0006y7-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:10:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJEc6-0005Xi-Hl; Mon, 10 Nov 2003 11:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJEbp-0005Wv-HK
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 11:09:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27163
	for <sipping@ietf.org>; Mon, 10 Nov 2003 11:09:30 -0500 (EST)
From: Dirk.Trossen@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJEbm-0006xq-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:09:42 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJEbm-0006xn-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:09:42 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAAG9eJ02122
	for <sipping@ietf.org>; Mon, 10 Nov 2003 18:09:40 +0200 (EET)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65d33e6c6aac158f25076@esvir05nok.ntc.nokia.com>;
 Mon, 10 Nov 2003 18:09:40 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 10 Nov 2003 10:09:20 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Questions and comments on on-demand authorization draft
Date: Mon, 10 Nov 2003 11:09:16 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB012460011CC7DE@bsebe001.americas.nokia.com>
Thread-Topic: [Sipping] Questions and comments on on-demand authorization draft
Thread-Index: AcOnWzUutljnIX84TVGS3Pc+FnzXSQASEjuQ
To: <jdrosen@dynamicsoft.com>, <hgs@cs.columbia.edu>
Cc: <sipping@ietf.org>
X-OriginalArrivalTime: 10 Nov 2003 16:09:20.0420 (UTC) FILETIME=[FFC6CE40:01C3A7A4]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Jonathan,

As Henning stated, the draft does not try to promote certain solutions =
(apologies if you read a certain preference for a ticket-based solution =
in there). It merely tries to identify if there are specific problems in =
current solutions wrt the presented scenarios.

The timing of access with setting the authorization is one them, as =
Henning pointed out. Binding the authorization to a particular =
subscription and the time window issues are other ones, characteristic =
for the presented scenarios.

Again, the overview of the solution space is not intended to promote a =
certain solution. Instead, the major objective of the draft is to =
outline possible problems and to find (if the WG agrees that these =
problems need to be addressed) a preferable direction to go ahead. Once =
this direction is found, we can look more deeply into what particular =
problems this solution would have wrt supporting the scenarios.

Thanks,

Dirk

>-----Original Message-----
>From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On=20
>Behalf Of
>ext Jonathan Rosenberg
>Sent: Monday, November 10, 2003 2:19 AM
>To: Henning Schulzrinne
>Cc: sipping
>Subject: Re: [Sipping] Questions and comments on on-demand=20
>authorization
>draft
>
>
>
>
>Henning Schulzrinne wrote:
>
>> This is clearly a very early discussion document, rather than=20
>> necessarily a way forward. The principal issue, I believe, is one of=20
>> getting the timing right. If I hand you a token, you can immediately=20
>> access the resource as soon as you have the token. If I need=20
>to update a=20
>> permissions file (e.g., XCAP), I need to tell you "please=20
>wait some time=20
>> before you try accessing the resource, to make sure you don't get=20
>> rejected" or you would have to have a feedback mechanism=20
>that says "ok,=20
>> please try now, you're in the list".
>
>With rfc3265, we have exactly this capability. The NOTIFY can indicate=20
>that the subscription state has moved from active to pending.
>
>-Jonathan R.
>
>--=20
>Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
>Chief Technology Officer                    Parsippany, NJ 07054-2711
>dynamicsoft
>jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
>http://www.jdrosen.net                      PHONE: (973) 952-5000
>http://www.dynamicsoft.com
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 11:38:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28882
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 11:38:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJF3G-0007ep-WD
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:38:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAGc6oO029424
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:38:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJF3G-0007eT-Lt
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 11:38:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28867
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 11:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJF3F-0007a2-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:38:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJF3F-0007Zz-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:38:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJF3B-0007c0-N2; Mon, 10 Nov 2003 11:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJF31-0007ZH-0d
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 11:37:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28860
	for <sipping@ietf.org>; Mon, 10 Nov 2003 11:37:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJF2z-0007Zg-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:37:49 -0500
Received: from smtp015.mail.yahoo.com ([216.136.173.59])
	by ietf-mx with smtp (Exim 4.12)
	id 1AJF2z-0007Zd-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:37:49 -0500
Received: from 12-235-146-159.client.attbi.com (HELO cranberry) (seancolson@12.235.146.159 with login)
  by smtp-v1.mail.vip.sc5.yahoo.com with SMTP; 10 Nov 2003 16:37:47 -0000
Reply-To: <seancolson@yahoo.com>
From: "Sean Olson" <seancolson@yahoo.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>,
        "'Cullen Jennings'" <fluffy@cisco.com>
Cc: "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] olson-sipping-refer-extensions  tail wagging the dog?
Date: Mon, 10 Nov 2003 08:37:48 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <3FAFAF5B.30504@cisco.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcOnoAqL3rYv7MUrToODgCNuOZic7QACMB2Q
Message-Id: <E1AJF2z-0007Zd-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I can see the potential for ambiguity here. Is it time to update the REFER
RFC with tighter semantics? 

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf Of
Paul Kyzivat
Sent: Monday, November 10, 2003 7:32 AM
To: Cullen Jennings
Cc: sipping
Subject: Re: [Sipping] olson-sipping-refer-extensions tail wagging the dog?

Cullen,

I agree with you. This isn't just restricted to referring responses. 
There is a general issue that the semantics of REFER are underspecified.

- when I send a REFER of an INVITE *in* an existing call dialog,
   I believe there is an assumption in the published call flows
   that the resulting new call will supercede the old one, taking
   over the media resources of that call. But AFAIK that assumption
   isn't written down, much less normative.

- when a REFER is sent to a phone, independently of any existing dialog,
   a lot of different things could happen, similar to what you mention
   blow for sending a 200:
   . the phone could alert, await acceptance by a local user,
     and then send the INVITE;
   . the phone could alert the local user and send the INVITE in
     parallel. If the Refer-To user answers first, that call could
     then hear ringback until the local user answers;
   . a speakerphone could be enabled, and then the INVITE sent;
   . ...
   It is hard to know how the feature can be used without knowing
   something of the semantics it will yield.

- there have been proposals for more exotic REFER uses, such as
   REFER of a GET method with an http url. While one can imagine some
   plausible semantics for this, it is again in general difficult to
   imagine how to use this capability without additional normative
   behavior.

So, I think there is a general issue of the semantics of REFER that needs to
be beefed up.

	Paul

Cullen Jennings wrote:
>    
> Mostly like this stuff but one thing I think *might* cause some
problems...
> 
> Signaling (such as the phone sending a 200) is an artifact of 
> something that happened on the phone - such as it got answered. By 
> telling the phone to do the artifact, the phone might have to guess 
> what the root cause operation to cause that artifact is.
> 
> For example, my phone might send a 200 in two different cases. One is 
> where it some goes hits the speaker phone button when it is ringing. 
> The other is when it has rung for 10 seconds and it answers, plays a 
> prompt and records a message and emails it to me. If the phone gets a 
> refer telling it to send a 200 to some ringing call - the phone will 
> need to guess if it should go off hook in speaker phone mode or use 
> voice mail mode. I know this is a somewhat contrived example but I 
> think you get the idea that refer is using a signaling artifact to 
> request a basic operation and that might lead to ambiguous cases. I 
> see the 200 as the tail and the speaker phone button as the dog.
> 
> Cullen
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 11:52:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29667
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 11:52:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFGn-0000Xj-4v
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:52:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAGq5k4002081
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 11:52:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFGm-0000XU-Uy
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 11:52:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29622
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 11:51:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFGl-00004K-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:52:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFGl-00004H-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 11:52:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFGk-0000WP-GJ; Mon, 10 Nov 2003 11:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFGa-0000Vu-Tn
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 11:51:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29613
	for <sipping@ietf.org>; Mon, 10 Nov 2003 11:51:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFGZ-000040-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:51:51 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFGZ-00003j-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:51:51 -0500
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 10 Nov 2003 08:53:04 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAAGpIAt009386;
	Mon, 10 Nov 2003 08:51:19 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ANK35485;
	Mon, 10 Nov 2003 08:51:12 -0800 (PST)
Date: Mon, 10 Nov 2003 08:51:10 -0800
Subject: Re: [Sipping] Comments on dialog-package-03
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "Sipping (E-mail)" <sipping@ietf.org>
To: "Eric Burger" <eburger@snowshore.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F691C@zoe.office.snowshore.com>
Message-Id: <15F8D936-139E-11D8-B472-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Thanks for your comments Eric.

inline...

On Thursday, November 6, 2003, at 01:44 AM, Eric Burger wrote:
> Section 3.3, last bullet:
> I don't like the "or" in the explicitly requested and / or explicitly 
> authorized.  Even if I am authorized, I don't want the information 
> unless I explicitly request it (making it an "and" only).
>
> How about, "The notifier MUST NOT include additional information 
> unless explicitly requested.  The notifier SHOULD authorize the 
> request before honoring the request."

sounds good.

> Section 3.10 on notification rate:
> I think the granularity is too small.  I would expect a flurry of 
> interesting activity during call state change, and then relative quiet 
> during conversations.  Given a conversation of 1 minute (efficient 
> call center), how about having a suggested limit of 10 messages (or 
> some other appropriate number) in one minute?  That way, you can have 
> a message per second (as people answer calls, etc.), without flooding 
> the network (as the dialog will be relatively quiet after the flurry).

good idea

> Section 4.1.1 open issue (escaped quotes):
> Don't forget, you get to chose between ' and ".  We could suggest 
> using single tics.

i don't think this is so easy.  a baroque call-id can contain both 
single and double quotes.  the question is if you can escape them with 
&quot; and &apos; .

> Example in 4.1.1 is not consistent with the draft.  The version 
> indicates which message number this is.  In the example, version=0, 
> which implies this is the first message.  However, state="partial", 
> which is wrong: the first message always conveys state="full".

sorry, I meant to update the version number on this one.  will fix.

> Open issue 4.1.6 (reporting route set): Is there a use case for this?

that's why I asked.

> Open issue 4.1.6.1.4 (reporting CSeq): What could anyone possibly do 
> with this information?

you mean other than be an evil B2BUA that wants to insert messages into 
the middle of your session?  I can't think of anything either.  ;-)

thanks,
-rohan

>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 12:00:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00262
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 12:00:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFOj-00015x-M7
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 12:00:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAH0HLr004205
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 12:00:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFOj-00015g-9i
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 12:00:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00204
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 12:00:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFOh-0000FH-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 12:00:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFOh-0000FE-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 12:00:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFOa-000122-IT; Mon, 10 Nov 2003 12:00:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFOC-0000zY-Am
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 11:59:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00103
	for <sipping@ietf.org>; Mon, 10 Nov 2003 11:59:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFOB-0000Dh-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:59:43 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFOA-0000Cz-00
	for sipping@ietf.org; Mon, 10 Nov 2003 11:59:42 -0500
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAAGx9mU003594;
	Mon, 10 Nov 2003 08:59:09 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ANK36211;
	Mon, 10 Nov 2003 08:59:07 -0800 (PST)
Date: Mon, 10 Nov 2003 08:59:09 -0800
Subject: Re: [Sipping] olson-sipping-refer-extensions  tail wagging the dog?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
To: Paul Kyzivat <pkyzivat@cisco.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <3FAFAF5B.30504@cisco.com>
Message-Id: <339720F8-139F-11D8-B472-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I'm presenting on Wednesday in SIP on the semantics of REFER.  I'm 
going to discuss several different possibilities semantically and make 
my own proposal/recommendation.  Feel free to pitch in some 
ideas/concerns for the slides.

thanks,
-rohan


On Monday, November 10, 2003, at 07:31 AM, Paul Kyzivat wrote:

> Cullen,
>
> I agree with you. This isn't just restricted to referring responses. 
> There is a general issue that the semantics of REFER are 
> underspecified.
>
> - when I send a REFER of an INVITE *in* an existing call dialog,
>   I believe there is an assumption in the published call flows
>   that the resulting new call will supercede the old one, taking
>   over the media resources of that call. But AFAIK that assumption
>   isn't written down, much less normative.
>
> - when a REFER is sent to a phone, independently of any existing 
> dialog,
>   a lot of different things could happen, similar to what you mention
>   blow for sending a 200:
>   . the phone could alert, await acceptance by a local user,
>     and then send the INVITE;
>   . the phone could alert the local user and send the INVITE in
>     parallel. If the Refer-To user answers first, that call could
>     then hear ringback until the local user answers;
>   . a speakerphone could be enabled, and then the INVITE sent;
>   . ...
>   It is hard to know how the feature can be used without knowing
>   something of the semantics it will yield.
>
> - there have been proposals for more exotic REFER uses, such as
>   REFER of a GET method with an http url. While one can imagine some
>   plausible semantics for this, it is again in general difficult to
>   imagine how to use this capability without additional normative
>   behavior.
>
> So, I think there is a general issue of the semantics of REFER that 
> needs to be beefed up.
>
> 	Paul
>
> Cullen Jennings wrote:
>>    Mostly like this stuff but one thing I think *might* cause some 
>> problems...
>> Signaling (such as the phone sending a 200) is an artifact of 
>> something that
>> happened on the phone - such as it got answered. By telling the phone 
>> to do
>> the artifact, the phone might have to guess what the root cause 
>> operation to
>> cause that artifact is.
>> For example, my phone might send a 200 in two different cases. One is 
>> where
>> it some goes hits the speaker phone button when it is ringing. The 
>> other is
>> when it has rung for 10 seconds and it answers, plays a prompt and 
>> records a
>> message and emails it to me. If the phone gets a refer telling it to 
>> send a
>> 200 to some ringing call - the phone will need to guess if it should 
>> go off
>> hook in speaker phone mode or use voice mail mode. I know this is a 
>> somewhat
>> contrived example but I think you get the idea that refer is using a
>> signaling artifact to request a basic operation and that might lead to
>> ambiguous cases. I see the 200 as the tail and the speaker phone 
>> button as
>> the dog.
>> Cullen
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 12:06:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00540
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 12:06:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFUL-0001uz-Iw
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 12:06:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAH654x007366
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 12:06:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFUL-0001uj-FN
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 12:06:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00509
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 12:05:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFUK-0000Nn-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 12:06:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFUJ-0000Nk-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 12:06:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFUI-0001t6-FP; Mon, 10 Nov 2003 12:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJFTl-0001sF-Cm
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 12:05:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00492
	for <sipping@ietf.org>; Mon, 10 Nov 2003 12:05:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFTk-0000NM-00
	for sipping@ietf.org; Mon, 10 Nov 2003 12:05:28 -0500
Received: from 138.muda.mnpl.sfldmibv.dsl.att.net ([12.98.223.138] helo=osrmail)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJFTj-0000NJ-00
	for sipping@ietf.org; Mon, 10 Nov 2003 12:05:27 -0500
Received: from sip (127.0.0.1)
	by localhost (127.0.0.1) with [XMail 0.74 (Win32/Ix86) ESMTP Server]
	id <S1A43> for <sipping@ietf.org> from <stredicke@snom.de>;
	Mon, 10 Nov 2003 08:59:28 -0000
From: "Christian Stredicke" <stredicke@snom.de>
To: "'Rohan Mahy'" <rohan@cisco.com>, "'Eric Burger'" <eburger@snowshore.com>
Cc: "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: AW: [Sipping] Comments on dialog-package-03
Date: Mon, 10 Nov 2003 11:05:47 -0600
Message-ID: <018e01c3a7ac$e2cac960$be08f20a@sip>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <15F8D936-139E-11D8-B472-0003938AF740@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> > Open issue 4.1.6 (reporting route set): Is there a use case for
this?
> 

This is helpful for call pick up. You might want to know how to reach
the one who is calling (with a Replaces header).

Christian 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 13:52:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05315
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 13:52:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJH98-0000w8-Lq
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 13:52:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAIqIhN003595
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 13:52:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJH97-0000vq-GI
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 13:52:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05263
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 13:52:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJH95-0002BF-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 13:52:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJH94-0002BC-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 13:52:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJH8s-0000r5-QC; Mon, 10 Nov 2003 13:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJH8P-0000pY-Ql
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 13:51:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05213
	for <sipping@ietf.org>; Mon, 10 Nov 2003 13:51:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJH8N-0002AJ-00
	for sipping@ietf.org; Mon, 10 Nov 2003 13:51:31 -0500
Received: from ckmso1.att.com ([12.20.58.69] helo=ckmso1.proxy.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJH8M-00029T-00
	for sipping@ietf.org; Mon, 10 Nov 2003 13:51:30 -0500
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id hAAHxYoc026410
	for <sipping@ietf.org>; Mon, 10 Nov 2003 13:50:59 -0500
Received: from occlust04evs1.ugd.att.com (135.38.164.12) by attrh5i.attrh.att.com (6.5.032)
        id 3F307C6C01C24E94 for sipping@ietf.org; Mon, 10 Nov 2003 13:50:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Nov 2003 12:50:58 -0600
Message-ID: <28F05913385EAC43AF019413F674A01705E3E975@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: dtmfad vs kpml
Thread-Index: AcOnu5RHzT0iTaHGRcmvZ7mx2LULlw==
X-Priority: 1
Priority: Urgent
Importance: high
X-Message-Flag: Follow up
From: "Dolly, Martin C, ALABS" <mdolly@att.com>
To: <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] dtmfad vs kpml
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello,

KPML is clearly the more flexible and robust solution.

If KPML was standard and available, then there would not be a need for =
the T1 request.

If KPML is stable after this meeting (meaning ready to implement... =
heading to approval), then the T1 request is moot.

Considering there is not a capability to an obvious problem, one might =
question whether there are those that do not want a answer???

Regards,

Martin
=20
Message: 7
Date: Sun, 09 Nov 2003 21:41:35 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Subject: [Sipping] Why draft-zebarth-sipping-dtmfad?


Seems there have been several other drafts on this problem including one
that is remarkably similar.  Any particular problems this solves that =
KPML
does not?



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 15:00:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09198
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 15:00:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJICn-0005gF-3q
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 15:00:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAK09wn021829
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 15:00:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJICm-0005g0-UG
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 15:00:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09158
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 14:59:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJICj-0003SH-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 15:00:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJICj-0003SE-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 15:00:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJICh-0005eb-1t; Mon, 10 Nov 2003 15:00:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJIBy-0005dY-2L
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 14:59:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09139
	for <sipping@ietf.org>; Mon, 10 Nov 2003 14:59:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJIBt-0003RB-00
	for sipping@ietf.org; Mon, 10 Nov 2003 14:59:13 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJIBt-0003R2-00
	for sipping@ietf.org; Mon, 10 Nov 2003 14:59:13 -0500
Received: from pingtel.com (dyn075-223.ietf58.ietf.org[130.129.75.223])
          by comcast.net (rwcrmhc11) with SMTP
          id <2003111019584101300jh77ie>
          (Authid: dgpetrie);
          Mon, 10 Nov 2003 19:58:42 +0000
Message-ID: <3FAFEB6D.BC65D99B@pingtel.com>
Date: Mon, 10 Nov 2003 13:47:57 -0600
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] draft-ietf-sipping-config-framework
References: <BBD46878.2407F%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yes manual discovery probably makes sense at both
the start and end.  The user may wish to override
which profile delivery server is discovered, effectively
making it the first discovery mechanizm.  It also makes
sense to be the last mechanizm when all other discovery
appoaches  fail.

Cullen Jennings wrote:

> Like it - one little NIT in discover stage...
>
> The manual configuration needs to override the DHCP or well known DNS name
> approach.
>
> Cullen
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 17:05:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16397
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 17:05:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJK9p-00085t-G8
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 17:05:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAM5D0g031109
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 17:05:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJK9p-00085g-Bg
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 17:05:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16381
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 17:04:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJK9m-0005kM-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 17:05:11 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJK9m-0005kI-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 17:05:10 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AJK9n-0005sQ-5E
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 17:05:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJK9e-00084D-WC; Mon, 10 Nov 2003 17:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJK8o-00081x-KA
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 17:04:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16325
	for <sipping@ietf.org>; Mon, 10 Nov 2003 17:03:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJK8m-0005jN-00
	for sipping@ietf.org; Mon, 10 Nov 2003 17:04:08 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJK8l-0005hw-00
	for sipping@ietf.org; Mon, 10 Nov 2003 17:04:07 -0500
Received: from dynamicsoft.com ([63.113.46.36])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hAAM3Zca014985
	for <sipping@ietf.org>; Mon, 10 Nov 2003 17:03:36 -0500 (EST)
Message-ID: <3FB00B35.1010807@dynamicsoft.com>
Date: Mon, 10 Nov 2003 17:03:33 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] user=phone discussion to take place in iptel
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

Due to the busy schedule in sipping, and the direct relevance of the 
user=phone discussion to the tel URI, we will be using agenda time in 
iptel at this ietf to discuss the user=phone issue. Background 
material is at:

www.ietf.org/internet-drafts/draft-ietf-iptel-rfc2806bis-02.txt
www.ietf.org/internet-drafts/draft-mahy-sipping-user-equals-phone-00.txt
www1.ietf.org/mail-archive/working-groups/sipping/current/msg05386.html

the iptel meeting is on Wednesday at 9am.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 17:40:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18294
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 17:40:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJKhk-0002rq-BP
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 17:40:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAMeGcB011022
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 17:40:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJKhk-0002rh-6S
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 17:40:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18245
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 17:40:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJKhh-0006Mq-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 17:40:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJKhh-0006Mn-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 17:40:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJKhW-0002nb-Tm; Mon, 10 Nov 2003 17:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJKhG-0002kK-Sm
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 17:39:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18237
	for <sipping@ietf.org>; Mon, 10 Nov 2003 17:39:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJKhE-0006MQ-00
	for sipping@ietf.org; Mon, 10 Nov 2003 17:39:44 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJKhD-0006MB-00
	for sipping@ietf.org; Mon, 10 Nov 2003 17:39:43 -0500
Received: from dynamicsoft.com ([63.113.46.36])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hAAMcxca014997;
	Mon, 10 Nov 2003 17:39:00 -0500 (EST)
Message-ID: <3FB01380.2000508@dynamicsoft.com>
Date: Mon, 10 Nov 2003 17:38:56 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Dolly, Martin C, ALABS" <mdolly@att.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] dtmfad vs kpml
References: <28F05913385EAC43AF019413F674A01705E3E975@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <28F05913385EAC43AF019413F674A01705E3E975@OCCLUST04EVS1.ugd.att.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I agree with Cullen and others that the zebarth draft overlaps in its 
entirety with the application interaction work, and in particular the 
KPML component of it.

Why has this solution not been completed yet? Well, many reasons:

1. We are attempting to address a broader problem than just DTMF 
conveyance. DTMF is just one example of stimulus signaling that can 
exist in a sip system. We want to make sure the framework supports not 
just DTMF input, but also web, voice and multi-modal systems.

2. For most DTMF-only applications, rfc2833 provides a fairly good 
solution that is widely implemented and mature. It is costly in some 
situations, such as the long-pound case for calling cards, but it 
works. Therefore, there is a solution available that is standards 
based today. The application interaction framework attempts to clarify 
when this mechanism is appropriate, vs. KPML.

3. One of the requirements which surfaced early on in this activity is 
that we didnt want the notifications to traverse the proxies that 
happened to record-route on the original call setup path. As a result, 
we have been working hard on solutions that would allow us to do that. 
Only recently has the GRUU capability materialized, which now enables 
a network server to initiate an out-of-dialog SUBSCRIBE to the 
endpoint (indeed, without GRUUs, the zebarth draft suffers the same 
problem). This should now resolve the long-standing debate which has 
been the primary holdup of this work.

As a result, I believe we can now move forward swifly on this solution.

-Jonathan R.

Dolly, Martin C, ALABS wrote:

> Hello,
> 
> KPML is clearly the more flexible and robust solution.
> 
> If KPML was standard and available, then there would not be a need
> for the T1 request.
> 
> If KPML is stable after this meeting (meaning ready to implement...
> heading to approval), then the T1 request is moot.
> 
> Considering there is not a capability to an obvious problem, one
> might question whether there are those that do not want a answer???
> 
> 
> Regards,
> 
> Martin
> 
> Message: 7 Date: Sun, 09 Nov 2003 21:41:35 -0800 From: Cullen
> Jennings <fluffy@cisco.com> To: sipping <sipping@ietf.org> Subject:
> [Sipping] Why draft-zebarth-sipping-dtmfad?
> 
> 
> Seems there have been several other drafts on this problem
> including one that is remarkably similar.  Any particular problems
> this solves that KPML does not?
> 
> 
> 
> _______________________________________________ Sipping mailing
> list  https://www1.ietf.org/mailman/listinfo/sipping This list is
> for NEW development of the application of SIP Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 18:01:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19429
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 18:01:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJL1u-0004Km-3q
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 18:01:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAN16ng016648
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 18:01:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJL1t-0004KJ-TI
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 18:01:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19381
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 18:00:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJL1q-0006nf-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 18:01:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJL1q-0006nc-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 18:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJL1q-0004Dx-Kt; Mon, 10 Nov 2003 18:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJL1d-0004D4-G7
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 18:00:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19367
	for <sipping@ietf.org>; Mon, 10 Nov 2003 18:00:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJL1a-0006nI-00
	for sipping@ietf.org; Mon, 10 Nov 2003 18:00:46 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJL1a-0006kj-00
	for sipping@ietf.org; Mon, 10 Nov 2003 18:00:46 -0500
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAAN0Dw5020477;
	Mon, 10 Nov 2003 15:00:14 -0800 (PST)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ANK84667;
	Mon, 10 Nov 2003 15:00:12 -0800 (PST)
Date: Mon, 10 Nov 2003 11:46:27 -0800
Subject: Re: AW: [Sipping] Comments on dialog-package-03
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'Eric Burger'" <eburger@snowshore.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
To: "Christian Stredicke" <stredicke@snom.de>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <018e01c3a7ac$e2cac960$be08f20a@sip>
Message-Id: <927C628C-13B6-11D8-B472-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I'm assuming you wouldn't need this if the remote target provided a 
Contact with GRUU properties.

thanks,
-rohan


On Monday, November 10, 2003, at 09:05 AM, Christian Stredicke wrote:

>>> Open issue 4.1.6 (reporting route set): Is there a use case for
> this?
>>
>
> This is helpful for call pick up. You might want to know how to reach
> the one who is calling (with a Replaces header).
>
> Christian
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 10 18:29:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22310
	for <sipping-archive@odin.ietf.org>; Mon, 10 Nov 2003 18:29:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJLT5-00069v-DJ
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 18:29:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAANTBiw023671
	for sipping-archive@odin.ietf.org; Mon, 10 Nov 2003 18:29:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJLT5-00069i-8v
	for sipping-web-archive@optimus.ietf.org; Mon, 10 Nov 2003 18:29:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22276
	for <sipping-web-archive@ietf.org>; Mon, 10 Nov 2003 18:28:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJLSx-0007Ln-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 18:29:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJLSw-0007Lk-00
	for sipping-web-archive@ietf.org; Mon, 10 Nov 2003 18:29:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJLSw-00067K-B3; Mon, 10 Nov 2003 18:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJLST-00064Q-02
	for sipping@optimus.ietf.org; Mon, 10 Nov 2003 18:28:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22258
	for <sipping@ietf.org>; Mon, 10 Nov 2003 18:28:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJLSP-0007LH-00
	for sipping@ietf.org; Mon, 10 Nov 2003 18:28:29 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AJLSO-0007KN-00
	for sipping@ietf.org; Mon, 10 Nov 2003 18:28:28 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 21642; Mon, 10 Nov 2003 18:34:54 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Please Read Committee T1 Draft on DTMF Notification
Date: Mon, 10 Nov 2003 18:27:57 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F697B@zoe.office.snowshore.com>
Thread-Topic: [Sipping] Please Read Committee T1 Draft on DTMF Notification
Thread-Index: AcOkB9E/H3uknBDYTSWo+fKGKnfrTADzVk5A
From: "Eric Burger" <eburger@snowshore.com>
To: "Joe Zebarth" <zebarth@nortelnetworks.com>
Cc: <sipping@ietf.org>, <t1s17@t1.org>, <bhall@labs.sbc.com>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Comments in-line.

Executive summary: the proposal does not work in general.  Moreover, it =
will not work for the limited scope scenario described.  Finally, there =
is another solution available that will meet (and exceed) all of the =
requirements for your situation.

It is up to the chairs and AD's, but I would offer that you would not be =
able to publish this draft, as it overlaps with the KPML work (a work =
group item) and is potentially harmful to the Internet.  That would make =
an IANA registration in the IETF tree impossible.


> -----Original Message----- From: Joe Zebarth =
[mailto:zebarth@nortelnetworks.com]
>=20
> Eric=20
> Thank you for taking the time to review this document which was
> developed to support the IANA registration of this event package. =20
> This event package was intended to support the use scenario as
> identified within the document, viz. "This event package MAY be used
> to allow an application server (subscriber) to request DTMF
> monitoring and notification of detection from a receiving agent
> (notifier) in order to enable a caller-initiated re-origination
> request while a call is in progress."  It is important to understand
> that this usage scenario assumes that the DTMF signal comes from the
> portion of the PSTN that uses TDM technology and that the application
> server supports SIP and also forms part of the PSTN.
> This is a reponse to your email, please see the comments in line.=20
>=20

I do not see how the DTMF being generated in the PSTN, generated in an =
IP Phone, generated by a gateway, etc. is at all relevant.  Is there a =
difference?

>=20
>=20
> Kindest regards,=20
> Joe Zebarth=20
> T1S1.7 Vice Chair=20
> Dept. 1A12=20
> ATI Strategic Standards=20
> Nortel Networks (Canada)=20
> Phone: +1 613 765 8481=20
> ESN:    6+395 8481=20
> Fax:     +1 613 763 2697=20
> ESN:    6+393 2697=20
> http://www.nortelnetworks.com=20
>  =20
>=20
>=20
>=20
> -----Original Message-----=20
> From: Eric Burger [mailto:eburger@snowshore.com]=20
> Sent: Wednesday, October 29, 2003 10:03 PM=20
> To: Dean Willis; sipping@ietf.org=20
> Cc: Zebarth, Joe [CAR:1A12:EXCH]=20
> Subject: RE: [Sipping] Please Read Committee T1 Draft on DTMF=20
> Notification=20
> Things I like in dtmfad:=20
>  =20
> 1. Explicit maxrate (but see below)=20
> 2. "Handshook" throttling (although isn't that normal SIP: no =
overlapping transactions?)=20
> 3. Very simple and compact=20
> 4. Described forking and state agent behavior (I forgot!)=20
>  =20
>  =20
> Things I don't like:=20
> 1. The model is worse than MGCP.  An event for every key press?  If
> you are interested in such low-level control, use H.248.
> =20
> Comment: JAZ=20
> This document is not discussing control.  Rather it is addressing the
> subject of capturing the DTMF digits that originated in the portion
> of the PSTN that uses TDM technology and which subsequently enter the
> portion of the PSTN that uses IP technology.  The application server
> already supports SIP.  The implementation of the event package is a
> modest extension to support this capability.

Unfortunately, the model of issuing one *or more* notifications per =
digit, with the express intent of capturing timing, signal strength, =
etc. is very much a device control model.  The SIP (applications and =
services) model is the client (the application server, in this case) =
makes a request of the server (the gateway).  That request uses =
application-layer semantics, like "give me digits that match this map" =
or "give me digits", not device-layer semantics, like "give me the tones =
and associated signal parameters."

> =20
> 2. The model only works for a B2BUA or machine end point.  The far
> end is the only entity that can request digit monitoring.  OK for a
> "softswitch", but not necessarily desirable in an Applications and
> Services Infrastructure.
> Comment: JAZ=20
> I believe that your observation is correct that the far end is the
> only entity that can request digit monitoring in this usage scenario.=20
> The usage scenario calls for the far end to request digit monitoring.=20

This says it will not work for pre-paid, which is your target =
application.

> =20
> 3. Duration: On the one hand, it is handy to be able to define what
> "long" is.  However, this is a disaster.  What if I set =
"duration=3D50"
> and I hold the octothorpe key down for 6 seconds?  I will get 120
> NOTIFY messages in that time.  That isn't helpful for traffic
> shaping.  What does the application do with all of those messages?=20
> The model is taken directly from RFC2833 (keep emitting tone and mark
> the end-of-tone) -- why not just use RFC2833 and be done with it?=20
> Eating a low-rate RTP stream has GOT to be easier than implementing a
> RFC3261 stack!
> =20
> Comment: JAZ=20
> The usage scenario assumes that SIP is implemented.  Thus, the
> proposed implementation is as you suggest "simple and compact" to add
> this capability.

60 bytes (including IP headers) per message for RFC2833 vs. 800 bytes =
per message for SIP does not make a compelling "simple and compact" =
argument.

> =20
> The following guidance is contained in the document to prevent
> operators from setting the optional duration parameter to some number
> like 50 ms. (If this optional parameter is not present, then event
> notification occurs only when the end of the DTMF tone is detected.),
> viz.
> =20
> 'Note: for long key presses, combined with short values of
> "duration", a single DTMF digit can result in many NOTIFY requests.=20
> With calling card re-origination requests, in particular, the
> Application Server (AS) cannot provide a prompt for a new destination
> number or begin collecting digits if the caller is still pressing a
> DTMF key, so the AS must wait for completion of the tone.  Therefore,
> it is likely that sending NOTIFY requests at the termination of each
> detected DTMF digit is preferable to sending many NOTIFY requests for
> each digit.  As a result, it is RECOMMENDED that the AS not include
> the "duration" parameter.'

Here is where you have tripped the device control vs. applications and =
services wire.  If you want a protocol that works like:

C: connect the call to the application server
S: OK

C: listen for # (alternately, "listen for digits")
S: OK

... time passes ...

S: # found
C: OK

C: Stop prompt
S: OK

C: Play new prompt
S: OK

C: Collect digits
S: OK

S: here are the digits
C: OK

Then I STRONGLY suggest H.248 or J.162.  They have exactly the above =
control model.

If you want:

C: listen for #
S: OK

... time passes...=20

S: # found
C: OK

C: stop prompt
S: OK

C: play new prompt
S: OK

C: Collect digits
S: OK

S: here are the digits
C: OK

Then if you have to use SIP for digit detection, use KPML for the digit =
detection, and H.248 or J.162 for the prompting.  Alternately, to keep =
it all SIP, use the IVR namespace of MSCML.=20


The best model in the applications and services environment is the =
following dialog:

C: listen for #. When you get a #, stop the current prompt, prompt for =
the new number, and tell me what you got
S: OK

... time passes ...

S: here is the new number
C: OK

This is SIP and VoiceXML.


> =20
> Additional guidance is also given in this regard, viz.=20
>  =20
> 'maxrate=20
> "maxrate" is an optional parameter defining a maximum number of
> NOTIFY transactions per minute initiated to report DTMF events.  The
> notifier MUST NOT exceed this limit in any one minute period, but MAY
> send notifications in more rapid bursts over shorter periods.  If
> "maxrate" is omitted, the notifier MUST limit reporting to forty (40)
> NOTIFY transactions per minute.  "maxrate" SHOULD NOT exceed 60.=20

Why offer this if the application server shouldn't use it?  Again, the =
default maxrate issues notifications FASTER than the packet time of the =
codec.  That is a less than optimal use of bandwidth.

> =20
> If the reporting rate limit causes a queue of unreported events to
> build up, the notifier MAY discard some or all of the excess events.=20
> If the notifier can choose which events to discard, the notifier
> SHOULD discard notifications of uncompleted DTMF events resulting
> from the presence of the "duration" parameter before discarding
> notifications of completed DTMF events.'
> =20
> Should the optional duration parameter be set, the text allows the
> notifier to delete/discard notifications of uncompleted DTMF events.
> =20
> 4. Hex codes don't really fit into the SIP gestalt.  Why not encode
> the information in a straightforward manner?  One cannot argue for
> compactness -- if one is going to live with 600+ bytes of SIP headers
> (see the example in the document), one can have a 35-byte text
> message that means something instead of a 12-byte "binary" message
> that is indecipherable.
> =20
> Comment:JAZ=20
> As the event package is intended to carry dtmf digits and as they are
> transparent to SIP processing, we believe that the defined event
> package is consistent with normal IETF style.

I fail to see how there can be ANY argument for a pseudo-binary payload.

>  =20
> Things I am open to:=20
> 1. Volume: Does anyone need this?  What for?  How would you know?=20
> What would you do with it?  Not for falsing detection: that is what
> the detection device should be doing.  If there is a good use case, I
> could see implementing it.  Then again, what do you do for RFC2833
> digit detection (no volume)?
> =20
> Comment JAZ=20
> The DTMF tone originates in the TDM portion of the PSTN and thus
> depending on the PSTN transmission plan the DTMF tone levels may
> vary.

Let me ask again:  What on earth would you USE this FOR?

> =20
> 2. Maxrate: I'm leaning towards not liking it, but I'm open to it.=20
> First, the SUBSCRIBER here only specifies its own ability to process
> NOTIFY requests.  Using this as a network-saving device isn't going
> to work: how does the subscriber have any idea what to set this to?=20
> Second, the default maxrate is one message every 16ms, or faster than
> G.711.  What could this be possibly useful for?=20
> Third (and the big one), the whole point of transporting digits in
> the signaling path is because the digits *are* signaling.  Said
> differently, the application needs reliable delivery of signaling
> (digits).  If the use case for this package allows unreliable
> delivery, then I would be very interested in understanding why one is
> not using RFC2833, which has EVERYTHING discussed in this draft,
> available today?
> =20
> Comment JAZ=20
> The usage scenario only calls for the far end to request digit
> monitoring.  The subscriber is typically using a PTSN phone to
> originate calls and subsequent in band dtmf tones.  Maxrate provides
> additional security against people who do insist upon holding down a
> DTMF digit when the carrier has set the duration parameter to a short
> duration.

Permit me a quick review on client-server terminology.  In the proposed =
protocol, the server is the PSTN gateway.  The client is the Application =
Server (far end).  Thus when I said that in your proposal the client =
does not need reliable delivery, I am referring to the far end.  This =
has absolutely nothing to do with the PSTN nature of the gateway.

Moreover, emitting a device-level notification ("is the key still =
pressed") instead of an application-level notification ("the key is =
pressed") highlights the evil of putting device control semantics on an =
application protocol.  In this case, it results in sending lots of =
notifications.  Again, if you care about low-level signal information, =
use RFC2833.

> As you indicated earlier, this is a "very simple and compact" way of
> implementing this feature.=20

Compact:  No, order of magnitude greater than RFC2833.  No, on the order =
of KPML.

Simple: Simple minded, yes; simple to implement, possibly; simple to =
operate, NO.

> In summary, based on your comments, I do not see any technical issues
> with the proposed event package.=20

Please re-read the first response, embellished with these responses.  =
There are many technical issues.  The maxrate / multiple notifications =
for a single key press is harmful to the Internet.  That is a major =
technical issue with the proposal.=20

> I would look forward to your support in having this work progress so
> that the event package can be registered with IANA in a timely
> fashion.

I am sorry I didn't get to this response sooner.

> Again I would like to thank you for taking the time to comment on
> this document.=20

You are welcome.  Although it may sound like I thought the proposal was =
less than ideal, there were a few aspects (noted above) that are =
valuable.  Moreover, if there are cogent use cases for things like =
duration or volume, we should put that into KPML.

Please keep the dialog open and update us if there are more, real, =
requirements.


> =20
> Kindest regards,=20
> Joe Zebarth=20
> T1S1.7 Vice Chair=20
> =20
>=20
>=20
>=20
>=20
> > -----Original Message-----=20
> > From: Dean Willis [mailto:dean.willis@softarmor.com]=20
> > Sent: Tue, October 28, 2003 2:27 AM=20
> > To: sipping@ietf.org=20
> > Cc: Joe Zebarth=20
> > Subject: [Sipping] Please Read Committee T1 Draft on DTMF =
Notification=20
> >=20
> >=20
> > While we were arguing about how to handle keypresses,=20
> > somebody went out=20
> > and wrote a draft for an event package for DTMF events.=20
> >=20
> > Please review the draft:=20
> >=20
> > =
http://www.softarmor.com/wgdb/docs/draft-zebarth-sipping-dtmfad-00.txt=20
> >=20
> > As I understand it, the mechanism that this draft is meant to=20
> > support is=20
> > defined in Committee T1 Technical Report T1.TR.82-2003.=20
> > Unfortunately, I=20
> > wasn't able to find said document on the T1 site, but that=20
> > could just be=20
> > me -- perhaps the author can give us a link?=20
> >=20
> > Questions to consider: Does this approach complement or conflict =
with=20
> > the KPML work? Is there danger of fragmenting, or is this work =
clearly=20
> > seperate? Would the world (or at least the Internet) be a better =
place=20
> > with, or without, this event package?=20
> >=20
> > Please copy the author, as well as the list, on any=20
> > responses. I expect=20
> > that discussion on this topic will come up during the Minneapolis=20
> > meeting.=20
> >=20
> > Thanks,=20
> >=20
> > --=20
> > Dean Willis=20
> > SIPPING co-chair


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 07:24:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28839
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 07:24:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJXZH-0006dG-SH
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 07:24:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABCONYs025495
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 07:24:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJXZH-0006d8-Mh
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 07:24:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28810
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 07:24:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJXZH-00023E-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 07:24:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJXZG-00023B-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 07:24:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJXYv-0006bn-21; Tue, 11 Nov 2003 07:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJXYN-0006az-7C
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 07:23:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28798
	for <sipping@ietf.org>; Tue, 11 Nov 2003 07:23:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJXYM-00022h-00
	for sipping@ietf.org; Tue, 11 Nov 2003 07:23:26 -0500
Received: from firewall.citel.com ([62.190.107.60] helo=ivor.citel.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJXYL-00022H-00
	for sipping@ietf.org; Tue, 11 Nov 2003 07:23:25 -0500
Received: by exchange.citel.com with Internet Mail Service (5.5.2653.19)
	id <V8WYP5P7>; Tue, 11 Nov 2003 12:26:22 -0000
Message-ID: <115ABFD69991D511B9860050FC22466677FBA5@exchange.citel.com>
From: Steve Langstaff <steve.langstaff@citel.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Tue, 11 Nov 2003 12:26:15 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Rationalisation of hostport/usernames in draft-ietf-sipping-tortu
 re-tests-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi All.

I am looking at automatic testing of a SIP implementation, and although
draft-ietf-sipping-torture-tests-01 says...

   "This document does not, however, attempt to be comprehensive. It should
be
   considered a seed to stimulate thinking and planning, not simply a
   set of tests to be passed."

...I was wondering if there were any reasons not to rationalise the test
messages in a number of ways:

1) There appear to be a large number of different host names present in the
test messages where surely only a few are needed, e.g.
	c.example.com
	example.com
	example.org
	example53.example.net
	fold-and-staple.example.com
	funky.example.com
	host-of-the-hour.example.com
	host.example.com
	host.example.net
	host1.examle.com
	host1.example.com
	host1.example.net
	host129.example.com
	host15.example.net
	host25.example.net
	host39923.example.net
	host4.example.com
	host5.example.com
	host5.example.net
	host59.example.net
	host9.example.com
	hungry.example.net
	iftgw.example.com
	saturn.example.com
	somehost.example.com
	t1.example.com

2) Shouldn't the call-ids be unique between messages, except where we are
specifically testing call-id issues? This would help us associate response
messages with the appropriate test message.

3) Could the URI always be 'user@example.com' except where we are
specifically testing URI issues? This would simplify the configuration of
the device under test.

4) Ditto the To: ('user@example.com') and From: ('caller@example.com')
headers?

5) The SDP o= and c= parameters mention about 7 different IP addresses.
Could this be rationalised down to one?

Thanks for any feedback,


-- 
Steve Langstaff. 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 12:53:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13291
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 12:53:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJchR-0006Es-Qq
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 12:53:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABHr9h4023976
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 12:53:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJchR-0006Ed-NM
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 12:53:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13264
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 12:52:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJchP-00077g-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 12:53:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJchP-00077d-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 12:53:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJchJ-0006DI-QA; Tue, 11 Nov 2003 12:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJchE-0006Cv-8V
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 12:52:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13236
	for <sipping@ietf.org>; Tue, 11 Nov 2003 12:52:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJchC-00076y-00
	for sipping@ietf.org; Tue, 11 Nov 2003 12:52:54 -0500
Received: from mail3.pi.se ([195.7.64.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJchB-000767-00
	for sipping@ietf.org; Tue, 11 Nov 2003 12:52:53 -0500
Received: from vit (americium.arin.net [130.129.135.221] (may be forged))
	(authenticated)
	by mail3.pi.se (8.11.2/8.11.2) with ESMTP id hABHq0820966
	for <sipping@ietf.org>; Tue, 11 Nov 2003 18:52:00 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "'Sipping@Ietf. Org'" <sipping@ietf.org>
Subject: [sipping] Emergency Call Text medium
Date: Tue, 11 Nov 2003 11:52:04 -0600
Message-ID: <BHEHLFPKIPMLPFNFAHJKEEGEDBAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mail3.pi.se id hABHq0820966
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

The status of the Emergency Call Design Team activities was presented tod=
ay
in the Sipping group.

The needs of deaf and hearing impaired users to be able to communicate wi=
th
emergency services in text, was very briefly touched.

This is an apparent need that has its own set of requirements and solutio=
ns
and needs to be properly expanded when the work on Emergency Services
progresses. Too many times, late introduction of requirements to access
Emergency services in text mode has resulted in a lot of work and not as
good solutions as if it was specified from the beginning.

Some points for consideration:

1. The requirement to access Emergency Services in character by character
text conversation is described in the new Text over IP draft:
draft-manyfolks-sipping-toip-00.txt

2. The main way to transmit text conversation in SIP sessions shall be by
starting a media stream for text. RFC2793 describes a transport for that.=
 A
proposed revision draft-hellstrom-avt-rfc2793bis-02.txt gives sdp example=
s
for invoking the text stream. It can exist in parallell with any other
media, as audio.

3. The scope of the current Emenrgency Call work is focused on a
PSTN-located Emergency Service. Therefore, conversion of the text transpo=
rt
in SIP to the PSTN forms of text telephony must take place in a text-awar=
e
gateway.

4. The status overview of the Emergency Call work mentioned some problems
related to today=B4s handling of emergency text calls in PSTN.

4.1 Some textphone systems do not give any audible indication of their ty=
pe,
when they are calling, but sit silent waiting for the called party to iss=
ue
the right text modem signals. That is problematic for Emergency Services.
The V.18 standard for text telephony that can automode to all regional te=
xt
telephone systems issues audible and machine detectable signals indicatin=
g
its text nature. It seems therefore wise to mandate use of V.18 in SIP -
PSTN gateways going to the Emergency services.

4.2 Some countries have separate PSTN numbers for text users. After an
investigation if they are planning to harmonize numbers, it could be stud=
ied
if it can be brought into the routing logic of the Emergency Call spec to
call the text number when the Sip call is initiated in text - althought t=
his
must be carefully thought through.

Looking forward to further co-operation between the Sipping Text over IP =
and
the Emergency Call Design teams.


Regards

Gunnar
-------------------------------------------
Gunnar Hellstr=F6m
Omnitor AB
Renathv=E4gen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 14:01:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15628
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 14:01:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdlH-0002jC-42
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 14:01:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABJ1Bj1010480
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 14:01:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdlG-0002ix-WE
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 14:01:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15613
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 14:00:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdlE-0000FJ-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 14:01:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdlE-0000FG-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 14:01:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdl7-0002hY-Tj; Tue, 11 Nov 2003 14:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJdkG-0002gE-0E
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 14:00:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15592
	for <sipping@ietf.org>; Tue, 11 Nov 2003 13:59:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdkD-0000Cb-00
	for sipping@ietf.org; Tue, 11 Nov 2003 14:00:05 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJdkD-0000C0-00
	for sipping@ietf.org; Tue, 11 Nov 2003 14:00:05 -0500
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 11 Nov 2003 11:06:07 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hABIxWw5008781;
	Tue, 11 Nov 2003 10:59:33 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA00567; Tue, 11 Nov 2003 10:59:31 -0800 (PST)
Message-Id: <4.3.2.7.2.20031111124609.026ccfe0@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 11 Nov 2003 12:59:30 -0600
To: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>,
        "'Sipping@Ietf. Org'" <sipping@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [sipping] Emergency Call Text medium
In-Reply-To: <BHEHLFPKIPMLPFNFAHJKEEGEDBAA.gunnar.hellstrom@omnitor.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

At 11:52 AM 11/11/2003 -0600, Gunnar Hellstrom wrote:
>The status of the Emergency Call Design Team activities was presented today
>in the Sipping group.
>
>The needs of deaf and hearing impaired users to be able to communicate with
>emergency services in text, was very briefly touched.

Gunnar

As a co-chair (with Brian Rosen) of the NENA VoIP WG - I can assure you=20
that group is looking at supporting deaf and hearing impaired users from=20
the beginning (which is only 4 months old now).  NENA's intention is to=20
generate requirements for IP delivery of emergency services in two groups:

1 - a Migration WG which is for situations in which there is an IP to/from=
=20
TDM transition

and

2 - an End to End IP WG (called the Long Term Definition  or LTD WG)

The requirements coming from NENA will be directed to SIP(PING) (and maybe=
=20
other WGs within the IETF if appropriate) to work on further

Both NENA WGs will work on your suggestions - and I look forward to your=20
involvement to further this effort.

Any other requirements you feel need to be met - please forward them to=20
Brian and me, as we will take each into NENA for their consideration.



>This is an apparent need that has its own set of requirements and solutions
>and needs to be properly expanded when the work on Emergency Services
>progresses. Too many times, late introduction of requirements to access
>Emergency services in text mode has resulted in a lot of work and not as
>good solutions as if it was specified from the beginning.
>
>Some points for consideration:
>
>1. The requirement to access Emergency Services in character by character
>text conversation is described in the new Text over IP draft:
>draft-manyfolks-sipping-toip-00.txt
>
>2. The main way to transmit text conversation in SIP sessions shall be by
>starting a media stream for text. RFC2793 describes a transport for that. A
>proposed revision draft-hellstrom-avt-rfc2793bis-02.txt gives sdp examples
>for invoking the text stream. It can exist in parallell with any other
>media, as audio.
>
>3. The scope of the current Emenrgency Call work is focused on a
>PSTN-located Emergency Service. Therefore, conversion of the text transport
>in SIP to the PSTN forms of text telephony must take place in a text-aware
>gateway.
>
>4. The status overview of the Emergency Call work mentioned some problems
>related to today=B4s handling of emergency text calls in PSTN.
>
>4.1 Some textphone systems do not give any audible indication of their=
 type,
>when they are calling, but sit silent waiting for the called party to issue
>the right text modem signals. That is problematic for Emergency Services.
>The V.18 standard for text telephony that can automode to all regional text
>telephone systems issues audible and machine detectable signals indicating
>its text nature. It seems therefore wise to mandate use of V.18 in SIP -
>PSTN gateways going to the Emergency services.
>
>4.2 Some countries have separate PSTN numbers for text users. After an
>investigation if they are planning to harmonize numbers, it could be=
 studied
>if it can be brought into the routing logic of the Emergency Call spec to
>call the text number when the Sip call is initiated in text - althought=
 this
>must be carefully thought through.
>
>Looking forward to further co-operation between the Sipping Text over IP=
 and
>the Emergency Call Design teams.
>
>
>Regards
>
>Gunnar
>-------------------------------------------
>Gunnar Hellstr=F6m
>Omnitor AB
>Renathv=E4gen 2
>SE 121 37 Johanneshov
>SWEDEN
>+46 8 556 002 03
>Mob: +46 708 204 288
>www.omnitor.se
>Gunnar.Hellstrom@Omnitor.se
>--------------------------------------------
>
>
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 18:44:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29017
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 18:44:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiB6-0001O0-MI
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 18:44:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hABNi8sk005322
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 18:44:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiB6-0001Nl-H8
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 18:44:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29000
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 18:43:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiB3-0004Zu-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 18:44:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiB2-0004Zr-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 18:44:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiAz-0001MX-46; Tue, 11 Nov 2003 18:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJiAA-0001Ly-PU
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 18:43:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28957
	for <sipping@ietf.org>; Tue, 11 Nov 2003 18:42:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiA7-0004ZD-00
	for sipping@ietf.org; Tue, 11 Nov 2003 18:43:07 -0500
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJiA7-0004ZA-00
	for sipping@ietf.org; Tue, 11 Nov 2003 18:43:07 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id hABNgVd03873
	for <sipping@ietf.org>; Tue, 11 Nov 2003 17:42:31 -0600
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sipping@ietf.org
Content-Type: text/plain
Message-Id: <1068594147.945.26.camel@RjS.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Tue, 11 Nov 2003 17:42:27 -0600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] torture test archive bug
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There are a few messages in the archive in the appendix of
draft-ietf-sipping-torture-test-01 that are not correct (due
to an implementation bug expanding <hex> - some whitespace
was not removed before digesting the string).

Version 02 of the draft will be released shortly after this
IETF meeting correcting (at least) that bug.

The affected files are intmeth.dat, smime01.dat, and unreason.dat.

RjS


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 22:22:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05809
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 22:22:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJla4-0000YH-JA
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 22:22:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC3M8W8002117
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 22:22:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJla4-0000Y4-FZ
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 22:22:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05806
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 22:21:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJla1-0007Xs-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 22:22:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJla0-0007Xp-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 22:22:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJlZx-0000Ww-7p; Tue, 11 Nov 2003 22:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJlZu-0000Wg-TD
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 22:21:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05798
	for <sipping@ietf.org>; Tue, 11 Nov 2003 22:21:45 -0500 (EST)
From: Markus.Isomaki@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJlZr-0007Xg-00
	for sipping@ietf.org; Tue, 11 Nov 2003 22:21:55 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJlZq-0007Xd-00
	for sipping@ietf.org; Tue, 11 Nov 2003 22:21:54 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAC3Lts17115
	for <sipping@ietf.org>; Wed, 12 Nov 2003 05:21:55 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65dacc3871ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 12 Nov 2003 05:21:53 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 12 Nov 2003 05:21:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Comment on the applicability of draft-ietf-sipping-config-framework
Date: Wed, 12 Nov 2003 05:21:52 +0200
Message-ID: <E392EEA75EC5F54AB75229B693B1B6A707E7A241@esebe018.ntc.nokia.com>
Thread-Topic: [Sipping] draft-ietf-sipping-config-framework
Thread-Index: AcOnxXwYDT/SibIuQ1mZhQMms1eSHgBAkr+A
To: <dpetrie@pingtel.com>
Cc: <sipping@ietf.org>
X-OriginalArrivalTime: 12 Nov 2003 03:21:53.0606 (UTC) FILETIME=[1E901660:01C3A8CC]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I want to elaborate on the comment I made about =
draft-ietf-sipping-config-framework and wireless devices in today's =
SIPPING session:

In general I think the framework presented in the draft is very good. =
However, it is not clear how usable it will be in its current form for =
wireless devices (more specifically wireless devices used mainly in =
cellular networks) having a SIP UA. For those kind of devices it is =
anyway essential to be able to configure a number of parameters related =
to various applications, e.g. MMS or e-mail. I believe there is nothing =
special about SIP-related parameters in this respect. So, rather than =
using a mechanism targeted specifically for SIP, it makes more sense to =
use a generic "device management" technology to take care of all =
applications.=20

The prevailing technology for this, at least in GSM/GPRS/WCDMA space is =
- SMS - which is obviously very limited. This is currently being =
superseded by SyncML-based device management technology standardized by =
the Open Mobile Alliance, OMA. This clearly diminishes the need for a =
separate SIP mechanism. (Note that so far e.g. 3GPP has not made any =
decision whether to follow sipping-config-framework or SyncML when =
configuring service parameters for IMS SIP UAs. It is as well possible =
that they will not specify anything on this for Release 6, which comes =
out next year.)

There may be, however, some synergies between sipping-config-framework =
and how SyncML device menagement needs to evolve. SyncML DM currently =
relies on WAP push technology to deliver notifications to devices, and =
uses MSISDN numbers to address them (this may sound bad, but the =
advantage is that it works even when the device is not connected to IP =
network). In the future when a large number of cellular devices have SIP =
and constant IP connectivity, it may actually make sense to replace the =
_notification part_ with SIP. This would conceptually fit in the =
sipping-config-framework, only it is not clear whether SUBSCRIBE-NOTIFY =
is actually the best (or at leat the only) solution.=20

We are going to take a look on the requirements from SyncML point of =
view, and after that comment if SIP has any role at all there, and =
whether a potential solution would have commonalities with the =
sipping-config-framework work done in the IETF. The optimal solution =
would be that there would be at least some commonalities how the device =
gets its configuration in cellular network and when it is used e.g. in =
an enterprise VoIP system with WLAN access.

Regards,
	Markus   =20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 11 23:11:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06967
	for <sipping-archive@odin.ietf.org>; Tue, 11 Nov 2003 23:11:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJmLh-0003jc-Ry
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 23:11:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC4BLXs014350
	for sipping-archive@odin.ietf.org; Tue, 11 Nov 2003 23:11:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJmLh-0003jN-KG
	for sipping-web-archive@optimus.ietf.org; Tue, 11 Nov 2003 23:11:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06952
	for <sipping-web-archive@ietf.org>; Tue, 11 Nov 2003 23:11:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJmLd-0000H2-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 23:11:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJmLd-0000Gz-00
	for sipping-web-archive@ietf.org; Tue, 11 Nov 2003 23:11:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJmLS-0003iE-KM; Tue, 11 Nov 2003 23:11:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJmKW-0003hA-Rh
	for sipping@optimus.ietf.org; Tue, 11 Nov 2003 23:10:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06930
	for <sipping@ietf.org>; Tue, 11 Nov 2003 23:09:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJmKS-0000GS-00
	for sipping@ietf.org; Tue, 11 Nov 2003 23:10:04 -0500
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJmKS-0000GI-00
	for sipping@ietf.org; Tue, 11 Nov 2003 23:10:04 -0500
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAC49XI14494
	for <sipping@ietf.org>; Tue, 11 Nov 2003 22:09:33 -0600 (CST)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <W3H4MP1C>; Tue, 11 Nov 2003 22:09:33 -0600
Message-ID: <870397D7C140C84DB081B88396458DAF578E06@zrc2c000.us.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Tue, 11 Nov 2003 22:09:25 -0600
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Sipping] Status of Request History Requirements
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I just wanted to make a comment about the current status of the Request
History Requirements draft. It was mentioned during the meeting that it is
now expired, however, the current draft doesn't expire until next month:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-req-history-04.txt
I did not rev the draft prior to this meeting as there's been no additional
discussion.  Some of the content forms background in the History-Info
solution draft that we'll be discussing in SIP WG tomorrow.  If there's no
value in progressing the requirements independently, they can certainly be
brought in a more complete form into the solution draft. 

Regards,
Mary H. Barnes
mary.barnes@nortelnetworks.com
972-684-5432



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 00:24:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08781
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 00:24:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUN-0008DS-LI
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 00:24:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAC5ONUV031576
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 00:24:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUN-0008DD-F8
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 00:24:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08627
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 00:24:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnUK-00012A-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 00:24:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnUK-000127-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 00:24:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnUC-00086a-Bc; Wed, 12 Nov 2003 00:24:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJnKa-0007JZ-Hg
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 00:14:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08343
	for <sipping@ietf.org>; Wed, 12 Nov 2003 00:14:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJnKY-0000tY-00
	for sipping@ietf.org; Wed, 12 Nov 2003 00:14:14 -0500
Received: from [202.96.122.72] (helo=mail1.eastcom.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AJnKX-0000tH-00
	for sipping@ietf.org; Wed, 12 Nov 2003 00:14:13 -0500
Received: from zfzhao ([10.8.18.89]) by mail1.eastcom.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 12 Nov 2003 13:13:27 +0800
Message-ID: <02a501c3a8db$359690f0$5912080a@rd.eastcom>
From: "Jeff zhao" <zhaozf@eastcom.com>
To: <sipping@ietf.org>
Date: Wed, 12 Nov 2003 13:09:54 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 12 Nov 2003 05:13:27.0707 (UTC) FILETIME=[B48ED6B0:01C3A8DB]
Content-Transfer-Encoding: base64
Subject: [Sipping] about SIP-I
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

SSBub3RpY2UgdGhhdCB0aGVyZSBpcyBhIG5ldyBwcm90b2NvbCBuYW1lZCBTSVAtSShTZXNzaW9u
IEluaXRpYXRpb24gUHJvdG9jb2wgZm9yIEludGVyd29ya2luZykuDQoNCkNvdWxkIGFueW9uZSB0
ZWxsIG1lIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQgaXQgb3Igd2hlcmUgSSBjYW4gZmluZCBtb3Jl
IGRvY3VtZW50Lg0KDQpUaGFua3MuDQoNCkplZmYgemhhbw==



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 08:21:15 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16628
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 08:21:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJuvV-0000xv-J0
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 08:20:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACDKrfM003707
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 08:20:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJuvV-0000xi-El
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 08:20:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16610
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 08:20:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJuvU-0006O3-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 08:20:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJuvT-0006Nu-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 08:20:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJuug-0000rA-0t; Wed, 12 Nov 2003 08:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJuti-0000jk-Qm
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 08:19:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16576
	for <sipping@ietf.org>; Wed, 12 Nov 2003 08:18:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJuth-0006N3-00
	for sipping@ietf.org; Wed, 12 Nov 2003 08:19:01 -0500
Received: from gateway.hns.com ([208.236.67.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJuth-0006N0-00
	for sipping@ietf.org; Wed, 12 Nov 2003 08:19:01 -0500
Received: from excore8.hns.com (excore8.hns.com [139.85.52.156])
	by gateway.hns.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hACDIimR009335
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 12 Nov 2003 08:18:51 -0500 (EST)
Received: from atlas (atlas.hns.com [139.85.177.110])
	by excore8.hns.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id hACDIE62001318;
	Wed, 12 Nov 2003 08:18:17 -0500 (EST)
To: "Jeff zhao" <zhaozf@eastcom.com>
Cc: sipping@ietf.org
Subject: Re: [Sipping] about SIP-I
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF4DA0725E.5B35E000-ON85256DDC.00487EEB@LocalDomain>
From: Arjun Roychowdhury <aroychow@hns.com>
Date: Wed, 12 Nov 2003 08:18:08 -0500
X-MIMETrack: Serialize by Router on Atlas/HNS(Release 5.0.12  |February 13, 2003) at 11/12/2003
 08:16:19 AM,
	Serialize complete at 11/12/2003 08:16:19 AM
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Jeff, I believe this is a part of ITU-SG11's effort to provide 
SIP/isup-bicc mapping afaik. if you are a ties member you can download
the document from itu. I dont believe its a new protocol. 
This is as far as my knowledge takes me .

regds
arjun

--
Arjun Roychowdhury @ Hughes Software Systems
11717 Exploration Lane, Germantown MD 20876
(O): 301 212 7860 
VOIP: (SIP) 10303@fwd.pulver.com (PSTN alias:360-207-0467)




"Jeff zhao" <zhaozf@eastcom.com>
Sent by: sipping-admin@ietf.org
11/12/2003 12:09 AM

 
        To:     <sipping@ietf.org>
        cc: 
        Subject:        [Sipping] about SIP-I


I notice that there is a new protocol named SIP-I(Session Initiation 
Protocol for Interworking).

Could anyone tell me more information about it or where I can find more 
document.

Thanks.

Jeff zhao



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 11:03:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24147
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 11:03:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJxSg-000296-4n
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 11:03:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACG3I3s008242
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 11:03:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJxSf-00028r-UD
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 11:03:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24119
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 11:03:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJxSd-00016o-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 11:03:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJxSc-00016l-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 11:03:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJxSS-00027L-3S; Wed, 12 Nov 2003 11:03:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJxRZ-00026Y-Ju
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 11:02:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24073
	for <sipping@ietf.org>; Wed, 12 Nov 2003 11:01:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJxRW-00015q-00
	for sipping@ietf.org; Wed, 12 Nov 2003 11:02:07 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJxRW-00015U-00
	for sipping@ietf.org; Wed, 12 Nov 2003 11:02:06 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hACG1Uxi005568;
	Wed, 12 Nov 2003 11:01:32 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ATV24045;
	Wed, 12 Nov 2003 08:01:29 -0800 (PST)
Message-Id: <4.3.2.7.2.20031112105525.00b37fc0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 12 Nov 2003 11:01:29 -0500
To: Arjun Roychowdhury <aroychow@hns.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] about SIP-I
Cc: "Jeff zhao" <zhaozf@eastcom.com>, sipping@ietf.org
In-Reply-To: <OF4DA0725E.5B35E000-ON85256DDC.00487EEB@LocalDomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

SIP-I stands for SIP with encapsulated ISUP.  Look for Q.1912.5 currently 
under ballot review.  It is 95% the same as RFC-3398, but also includes 
things such as Overlap signaling, different view of Cause code mapping, and 
some other details not covered already.

Mike

At 08:18 AM 11/12/2003 -0500, Arjun Roychowdhury wrote:
>Jeff, I believe this is a part of ITU-SG11's effort to provide
>SIP/isup-bicc mapping afaik. if you are a ties member you can download
>the document from itu. I dont believe its a new protocol.
>This is as far as my knowledge takes me .
>
>regds
>arjun
>
>--
>Arjun Roychowdhury @ Hughes Software Systems
>11717 Exploration Lane, Germantown MD 20876
>(O): 301 212 7860
>VOIP: (SIP) 10303@fwd.pulver.com (PSTN alias:360-207-0467)
>
>
>
>
>"Jeff zhao" <zhaozf@eastcom.com>
>Sent by: sipping-admin@ietf.org
>11/12/2003 12:09 AM
>
>
>         To:     <sipping@ietf.org>
>         cc:
>         Subject:        [Sipping] about SIP-I
>
>
>I notice that there is a new protocol named SIP-I(Session Initiation
>Protocol for Interworking).
>
>Could anyone tell me more information about it or where I can find more
>document.
>
>Thanks.
>
>Jeff zhao
>
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 12:19:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28364
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 12:19:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJye6-0001gp-5c
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 12:19:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACHJAaI006489
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 12:19:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJye6-0001ga-21
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 12:19:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28338
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 12:18:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJye4-0002fA-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 12:19:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJye4-0002f7-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 12:19:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJydx-0001fV-Fa; Wed, 12 Nov 2003 12:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AJydR-0001f5-3a
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 12:18:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28332
	for <sipping@ietf.org>; Wed, 12 Nov 2003 12:18:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJydP-0002f0-00
	for sipping@ietf.org; Wed, 12 Nov 2003 12:18:27 -0500
Received: from ondar.cablelabs.com ([192.160.73.61])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AJydO-0002et-00
	for sipping@ietf.org; Wed, 12 Nov 2003 12:18:26 -0500
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20])
	by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id hACHGtoK014352;
	Wed, 12 Nov 2003 10:16:56 -0700 (MST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] KPML Digit Maps
Date: Wed, 12 Nov 2003 10:16:55 -0700
Message-ID: <AEE1FD45F580334296FDA24A1167FFA50284DD@srvxchg.cablelabs.com>
Thread-Topic: [Sipping] KPML Digit Maps
Thread-Index: AcOpNktM5+75V99XRwCfG/28QAMtHwAA7U7w
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Eric Burger" <eburger@snowshore.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Cc: <fandreas@cisco.com>, <bfoster@cisco.com>
X-Approved: ondar
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Eric,
Comments inline.
Jean-Fran=E7ois=20

Eric Burger [mailto:eburger@snowshore.com] wrote
> Right now, KPML specifies 3 mandatory digit map styles:
>  - Regular Expressions
>  - H.248.1 digitmap
>  - J.162   digitmap
J.162 may appear an obscur ITU-T spec... it is the ITU-T recommendation =
for NCS, the Network Control Signaling protocol defined by PacketCable =
and it is based on the IETF MGCP RFC 2705. On digitmaps, NCS (j.162) =
digit maps follow the mgcp digit maps (Flemming or Bill can correct me - =
there are some variances between the digitmap bnf j.162-ncs, rfc2705 and =
rfc3534 but the latter could be considered as refinements).=20
This digitmap format is used by many PacketCable MTA CPE vendors and CMS =
call agents today.
BTW - MGCP digit map a la RFC 3435 which defines some additional =
ExtensionDigitMapLetters could be added above.

> Choices are:
>  1. We can pick one, and only one digit map style.
>  2. We can negotiate the style, with a mandatory
>     to implement for guaranteed baseline
>     interoperability.
>=20
> There was a leaning in Minneapolis towards option #2.
One can implement an mgcp digit map using a regexp. You eliminate the =
negotiation complexity for this and the management or registration of =
the styles. Why couldn't a regexp be the only option: option #1?

> The=20
> mechanism roughly would be to put a parameter on the event:=20
> kpml header in the SUBSCRIBE, with a suitable failure if the=20
> style is not supported by the KPML server.  Given that there=20
> are already three (or four, see below) different digit map=20
> styles, this probably would become an IANA-registered tag.

>=20
> For the people that think expression evaluation is=20
> computationally complex, one of the styles can be a hardcode=20
> of "match digit."  [Ed. Note: this mode is not really useful=20
> for the reasons given, in that expression evaluation is not=20
> computationally complex, especially when compared to the=20
> computational complexity of running a SIP stack or (if on a=20
> single processor) the complexity of detecting DTMF).]
>=20
> Comments?

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 14:40:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03644
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 14:40:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0qc-0001o6-8r
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 14:40:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACJeEQe006940
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 14:40:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0qa-0001nh-Kp
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 14:40:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03612
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 14:39:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0qX-0004Ru-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 14:40:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0qW-0004Rr-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 14:40:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0qQ-0001lh-Pg; Wed, 12 Nov 2003 14:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK0pa-0001ji-IS
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 14:39:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03561
	for <sipping@ietf.org>; Wed, 12 Nov 2003 14:38:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0pX-0004Qi-00
	for sipping@ietf.org; Wed, 12 Nov 2003 14:39:07 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK0pW-0004Qd-00
	for sipping@ietf.org; Wed, 12 Nov 2003 14:39:06 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hACJcRa00342;
	Wed, 12 Nov 2003 14:38:27 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W3H87RZQ; Wed, 12 Nov 2003 14:38:27 -0500
Received: from nortelnetworks.com (acart189.ca.nortel.com [47.130.17.68]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5NM4Q; Wed, 12 Nov 2003 14:38:27 -0500
Message-ID: <3FB28C2B.1050009@nortelnetworks.com>
Date: Wed, 12 Nov 2003 13:38:19 -0600
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: Eric Burger <eburger@snowshore.com>, "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] KPML Digit Maps
References: <AEE1FD45F580334296FDA24A1167FFA50284DD@srvxchg.cablelabs.com>
In-Reply-To: <AEE1FD45F580334296FDA24A1167FFA50284DD@srvxchg.cablelabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars04f.nortelnetworks.com id hACJcRa00342
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

H.248 actually has two digit map procedures now: H.248.1 and H.248.16.

Regarding Jean-Fran=E7ois's comment: what about digit timing?  That goes=20
beyond regexp.

Jean-Francois Mule wrote:

> Hi Eric,
> Comments inline.
> Jean-Fran=E7ois=20
>=20
> Eric Burger [mailto:eburger@snowshore.com] wrote
>=20
>>Right now, KPML specifies 3 mandatory digit map styles:
>> - Regular Expressions
>> - H.248.1 digitmap
>> - J.162   digitmap
>=20
> J.162 may appear an obscur ITU-T spec... it is the ITU-T recommendation=
 for NCS, the Network Control Signaling protocol defined by PacketCable a=
nd it is based on the IETF MGCP RFC 2705. On digitmaps, NCS (j.162) digit=
 maps follow the mgcp digit maps (Flemming or Bill can correct me - there=
 are some variances between the digitmap bnf j.162-ncs, rfc2705 and rfc35=
34 but the latter could be considered as refinements).=20
> This digitmap format is used by many PacketCable MTA CPE vendors and CM=
S call agents today.
> BTW - MGCP digit map a la RFC 3435 which defines some additional Extens=
ionDigitMapLetters could be added above.
>=20
>=20
>>Choices are:
>> 1. We can pick one, and only one digit map style.
>> 2. We can negotiate the style, with a mandatory
>>    to implement for guaranteed baseline
>>    interoperability.
>>
>>There was a leaning in Minneapolis towards option #2.
>=20
> One can implement an mgcp digit map using a regexp. You eliminate the n=
egotiation complexity for this and the management or registration of the =
styles. Why couldn't a regexp be the only option: option #1?
>=20
>=20
>>The=20
>>mechanism roughly would be to put a parameter on the event:=20
>>kpml header in the SUBSCRIBE, with a suitable failure if the=20
>>style is not supported by the KPML server.  Given that there=20
>>are already three (or four, see below) different digit map=20
>>styles, this probably would become an IANA-registered tag.
>=20
>=20
>>For the people that think expression evaluation is=20
>>computationally complex, one of the styles can be a hardcode=20
>>of "match digit."  [Ed. Note: this mode is not really useful=20
>>for the reasons given, in that expression evaluation is not=20
>>computationally complex, especially when compared to the=20
>>computational complexity of running a SIP stack or (if on a=20
>>single processor) the complexity of detecting DTMF).]
>>
>>Comments?
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 15:01:53 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04550
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 15:01:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1BG-0003jV-81
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:01:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACK1Ykj014345
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:01:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1BG-0003jI-1G
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 15:01:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04459
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 15:01:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1BC-0004ny-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:01:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1BC-0004nv-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:01:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1Ao-0003bi-3o; Wed, 12 Nov 2003 15:01:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK19z-0003L8-QX
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 15:00:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04391
	for <sipping@ietf.org>; Wed, 12 Nov 2003 15:00:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK19w-0004jo-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:00:12 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK19w-0004j9-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:00:12 -0500
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 12 Nov 2003 12:01:54 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hACJxcmU018850
	for <sipping@ietf.org>; Wed, 12 Nov 2003 11:59:39 -0800 (PST)
Received: from ORANLT.ietf58.ietf.org (sjc-vpn1-428.cisco.com [10.21.97.172])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJW89424;
	Wed, 12 Nov 2003 11:59:36 -0800 (PST)
Date: Wed, 12 Nov 2003 14:59:21 -0500
From: "David R. Oran" <oran@cisco.com>
To: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] KPML Digit Maps
Message-ID: <189736506.1068649161@ORANLT.ietf58.ietf.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Before giving up and playing negotiation games, I'd like to see if it 
impossible politically to "just pick".

So, I would like to formally propose:

1a. We pick regular expressions as the only digit map style supported by 
KPML.

I won't be terribly unhappy if this is shot down, but our lives would sure 
be better if we could KISS digit maps for KPML.

Dave.

--On Wednesday, November 12, 2003 11:04 AM -0500 Eric Burger 
<eburger@snowshore.com> wrote:

> Right now, KPML specifies 3 mandatory digit map styles:
>  - Regular Expressions
>  - H.248.1 digitmap
>  - J.162   digitmap
>
> Choices are:
>  1. We can pick one, and only one digit map style.
>  2. We can negotiate the style, with a mandatory
>     to implement for guaranteed baseline
>     interoperability.
>
> There was a leaning in Minneapolis towards option #2.  The mechanism
> roughly would be to put a parameter on the event: kpml header in the
> SUBSCRIBE, with a suitable failure if the style is not supported by the
> KPML server.  Given that there are already three (or four, see below)
> different digit map styles, this probably would become an IANA-registered
> tag.
>
> For the people that think expression evaluation is computationally
> complex, one of the styles can be a hardcode of "match digit."  [Ed.
> Note: this mode is not really useful for the reasons given, in that
> expression evaluation is not computationally complex, especially when
> compared to the computational complexity of running a SIP stack or (if on
> a single processor) the complexity of detecting DTMF).]
>
> Comments?
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP



------------------------
David R. Oran
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720
Office: +1 978 264 2048
VoIP: +1 408 571 4576
Email: oran@cisco.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 15:13:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06166
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 15:13:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1MV-0006S2-86
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:13:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACKDBQv024792
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:13:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1MV-0006Rn-0w
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 15:13:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06105
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 15:12:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1MT-00056g-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:13:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1MT-00056d-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:13:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1MJ-0006QP-Ku; Wed, 12 Nov 2003 15:12:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1Lw-0006PQ-LV
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 15:12:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06028
	for <sipping@ietf.org>; Wed, 12 Nov 2003 15:12:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Lv-000564-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:12:35 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Lu-00055d-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:12:34 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id hACKB7Gd021770;
	Wed, 12 Nov 2003 14:11:07 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <W4467W2W>; Wed, 12 Nov 2003 14:11:08 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E865FF@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "Sipping (E-mail)"
	 <sipping@ietf.org>
Subject: RE: [Sipping] KPML Digit Maps
Date: Wed, 12 Nov 2003 14:11:07 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Unless doing so will significantly impair progress, I'm
inclined to agree with Dave's recommendation: one digit
map format, and make it regexes.

/a

> -----Original Message-----
> From: David R. Oran [mailto:oran@cisco.com]
> Sent: Wednesday, November 12, 2003 13:59
> To: Sipping (E-mail)
> Subject: Re: [Sipping] KPML Digit Maps
> 
> 
> Before giving up and playing negotiation games, I'd like to see if it 
> impossible politically to "just pick".
> 
> So, I would like to formally propose:
> 
> 1a. We pick regular expressions as the only digit map style 
> supported by 
> KPML.
> 
> I won't be terribly unhappy if this is shot down, but our 
> lives would sure 
> be better if we could KISS digit maps for KPML.
> 
> Dave.
> 
> --On Wednesday, November 12, 2003 11:04 AM -0500 Eric Burger 
> <eburger@snowshore.com> wrote:
> 
> > Right now, KPML specifies 3 mandatory digit map styles:
> >  - Regular Expressions
> >  - H.248.1 digitmap
> >  - J.162   digitmap
> >
> > Choices are:
> >  1. We can pick one, and only one digit map style.
> >  2. We can negotiate the style, with a mandatory
> >     to implement for guaranteed baseline
> >     interoperability.
> >
> > There was a leaning in Minneapolis towards option #2.  The mechanism
> > roughly would be to put a parameter on the event: kpml header in the
> > SUBSCRIBE, with a suitable failure if the style is not 
> supported by the
> > KPML server.  Given that there are already three (or four, 
> see below)
> > different digit map styles, this probably would become an 
> IANA-registered
> > tag.
> >
> > For the people that think expression evaluation is computationally
> > complex, one of the styles can be a hardcode of "match digit."  [Ed.
> > Note: this mode is not really useful for the reasons given, in that
> > expression evaluation is not computationally complex, 
> especially when
> > compared to the computational complexity of running a SIP 
> stack or (if on
> > a single processor) the complexity of detecting DTMF).]
> >
> > Comments?
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> 
> 
> ------------------------
> David R. Oran
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720
> Office: +1 978 264 2048
> VoIP: +1 408 571 4576
> Email: oran@cisco.com
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 15:41:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08099
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 15:41:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1nc-0001Ti-7j
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:41:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACKfCDW005676
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 15:41:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1nb-0001TD-Rl
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 15:41:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08048
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 15:40:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1nZ-0005fZ-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:41:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1nZ-0005fW-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 15:41:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1nU-0001Ns-82; Wed, 12 Nov 2003 15:41:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1nN-0001Mn-3V
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 15:40:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08024
	for <sipping@ietf.org>; Wed, 12 Nov 2003 15:40:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1nL-0005fM-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:40:55 -0500
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1nI-0005et-00
	for sipping@ietf.org; Wed, 12 Nov 2003 15:40:53 -0500
Received: from zcard307.ca.nortel.com (americasm07.nt.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hACKdHW03652;
	Wed, 12 Nov 2003 15:39:17 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id WTC11T2V; Wed, 12 Nov 2003 15:39:17 -0500
Received: from nortelnetworks.com (acart189.ca.nortel.com [47.130.17.68]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5NMVK; Wed, 12 Nov 2003 15:39:17 -0500
Message-ID: <3FB29A70.305@nortelnetworks.com>
Date: Wed, 12 Nov 2003 14:39:12 -0600
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@dynamicsoft.com>
CC: "'Michael Hammer'" <mhammer@cisco.com>,
        Arjun Roychowdhury <aroychow@hns.com>, Jeff zhao <zhaozf@eastcom.com>,
        sipping@ietf.org
Subject: Re: [Sipping] about SIP-I
References: <9BF66EBF6BEFD942915B4D4D45C051F3E86600@dyn-tx-exch-001.dynamicsoft.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86600@dyn-tx-exch-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The first thing I can think of is that SIP-I doesn't bother to 
encapsulate SAMs (if encapsulation is being used).  The digits in the 
SAM get absorbed into the Request-URI.  The original IAM is still 
encapsulated, because, of course, it contains more than just called digits.

RFC 3578 and SIP-I are similar in that they both urge en bloc signalling 
if possible.  They both say that if you do use overlap across the SIP 
network, you must administer routing to ensure all messages for a given 
call go to the same gateway.

Adam Roach wrote:

> I haven't had the opportunity to look at Q.1912.5. Do the
> procedures described in it vary significantly from RFC 3578?
> 
> /a
> 
> 
>>-----Original Message-----
>>From: Michael Hammer [mailto:mhammer@cisco.com]
>>Sent: Wednesday, November 12, 2003 10:01
>>To: Arjun Roychowdhury
>>Cc: Jeff zhao; sipping@ietf.org
>>Subject: Re: [Sipping] about SIP-I
>>
>>
>>SIP-I stands for SIP with encapsulated ISUP.  Look for 
>>Q.1912.5 currently 
>>under ballot review.  It is 95% the same as RFC-3398, but 
>>also includes 
>>things such as Overlap signaling, different view of Cause 
>>code mapping, and 
>>some other details not covered already.
>>
>>Mike
>>
>>At 08:18 AM 11/12/2003 -0500, Arjun Roychowdhury wrote:
>>
>>>Jeff, I believe this is a part of ITU-SG11's effort to provide
>>>SIP/isup-bicc mapping afaik. if you are a ties member you 
>>
>>can download
>>
>>>the document from itu. I dont believe its a new protocol.
>>>This is as far as my knowledge takes me .
>>>
>>>regds
>>>arjun
>>>
>>>--
>>>Arjun Roychowdhury @ Hughes Software Systems
>>>11717 Exploration Lane, Germantown MD 20876
>>>(O): 301 212 7860
>>>VOIP: (SIP) 10303@fwd.pulver.com (PSTN alias:360-207-0467)
>>>
>>>
>>>
>>>
>>>"Jeff zhao" <zhaozf@eastcom.com>
>>>Sent by: sipping-admin@ietf.org
>>>11/12/2003 12:09 AM
>>>
>>>
>>>        To:     <sipping@ietf.org>
>>>        cc:
>>>        Subject:        [Sipping] about SIP-I
>>>
>>>
>>>I notice that there is a new protocol named SIP-I(Session Initiation
>>>Protocol for Interworking).
>>>
>>>Could anyone tell me more information about it or where I 
>>
>>can find more
>>
>>>document.
>>>
>>>Thanks.
>>>
>>>Jeff zhao
>>>
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>>Use sip@ietf.org for new developments of core SIP
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 16:16:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10100
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 16:16:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2LP-0007UF-V5
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:16:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACLG7qj028773
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:16:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2LP-0007U0-Rs
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 16:16:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10067
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 16:15:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2LN-0006WZ-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:16:05 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2LN-0006W8-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:16:05 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AK2Fa-0003mC-Ju
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:10:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2FV-0006iS-4i; Wed, 12 Nov 2003 16:10:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2Eo-0006dy-4i
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 16:09:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09768
	for <sipping@ietf.org>; Wed, 12 Nov 2003 16:09:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Em-0006NF-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:09:16 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Ek-0006NC-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:09:15 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hACL72I2003869;
	Wed, 12 Nov 2003 22:07:02 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <WHXD3CBR>; Wed, 12 Nov 2003 22:07:34 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF05683C6B@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: "'Adam Roach'" <adam@dynamicsoft.com>,
        Arjun Roychowdhury
	 <aroychow@hns.com>,
        Jeff zhao <zhaozf@eastcom.com>, sipping@ietf.org
Subject: RE: [Sipping] about SIP-I
Date: Wed, 12 Nov 2003 22:05:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Hi,

In a few cases Q.1912.5 also requires the interworking unit to "generate" an ISUP message to be encapsulated in the SIP message, when there is no incoming ISUP message triggering the SIP message.

Regards,

Christer Holmberg
Ericsson Finland

> -----Original Message-----
> From: Michael Hammer [mailto:mhammer@cisco.com]
> Sent: 12. marraskuuta 2003 23:03
> To: Christer Holmberg (JO/LMF)
> Cc: 'Adam Roach'; Arjun Roychowdhury; Jeff zhao; sipping@ietf.org
> Subject: RE: [Sipping] about SIP-I
> 
> 
> The other thing that comes to mind is the definition of interworking 
> timers:  T(OIW1), T(OIW2), and T(OIW3)=SIP dialog protection 
> timer, where 
> the OIW means outgoing interworking, i.e. from the ISUP to SIP 
> network.  Expiry results in sending of INVITE and ACM, 
> sending ACM, and 
> sending REL, respectively.
> 
> Mike
> 
> 
> At 09:45 PM 11/12/2003 +0100, Christer Holmberg (JO/LMF) wrote:
> 
> >Hi,
> >
> > From an ISUP encapsulation point of view, the major changes 
> I can think 
> > of (I don't have the spec in front of me) are the following:
> >
> >1. SIP-I does not require the use of S/MIME
> >2. SIP-I requires the receiver to understand ISUP (the value of the 
> >Content-Disposition handling parameter is "required").
> >3. In SIP overlap scenarios, "updated" IAMs are encapsulated 
> in every 
> >INVITE (instead of IAM + SAMs).
> >
> >When it comes to the "pure" SIP/ISUP message mapping the 
> procedures are 
> >rather similar (there are variations in the cause code mapping etc). 
> >Q.1912.5 does specify scenarios using pre-conditions, which 
> RFC3578 does 
> >not. Q.1912.5 also specifies ISUP parameters etc in more detail than 
> >RFC3578. The ISUP TMR parameters can also be changed depending on 
> >information that you get from the SIP network.
> >
> >I guess there is more differences, but these are the major 
> ones I could 
> >think of now.
> >
> >Regards,
> >
> >Christer Holmberg
> >Ericsson Finland
> >
> >
> > > -----Original Message-----
> > > From: sipping-admin@ietf.org
> > > [mailto:sipping-admin@ietf.org]On Behalf Of
> > > Adam Roach
> > > Sent: 12. marraskuuta 2003 22:18
> > > To: 'Michael Hammer'; Arjun Roychowdhury
> > > Cc: Jeff zhao; sipping@ietf.org
> > > Subject: RE: [Sipping] about SIP-I
> > >
> > >
> > > I haven't had the opportunity to look at Q.1912.5. Do the
> > > procedures described in it vary significantly from RFC 3578?
> > >
> > > /a
> > >
> > > > -----Original Message-----
> > > > From: Michael Hammer [mailto:mhammer@cisco.com]
> > > > Sent: Wednesday, November 12, 2003 10:01
> > > > To: Arjun Roychowdhury
> > > > Cc: Jeff zhao; sipping@ietf.org
> > > > Subject: Re: [Sipping] about SIP-I
> > > >
> > > >
> > > > SIP-I stands for SIP with encapsulated ISUP.  Look for
> > > > Q.1912.5 currently
> > > > under ballot review.  It is 95% the same as RFC-3398, but
> > > > also includes
> > > > things such as Overlap signaling, different view of Cause
> > > > code mapping, and
> > > > some other details not covered already.
> > > >
> > > > Mike
> > > >
> > > > At 08:18 AM 11/12/2003 -0500, Arjun Roychowdhury wrote:
> > > > >Jeff, I believe this is a part of ITU-SG11's effort to provide
> > > > >SIP/isup-bicc mapping afaik. if you are a ties member you
> > > > can download
> > > > >the document from itu. I dont believe its a new protocol.
> > > > >This is as far as my knowledge takes me .
> > > > >
> > > > >regds
> > > > >arjun
> > > > >
> > > > >--
> > > > >Arjun Roychowdhury @ Hughes Software Systems
> > > > >11717 Exploration Lane, Germantown MD 20876
> > > > >(O): 301 212 7860
> > > > >VOIP: (SIP) 10303@fwd.pulver.com (PSTN alias:360-207-0467)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >"Jeff zhao" <zhaozf@eastcom.com>
> > > > >Sent by: sipping-admin@ietf.org
> > > > >11/12/2003 12:09 AM
> > > > >
> > > > >
> > > > >         To:     <sipping@ietf.org>
> > > > >         cc:
> > > > >         Subject:        [Sipping] about SIP-I
> > > > >
> > > > >
> > > > >I notice that there is a new protocol named SIP-I(Session
> > > Initiation
> > > > >Protocol for Interworking).
> > > > >
> > > > >Could anyone tell me more information about it or where I
> > > > can find more
> > > > >document.
> > > > >
> > > > >Thanks.
> > > > >
> > > > >Jeff zhao
> > > > >
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >Sipping mailing list
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > > >This list is for NEW development of the application of SIP
> > > > >Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > >Use sip@ietf.org for new developments of core SIP
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 16:31:08 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10777
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 16:31:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2Ze-0008Dc-Q9
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:30:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACLUonZ031586
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:30:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2Ze-0008DN-ME
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 16:30:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10623
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 16:30:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Zb-0006j5-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:30:47 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Lg-0006W8-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:16:24 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AK29k-0003cS-QC
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:04:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK29h-0005KS-4D; Wed, 12 Nov 2003 16:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK28z-0005JX-Qt
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 16:03:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09528
	for <sipping@ietf.org>; Wed, 12 Nov 2003 16:03:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK28y-0006Gy-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:03:16 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK28x-0006Gd-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:03:15 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hACL2fxg022311;
	Wed, 12 Nov 2003 16:02:41 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ATW02841;
	Wed, 12 Nov 2003 13:02:40 -0800 (PST)
Message-Id: <4.3.2.7.2.20031112155652.02f78008@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 12 Nov 2003 16:02:39 -0500
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] about SIP-I
Cc: "'Adam Roach'" <adam@dynamicsoft.com>,
        Arjun Roychowdhury <aroychow@hns.com>, Jeff zhao <zhaozf@eastcom.com>,
        sipping@ietf.org
In-Reply-To: <F8EFC4B4A8C016428BC1F589296D4FBF05683C69@esealnt630.al.sw.
 ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

The other thing that comes to mind is the definition of interworking 
timers:  T(OIW1), T(OIW2), and T(OIW3)=SIP dialog protection timer, where 
the OIW means outgoing interworking, i.e. from the ISUP to SIP 
network.  Expiry results in sending of INVITE and ACM, sending ACM, and 
sending REL, respectively.

Mike


At 09:45 PM 11/12/2003 +0100, Christer Holmberg (JO/LMF) wrote:

>Hi,
>
> From an ISUP encapsulation point of view, the major changes I can think 
> of (I don't have the spec in front of me) are the following:
>
>1. SIP-I does not require the use of S/MIME
>2. SIP-I requires the receiver to understand ISUP (the value of the 
>Content-Disposition handling parameter is "required").
>3. In SIP overlap scenarios, "updated" IAMs are encapsulated in every 
>INVITE (instead of IAM + SAMs).
>
>When it comes to the "pure" SIP/ISUP message mapping the procedures are 
>rather similar (there are variations in the cause code mapping etc). 
>Q.1912.5 does specify scenarios using pre-conditions, which RFC3578 does 
>not. Q.1912.5 also specifies ISUP parameters etc in more detail than 
>RFC3578. The ISUP TMR parameters can also be changed depending on 
>information that you get from the SIP network.
>
>I guess there is more differences, but these are the major ones I could 
>think of now.
>
>Regards,
>
>Christer Holmberg
>Ericsson Finland
>
>
> > -----Original Message-----
> > From: sipping-admin@ietf.org
> > [mailto:sipping-admin@ietf.org]On Behalf Of
> > Adam Roach
> > Sent: 12. marraskuuta 2003 22:18
> > To: 'Michael Hammer'; Arjun Roychowdhury
> > Cc: Jeff zhao; sipping@ietf.org
> > Subject: RE: [Sipping] about SIP-I
> >
> >
> > I haven't had the opportunity to look at Q.1912.5. Do the
> > procedures described in it vary significantly from RFC 3578?
> >
> > /a
> >
> > > -----Original Message-----
> > > From: Michael Hammer [mailto:mhammer@cisco.com]
> > > Sent: Wednesday, November 12, 2003 10:01
> > > To: Arjun Roychowdhury
> > > Cc: Jeff zhao; sipping@ietf.org
> > > Subject: Re: [Sipping] about SIP-I
> > >
> > >
> > > SIP-I stands for SIP with encapsulated ISUP.  Look for
> > > Q.1912.5 currently
> > > under ballot review.  It is 95% the same as RFC-3398, but
> > > also includes
> > > things such as Overlap signaling, different view of Cause
> > > code mapping, and
> > > some other details not covered already.
> > >
> > > Mike
> > >
> > > At 08:18 AM 11/12/2003 -0500, Arjun Roychowdhury wrote:
> > > >Jeff, I believe this is a part of ITU-SG11's effort to provide
> > > >SIP/isup-bicc mapping afaik. if you are a ties member you
> > > can download
> > > >the document from itu. I dont believe its a new protocol.
> > > >This is as far as my knowledge takes me .
> > > >
> > > >regds
> > > >arjun
> > > >
> > > >--
> > > >Arjun Roychowdhury @ Hughes Software Systems
> > > >11717 Exploration Lane, Germantown MD 20876
> > > >(O): 301 212 7860
> > > >VOIP: (SIP) 10303@fwd.pulver.com (PSTN alias:360-207-0467)
> > > >
> > > >
> > > >
> > > >
> > > >"Jeff zhao" <zhaozf@eastcom.com>
> > > >Sent by: sipping-admin@ietf.org
> > > >11/12/2003 12:09 AM
> > > >
> > > >
> > > >         To:     <sipping@ietf.org>
> > > >         cc:
> > > >         Subject:        [Sipping] about SIP-I
> > > >
> > > >
> > > >I notice that there is a new protocol named SIP-I(Session
> > Initiation
> > > >Protocol for Interworking).
> > > >
> > > >Could anyone tell me more information about it or where I
> > > can find more
> > > >document.
> > > >
> > > >Thanks.
> > > >
> > > >Jeff zhao
> > > >
> > > >
> > > >
> > > >_______________________________________________
> > > >Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > > >This list is for NEW development of the application of SIP
> > > >Use sip-implementors@cs.columbia.edu for questions on current sip
> > > >Use sip@ietf.org for new developments of core SIP
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 12 16:31:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10805
	for <sipping-archive@odin.ietf.org>; Wed, 12 Nov 2003 16:31:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2Zn-0008EV-JG
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:31:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACLUxEA031641
	for sipping-archive@odin.ietf.org; Wed, 12 Nov 2003 16:30:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK2Zn-0008EF-FV
	for sipping-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 16:30:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10664
	for <sipping-web-archive@ietf.org>; Wed, 12 Nov 2003 16:30:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Zl-0006lU-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:30:57 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK2Lk-0006W8-00
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:16:29 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AK27x-0003a5-NF
	for sipping-web-archive@ietf.org; Wed, 12 Nov 2003 16:02:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK27m-00053T-SB; Wed, 12 Nov 2003 16:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK26x-0004ps-4c
	for sipping@optimus.ietf.org; Wed, 12 Nov 2003 16:01:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09420
	for <sipping@ietf.org>; Wed, 12 Nov 2003 16:00:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK26v-0006EZ-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:01:09 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK26p-0006C4-00
	for sipping@ietf.org; Wed, 12 Nov 2003 16:01:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hACL0La21905;
	Wed, 12 Nov 2003 16:00:22 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W3H87T9F; Wed, 12 Nov 2003 16:00:22 -0500
Received: from nortelnetworks.com (acart189.ca.nortel.com [47.130.17.68]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5NMVV; Wed, 12 Nov 2003 16:00:21 -0500
Message-ID: <3FB29F63.2070704@nortelnetworks.com>
Date: Wed, 12 Nov 2003 15:00:19 -0600
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] about SIP-I
References: <F8EFC4B4A8C016428BC1F589296D4FBF05683C69@esealnt630.al.sw.ericsson.se>
In-Reply-To: <F8EFC4B4A8C016428BC1F589296D4FBF05683C69@esealnt630.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

A key difference between Q.1912.5 and RFCs 3372-3398-3578 is that the 
latter contain a lot of good SIP-side advice.  The ITU-T considered this 
part of it to be beyond their scope.  The result is that I would 
recommend that people read the RFCs, even if their interest is in 
implementing Q.1912.5.

Christer Holmberg (JO/LMF) wrote:
> Hi,
> 
>>From an ISUP encapsulation point of view, the major changes I can think of (I don't have the spec in front of me) are the following:
> 
> 1. SIP-I does not require the use of S/MIME


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 02:23:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14488
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 02:23:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBoy-0005He-PZ
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 02:23:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD7NGUj020306
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 02:23:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBoy-0005HR-87
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 02:23:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14434
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 02:23:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBou-0007dt-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 02:23:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBou-0007dp-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 02:23:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBol-0005Fj-G2; Thu, 13 Nov 2003 02:23:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBnw-0005Ef-23
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 02:22:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14333
	for <sipping@ietf.org>; Thu, 13 Nov 2003 02:21:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBns-0007da-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:22:08 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBnr-0007dK-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:22:07 -0500
Received: from dynamicsoft.com ([63.113.46.127])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hAD7Kxca016518;
	Thu, 13 Nov 2003 02:20:59 -0500 (EST)
Message-ID: <3FB330D9.905@dynamicsoft.com>
Date: Thu, 13 Nov 2003 02:20:57 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@dynamicsoft.com>
CC: "'David R. Oran'" <oran@cisco.com>, "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] KPML Digit Maps
References: <9BF66EBF6BEFD942915B4D4D45C051F3E865FF@dyn-tx-exch-001.dynamicsoft.com>
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E865FF@dyn-tx-exch-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I feel strongly that we should pick one. Having multiple ways of doing 
something is a known bad thing, and here it just seems to bring no 
real extra value.

I feel less strongly about what the thing is. But having to negotiate 
this is just silly.

-Jonathan R.

Adam Roach wrote:

> Unless doing so will significantly impair progress, I'm
> inclined to agree with Dave's recommendation: one digit
> map format, and make it regexes.
> 
> /a
> 
> 
>>-----Original Message-----
>>From: David R. Oran [mailto:oran@cisco.com]
>>Sent: Wednesday, November 12, 2003 13:59
>>To: Sipping (E-mail)
>>Subject: Re: [Sipping] KPML Digit Maps
>>
>>
>>Before giving up and playing negotiation games, I'd like to see if it 
>>impossible politically to "just pick".
>>
>>So, I would like to formally propose:
>>
>>1a. We pick regular expressions as the only digit map style 
>>supported by 
>>KPML.
>>
>>I won't be terribly unhappy if this is shot down, but our 
>>lives would sure 
>>be better if we could KISS digit maps for KPML.
>>
>>Dave.
>>
>>--On Wednesday, November 12, 2003 11:04 AM -0500 Eric Burger 
>><eburger@snowshore.com> wrote:
>>
>>
>>>Right now, KPML specifies 3 mandatory digit map styles:
>>> - Regular Expressions
>>> - H.248.1 digitmap
>>> - J.162   digitmap
>>>
>>>Choices are:
>>> 1. We can pick one, and only one digit map style.
>>> 2. We can negotiate the style, with a mandatory
>>>    to implement for guaranteed baseline
>>>    interoperability.
>>>
>>>There was a leaning in Minneapolis towards option #2.  The mechanism
>>>roughly would be to put a parameter on the event: kpml header in the
>>>SUBSCRIBE, with a suitable failure if the style is not 
>>
>>supported by the
>>
>>>KPML server.  Given that there are already three (or four, 
>>
>>see below)
>>
>>>different digit map styles, this probably would become an 
>>
>>IANA-registered
>>
>>>tag.
>>>
>>>For the people that think expression evaluation is computationally
>>>complex, one of the styles can be a hardcode of "match digit."  [Ed.
>>>Note: this mode is not really useful for the reasons given, in that
>>>expression evaluation is not computationally complex, 
>>
>>especially when
>>
>>>compared to the computational complexity of running a SIP 
>>
>>stack or (if on
>>
>>>a single processor) the complexity of detecting DTMF).]
>>>
>>>Comments?
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>>Use sip@ietf.org for new developments of core SIP
>>
>>
>>
>>------------------------
>>David R. Oran
>>Cisco Systems
>>7 Ladyslipper Lane
>>Acton, MA 01720
>>Office: +1 978 264 2048
>>VoIP: +1 408 571 4576
>>Email: oran@cisco.com
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 02:32:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14981
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 02:32:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBxa-0005vm-Jo
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 02:32:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAD7WAvB022797
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 02:32:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBxZ-0005vc-DZ
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 02:32:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14974
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 02:31:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBxV-00006q-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 02:32:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBxV-00006n-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 02:32:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBxS-0005uS-Qw; Thu, 13 Nov 2003 02:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKBwa-0005sd-M7
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 02:31:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14953
	for <sipping@ietf.org>; Thu, 13 Nov 2003 02:30:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBwW-00006X-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:31:04 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKBwW-00004P-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:31:04 -0500
Received: from dynamicsoft.com ([63.113.46.127])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hAD7Ubca016522;
	Thu, 13 Nov 2003 02:30:37 -0500 (EST)
Message-ID: <3FB3331B.5010509@dynamicsoft.com>
Date: Thu, 13 Nov 2003 02:30:35 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] SDP addressing in KPML
References: <4A3384433CE2AB46A63468CB207E209D4F69C4@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F69C4@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

As it currently stands, the scope of the app interaction framework is 
to allow an element on the call path to monitor the keypad entries 
within that call. As a result, I would have to object to adding 
functionality into KPML for the purposes of allowing third party 
monitoring from devices based on session parameters.

Now, a real issue is how to handle the case where a single dialog has 
multiple media streams. The answer, I think, lies in the beginning 
sections of the app interaction framework, which try to clarify the 
difference between a user device and a user interface. In particular, 
once we have placed a user interface (in the form of a KPML script) 
onto the device, the device is now interacting directly with the user 
interface. THere are no media streams at all in that interface. Media 
streams only carry user input when the user interface is remote from 
the client, which is not the case here. As a result, any data entered 
by the user within the context of the dialog would be applicable to 
the KPML for that dialog. On a typical single line phone, all keypad 
entry applies to the current dialog. On a multi-line phone, presumably 
one has a way to select the line (i.e., dialog), and thus the line 
selection determines which dialog the keypresses are associated with.

Thus, I dont think we need to change anything in KPML, or add any 
SDP-level addressing. The framework probably needs to discuss this 
issue, however.

-Jonathan R.



Eric Burger wrote:

> The use case for the raw SDP addressing mode is for monitoring
> elements that are not aware of the mapping from SIP dialog to
> session parameters.
> 
> While this use is debatable (I'm willing to give it up), it is
> still useful, in conjunction with the SIP dialog addressing mode,
> to indicate which m-line needs monitoring.
> 
> Comments?
> 
> 
> _______________________________________________ Sipping mailing
> list  https://www1.ietf.org/mailman/listinfo/sipping This list is
> for NEW development of the application of SIP Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 08:35:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25605
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 08:35:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHcq-0001L2-FW
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 08:35:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADDZ8G6005138
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 08:35:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHcq-0001Kn-64
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 08:35:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25571
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 08:34:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHco-0004kb-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 08:35:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHco-0004kY-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 08:35:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHcj-0001JX-TE; Thu, 13 Nov 2003 08:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKC50-0006ef-Ig
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 02:39:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15166
	for <sipping@ietf.org>; Thu, 13 Nov 2003 02:39:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKC4w-0000AE-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:39:46 -0500
Received: from bay10-f33.bay10.hotmail.com ([64.4.37.33] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKC4v-0000A2-00
	for sipping@ietf.org; Thu, 13 Nov 2003 02:39:45 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 12 Nov 2003 23:39:13 -0800
Received: from 194.237.142.7 by by10fd.bay10.hotmail.msn.com with HTTP;
	Thu, 13 Nov 2003 07:39:13 GMT
X-Originating-IP: [194.237.142.7]
X-Originating-Email: [jwalia9@hotmail.com]
From: "J Walia" <jwalia9@hotmail.com>
To: taylor@nortelnetworks.com, christer.holmberg@ericsson.com,
        sipping@ietf.org, mhammer@cisco.com, adam@dynamicsoft.com
Cc: zhaozf@eastcom.com, aroychow@hns.com
Date: Thu, 13 Nov 2003 07:39:13 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY10-F33X2gAb8fyYI00001e82@hotmail.com>
X-OriginalArrivalTime: 13 Nov 2003 07:39:13.0600 (UTC) FILETIME=[3BEDF400:01C3A9B9]
Subject: [Sipping] about SIP-I
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Well i had been reading the thread on SIP-I . It was a bit confusing since 
SIP-T and SIP-I seem to do the same thing. From a carrier prospective what 
is a better bet when interworking PSTN with Packet based network. From Tom's 
reply it seems it seems SIP-T is better but as expalined by Christian SIP-I 
seems to take care of what SIP-T RFC do not talk about. Does that mean SIP-I 
is more complete and a standardised implemetation comparing to SIP-T.

Look forward to your comments

Regard

jw

_________________________________________________________________
BharatMatrimony.com. http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 
India's premium matrimonial website.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 08:50:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26460
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 08:50:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHrJ-0002cA-Pr
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 08:50:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADDo5kO010044
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 08:50:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHrJ-0002bv-Ly
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 08:50:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26453
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 08:49:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHrI-00051s-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 08:50:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHrH-00051p-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 08:50:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHrG-0002aq-Ey; Thu, 13 Nov 2003 08:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKHr4-0002aO-3G
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 08:49:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26445
	for <sipping@ietf.org>; Thu, 13 Nov 2003 08:49:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHr2-00051h-00
	for sipping@ietf.org; Thu, 13 Nov 2003 08:49:48 -0500
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKHr2-000516-00
	for sipping@ietf.org; Thu, 13 Nov 2003 08:49:48 -0500
Received: from bertculpepper@netscape.net
	by imo-d01.mx.aol.com (mail_out_v36_r1.1.) id r.1b3.885c795 (22680);
	Thu, 13 Nov 2003 08:48:57 -0500 (EST)
Received: from  netscape.net (87.67.33.65.cfl.rr.com [65.33.67.87]) by air-in04.mx.aol.com (v97.8) with ESMTP id MAILININ41-58983fb38bc8280; Thu, 13 Nov 2003 08:48:57 -0500
Message-ID: <3FB38BFE.1050402@netscape.net>
Date: Thu, 13 Nov 2003 08:49:50 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Eric Burger <eburger@snowshore.com>, "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] SDP addressing in KPML
References: <4A3384433CE2AB46A63468CB207E209D4F69C4@zoe.office.snowshore.com> <3FB3331B.5010509@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 65.33.67.87
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I agree with Jonathan, this is out of scope IMO.  In addition, this 
complicates what I've hoped would be a relatively simple mechanism for 
applications to receive user input associated with a SIP dialog. (At a 
minimum it complicates the specification defining the mechanism.)

Regards,
Bert

Jonathan Rosenberg wrote:

> As it currently stands, the scope of the app interaction framework is to 
> allow an element on the call path to monitor the keypad entries within 
> that call. As a result, I would have to object to adding functionality 
> into KPML for the purposes of allowing third party monitoring from 
> devices based on session parameters.
> 
> Now, a real issue is how to handle the case where a single dialog has 
> multiple media streams. The answer, I think, lies in the beginning 
> sections of the app interaction framework, which try to clarify the 
> difference between a user device and a user interface. In particular, 
> once we have placed a user interface (in the form of a KPML script) onto 
> the device, the device is now interacting directly with the user 
> interface. THere are no media streams at all in that interface. Media 
> streams only carry user input when the user interface is remote from the 
> client, which is not the case here. As a result, any data entered by the 
> user within the context of the dialog would be applicable to the KPML 
> for that dialog. On a typical single line phone, all keypad entry 
> applies to the current dialog. On a multi-line phone, presumably one has 
> a way to select the line (i.e., dialog), and thus the line selection 
> determines which dialog the keypresses are associated with.
> 
> Thus, I dont think we need to change anything in KPML, or add any 
> SDP-level addressing. The framework probably needs to discuss this 
> issue, however.
> 
> -Jonathan R.
> 
> 
> 
> Eric Burger wrote:
> 
>> The use case for the raw SDP addressing mode is for monitoring
>> elements that are not aware of the mapping from SIP dialog to
>> session parameters.
>>
>> While this use is debatable (I'm willing to give it up), it is
>> still useful, in conjunction with the SIP dialog addressing mode,
>> to indicate which m-line needs monitoring.
>>
>> Comments?
>>
>>
>> _______________________________________________ Sipping mailing
>> list  https://www1.ietf.org/mailman/listinfo/sipping This list is
>> for NEW development of the application of SIP Use
>> sip-implementors@cs.columbia.edu for questions on current sip Use
>> sip@ietf.org for new developments of core SIP
>>
> 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 09:34:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28435
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 09:34:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIXw-000563-K0
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 09:34:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADEY8o2019587
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 09:34:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIXw-00055q-GX
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 09:34:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28418
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 09:33:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIXu-0005mD-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 09:34:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIXu-0005mA-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 09:34:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIXq-00054V-16; Thu, 13 Nov 2003 09:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIXc-00053z-Vh
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 09:33:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28410
	for <sipping@ietf.org>; Thu, 13 Nov 2003 09:33:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIXa-0005lw-00
	for sipping@ietf.org; Thu, 13 Nov 2003 09:33:47 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIXa-0005lb-00
	for sipping@ietf.org; Thu, 13 Nov 2003 09:33:46 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hADEWbb9017500;
	Thu, 13 Nov 2003 14:32:37 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHK8F5>; Thu, 13 Nov 2003 08:32:37 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56447@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'J Walia'" <jwalia9@hotmail.com>,
        "'taylor@nortelnetworks.com'"
	 <taylor@nortelnetworks.com>,
        "'christer.holmberg@ericsson.com'"
	 <christer.holmberg@ericsson.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>,
        "'mhammer@cisco.com'" <mhammer@cisco.com>,
        "'adam@dynamicsoft.com'" <adam@dynamicsoft.com>
Cc: "'zhaozf@eastcom.com'" <zhaozf@eastcom.com>,
        "'aroychow@hns.com'"
	 <aroychow@hns.com>
Subject: RE: [Sipping] about SIP-I
Date: Thu, 13 Nov 2003 08:32:34 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Although I know this work in the ITU-T only from an earlier stage, I believe
one of the more important philosophical distinctions is that SIP-I is
concerned only with carriers interworking with one another, as opposed to
users interworking with carriers. In other words, they assume a constrained
network in which gateways will not interface with untrusted user agents, and
so on. Hence, they entertain different security requirements, and so on.
Here in the IETF, we must plan for the use of our protocols over the public
Internet. I do not believe that it is meaningful to say that one is "more
complete" than the other - they come from different communities with
different assumptions.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: J Walia [mailto:jwalia9@hotmail.com]
> Sent: Thursday, November 13, 2003 1:39 AM
> To: taylor@nortelnetworks.com; christer.holmberg@ericsson.com;
> sipping@ietf.org; mhammer@cisco.com; adam@dynamicsoft.com
> Cc: zhaozf@eastcom.com; aroychow@hns.com
> Subject: [Sipping] about SIP-I
> 
> 
> Well i had been reading the thread on SIP-I . It was a bit 
> confusing since 
> SIP-T and SIP-I seem to do the same thing. From a carrier 
> prospective what 
> is a better bet when interworking PSTN with Packet based 
> network. From Tom's 
> reply it seems it seems SIP-T is better but as expalined by 
> Christian SIP-I 
> seems to take care of what SIP-T RFC do not talk about. Does 
> that mean SIP-I 
> is more complete and a standardised implemetation comparing to SIP-T.
> 
> Look forward to your comments
> 
> Regard
> 
> jw
> 
> _________________________________________________________________
> BharatMatrimony.com. 
http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 
India's premium matrimonial website.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 09:51:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29255
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 09:51:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIoL-0006Zu-ML
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 09:51:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADEp5Sx025280
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 09:51:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIoL-0006Zf-Hn
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 09:51:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29227
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 09:50:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIoJ-000656-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 09:51:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIoI-000653-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 09:51:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIoI-0006YU-Kw; Thu, 13 Nov 2003 09:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKInu-0006W1-M5
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 09:50:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29205
	for <sipping@ietf.org>; Thu, 13 Nov 2003 09:50:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIns-00064y-00
	for sipping@ietf.org; Thu, 13 Nov 2003 09:50:36 -0500
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIns-00064t-00
	for sipping@ietf.org; Thu, 13 Nov 2003 09:50:36 -0500
Received: from bertculpepper@netscape.net
	by imo-d01.mx.aol.com (mail_out_v36_r1.1.) id 7.1b5.88811ac (16237);
	Thu, 13 Nov 2003 09:50:02 -0500 (EST)
Received: from  netscape.net (87.67.33.65.cfl.rr.com [65.33.67.87]) by air-in03.mx.aol.com (v97.8) with ESMTP id MAILININ31-3f6d3fb39a18241; Thu, 13 Nov 2003 09:50:02 -0500
Message-ID: <3FB39A4F.8040202@netscape.net>
Date: Thu, 13 Nov 2003 09:50:55 -0500
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>, SIPPING List <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 65.33.67.87
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Comments on draft-ietf-sipping-kpml-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I noticed the following on my first read of the draft.

It's not clear to me how to indicate in a KPML document the SIP dialog 
an entity in the call path wishes to receive associated key presses. 
The "leg", "call-id", "from-tag", and "to-tag" described in section 3.2 
don't seem to be specified in section 7.  (BTW, I don't think "leg" will 
be needed if the SDP addressing is removed.)  An example code fragment 
would be useful I believe.

Section 3.6.3 contains the text

    This means that further SUBSCRIBE requests on the same dialog MUST
    result in SIP 481 SUBSCRIPTION DOES NOT EXIST response.

This seems odd to me, wouldn't a subsequent SUBSCRIBE request result in 
a new subscription or be denied by the notifier.  Or maybe it should 
read "...NOTIFY requests..." in the above.

The message examples in section 6.1 have what looks like editorial 
comments around the CSeq lines, specifically F10 and F11.

Regards,
Bert


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 10:37:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03316
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 10:37:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJWu-0004Zo-Vn
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 10:37:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADFb8Xi017586
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 10:37:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJWu-0004ZZ-HG
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 10:37:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03301
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 10:36:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWq-00072n-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 10:37:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWq-00072j-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 10:37:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJWo-0004XJ-6I; Thu, 13 Nov 2003 10:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJWG-0004WU-WF
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 10:36:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03280
	for <sipping@ietf.org>; Thu, 13 Nov 2003 10:36:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWE-00071e-00
	for sipping@ietf.org; Thu, 13 Nov 2003 10:36:26 -0500
Received: from mail4.telekom.de ([195.243.210.197])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWD-00070u-00
	for sipping@ietf.org; Thu, 13 Nov 2003 10:36:25 -0500
Received: from g8pbr.blf01.telekom.de by mail2.dmz.telekom.de with ESMTP; Thu, 13 Nov 2003 16:35:36 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <WTJWFBAW>; Thu, 13 Nov 2003 16:35:50 +0100
Message-Id: <953B9B08F98DD61183F8000347AE660102862D09@G8PPV.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: jwalia9@hotmail.com, taylor@nortelnetworks.com,
        christer.holmberg@ericsson.com, sipping@ietf.org, mhammer@cisco.com,
        adam@dynamicsoft.com
Cc: zhaozf@eastcom.com, aroychow@hns.com
Subject: AW: [Sipping] about SIP-I
Date: Thu, 13 Nov 2003 16:35:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi,
From a telecom operator point of view SIP-I is the solution that guarantees a carrier grade and trusted connection for the trunking case. A operator using SIP-I between public PSTN/ISDN networks will ever stick to the Q.1912.5 solution, because it is describing the procedures and demands regarding the Interworking Unit at the network boundary.
The philosophy behind Q.1912.5 is that the SIP interface is seen as an NNI and not as defined within IETF as an UNI.

Best Regards

Roland

> -----Ursprungliche Nachricht-----
> Von: J Walia [mailto:jwalia9@hotmail.com]
> Gesendet: Donnerstag, 13. November 2003 08:39
> An: taylor@nortelnetworks.com; christer.holmberg@ericsson.com;
> sipping@ietf.org; mhammer@cisco.com; adam@dynamicsoft.com
> Cc: zhaozf@eastcom.com; aroychow@hns.com
> Betreff: [Sipping] about SIP-I
> 
> 
> Well i had been reading the thread on SIP-I . It was a bit 
> confusing since 
> SIP-T and SIP-I seem to do the same thing. From a carrier 
> prospective what 
> is a better bet when interworking PSTN with Packet based 
> network. From Tom's 
> reply it seems it seems SIP-T is better but as expalined by 
> Christian SIP-I 
> seems to take care of what SIP-T RFC do not talk about. Does 
> that mean SIP-I 
> is more complete and a standardised implemetation comparing to SIP-T.
> 
> Look forward to your comments
> 
> Regard
> 
> jw
> 
> _________________________________________________________________
> BharatMatrimony.com. 
> http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 
> India's premium matrimonial website.
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 14:08:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13160
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 14:08:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKMp9-0004et-VB
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 14:08:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADJ8BBd017908
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 14:08:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKMp9-0004el-M2
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 14:08:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13146
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 14:07:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKMp7-00031f-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 14:08:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKMp6-00031c-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 14:08:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKMp0-0004d3-FO; Thu, 13 Nov 2003 14:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKMoK-0004RS-Ue
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 14:07:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13098
	for <sipping@ietf.org>; Thu, 13 Nov 2003 14:07:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKMoI-00030i-00
	for sipping@ietf.org; Thu, 13 Nov 2003 14:07:18 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKMoI-00030F-00
	for sipping@ietf.org; Thu, 13 Nov 2003 14:07:18 -0500
Received: from cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 13 Nov 2003 11:09:14 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hADJ6lFx018275;
	Thu, 13 Nov 2003 11:06:47 -0800 (PST)
Received: from [130.129.129.178] (rtp-vpn1-41.cisco.com [10.82.224.41])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJX82172;
	Thu, 13 Nov 2003 11:06:45 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Wed, 12 Nov 2003 11:56:33 -0800
Subject: Re: [Sipping] draft-ietf-sipping-config-framework
From: Cullen Jennings <fluffy@cisco.com>
To: Dan Petrie <dpetrie@pingtel.com>
CC: sipping <sipping@ietf.org>
Message-ID: <BBD7D071.24706%fluffy@cisco.com>
In-Reply-To: <3FAFEB6D.BC65D99B@pingtel.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Yes, makes sense.

On 11/10/03 11:47 AM, "Daniel G. Petrie" <dpetrie@pingtel.com> wrote:

> Yes manual discovery probably makes sense at both
> the start and end.  The user may wish to override
> which profile delivery server is discovered, effectively
> making it the first discovery mechanizm.  It also makes
> sense to be the last mechanizm when all other discovery
> appoaches  fail.
> 
> Cullen Jennings wrote:
> 
>> Like it - one little NIT in discover stage...
>> 
>> The manual configuration needs to override the DHCP or well known DNS name
>> approach.
>> 
>> Cullen
>> 
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 15:24:09 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18426
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 15:24:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKO0M-0003M2-DF
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 15:23:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADKNom6012893
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 15:23:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKO0M-0003Ls-95
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 15:23:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18336
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 15:23:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKO0K-0004S3-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 15:23:48 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKO0J-0004RZ-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 15:23:48 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AKNwr-0002uj-9i
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 15:20:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNwg-0002oz-Rn; Thu, 13 Nov 2003 15:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKNwe-0002o7-An
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 15:20:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18137
	for <sipping@ietf.org>; Thu, 13 Nov 2003 15:19:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNwc-0004Nh-00
	for sipping@ietf.org; Thu, 13 Nov 2003 15:19:58 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKNwb-0004Ne-00
	for sipping@ietf.org; Thu, 13 Nov 2003 15:19:57 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hADKJ4Ss012651;
	Thu, 13 Nov 2003 21:19:04 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <WHXDYSL8>; Thu, 13 Nov 2003 21:19:39 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF05683C7B@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        Adam Roach
	 <adam@dynamicsoft.com>
Cc: "'David R. Oran'" <oran@cisco.com>,
        "Sipping (E-mail)"
	 <sipping@ietf.org>
Subject: RE: [Sipping] KPML Digit Maps
Date: Thu, 13 Nov 2003 21:17:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Hi,

I see no problem with different styles, if one is "mandotory" to support. There will always be a "style match".

Regards,

Christer Holmberg
Ericsson Finland


> -----Original Message-----
> From: sipping-admin@ietf.org 
> [mailto:sipping-admin@ietf.org]On Behalf Of
> Jonathan Rosenberg
> Sent: 13. marraskuuta 2003 9:21
> To: Adam Roach
> Cc: 'David R. Oran'; Sipping (E-mail)
> Subject: Re: [Sipping] KPML Digit Maps
> 
> 
> I feel strongly that we should pick one. Having multiple ways 
> of doing 
> something is a known bad thing, and here it just seems to bring no 
> real extra value.
> 
> I feel less strongly about what the thing is. But having to negotiate 
> this is just silly.
> 
> -Jonathan R.
> 
> Adam Roach wrote:
> 
> > Unless doing so will significantly impair progress, I'm
> > inclined to agree with Dave's recommendation: one digit
> > map format, and make it regexes.
> > 
> > /a
> > 
> > 
> >>-----Original Message-----
> >>From: David R. Oran [mailto:oran@cisco.com]
> >>Sent: Wednesday, November 12, 2003 13:59
> >>To: Sipping (E-mail)
> >>Subject: Re: [Sipping] KPML Digit Maps
> >>
> >>
> >>Before giving up and playing negotiation games, I'd like to 
> see if it 
> >>impossible politically to "just pick".
> >>
> >>So, I would like to formally propose:
> >>
> >>1a. We pick regular expressions as the only digit map style 
> >>supported by 
> >>KPML.
> >>
> >>I won't be terribly unhappy if this is shot down, but our 
> >>lives would sure 
> >>be better if we could KISS digit maps for KPML.
> >>
> >>Dave.
> >>
> >>--On Wednesday, November 12, 2003 11:04 AM -0500 Eric Burger 
> >><eburger@snowshore.com> wrote:
> >>
> >>
> >>>Right now, KPML specifies 3 mandatory digit map styles:
> >>> - Regular Expressions
> >>> - H.248.1 digitmap
> >>> - J.162   digitmap
> >>>
> >>>Choices are:
> >>> 1. We can pick one, and only one digit map style.
> >>> 2. We can negotiate the style, with a mandatory
> >>>    to implement for guaranteed baseline
> >>>    interoperability.
> >>>
> >>>There was a leaning in Minneapolis towards option #2.  The 
> mechanism
> >>>roughly would be to put a parameter on the event: kpml 
> header in the
> >>>SUBSCRIBE, with a suitable failure if the style is not 
> >>
> >>supported by the
> >>
> >>>KPML server.  Given that there are already three (or four, 
> >>
> >>see below)
> >>
> >>>different digit map styles, this probably would become an 
> >>
> >>IANA-registered
> >>
> >>>tag.
> >>>
> >>>For the people that think expression evaluation is computationally
> >>>complex, one of the styles can be a hardcode of "match 
> digit."  [Ed.
> >>>Note: this mode is not really useful for the reasons given, in that
> >>>expression evaluation is not computationally complex, 
> >>
> >>especially when
> >>
> >>>compared to the computational complexity of running a SIP 
> >>
> >>stack or (if on
> >>
> >>>a single processor) the complexity of detecting DTMF).]
> >>>
> >>>Comments?
> >>>
> >>>
> >>>_______________________________________________
> >>>Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> >>>This list is for NEW development of the application of SIP
> >>>Use sip-implementors@cs.columbia.edu for questions on current sip
> >>>Use sip@ietf.org for new developments of core SIP
> >>
> >>
> >>
> >>------------------------
> >>David R. Oran
> >>Cisco Systems
> >>7 Ladyslipper Lane
> >>Acton, MA 01720
> >>Office: +1 978 264 2048
> >>VoIP: +1 408 571 4576
> >>Email: oran@cisco.com
> >>
> >>_______________________________________________
> >>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >>This list is for NEW development of the application of SIP
> >>Use sip-implementors@cs.columbia.edu for questions on current sip
> >>Use sip@ietf.org for new developments of core SIP
> >>
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 18:28:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29073
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 18:28:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQsj-0000Vw-LK
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:28:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADNS9Q7001976
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:28:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQsj-0000Vn-Ey
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 18:28:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29021
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 18:27:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQsf-00001b-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:28:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQsf-00001Y-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:28:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQsb-0000Ui-Dr; Thu, 13 Nov 2003 18:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQrt-0000UE-LO
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 18:27:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29000
	for <sipping@ietf.org>; Thu, 13 Nov 2003 18:27:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQrq-000018-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:27:14 -0500
Received: from mtagate3.de.ibm.com ([195.212.29.152])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQrp-00000y-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:27:14 -0500
Received: from d12relay01.megacenter.de.ibm.com (d12relay01.megacenter.de.ibm.com [9.149.165.180] (may be forged))
	by mtagate3.de.ibm.com (8.12.10/8.12.10) with ESMTP id hADNOFCW082810
	for <sipping@ietf.org>; Thu, 13 Nov 2003 23:24:15 GMT
Received: from d10ml001.telaviv.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12relay01.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id hADNQgw2256058
	for <sipping@ietf.org>; Fri, 14 Nov 2003 00:26:43 +0100
In-Reply-To: <F8EFC4B4A8C016428BC1F589296D4FBF05683C7B@esealnt630.al.sw.ericsson.se>
To: sipping@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V65_07292003 July 29, 2003
Message-ID: <OF52FB1064.F0B2FDAF-ONC2256DDD.00805358-C2256DDD.0080C086@il.ibm.com>
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Date: Fri, 14 Nov 2003 01:26:17 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 6.0.2CF2|July 23, 2003) at
 14/11/2003 01:26:42,
	Serialize complete at 14/11/2003 01:26:42
Content-Type: multipart/alternative; boundary="=_alternative 0080C082C2256DDD_="
Subject: [Sipping] Throttling & Event filtering
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multipart message in MIME format.
--=_alternative 0080C082C2256DDD_=
Content-Type: text/plain; charset="US-ASCII"

Why we need a different throttling mechanism? Can it be added to the event 
filtering?
It means that there will be a filter that is dependent on the rate of the 
events and not on the content
of the events.

Avshalom

--=_alternative 0080C082C2256DDD_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Why we need a different throttling mechanism?
Can it be added to the event filtering?</font>
<br><font size=2 face="sans-serif">It means that there will be a filter
that is dependent on the rate of the events and not on the content</font>
<br><font size=2 face="sans-serif">of the events.</font>
<br>
<br><font size=2 face="sans-serif">Avshalom</font>
<br>
--=_alternative 0080C082C2256DDD_=--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 18:32:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29396
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 18:32:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQwU-0000sP-Dk
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:32:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADNW2dY003303
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQwU-0000qE-4Q
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 18:32:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29385
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 18:31:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQwQ-0000BU-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:31:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQwQ-0000BR-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:31:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQwS-0000p4-ED; Thu, 13 Nov 2003 18:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKQvW-0000ne-51
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 18:31:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29323
	for <sipping@ietf.org>; Thu, 13 Nov 2003 18:30:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQvS-0000AR-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:30:58 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKQvR-000081-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:30:57 -0500
Received: from dynamicsoft.com ([63.113.46.11])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hADNUSca016962
	for <sipping@ietf.org>; Thu, 13 Nov 2003 18:30:29 -0500 (EST)
Message-ID: <3FB41412.2010507@dynamicsoft.com>
Date: Thu, 13 Nov 2003 18:30:26 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] How to control drop algorithms for throttling
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This mail is a followup to some comments I made during sipping today 
on the event throttling work.

Once we add throttling capabilities to the SIP event framework, we end 
up with a lossy system. Some notifications will be dropped, and others 
will be transmitted. The problem is that all notifications are not 
created equally. If the notififer drops notifications at random, will 
the resulting stream of notifications meet the needs of the watcher? 
Can we do better than simply dropping notifications randomly?

Some possible things we might do:

1. instead of dropping notifications, the notifier buffers them. If it 
receives another notification within the next M seconds, it drops the 
older one, and sends the newer one. This would allow you to control 
the rate through delays. I suspect that many applications will have a 
better sense of the utility of the presence data as a function of age. 
Do we want the mechanism to support this?

2. the watcher could provide a filter type of document in the 
subscription. This filter could indicate that certain transitions are 
more important than others. For example, in the case of presence, it 
might say that transitions of the <basic> status are more important 
than transitions of the <placetype> from RPID. The notifier could use 
these to preferentially drop certain notifications over others. Do we 
want the mechanism to support this?

3. If we don't use the concepts of (1) and (2), is there any value in 
applying algorithms like RED to the systems (I dont think so, but its 
worth considering).

4. Do we want to specify that each package should have a 
considerations section about how to use throttling? In particular, 
what will be the typical impact on service for various loss rates? Or, 
  which components of a document should a client ask to have dropped 
(assuming the filtering of (2)).


Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 18:38:40 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29728
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 18:38:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKR2d-0001zY-8P
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:38:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADNcMeB007644
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 18:38:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKR2c-0001zB-OD
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 18:38:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29675
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 18:38:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKR2Z-0000I4-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:38:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKR2Z-0000I1-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 18:38:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKR2N-0001mO-ET; Thu, 13 Nov 2003 18:38:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKR23-0001hx-Cn
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 18:37:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29630
	for <sipping@ietf.org>; Thu, 13 Nov 2003 18:37:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKR20-0000HU-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:37:44 -0500
Received: from mail4.dynamicsoft.com ([63.110.3.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKR1z-0000Gq-00
	for sipping@ietf.org; Thu, 13 Nov 2003 18:37:43 -0500
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail4.dynamicsoft.com (8.12.8/8.12.8) with ESMTP id hADNbCGd027543;
	Thu, 13 Nov 2003 17:37:13 -0600 (CST)
Received: by dyn-tx-exch-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <W4467XCP>; Thu, 13 Nov 2003 17:37:13 -0600
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3E86612@dyn-tx-exch-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Avshalom Houri'" <AVSHALOM@il.ibm.com>, sipping@ietf.org
Subject: RE: [Sipping] Throttling & Event filtering
Date: Thu, 13 Nov 2003 17:37:03 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


The logic that has historically been offered for doing these as
two separate efforts is that the throttling work is expected to
be completed quickly, while the generic event filtering is
expected to take significantly more time.

A significant amount of time has passed since we made that decision,
but I think it is still arguably true that the throttling work
(which we just voted to pass to SIP) is significantly closer to
completion than generic event filters.

I'd be interesting to hear other opinions on the topic.

/a

-----Original Message-----
From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]
Sent: Thursday, November 13, 2003 17:26
To: sipping@ietf.org
Subject: [Sipping] Throttling & Event filtering



Why we need a different throttling mechanism? Can it be added to the event
filtering? 
It means that there will be a filter that is dependent on the rate of the
events and not on the content 
of the events. 

Avshalom 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 20:15:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02898
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 20:15:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKSYD-0007mt-FP
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 20:15:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE1F5o7029929
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 20:15:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKSYD-0007me-Ax
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 20:15:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02888
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 20:14:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKSYB-0001md-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 20:15:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKSYA-0001ma-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 20:15:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKSYB-0007lD-3j; Thu, 13 Nov 2003 20:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKSXk-0007k6-47
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 20:14:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02849
	for <sipping@ietf.org>; Thu, 13 Nov 2003 20:14:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKSXh-0001lo-00
	for sipping@ietf.org; Thu, 13 Nov 2003 20:14:34 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKSXh-0001lA-00
	for sipping@ietf.org; Thu, 13 Nov 2003 20:14:33 -0500
Received: from cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 13 Nov 2003 17:21:10 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAE1E1w5026042;
	Thu, 13 Nov 2003 17:14:01 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-2-116.cisco.com [10.86.242.116])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ADZ16123;
	Thu, 13 Nov 2003 20:13:59 -0500 (EST)
Message-ID: <3FB42C57.3080306@cisco.com>
Date: Thu, 13 Nov 2003 20:13:59 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] How to control drop algorithms for throttling
References: <3FB41412.2010507@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jonathan,

I pretty much agree with you - especially on the need for a throttling 
considerations section. Ultimately, I think this means that the notifier 
application must participate in the throttling in order to ensure that 
the right thing is done.

In some cases it might make the most sense to simply terminate the 
subscription rather than provide a deceptive view. (So that when an 
event was discarded, at the next permissible time the server would 
simply send a notification terminating the subscription.)

	Paul

Jonathan Rosenberg wrote:
> This mail is a followup to some comments I made during sipping today on 
> the event throttling work.
> 
> Once we add throttling capabilities to the SIP event framework, we end 
> up with a lossy system. Some notifications will be dropped, and others 
> will be transmitted. The problem is that all notifications are not 
> created equally. If the notififer drops notifications at random, will 
> the resulting stream of notifications meet the needs of the watcher? Can 
> we do better than simply dropping notifications randomly?
> 
> Some possible things we might do:
> 
> 1. instead of dropping notifications, the notifier buffers them. If it 
> receives another notification within the next M seconds, it drops the 
> older one, and sends the newer one. This would allow you to control the 
> rate through delays. I suspect that many applications will have a better 
> sense of the utility of the presence data as a function of age. Do we 
> want the mechanism to support this?
> 
> 2. the watcher could provide a filter type of document in the 
> subscription. This filter could indicate that certain transitions are 
> more important than others. For example, in the case of presence, it 
> might say that transitions of the <basic> status are more important than 
> transitions of the <placetype> from RPID. The notifier could use these 
> to preferentially drop certain notifications over others. Do we want the 
> mechanism to support this?
> 
> 3. If we don't use the concepts of (1) and (2), is there any value in 
> applying algorithms like RED to the systems (I dont think so, but its 
> worth considering).
> 
> 4. Do we want to specify that each package should have a considerations 
> section about how to use throttling? In particular, what will be the 
> typical impact on service for various loss rates? Or,  which components 
> of a document should a client ask to have dropped (assuming the 
> filtering of (2)).
> 
> 
> Thanks,
> Jonathan R.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 22:51:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09951
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 22:51:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKUzI-0003Jc-PM
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 22:51:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE3pCET012735
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 22:51:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKUzI-0003JA-IV
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 22:51:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09933
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 22:50:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKUzE-0004iH-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 22:51:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKUzE-0004iE-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 22:51:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKUzB-0003GB-74; Thu, 13 Nov 2003 22:51:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKUyQ-0003Ce-ND
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 22:50:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09899
	for <sipping@ietf.org>; Thu, 13 Nov 2003 22:50:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKUyN-0004hJ-00
	for sipping@ietf.org; Thu, 13 Nov 2003 22:50:15 -0500
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKUyM-0004gu-00
	for sipping@ietf.org; Thu, 13 Nov 2003 22:50:14 -0500
Received: from razor.cs.columbia.edu (IDENT:root@razor.cs.columbia.edu [128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hAE3nk9D015573;
	Thu, 13 Nov 2003 22:49:46 -0500 (EST)
Received: from cs.columbia.edu (IDENT:root@localhost [127.0.0.1])
	by razor.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id hAE3nif18914;
	Thu, 13 Nov 2003 22:49:44 -0500
Message-ID: <3FB450D8.5090504@cs.columbia.edu>
Date: Thu, 13 Nov 2003 22:49:44 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, sipping <sipping@ietf.org>
Subject: Re: [Sipping] How to control drop algorithms for throttling
References: <3FB41412.2010507@dynamicsoft.com> <3FB42C57.3080306@cisco.com>
In-Reply-To: <3FB42C57.3080306@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There are different types of notifications, at least two:

(C) systems where changes are naturally bounded (continuous)

(D) changes where they are not (discrete)

Geo information is an example of the first one. In that case, it makes 
sense to simply restrict updates to some time period or some significant 
change. After all, I can be pretty sure that the offset from the last 
update is less than the speed of sound times the distance, now that the 
Concorde is no longer in service. (Use on Startrek may differ.)

In some cases, I suspect that people will have low-frequency background 
status updates and not care about brief 'transients' (leave office to 
visit cafeteria for coffee), but rather ask for an explicit status 
update if they want to ask somebody something, for example. After all, 
unless the watcher is a busybody with nothing else to do, he won't watch 
every move of every presentity in detail.

Indeed, I wonder if users will really want to get continuous updates on 
their buddy list members. I may want some general sense of how many of 
my colleagues are around and I may want to quickly determine whether a 
particular colleague is around right now, but clicking on the name seems 
perfectly fine for that, without getting the detailed updates on the 
person's cell phone idle time every five minutes.

Paul Kyzivat wrote:

> Jonathan,
> 
> I pretty much agree with you - especially on the need for a throttling 
> considerations section. Ultimately, I think this means that the notifier 
> application must participate in the throttling in order to ensure that 
> the right thing is done.
> 
> In some cases it might make the most sense to simply terminate the 
> subscription rather than provide a deceptive view. (So that when an 
> event was discarded, at the next permissible time the server would 
> simply send a notification terminating the subscription.)
> 
>     Paul
> 
> Jonathan Rosenberg wrote:
> 
>> This mail is a followup to some comments I made during sipping today 
>> on the event throttling work.
>>
>> Once we add throttling capabilities to the SIP event framework, we end 
>> up with a lossy system. Some notifications will be dropped, and others 
>> will be transmitted. The problem is that all notifications are not 
>> created equally. If the notififer drops notifications at random, will 
>> the resulting stream of notifications meet the needs of the watcher? 
>> Can we do better than simply dropping notifications randomly?
>>
>> Some possible things we might do:
>>
>> 1. instead of dropping notifications, the notifier buffers them. If it 
>> receives another notification within the next M seconds, it drops the 
>> older one, and sends the newer one. This would allow you to control 
>> the rate through delays. I suspect that many applications will have a 
>> better sense of the utility of the presence data as a function of age. 
>> Do we want the mechanism to support this?
>>
>> 2. the watcher could provide a filter type of document in the 
>> subscription. This filter could indicate that certain transitions are 
>> more important than others. For example, in the case of presence, it 
>> might say that transitions of the <basic> status are more important 
>> than transitions of the <placetype> from RPID. The notifier could use 
>> these to preferentially drop certain notifications over others. Do we 
>> want the mechanism to support this?
>>
>> 3. If we don't use the concepts of (1) and (2), is there any value in 
>> applying algorithms like RED to the systems (I dont think so, but its 
>> worth considering).
>>
>> 4. Do we want to specify that each package should have a 
>> considerations section about how to use throttling? In particular, 
>> what will be the typical impact on service for various loss rates? 
>> Or,  which components of a document should a client ask to have 
>> dropped (assuming the filtering of (2)).
>>
>>
>> Thanks,
>> Jonathan R.
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 13 23:45:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11749
	for <sipping-archive@odin.ietf.org>; Thu, 13 Nov 2003 23:45:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVpV-0007FG-KD
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 23:45:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAE4j9qg027844
	for sipping-archive@odin.ietf.org; Thu, 13 Nov 2003 23:45:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVpV-0007Ev-8j
	for sipping-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 23:45:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11680
	for <sipping-web-archive@ietf.org>; Thu, 13 Nov 2003 23:44:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVpS-0005WY-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 23:45:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVpR-0005WU-00
	for sipping-web-archive@ietf.org; Thu, 13 Nov 2003 23:45:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVpN-0007Di-H5; Thu, 13 Nov 2003 23:45:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKVpE-0007DN-VX
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 23:44:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11676
	for <sipping@ietf.org>; Thu, 13 Nov 2003 23:44:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVpC-0005WL-00
	for sipping@ietf.org; Thu, 13 Nov 2003 23:44:50 -0500
Received: from mtagate7.de.ibm.com ([195.212.29.156])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKVpB-0005WA-00
	for sipping@ietf.org; Thu, 13 Nov 2003 23:44:50 -0500
Received: from d12relay02.megacenter.de.ibm.com (d12relay02.megacenter.de.ibm.com [9.149.165.196] (may be forged))
	by mtagate7.de.ibm.com (8.12.10/8.12.10) with ESMTP id hAE4iCqg049438;
	Fri, 14 Nov 2003 04:44:12 GMT
Received: from d10ml001.telaviv.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12relay02.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id hAE4iBBE235538;
	Fri, 14 Nov 2003 05:44:11 +0100
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86612@dyn-tx-exch-001.dynamicsoft.com>
To: Adam Roach <adam@dynamicsoft.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] Throttling & Event filtering
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V65_07292003 July 29, 2003
Message-ID: <OF9E61C220.89AE2C17-ONC2256DDE.0019B862-C2256DDE.001A0564@il.ibm.com>
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Date: Fri, 14 Nov 2003 06:44:11 +0200
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 6.0.2CF2|July 23, 2003) at
 14/11/2003 06:44:11,
	Serialize complete at 14/11/2003 06:44:11
Content-Type: multipart/alternative; boundary="=_alternative 001A055BC2256DDE_="
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multipart message in MIME format.
--=_alternative 001A055BC2256DDE_=
Content-Type: text/plain; charset="US-ASCII"

Given that:

a) A significant amount of time has passed
b) Work on event filtering have progressed meanwhile
c) As far as I know no one has urgent need for event throttling right now

We may want to revise the decision in order to reduce the amount of work 
items.

Avshalom




Adam Roach <adam@dynamicsoft.com> 
Sent by: sipping-admin@ietf.org
14/11/2003 01:37 AM

To
Avshalom Houri/Haifa/IBM@IBMIL, sipping@ietf.org
cc

Subject
RE: [Sipping] Throttling & Event filtering







The logic that has historically been offered for doing these as
two separate efforts is that the throttling work is expected to
be completed quickly, while the generic event filtering is
expected to take significantly more time.

A significant amount of time has passed since we made that decision,
but I think it is still arguably true that the throttling work
(which we just voted to pass to SIP) is significantly closer to
completion than generic event filters.

I'd be interesting to hear other opinions on the topic.

/a

-----Original Message-----
From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]
Sent: Thursday, November 13, 2003 17:26
To: sipping@ietf.org
Subject: [Sipping] Throttling & Event filtering



Why we need a different throttling mechanism? Can it be added to the event
filtering? 
It means that there will be a filter that is dependent on the rate of the
events and not on the content 
of the events. 

Avshalom 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



--=_alternative 001A055BC2256DDE_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Given that:</font>
<br>
<br><font size=2 face="sans-serif">a) A significant amount of time has
passed</font>
<br><font size=2 face="sans-serif">b) Work on event filtering have progressed
meanwhile</font>
<br><font size=2 face="sans-serif">c) As far as I know no one has urgent
need for event throttling right now</font>
<br>
<br><font size=2 face="sans-serif">We may want to revise the decision in
order to reduce the amount of work items.</font>
<br>
<br><font size=2 face="sans-serif">Avshalom</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Adam Roach &lt;adam@dynamicsoft.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: sipping-admin@ietf.org</font>
<p><font size=1 face="sans-serif">14/11/2003 01:37 AM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Avshalom Houri/Haifa/IBM@IBMIL,
sipping@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: [Sipping] Throttling
&amp; Event filtering</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
The logic that has historically been offered for doing these as<br>
two separate efforts is that the throttling work is expected to<br>
be completed quickly, while the generic event filtering is<br>
expected to take significantly more time.<br>
<br>
A significant amount of time has passed since we made that decision,<br>
but I think it is still arguably true that the throttling work<br>
(which we just voted to pass to SIP) is significantly closer to<br>
completion than generic event filters.<br>
<br>
I'd be interesting to hear other opinions on the topic.<br>
<br>
/a<br>
<br>
-----Original Message-----<br>
From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]<br>
Sent: Thursday, November 13, 2003 17:26<br>
To: sipping@ietf.org<br>
Subject: [Sipping] Throttling &amp; Event filtering<br>
<br>
<br>
<br>
Why we need a different throttling mechanism? Can it be added to the event<br>
filtering? <br>
It means that there will be a filter that is dependent on the rate of the<br>
events and not on the content <br>
of the events. <br>
<br>
Avshalom <br>
<br>
_______________________________________________<br>
Sipping mailing list &nbsp;https://www1.ietf.org/mailman/listinfo/sipping<br>
This list is for NEW development of the application of SIP<br>
Use sip-implementors@cs.columbia.edu for questions on current sip<br>
Use sip@ietf.org for new developments of core SIP<br>
<br>
</tt></font>
<br>
--=_alternative 001A055BC2256DDE_=--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 14 10:03:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12622
	for <sipping-archive@odin.ietf.org>; Fri, 14 Nov 2003 10:03:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKfTb-0003yC-Dh
	for sipping-archive@odin.ietf.org; Fri, 14 Nov 2003 10:03:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEF3BUq015254
	for sipping-archive@odin.ietf.org; Fri, 14 Nov 2003 10:03:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKfTb-0003xx-9z
	for sipping-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 10:03:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12582
	for <sipping-web-archive@ietf.org>; Fri, 14 Nov 2003 10:02:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKfTY-0006M0-00
	for sipping-web-archive@ietf.org; Fri, 14 Nov 2003 10:03:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKfTY-0006Lv-00
	for sipping-web-archive@ietf.org; Fri, 14 Nov 2003 10:03:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKfTQ-0003vz-Tr; Fri, 14 Nov 2003 10:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKfT1-0003u6-F9
	for sipping@optimus.ietf.org; Fri, 14 Nov 2003 10:02:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12487
	for <sipping@ietf.org>; Fri, 14 Nov 2003 10:02:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKfSz-0006Jp-00
	for sipping@ietf.org; Fri, 14 Nov 2003 10:02:33 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKfSy-0006If-00
	for sipping@ietf.org; Fri, 14 Nov 2003 10:02:33 -0500
Received: from cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 14 Nov 2003 07:04:41 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAEF1xw5007626;
	Fri, 14 Nov 2003 07:02:00 -0800 (PST)
Received: from [130.129.129.178] (sjc-vpn1-405.cisco.com [10.21.97.149])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AJY57840;
	Fri, 14 Nov 2003 07:01:58 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Thu, 13 Nov 2003 20:24:21 -0800
Subject: Re: [Sipping] KPML Digit Maps
From: Cullen Jennings <fluffy@cisco.com>
To: Eric Burger <eburger@snowshore.com>, "Sipping (E-mail)" <sipping@ietf.org>
Message-ID: <BBD998F5.24A30%fluffy@cisco.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F69C5@zoe.office.snowshore.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Choices are:
> 1. We can pick one, and only one digit map style.
> 2. We can negotiate the style, with a mandatory
>   to implement for guaranteed baseline
>   interoperability.

Please just one - and a very simple one.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 14 13:25:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23501
	for <sipping-archive@odin.ietf.org>; Fri, 14 Nov 2003 13:25:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKid4-0005We-AA
	for sipping-archive@odin.ietf.org; Fri, 14 Nov 2003 13:25:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAEIPAxE021234
	for sipping-archive@odin.ietf.org; Fri, 14 Nov 2003 13:25:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKid4-0005WP-5r
	for sipping-web-archive@optimus.ietf.org; Fri, 14 Nov 2003 13:25:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23485
	for <sipping-web-archive@ietf.org>; Fri, 14 Nov 2003 13:24:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKid2-0002Jj-00
	for sipping-web-archive@ietf.org; Fri, 14 Nov 2003 13:25:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKid1-0002Jg-00
	for sipping-web-archive@ietf.org; Fri, 14 Nov 2003 13:25:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKicw-0005PS-To; Fri, 14 Nov 2003 13:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKicc-0005Ii-L5
	for sipping@optimus.ietf.org; Fri, 14 Nov 2003 13:24:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23472;
	Fri, 14 Nov 2003 13:24:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKica-0002JC-00; Fri, 14 Nov 2003 13:24:40 -0500
Received: from mail3.pi.se ([195.7.64.137])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKicZ-0002Iz-00; Fri, 14 Nov 2003 13:24:39 -0500
Received: from vit (dyn128-155.ietf58.ietf.org [130.129.128.155])
	(authenticated)
	by mail3.pi.se (8.11.2/8.11.2) with ESMTP id hAEIOAZ19779;
	Fri, 14 Nov 2003 19:24:10 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "'Sipping@Ietf. Org'" <sipping@ietf.org>, <mmusic@ietf.org>
Cc: "Toip list" <toip@snowshore.com>
Date: Fri, 14 Nov 2003 12:24:12 -0600
Message-ID: <BHEHLFPKIPMLPFNFAHJKEEMFDBAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mail3.pi.se id hAEIOAZ19779
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] [mmusic] Inclusion of media type = "text" in SDP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

This is a request for a minor addition to draft-ietf-mmusic-sdp-new-15.tx=
t
to acknowledge use of the media type "text" in sessions.

An RTP transport for real time character by character transmission of tex=
t
was defined a couple of years ago in RFC2793.
It is now successfully used in conversational applications, usually combi=
ned
with voice and/or video to enable the participants in the session to
communicate in any preferred medium. One important user group is deaf and
hard-of-hearing people, but the feature is of course of value for all.

In the past, most multimedia implementors have been eager to create
interoperability in video and audio, while the text part has been left
behind and iimplemented as manufacturer specific message-oriented
"chat"-additions. It is time for a change, to raise all the three media o=
f
video, text and audio to the same status of interoperability and deployme=
nt.
That will give SIP based conversational services a real benefit.

This is also needed for the transcoding work.

By mistake no registration of "text" as an allowed media in the m=3D
descriptor of SDP has yet taken place. This was discussed in the mmusic
meeting today, and the conclusion was that since it is already a MIME top
level medium, it is just a matter of including it in the sdp document to
make it allowed.

Therefore I suggest the addition of the word "text" in the following thre=
e
places in draft-ietf-mmusic-sdp-new-15.txt .
In discussion with Colin, we came to the conclusion that this action woul=
d
be sufficient for acknowledging the text medium.


--------in section 5.14 ----------------------------------------------
5.14 Media Announcements ("m=3D")

      m=3D<media> <port> <transport> <fmt list>

   A session description may contain a number of media descriptions.
   Each media description starts with an "m=3D" field, and is terminated
   by either the next "m=3D" field or by the end of the session
   description. A media field has several sub-fields.

   The first sub-field is the media type.  Currently defined media are
   "audio", "video", "text", "application", "data" and "control", though
this
   list may be extended in future.

-----further down, same section -----------

   The fourth and subsequent sub-fields are media formats.  For audio
   text and video, these SHOULD reference a MIME sub-type describing the
   format under the "audio", "text" and "video" top-level MIME types.

------In Appendix A------------------------------

; sub-rules of 'm=3D'
      media =3D               token
                            ;typically "audio", "video", "text",
"application"
                            ;or "data"
------End of
proposal-----------------------------------------------------------------=
---
--------

Regards

Gunnar
-------------------------------------------
Gunnar Hellstr=F6m
Omnitor AB
Renathv=E4gen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 17 00:16:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18847
	for <sipping-archive@odin.ietf.org>; Mon, 17 Nov 2003 00:16:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbkA-0005Oz-QW
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 00:16:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAH5GACX020761
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 00:16:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbkA-0005Om-NN
	for sipping-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 00:16:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18840
	for <sipping-web-archive@ietf.org>; Mon, 17 Nov 2003 00:15:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALbk7-00011H-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 00:16:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALbk6-000119-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 00:16:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbk3-0005Mc-CW; Mon, 17 Nov 2003 00:16:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALTZn-0004TW-QH
	for sipping@optimus.ietf.org; Sun, 16 Nov 2003 15:32:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07055;
	Sun, 16 Nov 2003 15:32:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALTZl-0002fB-00; Sun, 16 Nov 2003 15:32:53 -0500
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALTZl-0002eZ-00; Sun, 16 Nov 2003 15:32:53 -0500
Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225])
	by mail-out4.apple.com (8.12.10/8.12.9) with ESMTP id hAGKWNnc015101;
	Sun, 16 Nov 2003 12:32:23 -0800 (PST)
Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T65f0ef2781118064e15e4@mailgate1.apple.com>;
 Sun, 16 Nov 2003 12:31:41 -0800
Received: from [17.202.35.52] (singeridsl2.apple.com [17.219.157.83])
	by scv2.apple.com (8.12.9/8.12.9) with ESMTP id hAGKVrEY006415;
	Sun, 16 Nov 2003 12:31:56 -0800 (PST)
Mime-Version: 1.0
X-Sender: singer@mail.apple.com (Unverified)
Message-Id: <p0600200bbbdd8f26bba2@[17.202.35.52]>
In-Reply-To: <BHEHLFPKIPMLPFNFAHJKEEMFDBAA.gunnar.hellstrom@omnitor.se>
References: <BHEHLFPKIPMLPFNFAHJKEEMFDBAA.gunnar.hellstrom@omnitor.se>
Date: Sun, 16 Nov 2003 12:32:04 -0800
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>,
        "'Sipping@Ietf. Org'" <sipping@ietf.org>, mmusic@ietf.org
From: Dave Singer <singer@apple.com>
Cc: Toip list <toip@snowshore.com>
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Re: [mmusic] Inclusion of media type = "text" in SDP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

There is also the 3G timed text draft, of course,=20
and the upcoming MPEG and W3C work in timed text.


At 12:24 PM -0600 11/14/03, Gunnar Hellstrom wrote:
>This is a request for a minor addition to draft-ietf-mmusic-sdp-new-15.txt
>to acknowledge use of the media type "text" in sessions.
>
>An RTP transport for real time character by character transmission of text
>was defined a couple of years ago in RFC2793.
>It is now successfully used in conversational applications, usually combine=
d
>with voice and/or video to enable the participants in the session to
>communicate in any preferred medium. One important user group is deaf and
>hard-of-hearing people, but the feature is of course of value for all.
>
>In the past, most multimedia implementors have been eager to create
>interoperability in video and audio, while the text part has been left
>behind and iimplemented as manufacturer specific message-oriented
>"chat"-additions. It is time for a change, to raise all the three media of
>video, text and audio to the same status of interoperability and deployment=
=2E
>That will give SIP based conversational services a real benefit.
>
>This is also needed for the transcoding work.
>
>By mistake no registration of "text" as an allowed media in the m=3D
>descriptor of SDP has yet taken place. This was discussed in the mmusic
>meeting today, and the conclusion was that since it is already a MIME top
>level medium, it is just a matter of including it in the sdp document to
>make it allowed.
>
>Therefore I suggest the addition of the word "text" in the following three
>places in draft-ietf-mmusic-sdp-new-15.txt .
>In discussion with Colin, we came to the conclusion that this action would
>be sufficient for acknowledging the text medium.
>
>
>--------in section 5.14 ----------------------------------------------
>5.14 Media Announcements ("m=3D")
>
>       m=3D<media> <port> <transport> <fmt list>
>
>    A session description may contain a number of media descriptions.
>    Each media description starts with an "m=3D" field, and is terminated
>    by either the next "m=3D" field or by the end of the session
>    description. A media field has several sub-fields.
>
>    The first sub-field is the media type.  Currently defined media are
>    "audio", "video", "text", "application", "data" and "control", though
>this
>    list may be extended in future.
>
>-----further down, same section -----------
>
>    The fourth and subsequent sub-fields are media formats.  For audio
>    text and video, these SHOULD reference a MIME sub-type describing the
>    format under the "audio", "text" and "video" top-level MIME types.
>
>------In Appendix A------------------------------
>
>; sub-rules of 'm=3D'
>       media =3D               token
>                             ;typically "audio", "video", "text",
>"application"
>                             ;or "data"
>------End of
>proposal-------------------------------------------------------------------=
-
>--------
>
>Regards
>
>Gunnar
>-------------------------------------------
>Gunnar Hellstr=F6m
>Omnitor AB
>Renathv=E4gen 2
>SE 121 37 Johanneshov
>SWEDEN
>+46 8 556 002 03
>Mob: +46 708 204 288
>www.omnitor.se
>Gunnar.Hellstrom@Omnitor.se
>--------------------------------------------
>
>
>
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic


-- 
David Singer
Apple Computer/QuickTime

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 17 00:16:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18865
	for <sipping-archive@odin.ietf.org>; Mon, 17 Nov 2003 00:16:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbkC-0005PJ-4N
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 00:16:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAH5GCHj020779
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 00:16:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbkC-0005P4-0Z
	for sipping-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 00:16:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18838
	for <sipping-web-archive@ietf.org>; Mon, 17 Nov 2003 00:15:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALbk7-00011E-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 00:16:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALbk6-000118-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 00:16:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALbk2-0005MP-Fl; Mon, 17 Nov 2003 00:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKM5y-0001eV-Io
	for sipping@optimus.ietf.org; Thu, 13 Nov 2003 13:21:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11447
	for <sipping@ietf.org>; Thu, 13 Nov 2003 13:21:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKM5k-0002G7-00
	for sipping@ietf.org; Thu, 13 Nov 2003 13:21:16 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKM5j-0002G3-00
	for sipping@ietf.org; Thu, 13 Nov 2003 13:21:15 -0500
Received: from parmhs2.rd.francetelecom.fr ([10.193.117.61]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 13 Nov 2003 19:19:30 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE : [Sipping] about SIP-I
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Thu, 13 Nov 2003 19:19:29 +0100
Message-ID: <448914041F29D7499FA5F0B8ED1C708701A6030D@parmhs2.rd.francetelecom.fr>
Thread-Topic: [Sipping] about SIP-I
Thread-Index: AcOp/A4WGy4BF808QxS4LG3qpevsagAFW/Rg
From: =?iso-8859-1?Q?GARCIN_S=E9bastien_FTRD/DAC/ISS?= <sebastien.garcin@francetelecom.com>
To: "Jesske, R" <R.Jesske@t-com.net>, <jwalia9@hotmail.com>,
        <taylor@nortelnetworks.com>, <christer.holmberg@ericsson.com>,
        <sipping@ietf.org>, <mhammer@cisco.com>, <adam@dynamicsoft.com>
Cc: <zhaozf@eastcom.com>, <aroychow@hns.com>
X-OriginalArrivalTime: 13 Nov 2003 18:19:30.0326 (UTC) FILETIME=[AE152360:01C3AA12]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

SIP-T stands a general framework for interworking with ISUP, this =
framework considering the use of SIP to carry ISUP as a MIME body. As =
tom mentionned, SIP-T also provides some advice on how mapping and =
encapsulation should be performed in this case.

SIP-I provides in greeter details how encapsulation and mapping should =
be performed at an NNI interface. I actually does deviate to some extent =
with the advice provided in RFC 3372.=20

For example a key difference between SIP-T and SIP-I is that when =
de-encapsulating an ISUP message :
SIP-T sees the encapsulated ISUP as a template that is overridden by SIP =
headers=20
Q.1912.5 specifies what information should be taken from ISUP body (TMR =
is an example), and what information taken from the result of =
interworking from SIP headers to ISUP parameters.=20

Regards

s=E9bastien



-----Message d'origine-----
De : Jesske, R [mailto:R.Jesske@t-com.net]=20
Envoy=E9 : jeudi 13 novembre 2003 16:36
=C0 : jwalia9@hotmail.com; taylor@nortelnetworks.com; =
christer.holmberg@ericsson.com; sipping@ietf.org; mhammer@cisco.com; =
adam@dynamicsoft.com
Cc : zhaozf@eastcom.com; aroychow@hns.com
Objet : AW: [Sipping] about SIP-I


Hi,
From a telecom operator point of view SIP-I is the solution that =
guarantees a carrier grade and trusted connection for the trunking case. =
A operator using SIP-I between public PSTN/ISDN networks will ever stick =
to the Q.1912.5 solution, because it is describing the procedures and =
demands regarding the Interworking Unit at the network boundary. The =
philosophy behind Q.1912.5 is that the SIP interface is seen as an NNI =
and not as defined within IETF as an UNI.

Best Regards

Roland

> -----Ursprungliche Nachricht-----
> Von: J Walia [mailto:jwalia9@hotmail.com]
> Gesendet: Donnerstag, 13. November 2003 08:39
> An: taylor@nortelnetworks.com; christer.holmberg@ericsson.com;=20
> sipping@ietf.org; mhammer@cisco.com; adam@dynamicsoft.com
> Cc: zhaozf@eastcom.com; aroychow@hns.com
> Betreff: [Sipping] about SIP-I
>=20
>=20
> Well i had been reading the thread on SIP-I . It was a bit
> confusing since=20
> SIP-T and SIP-I seem to do the same thing. From a carrier=20
> prospective what=20
> is a better bet when interworking PSTN with Packet based=20
> network. From Tom's=20
> reply it seems it seems SIP-T is better but as expalined by=20
> Christian SIP-I=20
> seems to take care of what SIP-T RFC do not talk about. Does=20
> that mean SIP-I=20
> is more complete and a standardised implemetation comparing to SIP-T.
>=20
> Look forward to your comments
>=20
> Regard
>=20
> jw
>=20
> _________________________________________________________________
> BharatMatrimony.com.
> http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74=20
> India's premium matrimonial website.
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use=20
> sip-implementors@cs.columbia.edu for questions on current sip Use=20
> sip@ietf.org for new developments of core SIP
>=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip Use =
sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 17 07:00:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09078
	for <sipping-archive@odin.ietf.org>; Mon, 17 Nov 2003 07:00:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALi3B-0003LC-7v
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 07:00:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHC0D2Q012841
	for sipping-archive@odin.ietf.org; Mon, 17 Nov 2003 07:00:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALi3B-0003L2-2O
	for sipping-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 07:00:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09056
	for <sipping-web-archive@ietf.org>; Mon, 17 Nov 2003 06:59:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALi36-0005I7-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 07:00:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALi36-0005I4-00
	for sipping-web-archive@ietf.org; Mon, 17 Nov 2003 07:00:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALi2z-0003Jb-D3; Mon, 17 Nov 2003 07:00:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALi2q-0003HQ-JH
	for sipping@optimus.ietf.org; Mon, 17 Nov 2003 06:59:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09042
	for <sipping@ietf.org>; Mon, 17 Nov 2003 06:59:37 -0500 (EST)
From: aki.niemi@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALi2m-0005Hf-00
	for sipping@ietf.org; Mon, 17 Nov 2003 06:59:48 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALi2k-0005Hb-00
	for sipping@ietf.org; Mon, 17 Nov 2003 06:59:47 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAHBxlA05498
	for <sipping@ietf.org>; Mon, 17 Nov 2003 13:59:47 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65f66627f9ac158f25129@esvir05nok.ntc.nokia.com>;
 Mon, 17 Nov 2003 13:59:46 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 17 Nov 2003 13:59:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Throttling & Event filtering
Date: Mon, 17 Nov 2003 13:59:46 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592B8@esebe013.ntc.nokia.com>
Thread-Topic: [Sipping] Throttling & Event filtering
Thread-Index: AcOqaivKJ9QBt8STQESGj8hdAEteDACl0YSg
To: <AVSHALOM@il.ibm.com>, <adam@dynamicsoft.com>
Cc: <sipping@ietf.org>
X-OriginalArrivalTime: 17 Nov 2003 11:59:47.0022 (UTC) FILETIME=[4BD3D6E0:01C3AD02]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Avshalom,

I don't understand quite what you're suggesting here? Both filtering and =
throttling have committed resources working on them, so that clearly =
isn't the problem. As I am the resource working on throttling, are you =
telling me to find other work?

Technically, there is no change in direction. Filtering and throttling =
are still completely orthogonal, and even their scope is different. So I =
don't see why we should put them into a single draft. What would that =
buy us?

Cheers,
Aki


-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of =
ext Avshalom Houri
Sent: 14 November, 2003 06:44
To: Adam Roach
Cc: sipping@ietf.org
Subject: RE: [Sipping] Throttling & Event filtering



Given that:=20

a) A significant amount of time has passed=20
b) Work on event filtering have progressed meanwhile=20
c) As far as I know no one has urgent need for event throttling right =
now=20

We may want to revise the decision in order to reduce the amount of work =
items.=20

Avshalom=20



Adam Roach <adam@dynamicsoft.com>=20
Sent by: sipping-admin@ietf.org=20
14/11/2003 01:37 AM ToAvshalom Houri/Haifa/IBM@IBMIL, sipping@ietf.org=20
cc
SubjectRE: [Sipping] Throttling & Event filtering








The logic that has historically been offered for doing these as
two separate efforts is that the throttling work is expected to
be completed quickly, while the generic event filtering is
expected to take significantly more time.

A significant amount of time has passed since we made that decision,
but I think it is still arguably true that the throttling work
(which we just voted to pass to SIP) is significantly closer to
completion than generic event filters.

I'd be interesting to hear other opinions on the topic.

/a

-----Original Message-----
From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]
Sent: Thursday, November 13, 2003 17:26
To: sipping@ietf.org
Subject: [Sipping] Throttling & Event filtering



Why we need a different throttling mechanism? Can it be added to the =
event
filtering?=20
It means that there will be a filter that is dependent on the rate of =
the
events and not on the content=20
of the events.=20

Avshalom=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 15:09:09 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11345
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 15:09:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMC9c-0004F0-GT
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:08:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIK8qYK016298
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:08:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMC9c-0004En-C9
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 15:08:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11221
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 15:08:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMC9Z-0004aD-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:08:49 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMC9Y-0004a9-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:08:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMC8q-0003tr-Ph; Tue, 18 Nov 2003 15:08:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMC8W-0003pJ-7c
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 15:07:44 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10989;
	Tue, 18 Nov 2003 15:07:30 -0500 (EST)
Message-Id: <200311182007.PAA10989@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
From: Internet-Drafts@ietf.org
Cc: sipping@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 18 Nov 2003 15:07:30 -0500
Subject: [Sipping] I-D ACTION:draft-jain-sipping-persistent-conn-reqs-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Requirements for Persistent Connection Management 
			  in the Session Initiation Protocol (SIP)
	Author(s)	: R. Jain, V. Gurbani
	Filename	: draft-jain-sipping-persistent-conn-reqs-01.txt
	Pages		: 15
	Date		: 2003-11-18
	
SIP over connection-oriented transport protocol based systems are 
likely to face certain distinct performance and behavioral issues 
that are not manifest when SIP is transported over connectionless 
protocols. Allowing SIP entities to mutually conserve connections 
over a predictable, extended period of time is one of the leading 
requirements to help SIP entities deliver their optimal 
performance in the network. Overall, this document contemplates 
transport layer connection management issues relating to SIP. 
Requirements and potential solutions for introducing a backward 
compatible notion of persistent connections in SIP are presented.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-jain-sipping-persistent-conn-reqs-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-18124056.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-jain-sipping-persistent-conn-reqs-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-jain-sipping-persistent-conn-reqs-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-18124056.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 15:16:06 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12319
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 15:16:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCGG-0005DA-AM
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:15:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIKFihN020032
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:15:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCGG-0005Cy-4O
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 15:15:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12252
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 15:15:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCGE-0004gR-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:15:42 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCGD-0004gO-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:15:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCFb-0004wm-Fn; Tue, 18 Nov 2003 15:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCFQ-0004vn-7Y
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 15:14:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12151
	for <sipping@ietf.org>; Tue, 18 Nov 2003 15:14:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCFO-0004fZ-00
	for sipping@ietf.org; Tue, 18 Nov 2003 15:14:50 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCFO-0004f7-00
	for sipping@ietf.org; Tue, 18 Nov 2003 15:14:50 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hAIKEKb9015407;
	Tue, 18 Nov 2003 20:14:20 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHLDBD>; Tue, 18 Nov 2003 14:14:20 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56462@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Frank W. Miller'" <fmiller@sentito.com>,
        "'Chong, Koan S, ALABS'"
	 <kschong@att.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'McCandless, Kevin'"
	 <KMcCandless@verisign.com>
Date: Tue, 18 Nov 2003 14:14:13 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3AE10.88A8CEE0"
Subject: [Sipping] RE: [Sip] Sip support for TCAP queries
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3AE10.88A8CEE0
Content-Type: text/plain;
	charset="iso-8859-1"

 [Moving this thread to SIPPING, where it belongs]
 
Leaving aside the question of whether or not ENUM supports all of the
functions of TCAP, the main issue is whether or not SIP is the right sort of
protocol to handle this function. A query-response protocol that carries XML
documents from a client to a server? Does SIP INFO really seem to map onto
that well? Aren't there other protocols that are tooled specifically to that
purpose?
 
Furthermore, is the encoding really the issue? XML vs. binary doesn't seem
that significant to me - if a SIP endpoint can template the XML format, it
could template the binary format as well. Regardless of the syntax, should
we expect SIP endpoints to understand the semantics of TCAP? Do we expect a
SIP user agent to understand and implement the concept of, say, a code gap?
That isn't "translation" in any sense that I recognize - it is closer to
saying that SIP user agents have to run a dual stack (SIP and TCAP). Just
look at the <Digits> stanza of the example in 6.1.1.1 of the draft: what
sorts of SIP elements are going to understand binary coded decimal,
recognize numbering plans, and the like? If the answer is "only PSTN-SIP
gateways with that already have SS7 links and could therefore just send TCAP
queries over SS7", then I think there is a design issue here.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Frank W. Miller [mailto:fmiller@sentito.com]
Sent: Tuesday, November 18, 2003 8:50 AM
To: 'Chong, Koan S, ALABS'
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries



 

The main idea of this draft was to provide a capability for SIP endpoints to
do TCAP queries without having to implement the binary TCAP protocol.  The
motivation is that there are a lot of TCAP queries that take place (800,
LNP, CNAME) that are really simple and that major carriers may not want to
go and reimplement in an ENUM database in the short term.  These carriers
have spent a lot of money on their SCPs and converting the to ENUM is
non-trivial.  Now, the SCPs could be front-ended and conversion can be
automated but this draft provides an alternative.  So, to answer the first
question, the SIP endpoint formats the correct query in the XML format
specified and sends if using an INFO to a Signaling Gateway (SG).  The SG
then converts the query to binary TCAP and dips the SCP.  The XML format can
be templated in the implementation so the effort is quite minimal on the SIP
endpoint.  To answer the second question, the draft talks about a couple of
examples but the specification encompasses the entire TCAP message set so
you can format the appropriate dip for AR/C.  One caveat is that the draft
is Telcordia based.  It would need to be extended to take into account other
variants.  On the third question, <personal view> I'm a believer in
translation over tunneling, tunneling just puts off work and mixes messaging
from different signaling networks unnecessarily</personal view>.

 

FM

 

 

 

Frank W. Miller, Ph.D.

Chief Technical Officer

sentitO Networks, Inc.

fmiller@sentito.com

 

-----Original Message-----
From: Chong, Koan S, ALABS [mailto:kschong@att.com] 
Sent: Tuesday, November 18, 2003 11:27 AM
To: Frank W. Miller; McCandless, Kevin
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries

 

 

A couple specific questions:

 

What is the recommendation on how a SIP network element can access the
callers' name databases (CNAM in US) in PSTN after the SIP element has
determined that the called parties have subscribed to Caller ID?

 

How about interworking with CLASS Auto-Recall/Callback (CCBS in ITU?)
procedures?

 

Assume TCAP over SIGTRAN is a bit long long term....

 

Koan

Koan S.Chong

AT&T

1-732-420-4557

 

-----Original Message-----
From: Frank W. Miller [mailto:fmiller@sentito.com]
Sent: Monday, November 17, 2003 6:18 PM
To: 'McCandless, Kevin'
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries

 

You mean other than us implementing it?  No, I don't think so.  I think its
considered Rosemary's Baby by most...

 

FM

 

 

Frank W. Miller, Ph.D.

Chief Technical Officer

sentitO Networks, Inc.

fmiller@sentito.com

 

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
McCandless, Kevin
Sent: Monday, November 17, 2003 4:11 PM
To: sip@ietf.org
Subject: [Sip] Sip support for TCAP queries

 

Has any progress been taken on the draft by Frank Miller on Carrying TCAP in
SIP messages?  Are there other drafts that address SIP access to SS7
database information through TCAP or another method?

 

Thanks,

 

Kevin 


------_=_NextPart_001_01C3AE10.88A8CEE0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1226" name=GENERATOR>
<STYLE>@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Monotype Corsiva;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.emailstyle17 {
	COLOR: navy; FONT-FAMILY: Arial
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2>&nbsp;[Moving this thread to SIPPING, where it 
belongs]</FONT></SPAN></DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2>Leaving aside the question of whether or not ENUM supports all of the 
functions of TCAP, the main issue is whether or not SIP is the right sort of 
protocol to handle this function. A query-response protocol that carries XML 
documents from a client to a server? Does SIP INFO really seem to map onto that 
well? Aren't there other protocols that are tooled specifically to that 
purpose?</FONT></SPAN></DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2>Furthermore, is the encoding really the issue? XML vs. binary doesn't 
seem that significant to me&nbsp;- if&nbsp;a SIP endpoint can template the XML 
format, it could template the binary format as well. Regardless of the syntax, 
should we expect SIP endpoints to understand the semantics of TCAP? Do we expect 
a SIP user agent to understand and implement&nbsp;the concept of, say, a code 
gap? That isn't "translation" in any sense that I recognize&nbsp;- it is closer 
to saying that SIP user agents have to run a dual stack (SIP and TCAP). Just 
look at the &lt;Digits&gt; stanza of the example in 6.1.1.1 of the draft: what 
sorts of SIP elements are going to understand binary coded decimal, recognize 
numbering plans, and the like? If the answer is "only PSTN-SIP&nbsp;gateways 
with that already have SS7 links and could therefore just send TCAP queries over 
SS7", then I think there is a design issue here.</FONT></SPAN></DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=430544919-18112003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Frank W. Miller 
  [mailto:fmiller@sentito.com]<BR><B>Sent:</B> Tuesday, November 18, 2003 8:50 
  AM<BR><B>To:</B> 'Chong, Koan S, ALABS'<BR><B>Cc:</B> 
  sip@ietf.org<BR><B>Subject:</B> RE: [Sip] Sip support for TCAP 
  queries<BR><BR></FONT></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The main idea of this 
  draft was to provide a capability for SIP endpoints to do TCAP queries without 
  having to implement the binary TCAP protocol. &nbsp;The motivation is that 
  there are a lot of TCAP queries that take place (800, LNP, CNAME) that are 
  really simple and that major carriers may not want to go and reimplement in an 
  ENUM database in the short term. &nbsp;These carriers have spent a lot of 
  money on their SCPs and converting the to ENUM is non-trivial.&nbsp; Now, the 
  SCPs could be front-ended and conversion can be automated but this draft 
  provides an alternative.&nbsp; So, to answer the first question, the SIP 
  endpoint formats the correct query in the XML format specified and sends if 
  using an INFO to a Signaling Gateway (SG). &nbsp;The SG then converts the 
  query to binary TCAP and dips the SCP.&nbsp; The XML format can be templated 
  in the implementation so the effort is quite minimal on the SIP 
  endpoint.&nbsp; To answer the second question, the draft talks about a couple 
  of examples but the specification encompasses the entire TCAP message set so 
  you can format the appropriate dip for AR/C.&nbsp; One caveat is that the 
  draft is Telcordia based.&nbsp; It would need to be extended to take into 
  account other variants.&nbsp; On the third question, &lt;personal view&gt; I'm 
  a believer in translation over tunneling, tunneling just puts off work and 
  mixes messaging from different signaling networks unnecessarily&lt;/personal 
  view&gt;.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">FM</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN lang=DE 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Frank W. Miller, 
  Ph.D.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Chief Technical 
  Officer</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">sentitO Networks, 
  Inc.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">fmiller@sentito.com</SPAN></FONT></P></DIV>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Tahoma size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Chong, 
  Koan S, ALABS [mailto:kschong@att.com] <BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, November 18, 2003 11:27 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Frank W. Miller; 
  McCandless, Kevin<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  sip@ietf.org<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 
  [Sip] Sip support for TCAP queries</SPAN></FONT></P>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">A 
  couple&nbsp;specific questions:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What is 
  the recommendation on how a SIP network element can access the callers' name 
  databases (CNAM in US) in PSTN after the SIP element has determined that the 
  called parties have subscribed to Caller ID?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">How 
  about interworking with CLASS Auto-Recall/Callback (CCBS in ITU?) 
  procedures?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Assume 
  TCAP over SIGTRAN&nbsp;is a bit long long term....</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Koan</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Koan 
  S.Chong</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">AT&amp;T</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=blue 
  size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1-732-420-4557</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
  size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <BLOCKQUOTE 
  style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 3pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <P class=MsoNormal 
    style="MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in"><FONT 
    face=Tahoma size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
    Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Frank W. 
    Miller [mailto:fmiller@sentito.com]<BR><B><SPAN 
    style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, November 17, 2003 6:18 
    PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'McCandless, 
    Kevin'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
    sip@ietf.org<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 
    [Sip] Sip support for TCAP queries</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">You 
    mean other than us implementing it?&nbsp; No, I don't think so.&nbsp; I 
    think its considered Rosemary's Baby by most...</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN 
    style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">FM</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN lang=DE 
    style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Frank W. Miller, 
    Ph.D.</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Chief 
    Technical Officer</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN 
    style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">sentitO Networks, 
    Inc.</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Arial color=navy 
    size=2><SPAN 
    style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">fmiller@sentito.com</SPAN></FONT></P></DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face=Tahoma size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
    Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> 
    sip-admin@ietf.org [mailto:sip-admin@ietf.org] <B><SPAN 
    style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>McCandless, 
    Kevin<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, 
    November 17, 2003 4:11 PM<BR><B><SPAN 
    style="FONT-WEIGHT: bold">To:</SPAN></B> sip@ietf.org<BR><B><SPAN 
    style="FONT-WEIGHT: bold">Subject:</SPAN></B> [Sip] Sip support for TCAP 
    queries</SPAN></FONT></P>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
    <DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Has any progress been taken on 
    the draft by Frank Miller on Carrying TCAP in SIP messages?&nbsp; Are there 
    other drafts that address SIP access to SS7 database information through 
    TCAP or another method?</SPAN></FONT></P></DIV>
    <DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
    <DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face=Arial size=2><SPAN 
    style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks,</SPAN></FONT></P></DIV>
    <DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face="Times New Roman" 
    size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
    <P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face="Monotype Corsiva" 
    size=4><SPAN 
    style="FONT-SIZE: 13.5pt; FONT-FAMILY: 'Monotype Corsiva'">Kevin 
    </SPAN></FONT></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3AE10.88A8CEE0--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 15:53:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15547
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 15:53:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCqM-0007IV-Gy
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:53:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIKr20v028045
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 15:53:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCqL-0007IG-RR
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 15:53:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15516
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 15:52:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCqK-0005o5-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:53:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCqJ-0005o2-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 15:52:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCpO-00078E-3L; Tue, 18 Nov 2003 15:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMCox-00077s-9v
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 15:51:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15444
	for <sipping@ietf.org>; Tue, 18 Nov 2003 15:51:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMCov-0005mE-00
	for sipping@ietf.org; Tue, 18 Nov 2003 15:51:33 -0500
Received: from airwolf.sentito.com ([65.202.222.11])
	by ietf-mx with smtp (Exim 4.12)
	id 1AMCou-0005lp-00
	for sipping@ietf.org; Tue, 18 Nov 2003 15:51:32 -0500
Received: (qmail 30575 invoked from network); 18 Nov 2003 20:52:20 -0000
Received: from unknown (HELO frankgks0u6mmz) (relay@65.202.222.2)
  by airwolf.sentito.com with SMTP; 18 Nov 2003 20:52:20 -0000
From: "Frank W. Miller" <fmiller@sentito.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>
Cc: <sipping@ietf.org>
Date: Tue, 18 Nov 2003 15:50:59 -0500
Message-ID: <009601c3ae15$abdfe830$9100000a@frankgks0u6mmz>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0097_01C3ADEB.C309E030"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513CD56462@stntexch03.va.neustar.com>
Importance: Normal
Subject: [Sipping] RE: [Sip] Sip support for TCAP queries
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0097_01C3ADEB.C309E030
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

Aiieee, a cross is raised!!  ;)

=20

Anyway, you're right, the format doesn't matter at all, except for one
thing.  Expedience.  The essence of the argument against this type of =
draft
in general, i.e. one that uses INFO to carry anything, is usually based =
on
the fact that the content is application specific and so doesn't fit =
with
the base SIP protocol.  I can understand that and accept it, it really
doesn't matter to me.  I'm an implementor, not a protocol specifier.
Unfortunately, the protocol doesn't do everything I need it to do so I =
have
to add stuff to fill in the holes when I take it into the real world.  =
The
other draft in this area draft-miller-sip-isup-annex is another example =
of
augmentation, the addition of ISUP maintenance commands to the ISUP
translation now RFC.  I could write/buy an SS7 implementation and =
template
the messages and hook that into my CNAME/LNP/whatever at the call =
control
layer and to SCTP/UDP/whatever on the network side but why, to keep the =
SIP
implementation "beautiful"?  The bottom line is I'm not going to pass =
the
cost of the SS7 stack on to my customers if I can make a simple addition =
to
the SIP stuff and do exactly the same thing basically for free.

=20

Now with respect to the specifics of the encoding, we can certainly talk
about anything.  That was the whole reason for publishing the work in =
the
IETF to begin with.  On 6.1.1.1 specifically, this is simply a field
required in the QWP message.  The actual digits are specified in a =
string
not in BCD binary.  The Signaling Gateway/Softswitch/whatever just picks =
up
BCD from the Encoding field and fills in the appropriate value in the =
actual
TCAP binary message when the translation is done.  The digits in the =
ASCII
string are converted similarly to BCD format in the TCAP binary message =
also
at that time.  The <Encoding  > field doesn't change and is therefore a
perfect candidate for being templated.  The only real information that =
needs
to be handled per query here is the actual number.

=20

FM

=20

=20

=20

Frank W. Miller, Ph.D.

Chief Technical Officer

sentitO Networks, Inc.

fmiller@sentito.com

=20

-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]=20
Sent: Tuesday, November 18, 2003 3:14 PM
To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
Subject: RE: [Sip] Sip support for TCAP queries

=20

 [Moving this thread to SIPPING, where it belongs]

=20

Leaving aside the question of whether or not ENUM supports all of the
functions of TCAP, the main issue is whether or not SIP is the right =
sort of
protocol to handle this function. A query-response protocol that carries =
XML
documents from a client to a server? Does SIP INFO really seem to map =
onto
that well? Aren't there other protocols that are tooled specifically to =
that
purpose?

=20

Furthermore, is the encoding really the issue? XML vs. binary doesn't =
seem
that significant to me - if a SIP endpoint can template the XML format, =
it
could template the binary format as well. Regardless of the syntax, =
should
we expect SIP endpoints to understand the semantics of TCAP? Do we =
expect a
SIP user agent to understand and implement the concept of, say, a code =
gap?
That isn't "translation" in any sense that I recognize - it is closer to
saying that SIP user agents have to run a dual stack (SIP and TCAP). =
Just
look at the <Digits> stanza of the example in 6.1.1.1 of the draft: what
sorts of SIP elements are going to understand binary coded decimal,
recognize numbering plans, and the like? If the answer is "only PSTN-SIP
gateways with that already have SS7 links and could therefore just send =
TCAP
queries over SS7", then I think there is a design issue here.

=20

Jon Peterson

NeuStar, Inc.

-----Original Message-----
From: Frank W. Miller [mailto:fmiller@sentito.com]
Sent: Tuesday, November 18, 2003 8:50 AM
To: 'Chong, Koan S, ALABS'
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries

=20

The main idea of this draft was to provide a capability for SIP =
endpoints to
do TCAP queries without having to implement the binary TCAP protocol.  =
The
motivation is that there are a lot of TCAP queries that take place (800,
LNP, CNAME) that are really simple and that major carriers may not want =
to
go and reimplement in an ENUM database in the short term.  These =
carriers
have spent a lot of money on their SCPs and converting the to ENUM is
non-trivial.  Now, the SCPs could be front-ended and conversion can be
automated but this draft provides an alternative.  So, to answer the =
first
question, the SIP endpoint formats the correct query in the XML format
specified and sends if using an INFO to a Signaling Gateway (SG).  The =
SG
then converts the query to binary TCAP and dips the SCP.  The XML format =
can
be templated in the implementation so the effort is quite minimal on the =
SIP
endpoint.  To answer the second question, the draft talks about a couple =
of
examples but the specification encompasses the entire TCAP message set =
so
you can format the appropriate dip for AR/C.  One caveat is that the =
draft
is Telcordia based.  It would need to be extended to take into account =
other
variants.  On the third question, <personal view> I'm a believer in
translation over tunneling, tunneling just puts off work and mixes =
messaging
from different signaling networks unnecessarily</personal view>.

=20

FM

=20

=20

=20

Frank W. Miller, Ph.D.

Chief Technical Officer

sentitO Networks, Inc.

fmiller@sentito.com

=20

-----Original Message-----
From: Chong, Koan S, ALABS [mailto:kschong@att.com]=20
Sent: Tuesday, November 18, 2003 11:27 AM
To: Frank W. Miller; McCandless, Kevin
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries

=20

=20

A couple specific questions:

=20

What is the recommendation on how a SIP network element can access the
callers' name databases (CNAM in US) in PSTN after the SIP element has
determined that the called parties have subscribed to Caller ID?

=20

How about interworking with CLASS Auto-Recall/Callback (CCBS in ITU?)
procedures?

=20

Assume TCAP over SIGTRAN is a bit long long term....

=20

Koan

Koan S.Chong

AT&T

1-732-420-4557

=20

-----Original Message-----
From: Frank W. Miller [mailto:fmiller@sentito.com]
Sent: Monday, November 17, 2003 6:18 PM
To: 'McCandless, Kevin'
Cc: sip@ietf.org
Subject: RE: [Sip] Sip support for TCAP queries

=20

You mean other than us implementing it?  No, I don't think so.  I think =
its
considered Rosemary's Baby by most...

=20

FM

=20

=20

Frank W. Miller, Ph.D.

Chief Technical Officer

sentitO Networks, Inc.

fmiller@sentito.com

=20

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
McCandless, Kevin
Sent: Monday, November 17, 2003 4:11 PM
To: sip@ietf.org
Subject: [Sip] Sip support for TCAP queries

=20

Has any progress been taken on the draft by Frank Miller on Carrying =
TCAP in
SIP messages?  Are there other drafts that address SIP access to SS7
database information through TCAP or another method?

=20

Thanks,

=20

Kevin=20


------=_NextPart_000_0097_01C3ADEB.C309E030
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<title>Message</title>

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Monotype Corsiva";
	panose-1:3 1 1 1 1 2 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.emailstyle17
	{font-family:Arial;
	color:navy;}
span.emailstyle18
	{font-family:Arial;
	color:navy;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Aiieee, a cross is raised!!&nbsp; =
;)</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Anyway, you&#8217;re right, the =
format doesn&#8217;t
matter at all, except for one thing.&nbsp; Expedience.&nbsp; The essence =
of the
argument against this type of draft in general, i.e. one that uses INFO =
to
carry anything, is usually based on the fact that the content is =
application
specific and so doesn&#8217;t fit with the base SIP protocol.&nbsp; I =
can
understand that and accept it, it really doesn&#8217;t matter to =
me.&nbsp; I&#8217;m
an implementor, not a protocol specifier.&nbsp; Unfortunately, the =
protocol doesn&#8217;t
do everything I need it to do so I have to add stuff to fill in the =
holes when
I take it into the real world.&nbsp; The other draft in this area
draft-miller-sip-isup-annex is another example of augmentation, the =
addition of
ISUP maintenance commands to the ISUP translation now RFC. &nbsp;I could
write/buy an SS7 implementation and template the messages and hook that =
into my
CNAME/LNP/whatever at the call control layer and to SCTP/UDP/whatever on =
the
network side but why, to keep the SIP implementation =
&#8220;beautiful&#8221;?&nbsp;
The bottom line is I&#8217;m not going to pass the cost of the SS7 stack =
on to
my customers if I can make a simple addition to the SIP stuff and do =
exactly
the same thing basically for free.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Now with respect to the specifics =
of the
encoding, we can certainly talk about anything. &nbsp;That was the whole =
reason
for publishing the work in the IETF to begin with.&nbsp; On 6.1.1.1
specifically, this is simply a field required in the QWP message.&nbsp; =
The
actual digits are specified in a string not in BCD binary.&nbsp; The =
Signaling
Gateway/Softswitch/whatever just picks up BCD from the Encoding field =
and fills
in the appropriate value in the actual TCAP binary message when the =
translation
is done.&nbsp; The digits in the ASCII string are converted similarly to =
BCD format
in the TCAP binary message also at that time. &nbsp;The =
&lt;Encoding&nbsp; &gt;
field doesn&#8217;t change and is therefore a perfect candidate for =
being templated.&nbsp;
The only real information that needs to be handled per query here is the =
actual
number.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>FM</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Frank W. Miller, =
Ph.D.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Chief Technical =
Officer</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>sentitO Networks, =
Inc.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
 =
10.0pt;font-family:Arial;color:navy'>fmiller@sentito.com</span></font></p=
>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Peterson, Jon
[mailto:jon.peterson@neustar.biz] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
18, 2003
3:14 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Frank W. Miller'; =
'Chong,
Koan S, ALABS'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'sipping@ietf.org';
'McCandless, Kevin'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] Sip =
support for
TCAP queries</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>&nbsp;[Moving =
this thread
to SIPPING, where it belongs]</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Leaving aside =
the
question of whether or not ENUM supports all of the functions of TCAP, =
the main
issue is whether or not SIP is the right sort of protocol to handle this
function. A query-response protocol that carries XML documents from a =
client to
a server? Does SIP INFO really seem to map onto that well? Aren't there =
other
protocols that are tooled specifically to that =
purpose?</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Furthermore, is =
the
encoding really the issue? XML vs. binary doesn't seem that significant =
to
me&nbsp;- if&nbsp;a SIP endpoint can template the XML format, it could =
template
the binary format as well. Regardless of the syntax, should we expect =
SIP
endpoints to understand the semantics of TCAP? Do we expect a SIP user =
agent to
understand and implement&nbsp;the concept of, say, a code gap? That =
isn't
&quot;translation&quot; in any sense that I recognize&nbsp;- it is =
closer to
saying that SIP user agents have to run a dual stack (SIP and TCAP). =
Just look
at the &lt;Digits&gt; stanza of the example in 6.1.1.1 of the draft: =
what sorts
of SIP elements are going to understand binary coded decimal, recognize
numbering plans, and the like? If the answer is &quot;only
PSTN-SIP&nbsp;gateways with that already have SS7 links and could =
therefore
just send TCAP queries over SS7&quot;, then I think there is a design =
issue
here.</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Jon =
Peterson</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>NeuStar, =
Inc.</span></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>=


<p class=3DMsoNormal =
style=3D'margin-right:0in;margin-bottom:12.0pt;margin-left:
.5in'><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Frank W. Miller
[mailto:fmiller@sentito.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
18, 2003
8:50 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Chong, Koan S, =
ALABS'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> sip@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] Sip =
support for
TCAP queries</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The main idea of =
this
draft was to provide a capability for SIP endpoints to do TCAP queries =
without
having to implement the binary TCAP protocol. &nbsp;The motivation is =
that
there are a lot of TCAP queries that take place (800, LNP, CNAME) that =
are
really simple and that major carriers may not want to go and reimplement =
in an
ENUM database in the short term. &nbsp;These carriers have spent a lot =
of money
on their SCPs and converting the to ENUM is non-trivial.&nbsp; Now, the =
SCPs
could be front-ended and conversion can be automated but this draft =
provides an
alternative.&nbsp; So, to answer the first question, the SIP endpoint =
formats
the correct query in the XML format specified and sends if using an INFO =
to a
Signaling Gateway (SG). &nbsp;The SG then converts the query to binary =
TCAP and
dips the SCP.&nbsp; The XML format can be templated in the =
implementation so
the effort is quite minimal on the SIP endpoint.&nbsp; To answer the =
second
question, the draft talks about a couple of examples but the =
specification
encompasses the entire TCAP message set so you can format the =
appropriate dip
for AR/C.&nbsp; One caveat is that the draft is Telcordia based.&nbsp; =
It would
need to be extended to take into account other variants.&nbsp; On the =
third
question, &lt;personal view&gt; I'm a believer in translation over =
tunneling,
tunneling just puts off work and mixes messaging from different =
signaling
networks unnecessarily&lt;/personal view&gt;.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>FM</span></font><=
/p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
lang=3DDE style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Frank =
W. Miller,
Ph.D.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Chief Technical =
Officer</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>sentitO =
Networks, Inc.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>fmiller@sentito.c=
om</span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Chong, Koan S, =
ALABS
[mailto:kschong@att.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, November =
18, 2003
11:27 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Frank W. Miller; =
McCandless,
Kevin<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> sip@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] Sip =
support for
TCAP queries</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>A =
couple&nbsp;specific
questions:</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>What is
the recommendation on how a SIP network element can access the callers' =
name
databases (CNAM in US) in PSTN after the SIP element has determined that =
the
called parties have subscribed to Caller ID?</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>How
about interworking with CLASS Auto-Recall/Callback (CCBS in ITU?) =
procedures?</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Assume
TCAP over SIGTRAN&nbsp;is a bit long long term....</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Koan</span></font=
></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>Koan
S.Chong</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>AT&amp;T</span></=
font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dblue
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>1-732-420-4557</s=
pan></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>=


<p class=3DMsoNormal =
style=3D'margin-right:0in;margin-bottom:12.0pt;margin-left:
1.0in'><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Frank W. Miller
[mailto:fmiller@sentito.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, November =
17, 2003
6:18 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'McCandless, =
Kevin'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> sip@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] Sip =
support for
TCAP queries</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>You mean
other than us implementing it?&nbsp; No, I don't think so.&nbsp; I think =
its
considered Rosemary's Baby by most...</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>FM</span></font><=
/p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Frank
W. Miller, Ph.D.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Chief
Technical Officer</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>sentitO
Networks, Inc.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>fmiller@sentito.c=
om</span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> sip-admin@ietf.org
[mailto:sip-admin@ietf.org] <b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>McCandless,
Kevin<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, November =
17, 2003
4:11 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sip@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sip] Sip =
support for
TCAP queries</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Has any progress been taken =
on the
draft by Frank Miller on Carrying TCAP in SIP messages?&nbsp; Are there =
other
drafts that address SIP access to SS7 database information through TCAP =
or
another method?</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Thanks,</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:1.5in'><font size=3D4
face=3D"Monotype Corsiva"><span =
style=3D'font-size:13.5pt;font-family:"Monotype Corsiva"'>Kevin
</span></font></p>

</blockquote>

</blockquote>

</div>

</body>

</html>

------=_NextPart_000_0097_01C3ADEB.C309E030--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 16:11:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16370
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 16:11:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD7u-0008RX-8s
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:11:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAILBANx032454
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:11:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD7u-0008RN-4W
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 16:11:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16345
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 16:10:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD7s-0006AF-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:11:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD7s-0006A8-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:11:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD6o-0008J1-Ff; Tue, 18 Nov 2003 16:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD67-0008Fn-Sa
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 16:09:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16267
	for <sipping@ietf.org>; Tue, 18 Nov 2003 16:09:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD66-00068r-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:09:18 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD65-00068A-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:09:17 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hAILFFf10032
	for <sipping@ietf.org>; Tue, 18 Nov 2003 13:15:15 -0800
Message-Id: <6.0.0.22.2.20031118155744.03642c70@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 18 Nov 2003 16:08:36 -0500
To: <sipping@ietf.org>
From: Richard Shockey <richard@shockey.us>
Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
In-Reply-To: <009601c3ae15$abdfe830$9100000a@frankgks0u6mmz>
References: <A9DECB0B8A01A54DBECC03B25D29513CD56462@stntexch03.va.neustar.com>
 <009601c3ae15$abdfe830$9100000a@frankgks0u6mmz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 03:50 PM 11/18/2003, Frank W. Miller wrote:

As the distributor of the NO TCAP buttons on generous display at IETF 59 
and fine trade shows nationwide , let me comment that this is one of the 
silliest ideas I have yet seen cross the SIPPING landscape.

Why ..why on earth would you want to do this ..any query response mechanism 
can get you the data points necessary without the baggage TCAP puts you 
through.

Talk to your SS7 vendor and demand better service or fire them. Get them to 
support SIP itself  query response mechanism. Send an INVITE expect a 302 
MOVE in response and encapsulate SS7 the data as part of a TEL URL in the 
response.

This is a "bad idea" tm worthy of the big gong and hook.


>
>Aiieee, a cross is raised!!  ;)
>
>Anyway, you're right, the format doesn't matter at all, except for one 
>thing.  Expedience.  The essence of the argument against this type of 
>draft in general, i.e. one that uses INFO to carry anything, is usually 
>based on the fact that the content is application specific and so doesn't 
>fit with the base SIP protocol.  I can understand that and accept it, it 
>really doesn't matter to me.  I'm an implementor, not a protocol 
>specifier.  Unfortunately, the protocol doesn't do everything I need it to 
>do so I have to add stuff to fill in the holes when I take it into the 
>real world.  The other draft in this area draft-miller-sip-isup-annex is 
>another example of augmentation, the addition of ISUP maintenance commands 
>to the ISUP translation now RFC.  I could write/buy an SS7 implementation 
>and template the messages and hook that into my CNAME/LNP/whatever at the 
>call control layer and to SCTP/UDP/whatever on the network side but why, 
>to keep the SIP implementation "beautiful"?  The bottom line is I'm not 
>going to pass the cost of the SS7 stack on to my customers if I can make a 
>simple addition to the SIP stuff and do exactly the same thing basically 
>for free.
>
>Now with respect to the specifics of the encoding, we can certainly talk 
>about anything.  That was the whole reason for publishing the work in the 
>IETF to begin with.  On 6.1.1.1 specifically, this is simply a field 
>required in the QWP message.  The actual digits are specified in a string 
>not in BCD binary.  The Signaling Gateway/Softswitch/whatever just picks 
>up BCD from the Encoding field and fills in the appropriate value in the 
>actual TCAP binary message when the translation is done.  The digits in 
>the ASCII string are converted similarly to BCD format in the TCAP binary 
>message also at that time.  The <Encoding  > field doesn't change and is 
>therefore a perfect candidate for being templated.  The only real 
>information that needs to be handled per query here is the actual number.
>
>FM
>
>
>
>Frank W. Miller, Ph.D.
>Chief Technical Officer
>sentitO Networks, Inc.
>fmiller@sentito.com
>
>-----Original Message-----
>From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
>Sent: Tuesday, November 18, 2003 3:14 PM
>To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
>Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
>Subject: RE: [Sip] Sip support for TCAP queries
>
>  [Moving this thread to SIPPING, where it belongs]
>
>Leaving aside the question of whether or not ENUM supports all of the 
>functions of TCAP, the main issue is whether or not SIP is the right sort 
>of protocol to handle this function. A query-response protocol that 
>carries XML documents from a client to a server? Does SIP INFO really seem 
>to map onto that well? Aren't there other protocols that are tooled 
>specifically to that purpose?
>
>Furthermore, is the encoding really the issue? XML vs. binary doesn't seem 
>that significant to me - if a SIP endpoint can template the XML format, it 
>could template the binary format as well. Regardless of the syntax, should 
>we expect SIP endpoints to understand the semantics of TCAP? Do we expect 
>a SIP user agent to understand and implement the concept of, say, a code 
>gap? That isn't "translation" in any sense that I recognize - it is closer 
>to saying that SIP user agents have to run a dual stack (SIP and TCAP). 
>Just look at the <Digits> stanza of the example in 6.1.1.1 of the draft: 
>what sorts of SIP elements are going to understand binary coded decimal, 
>recognize numbering plans, and the like? If the answer is "only PSTN-SIP 
>gateways with that already have SS7 links and could therefore just send 
>TCAP queries over SS7", then I think there is a design issue here.
>
>Jon Peterson
>NeuStar, Inc.
>-----Original Message-----
>From: Frank W. Miller [mailto:fmiller@sentito.com]
>Sent: Tuesday, November 18, 2003 8:50 AM
>To: 'Chong, Koan S, ALABS'
>Cc: sip@ietf.org
>Subject: RE: [Sip] Sip support for TCAP queries
>
>The main idea of this draft was to provide a capability for SIP endpoints 
>to do TCAP queries without having to implement the binary TCAP 
>protocol.  The motivation is that there are a lot of TCAP queries that 
>take place (800, LNP, CNAME) that are really simple and that major 
>carriers may not want to go and reimplement in an ENUM database in the 
>short term.  These carriers have spent a lot of money on their SCPs and 
>converting the to ENUM is non-trivial.  Now, the SCPs could be front-ended 
>and conversion can be automated but this draft provides an 
>alternative.  So, to answer the first question, the SIP endpoint formats 
>the correct query in the XML format specified and sends if using an INFO 
>to a Signaling Gateway (SG).  The SG then converts the query to binary 
>TCAP and dips the SCP.  The XML format can be templated in the 
>implementation so the effort is quite minimal on the SIP endpoint.  To 
>answer the second question, the draft talks about a couple of examples but 
>the specification encompasses the entire TCAP message set so you can 
>format the appropriate dip for AR/C.  One caveat is that the draft is 
>Telcordia based.  It would need to be extended to take into account other 
>variants.  On the third question, <personal view> I'm a believer in 
>translation over tunneling, tunneling just puts off work and mixes 
>messaging from different signaling networks unnecessarily</personal view>.
>
>FM
>
>
>
>Frank W. Miller, Ph.D.
>Chief Technical Officer
>sentitO Networks, Inc.
>fmiller@sentito.com
>
>-----Original Message-----
>From: Chong, Koan S, ALABS [mailto:kschong@att.com]
>Sent: Tuesday, November 18, 2003 11:27 AM
>To: Frank W. Miller; McCandless, Kevin
>Cc: sip@ietf.org
>Subject: RE: [Sip] Sip support for TCAP queries
>
>
>A couple specific questions:
>
>What is the recommendation on how a SIP network element can access the 
>callers' name databases (CNAM in US) in PSTN after the SIP element has 
>determined that the called parties have subscribed to Caller ID?
>
>How about interworking with CLASS Auto-Recall/Callback (CCBS in ITU?) 
>procedures?
>
>Assume TCAP over SIGTRAN is a bit long long term....
>
>Koan
>Koan S.Chong
>AT&T
>1-732-420-4557
>
>-----Original Message-----
>From: Frank W. Miller [mailto:fmiller@sentito.com]
>Sent: Monday, November 17, 2003 6:18 PM
>To: 'McCandless, Kevin'
>Cc: sip@ietf.org
>Subject: RE: [Sip] Sip support for TCAP queries
>
>You mean other than us implementing it?  No, I don't think so.  I think 
>its considered Rosemary's Baby by most...
>
>FM
>
>
>Frank W. Miller, Ph.D.
>Chief Technical Officer
>sentitO Networks, Inc.
>fmiller@sentito.com
>
>-----Original Message-----
>From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of 
>McCandless, Kevin
>Sent: Monday, November 17, 2003 4:11 PM
>To: sip@ietf.org
>Subject: [Sip] Sip support for TCAP queries
>
>Has any progress been taken on the draft by Frank Miller on Carrying TCAP 
>in SIP messages?  Are there other drafts that address SIP access to SS7 
>database information through TCAP or another method?
>
>Thanks,
>
>Kevin


 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 16:13:57 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16569
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 16:13:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDAI-0000Le-3V
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:13:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAILDc0H001332
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:13:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDAH-0000LP-W0
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 16:13:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16482
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 16:13:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDAG-0006DZ-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:13:36 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDAF-0006DW-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:13:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD9h-00008F-3H; Tue, 18 Nov 2003 16:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMD8x-000079-KX
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 16:12:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16408
	for <sipping@ietf.org>; Tue, 18 Nov 2003 16:12:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD8v-0006Be-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:12:13 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMD8u-0006At-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:12:12 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAILBYp23106;
	Tue, 18 Nov 2003 16:11:34 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W3H80NWT; Tue, 18 Nov 2003 16:11:34 -0500
Received: from nortelnetworks.com (acart1mq.ca.nortel.com [47.129.130.76]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5N33T; Tue, 18 Nov 2003 16:11:34 -0500
Message-ID: <3FBA8B05.7080303@nortelnetworks.com>
Date: Tue, 18 Nov 2003 16:11:33 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Frank W. Miller" <fmiller@sentito.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
References: <009601c3ae15$abdfe830$9100000a@frankgks0u6mmz>
In-Reply-To: <009601c3ae15$abdfe830$9100000a@frankgks0u6mmz>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars0m9.nortelnetworks.com id hAILBYp23106
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Why not use HTML rather than SIP?

Frank W. Miller wrote:

> =20
>=20
> Aiieee, a cross is raised!!  ;)
>=20
> =20
>=20
> Anyway, you=92re right, the format doesn=92t matter at all, except for =
one=20
> thing.  Expedience.  The essence of the argument against this type of=20
> draft in general, i.e. one that uses INFO to carry anything, is usually=
=20
> based on the fact that the content is application specific and so=20
> doesn=92t fit with the base SIP protocol.  I can understand that and=20
> accept it, it really doesn=92t matter to me.  I=92m an implementor, not=
 a=20
> protocol specifier.  Unfortunately, the protocol doesn=92t do everythin=
g I=20
> need it to do so I have to add stuff to fill in the holes when I take i=
t=20
> into the real world.  The other draft in this area=20
> draft-miller-sip-isup-annex is another example of augmentation, the=20
> addition of ISUP maintenance commands to the ISUP translation now RFC.=20
>  I could write/buy an SS7 implementation and template the messages and=20
> hook that into my CNAME/LNP/whatever at the call control layer and to=20
> SCTP/UDP/whatever on the network side but why, to keep the SIP=20
> implementation =93beautiful=94?  The bottom line is I=92m not going to =
pass=20
> the cost of the SS7 stack on to my customers if I can make a simple=20
> addition to the SIP stuff and do exactly the same thing basically for f=
ree.
>=20
> =20
>=20
> Now with respect to the specifics of the encoding, we can certainly tal=
k=20
> about anything.  That was the whole reason for publishing the work in=20
> the IETF to begin with.  On 6.1.1.1 specifically, this is simply a fiel=
d=20
> required in the QWP message.  The actual digits are specified in a=20
> string not in BCD binary.  The Signaling Gateway/Softswitch/whatever=20
> just picks up BCD from the Encoding field and fills in the appropriate=20
> value in the actual TCAP binary message when the translation is done. =20
> The digits in the ASCII string are converted similarly to BCD format in=
=20
> the TCAP binary message also at that time.  The <Encoding  > field=20
> doesn=92t change and is therefore a perfect candidate for being=20
> templated.  The only real information that needs to be handled per quer=
y=20
> here is the actual number.
>=20
> =20
>=20
> FM
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> Frank W. Miller, Ph.D.
>=20
> Chief Technical Officer
>=20
> sentitO Networks, Inc.
>=20
> fmiller@sentito.com
>=20
> =20
>=20
> -----Original Message-----
> *From:* Peterson, Jon [mailto:jon.peterson@neustar.biz]
> *Sent:* Tuesday, November 18, 2003 3:14 PM
> *To:* 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> *Cc:* 'sipping@ietf.org'; 'McCandless, Kevin'
> *Subject:* RE: [Sip] Sip support for TCAP queries
>=20
> =20
>=20
>  [Moving this thread to SIPPING, where it belongs]
>=20
> =20
>=20
> Leaving aside the question of whether or not ENUM supports all of the=20
> functions of TCAP, the main issue is whether or not SIP is the right=20
> sort of protocol to handle this function. A query-response protocol tha=
t=20
> carries XML documents from a client to a server? Does SIP INFO really=20
> seem to map onto that well? Aren't there other protocols that are toole=
d=20
> specifically to that purpose?
>=20
> =20
>=20
> Furthermore, is the encoding really the issue? XML vs. binary doesn't=20
> seem that significant to me - if a SIP endpoint can template the XML=20
> format, it could template the binary format as well. Regardless of the=20
> syntax, should we expect SIP endpoints to understand the semantics of=20
> TCAP? Do we expect a SIP user agent to understand and implement the=20
> concept of, say, a code gap? That isn't "translation" in any sense that=
=20
> I recognize - it is closer to saying that SIP user agents have to run a=
=20
> dual stack (SIP and TCAP). Just look at the <Digits> stanza of the=20
> example in 6.1.1.1 of the draft: what sorts of SIP elements are going t=
o=20
> understand binary coded decimal, recognize numbering plans, and the=20
> like? If the answer is "only PSTN-SIP gateways with that already have=20
> SS7 links and could therefore just send TCAP queries over SS7", then I=20
> think there is a design issue here.
>=20
> =20
>=20
> Jon Peterson
>=20
> NeuStar, Inc.
>=20
>     -----Original Message-----
>     *From:* Frank W. Miller [mailto:fmiller@sentito.com]
>     *Sent:* Tuesday, November 18, 2003 8:50 AM
>     *To:* 'Chong, Koan S, ALABS'
>     *Cc:* sip@ietf.org
>     *Subject:* RE: [Sip] Sip support for TCAP queries
>=20
>     =20
>=20
>     The main idea of this draft was to provide a capability for SIP
>     endpoints to do TCAP queries without having to implement the binary
>     TCAP protocol.  The motivation is that there are a lot of TCAP
>     queries that take place (800, LNP, CNAME) that are really simple an=
d
>     that major carriers may not want to go and reimplement in an ENUM
>     database in the short term.  These carriers have spent a lot of
>     money on their SCPs and converting the to ENUM is non-trivial.  Now=
,
>     the SCPs could be front-ended and conversion can be automated but
>     this draft provides an alternative.  So, to answer the first
>     question, the SIP endpoint formats the correct query in the XML
>     format specified and sends if using an INFO to a Signaling Gateway
>     (SG).  The SG then converts the query to binary TCAP and dips the
>     SCP.  The XML format can be templated in the implementation so the
>     effort is quite minimal on the SIP endpoint.  To answer the second
>     question, the draft talks about a couple of examples but the
>     specification encompasses the entire TCAP message set so you can
>     format the appropriate dip for AR/C.  One caveat is that the draft
>     is Telcordia based.  It would need to be extended to take into
>     account other variants.  On the third question, <personal view> I'm
>     a believer in translation over tunneling, tunneling just puts off
>     work and mixes messaging from different signaling networks
>     unnecessarily</personal view>.
>=20
>     =20
>=20
>     FM
>=20
>     =20
>=20
>     =20
>=20
>     =20
>=20
>     Frank W. Miller, Ph.D.
>=20
>     Chief Technical Officer
>=20
>     sentitO Networks, Inc.
>=20
>     fmiller@sentito.com
>=20
>     =20
>=20
>     -----Original Message-----
>     *From:* Chong, Koan S, ALABS [mailto:kschong@att.com]
>     *Sent:* Tuesday, November 18, 2003 11:27 AM
>     *To:* Frank W. Miller; McCandless, Kevin
>     *Cc:* sip@ietf.org
>     *Subject:* RE: [Sip] Sip support for TCAP queries
>=20
>     =20
>=20
>     =20
>=20
>     A couple specific questions:
>=20
>     =20
>=20
>     What is the recommendation on how a SIP network element can access
>     the callers' name databases (CNAM in US) in PSTN after the SIP
>     element has determined that the called parties have subscribed to
>     Caller ID?
>=20
>     =20
>=20
>     How about interworking with CLASS Auto-Recall/Callback (CCBS in
>     ITU?) procedures?
>=20
>     =20
>=20
>     Assume TCAP over SIGTRAN is a bit long long term....
>=20
>     =20
>=20
>     Koan
>=20
>     Koan S.Chong
>=20
>     AT&T
>=20
>     1-732-420-4557
>=20
>     =20
>=20
>         -----Original Message-----
>         *From:* Frank W. Miller [mailto:fmiller@sentito.com]
>         *Sent:* Monday, November 17, 2003 6:18 PM
>         *To:* 'McCandless, Kevin'
>         *Cc:* sip@ietf.org
>         *Subject:* RE: [Sip] Sip support for TCAP queries
>=20
>         =20
>=20
>         You mean other than us implementing it?  No, I don't think so.=20
>         I think its considered Rosemary's Baby by most...
>=20
>         =20
>=20
>         FM
>=20
>         =20
>=20
>         =20
>=20
>         Frank W. Miller, Ph.D.
>=20
>         Chief Technical Officer
>=20
>         sentitO Networks, Inc.
>=20
>         fmiller@sentito.com
>=20
>         =20
>=20
>         -----Original Message-----
>         *From:* sip-admin@ietf.org [mailto:sip-admin@ietf.org] *On
>         Behalf Of *McCandless, Kevin
>         *Sent:* Monday, November 17, 2003 4:11 PM
>         *To:* sip@ietf.org
>         *Subject:* [Sip] Sip support for TCAP queries
>=20
>         =20
>=20
>         Has any progress been taken on the draft by Frank Miller on
>         Carrying TCAP in SIP messages?  Are there other drafts that
>         address SIP access to SS7 database information through TCAP or
>         another method?
>=20
>         =20
>=20
>         Thanks,
>=20
>         =20
>=20
>         Kevin
>=20


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 16:55:02 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19964
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 16:55:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDo4-00032H-Ov
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:54:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAILsiUa011665
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:54:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDo4-000324-EB
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 16:54:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19939
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 16:54:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDo2-0007fZ-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:54:42 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDo2-0007fW-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:54:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDnN-0002rI-1T; Tue, 18 Nov 2003 16:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDmT-0002qG-T8
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 16:53:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19865
	for <sipping@ietf.org>; Tue, 18 Nov 2003 16:52:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDmR-0007cz-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:53:03 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDmQ-0007br-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:53:03 -0500
Received: from cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 18 Nov 2003 13:53:21 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id hAILr1iN009101
	for <sipping@ietf.org>; Tue, 18 Nov 2003 13:53:01 -0800 (PST)
Received: from [128.107.171.228] ([128.107.171.228])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKB31187;
	Tue, 18 Nov 2003 13:52:53 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Tue, 18 Nov 2003 13:52:53 -0800
Subject: Re: [Sipping] Comment on the applicability of
	draft-ietf-sipping-config-framework
From: Cullen Jennings <fluffy@cisco.com>
To: <sipping@ietf.org>
Message-ID: <BBDFD4B5.25249%fluffy@cisco.com>
In-Reply-To: <E392EEA75EC5F54AB75229B693B1B6A707E7A241@esebe018.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Are there are any patents or other IPR issues with SyncML?


On 11/11/03 7:21 PM, "Markus.Isomaki@nokia.com" <Markus.Isomaki@nokia.com>
wrote:

> Hi,
> 
> I want to elaborate on the comment I made about
> draft-ietf-sipping-config-framework and wireless devices in today's SIPPING
> session:
> 
> In general I think the framework presented in the draft is very good. However,
> it is not clear how usable it will be in its current form for wireless devices
> (more specifically wireless devices used mainly in cellular networks) having a
> SIP UA. For those kind of devices it is anyway essential to be able to
> configure a number of parameters related to various applications, e.g. MMS or
> e-mail. I believe there is nothing special about SIP-related parameters in
> this respect. So, rather than using a mechanism targeted specifically for SIP,
> it makes more sense to use a generic "device management" technology to take
> care of all applications.
> 
> The prevailing technology for this, at least in GSM/GPRS/WCDMA space is - SMS
> - which is obviously very limited. This is currently being superseded by
> SyncML-based device management technology standardized by the Open Mobile
> Alliance, OMA. This clearly diminishes the need for a separate SIP mechanism.
> (Note that so far e.g. 3GPP has not made any decision whether to follow
> sipping-config-framework or SyncML when configuring service parameters for IMS
> SIP UAs. It is as well possible that they will not specify anything on this
> for Release 6, which comes out next year.)
> 
> There may be, however, some synergies between sipping-config-framework and how
> SyncML device menagement needs to evolve. SyncML DM currently relies on WAP
> push technology to deliver notifications to devices, and uses MSISDN numbers
> to address them (this may sound bad, but the advantage is that it works even
> when the device is not connected to IP network). In the future when a large
> number of cellular devices have SIP and constant IP connectivity, it may
> actually make sense to replace the _notification part_ with SIP. This would
> conceptually fit in the sipping-config-framework, only it is not clear whether
> SUBSCRIBE-NOTIFY is actually the best (or at leat the only) solution.
> 
> We are going to take a look on the requirements from SyncML point of view, and
> after that comment if SIP has any role at all there, and whether a potential
> solution would have commonalities with the sipping-config-framework work done
> in the IETF. The optimal solution would be that there would be at least some
> commonalities how the device gets its configuration in cellular network and
> when it is used e.g. in an enterprise VoIP system with WLAN access.
> 
> Regards,
> Markus    
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 16:56:56 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20057
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 16:56:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDpu-0003Em-OR
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:56:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAILucTo012438
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 16:56:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDpu-0003EX-JB
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 16:56:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20049
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 16:56:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDps-0007iv-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:56:36 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDps-0007is-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 16:56:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDpK-00034M-F8; Tue, 18 Nov 2003 16:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMDoZ-00033L-5S
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 16:55:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19962
	for <sipping@ietf.org>; Tue, 18 Nov 2003 16:55:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDoW-0007gZ-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:55:13 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMDoW-0007fV-00
	for sipping@ietf.org; Tue, 18 Nov 2003 16:55:12 -0500
Received: from cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 18 Nov 2003 13:54:59 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id hAILserX016247;
	Tue, 18 Nov 2003 13:54:40 -0800 (PST)
Received: from [128.107.171.228] ([128.107.171.228])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKB31438;
	Tue, 18 Nov 2003 13:54:38 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Tue, 18 Nov 2003 13:54:38 -0800
Subject: Re: [Sipping] RE: draft-rosenberg-sipping-ice-01 & draft-camarill
	o-mmusic-alt-0 2.tx t
From: Cullen Jennings <fluffy@cisco.com>
To: Francois Audet <audet@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Message-ID: <BBDFD51E.2524A%fluffy@cisco.com>
In-Reply-To: <2F1FC1DEA077D5119FAD00508BCFD6D20BC8D7F6@zsc3c030.us.nortel.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On 10/26/03 9:21 AM, "Francois Audet" <audet@nortelnetworks.com> wrote:

> Good point. Thanks.
> 
> However, reading through STUN carefully, it seems to me that it only
> allows for IPv4 addresses in the STUN messages themselves. For
> example, the MAPPED-ADDRESS only allows for IPv4 addresses at this point.
> Unless of course we extend it. (It currently only has a 0x01 Family
> corresponding to IPv4).
>

Ah yes, very interesting to read STUN. The address family is forced to 1
which represents V4. Of course if this was the only value it could ever
have, then there would be no point in having the field or support for
variable length address at all. If you set the value to v6 family (violating
the RFC) then some implementation seem to happily work with v6. Go figure
:-) 

I would not want to guess why v6 support was not included. 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 18 19:20:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27285
	for <sipping-archive@odin.ietf.org>; Tue, 18 Nov 2003 19:20:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMG4g-0003Nr-MS
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 19:20:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJ0K2lc012996
	for sipping-archive@odin.ietf.org; Tue, 18 Nov 2003 19:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMG4f-0003NI-Sf
	for sipping-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 19:20:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27260
	for <sipping-web-archive@ietf.org>; Tue, 18 Nov 2003 19:19:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMG4e-0003VR-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 19:20:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMG4d-0003VO-00
	for sipping-web-archive@ietf.org; Tue, 18 Nov 2003 19:19:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMG3h-0003Ii-Fu; Tue, 18 Nov 2003 19:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMG3C-0003IQ-RV
	for sipping@optimus.ietf.org; Tue, 18 Nov 2003 19:18:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27245
	for <sipping@ietf.org>; Tue, 18 Nov 2003 19:18:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMG3B-0003UL-00
	for sipping@ietf.org; Tue, 18 Nov 2003 19:18:29 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMG3A-0003Tv-00
	for sipping@ietf.org; Tue, 18 Nov 2003 19:18:28 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hAJ0Hwb9019554
	for <sipping@ietf.org>; Wed, 19 Nov 2003 00:17:58 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHLD33>; Tue, 18 Nov 2003 18:17:59 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56467@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] about SIP-I
Date: Tue, 18 Nov 2003 18:17:54 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


The core point, I think, is that they assume different operating
environments. The Network-to-Network Interface (NNI) approach assumes
essentially a closed network in which only telephone switches exchange =
SIP
messages with one another (just like an SS7/ISUP network). This =
excludes the
User-to-Network Interface (UNI) cases, which ultimately means that the
designers of Q.1912.5 assume that ordinary SIP user agents will not be =
able
to send SIP messages to telephone switches participating in Q.1912.5
networks (the same way that an ordinary black phone is completely =
ignorant
of ISUP).

Here at the IETF, we assumed that the purpose of an RFC3372 gateway is =
to
allow ordinary user agents to hold telephone calls involving the PSTN, =
and
that accordingly an implementation of RFC3372 is a gateway, just a
peripheral that exists on the public Internet, not a "telephone switch" =
that
is part of some private network. We therefore arrived at different =
security
principles (requirements for S/MIME would be one good example), and =
perhaps
some different assumptions about details of the mapping.

I suspect that each of the specifications is complete for its own =
purposes -
they've just chosen different domains of applicability. Personally, I =
think
that any SIP-ISUP architecture that assumes an exclusively NNI =
environment
has more or less missed the point of SIP entirely, or at least has =
chosen an
environment where SIP adds questionable value.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: GARCIN S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.garcin@francetelecom.com]
> Sent: Thursday, November 13, 2003 10:19 AM
> To: Jesske, R; jwalia9@hotmail.com; taylor@nortelnetworks.com;
> christer.holmberg@ericsson.com; sipping@ietf.org; mhammer@cisco.com;
> adam@dynamicsoft.com
> Cc: zhaozf@eastcom.com; aroychow@hns.com
> Subject: RE : [Sipping] about SIP-I
>=20
>=20
> Hi,
>=20
> SIP-T stands a general framework for interworking with ISUP,=20
> this framework considering the use of SIP to carry ISUP as a=20
> MIME body. As tom mentionned, SIP-T also provides some advice=20
> on how mapping and encapsulation should be performed in this case.
>=20
> SIP-I provides in greeter details how encapsulation and=20
> mapping should be performed at an NNI interface. I actually=20
> does deviate to some extent with the advice provided in RFC 3372.=20
>=20
> For example a key difference between SIP-T and SIP-I is that=20
> when de-encapsulating an ISUP message :
> SIP-T sees the encapsulated ISUP as a template that is=20
> overridden by SIP headers=20
> Q.1912.5 specifies what information should be taken from ISUP=20
> body (TMR is an example), and what information taken from the=20
> result of interworking from SIP headers to ISUP parameters.=20
>=20
> Regards
>=20
> s=E9bastien
>=20
>=20
>=20
> -----Message d'origine-----
> De : Jesske, R [mailto:R.Jesske@t-com.net]=20
> Envoy=E9 : jeudi 13 novembre 2003 16:36
> =C0 : jwalia9@hotmail.com; taylor@nortelnetworks.com;=20
> christer.holmberg@ericsson.com; sipping@ietf.org;=20
> mhammer@cisco.com; adam@dynamicsoft.com
> Cc : zhaozf@eastcom.com; aroychow@hns.com
> Objet : AW: [Sipping] about SIP-I
>=20
>=20
> Hi,
> From a telecom operator point of view SIP-I is the solution=20
> that guarantees a carrier grade and trusted connection for=20
> the trunking case. A operator using SIP-I between public=20
> PSTN/ISDN networks will ever stick to the Q.1912.5 solution,=20
> because it is describing the procedures and demands regarding=20
> the Interworking Unit at the network boundary. The philosophy=20
> behind Q.1912.5 is that the SIP interface is seen as an NNI=20
> and not as defined within IETF as an UNI.
>=20
> Best Regards
>=20
> Roland
>=20
> > -----Ursprungliche Nachricht-----
> > Von: J Walia [mailto:jwalia9@hotmail.com]
> > Gesendet: Donnerstag, 13. November 2003 08:39
> > An: taylor@nortelnetworks.com; christer.holmberg@ericsson.com;=20
> > sipping@ietf.org; mhammer@cisco.com; adam@dynamicsoft.com
> > Cc: zhaozf@eastcom.com; aroychow@hns.com
> > Betreff: [Sipping] about SIP-I
> >=20
> >=20
> > Well i had been reading the thread on SIP-I . It was a bit
> > confusing since=20
> > SIP-T and SIP-I seem to do the same thing. From a carrier=20
> > prospective what=20
> > is a better bet when interworking PSTN with Packet based=20
> > network. From Tom's=20
> > reply it seems it seems SIP-T is better but as expalined by=20
> > Christian SIP-I=20
> > seems to take care of what SIP-T RFC do not talk about. Does=20
> > that mean SIP-I=20
> > is more complete and a standardised implemetation comparing=20
> to SIP-T.
> >=20
> > Look forward to your comments
> >=20
> > Regard
> >=20
> > jw
> >=20
> > _________________________________________________________________
> > BharatMatrimony.com.
> > http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74=20
> > India's premium matrimonial website.
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 09:47:58 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18488
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 09:47:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTcL-0006Od-3H
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 09:47:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJElf0N024581
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 09:47:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTcK-0006OO-Vf
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 09:47:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18420
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 09:47:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTcJ-0000K3-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 09:47:39 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTcI-0000K0-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 09:47:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTbj-00066P-C7; Wed, 19 Nov 2003 09:47:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTbb-00064L-Ek
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 09:46:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18390
	for <sipping@ietf.org>; Wed, 19 Nov 2003 09:46:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTbZ-0000Ih-00
	for sipping@ietf.org; Wed, 19 Nov 2003 09:46:53 -0500
Received: from [198.202.216.4] (helo=fullsail.illuminet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTbY-0000Ie-00
	for sipping@ietf.org; Wed, 19 Nov 2003 09:46:52 -0500
Received: from oly1wnexc01.corp.illuminet.com (oly1wnexc01.corp.illuminet.com [10.55.13.12])
	by fullsail.illuminet.com (8.12.10/8.12.10) with ESMTP id hAJEkpLm021125;
	Wed, 19 Nov 2003 06:46:51 -0800 (PST)
Received: by oly1wnexc01.corp.illuminet.com with Internet Mail Service (5.5.2653.19)
	id <W35GMFQ0>; Wed, 19 Nov 2003 06:46:46 -0800
Message-ID: <318266A4431BC549B4C4D6FD3EA6E24D012CED0A@ove1wnexm01.corp.illuminet.com>
From: "McCandless, Kevin" <KMcCandless@verisign.com>
To: "'Richard Shockey'" <richard@shockey.us>
Cc: sipping@ietf.org
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 06:46:39 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Ignorance awakens in the dawn of reality.

SIP needs a formal methodology for obtaining a TCAP query.  Whether the SS7 providers does this with their signaling gateway or not is not the issue.  A formalized approach that a vendor can implement is the point that is being raised.



> -----Original Message-----
> From: Richard Shockey [mailto:richard@shockey.us] 
> Sent: Tuesday, November 18, 2003 3:09 PM
> To: sipping@ietf.org
> Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> 
> At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> 
> As the distributor of the NO TCAP buttons on generous display 
> at IETF 59 
> and fine trade shows nationwide , let me comment that this is 
> one of the 
> silliest ideas I have yet seen cross the SIPPING landscape.
> 
> Why ..why on earth would you want to do this ..any query 
> response mechanism 
> can get you the data points necessary without the baggage 
> TCAP puts you 
> through.
> 
> Talk to your SS7 vendor and demand better service or fire 
> them. Get them to 
> support SIP itself  query response mechanism. Send an INVITE 
> expect a 302 
> MOVE in response and encapsulate SS7 the data as part of a 
> TEL URL in the 
> response.
> 
> This is a "bad idea" tm worthy of the big gong and hook.
> 
> 
> >
> >Aiieee, a cross is raised!!  ;)
> >
> >Anyway, you're right, the format doesn't matter at all, 
> except for one 
> >thing.  Expedience.  The essence of the argument against 
> this type of 
> >draft in general, i.e. one that uses INFO to carry anything, 
> is usually 
> >based on the fact that the content is application specific 
> and so doesn't 
> >fit with the base SIP protocol.  I can understand that and 
> accept it, it 
> >really doesn't matter to me.  I'm an implementor, not a protocol 
> >specifier.  Unfortunately, the protocol doesn't do 
> everything I need it to 
> >do so I have to add stuff to fill in the holes when I take 
> it into the 
> >real world.  The other draft in this area 
> draft-miller-sip-isup-annex is 
> >another example of augmentation, the addition of ISUP 
> maintenance commands 
> >to the ISUP translation now RFC.  I could write/buy an SS7 
> implementation 
> >and template the messages and hook that into my 
> CNAME/LNP/whatever at the 
> >call control layer and to SCTP/UDP/whatever on the network 
> side but why, 
> >to keep the SIP implementation "beautiful"?  The bottom line 
> is I'm not 
> >going to pass the cost of the SS7 stack on to my customers 
> if I can make a 
> >simple addition to the SIP stuff and do exactly the same 
> thing basically 
> >for free.
> >
> >Now with respect to the specifics of the encoding, we can 
> certainly talk 
> >about anything.  That was the whole reason for publishing 
> the work in the 
> >IETF to begin with.  On 6.1.1.1 specifically, this is simply a field 
> >required in the QWP message.  The actual digits are 
> specified in a string 
> >not in BCD binary.  The Signaling 
> Gateway/Softswitch/whatever just picks 
> >up BCD from the Encoding field and fills in the appropriate 
> value in the 
> >actual TCAP binary message when the translation is done.  
> The digits in 
> >the ASCII string are converted similarly to BCD format in 
> the TCAP binary 
> >message also at that time.  The <Encoding  > field doesn't 
> change and is 
> >therefore a perfect candidate for being templated.  The only real 
> >information that needs to be handled per query here is the 
> actual number.
> >
> >FM
> >
> >
> >
> >Frank W. Miller, Ph.D.
> >Chief Technical Officer
> >sentitO Networks, Inc.
> >fmiller@sentito.com
> >
> >-----Original Message-----
> >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> >Sent: Tuesday, November 18, 2003 3:14 PM
> >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> >Subject: RE: [Sip] Sip support for TCAP queries
> >
> >  [Moving this thread to SIPPING, where it belongs]
> >
> >Leaving aside the question of whether or not ENUM supports 
> all of the 
> >functions of TCAP, the main issue is whether or not SIP is 
> the right sort 
> >of protocol to handle this function. A query-response protocol that 
> >carries XML documents from a client to a server? Does SIP 
> INFO really seem 
> >to map onto that well? Aren't there other protocols that are tooled 
> >specifically to that purpose?
> >
> >Furthermore, is the encoding really the issue? XML vs. 
> binary doesn't seem 
> >that significant to me - if a SIP endpoint can template the 
> XML format, it 
> >could template the binary format as well. Regardless of the 
> syntax, should 
> >we expect SIP endpoints to understand the semantics of TCAP? 
> Do we expect 
> >a SIP user agent to understand and implement the concept of, 
> say, a code 
> >gap? That isn't "translation" in any sense that I recognize 
> - it is closer 
> >to saying that SIP user agents have to run a dual stack (SIP 
> and TCAP). 
> >Just look at the <Digits> stanza of the example in 6.1.1.1 
> of the draft: 
> >what sorts of SIP elements are going to understand binary 
> coded decimal, 
> >recognize numbering plans, and the like? If the answer is 
> "only PSTN-SIP 
> >gateways with that already have SS7 links and could 
> therefore just send 
> >TCAP queries over SS7", then I think there is a design issue here.
> >
> >Jon Peterson
> >NeuStar, Inc.
> >-----Original Message-----
> >From: Frank W. Miller [mailto:fmiller@sentito.com]
> >Sent: Tuesday, November 18, 2003 8:50 AM
> >To: 'Chong, Koan S, ALABS'
> >Cc: sip@ietf.org
> >Subject: RE: [Sip] Sip support for TCAP queries
> >
> >The main idea of this draft was to provide a capability for 
> SIP endpoints 
> >to do TCAP queries without having to implement the binary TCAP 
> >protocol.  The motivation is that there are a lot of TCAP 
> queries that 
> >take place (800, LNP, CNAME) that are really simple and that major 
> >carriers may not want to go and reimplement in an ENUM 
> database in the 
> >short term.  These carriers have spent a lot of money on 
> their SCPs and 
> >converting the to ENUM is non-trivial.  Now, the SCPs could 
> be front-ended 
> >and conversion can be automated but this draft provides an 
> >alternative.  So, to answer the first question, the SIP 
> endpoint formats 
> >the correct query in the XML format specified and sends if 
> using an INFO 
> >to a Signaling Gateway (SG).  The SG then converts the query 
> to binary 
> >TCAP and dips the SCP.  The XML format can be templated in the 
> >implementation so the effort is quite minimal on the SIP 
> endpoint.  To 
> >answer the second question, the draft talks about a couple 
> of examples but 
> >the specification encompasses the entire TCAP message set so you can 
> >format the appropriate dip for AR/C.  One caveat is that the 
> draft is 
> >Telcordia based.  It would need to be extended to take into 
> account other 
> >variants.  On the third question, <personal view> I'm a believer in 
> >translation over tunneling, tunneling just puts off work and mixes 
> >messaging from different signaling networks 
> unnecessarily</personal view>.
> >
> >FM
> >
> >
> >
> >Frank W. Miller, Ph.D.
> >Chief Technical Officer
> >sentitO Networks, Inc.
> >fmiller@sentito.com
> >
> >-----Original Message-----
> >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> >Sent: Tuesday, November 18, 2003 11:27 AM
> >To: Frank W. Miller; McCandless, Kevin
> >Cc: sip@ietf.org
> >Subject: RE: [Sip] Sip support for TCAP queries
> >
> >
> >A couple specific questions:
> >
> >What is the recommendation on how a SIP network element can 
> access the 
> >callers' name databases (CNAM in US) in PSTN after the SIP 
> element has 
> >determined that the called parties have subscribed to Caller ID?
> >
> >How about interworking with CLASS Auto-Recall/Callback (CCBS 
> in ITU?) 
> >procedures?
> >
> >Assume TCAP over SIGTRAN is a bit long long term....
> >
> >Koan
> >Koan S.Chong
> >AT&T
> >1-732-420-4557
> >
> >-----Original Message-----
> >From: Frank W. Miller [mailto:fmiller@sentito.com]
> >Sent: Monday, November 17, 2003 6:18 PM
> >To: 'McCandless, Kevin'
> >Cc: sip@ietf.org
> >Subject: RE: [Sip] Sip support for TCAP queries
> >
> >You mean other than us implementing it?  No, I don't think 
> so.  I think 
> >its considered Rosemary's Baby by most...
> >
> >FM
> >
> >
> >Frank W. Miller, Ph.D.
> >Chief Technical Officer
> >sentitO Networks, Inc.
> >fmiller@sentito.com
> >
> >-----Original Message-----
> >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of 
> >McCandless, Kevin
> >Sent: Monday, November 17, 2003 4:11 PM
> >To: sip@ietf.org
> >Subject: [Sip] Sip support for TCAP queries
> >
> >Has any progress been taken on the draft by Frank Miller on 
> Carrying TCAP 
> >in SIP messages?  Are there other drafts that address SIP 
> access to SS7 
> >database information through TCAP or another method?
> >
> >Thanks,
> >
> >Kevin
> 
> 
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Richard Shockey, Senior Manager, Strategic Technology Initiatives
> NeuStar Inc.
> 46000 Center Oak Plaza  -   Sterling, VA  20166
> sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  
> Fax: +1 815.333.1237
> <mailto:richard(at)shockey.us> or 
> <mailto:richard.shockey(at)neustar.biz>
> 
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 10:02:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19241
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 10:02:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTqI-0007H6-Dy
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 10:02:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJF265H027958
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 10:02:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTqI-0007Gr-95
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 10:02:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19189
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 10:01:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTqF-0000Zn-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 10:02:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTqF-0000Zk-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 10:02:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTqD-0007FU-JT; Wed, 19 Nov 2003 10:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMTpy-0007Ew-Ol
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 10:01:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19151
	for <sipping@ietf.org>; Wed, 19 Nov 2003 10:01:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTpw-0000Yf-00
	for sipping@ietf.org; Wed, 19 Nov 2003 10:01:44 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMTpv-0000YM-00
	for sipping@ietf.org; Wed, 19 Nov 2003 10:01:44 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id KAA03171;
	Wed, 19 Nov 2003 10:01:38 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "McCandless, Kevin" <KMcCandless@verisign.com>,
        "'Richard Shockey'" <richard@shockey.us>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 10:01:24 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMGEFFCCAA.asveren@ulticom.com>
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 IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <318266A4431BC549B4C4D6FD3EA6E24D012CED0A@ove1wnexm01.corp.illuminet.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> McCandless, Kevin
> Sent: Wednesday, November 19, 2003 9:47 AM
> To: 'Richard Shockey'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>
>
> Ignorance awakens in the dawn of reality.
>
> SIP needs a formal methodology for obtaining a TCAP query.
> Whether the SS7 providers does this with their signaling gateway
> or not is not the issue.  A formalized approach that a vendor can
> implement is the point that is being raised.
[TOLGA] I fail to see the reason for statement "SIP needs a formal
methodology for obtaining TCAP query." Why? SIP is the protocol to
create/modify sessions. And to do the query, one uses another protocol, TCAP
or something else. Especially if TCAP is going to be used, IMO there is no
need to discuss this in SIP/SIPPING list, it just is a different protocol.
Also for SS7 case, ISUP is used for call control and TCAP for queries. With
the same logic, one should be asking ISUP to be enhanced to support queries.
>
>
>
> > -----Original Message-----
> > From: Richard Shockey [mailto:richard@shockey.us]
> > Sent: Tuesday, November 18, 2003 3:09 PM
> > To: sipping@ietf.org
> > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> >
> >
> > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> >
> > As the distributor of the NO TCAP buttons on generous display
> > at IETF 59
> > and fine trade shows nationwide , let me comment that this is
> > one of the
> > silliest ideas I have yet seen cross the SIPPING landscape.
> >
> > Why ..why on earth would you want to do this ..any query
> > response mechanism
> > can get you the data points necessary without the baggage
> > TCAP puts you
> > through.
> >
> > Talk to your SS7 vendor and demand better service or fire
> > them. Get them to
> > support SIP itself  query response mechanism. Send an INVITE
> > expect a 302
> > MOVE in response and encapsulate SS7 the data as part of a
> > TEL URL in the
> > response.
> >
> > This is a "bad idea" tm worthy of the big gong and hook.
> >
> >
> > >
> > >Aiieee, a cross is raised!!  ;)
> > >
> > >Anyway, you're right, the format doesn't matter at all,
> > except for one
> > >thing.  Expedience.  The essence of the argument against
> > this type of
> > >draft in general, i.e. one that uses INFO to carry anything,
> > is usually
> > >based on the fact that the content is application specific
> > and so doesn't
> > >fit with the base SIP protocol.  I can understand that and
> > accept it, it
> > >really doesn't matter to me.  I'm an implementor, not a protocol
> > >specifier.  Unfortunately, the protocol doesn't do
> > everything I need it to
> > >do so I have to add stuff to fill in the holes when I take
> > it into the
> > >real world.  The other draft in this area
> > draft-miller-sip-isup-annex is
> > >another example of augmentation, the addition of ISUP
> > maintenance commands
> > >to the ISUP translation now RFC.  I could write/buy an SS7
> > implementation
> > >and template the messages and hook that into my
> > CNAME/LNP/whatever at the
> > >call control layer and to SCTP/UDP/whatever on the network
> > side but why,
> > >to keep the SIP implementation "beautiful"?  The bottom line
> > is I'm not
> > >going to pass the cost of the SS7 stack on to my customers
> > if I can make a
> > >simple addition to the SIP stuff and do exactly the same
> > thing basically
> > >for free.
> > >
> > >Now with respect to the specifics of the encoding, we can
> > certainly talk
> > >about anything.  That was the whole reason for publishing
> > the work in the
> > >IETF to begin with.  On 6.1.1.1 specifically, this is simply a field
> > >required in the QWP message.  The actual digits are
> > specified in a string
> > >not in BCD binary.  The Signaling
> > Gateway/Softswitch/whatever just picks
> > >up BCD from the Encoding field and fills in the appropriate
> > value in the
> > >actual TCAP binary message when the translation is done.
> > The digits in
> > >the ASCII string are converted similarly to BCD format in
> > the TCAP binary
> > >message also at that time.  The <Encoding  > field doesn't
> > change and is
> > >therefore a perfect candidate for being templated.  The only real
> > >information that needs to be handled per query here is the
> > actual number.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > >Sent: Tuesday, November 18, 2003 3:14 PM
> > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >  [Moving this thread to SIPPING, where it belongs]
> > >
> > >Leaving aside the question of whether or not ENUM supports
> > all of the
> > >functions of TCAP, the main issue is whether or not SIP is
> > the right sort
> > >of protocol to handle this function. A query-response protocol that
> > >carries XML documents from a client to a server? Does SIP
> > INFO really seem
> > >to map onto that well? Aren't there other protocols that are tooled
> > >specifically to that purpose?
> > >
> > >Furthermore, is the encoding really the issue? XML vs.
> > binary doesn't seem
> > >that significant to me - if a SIP endpoint can template the
> > XML format, it
> > >could template the binary format as well. Regardless of the
> > syntax, should
> > >we expect SIP endpoints to understand the semantics of TCAP?
> > Do we expect
> > >a SIP user agent to understand and implement the concept of,
> > say, a code
> > >gap? That isn't "translation" in any sense that I recognize
> > - it is closer
> > >to saying that SIP user agents have to run a dual stack (SIP
> > and TCAP).
> > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > of the draft:
> > >what sorts of SIP elements are going to understand binary
> > coded decimal,
> > >recognize numbering plans, and the like? If the answer is
> > "only PSTN-SIP
> > >gateways with that already have SS7 links and could
> > therefore just send
> > >TCAP queries over SS7", then I think there is a design issue here.
> > >
> > >Jon Peterson
> > >NeuStar, Inc.
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Tuesday, November 18, 2003 8:50 AM
> > >To: 'Chong, Koan S, ALABS'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >The main idea of this draft was to provide a capability for
> > SIP endpoints
> > >to do TCAP queries without having to implement the binary TCAP
> > >protocol.  The motivation is that there are a lot of TCAP
> > queries that
> > >take place (800, LNP, CNAME) that are really simple and that major
> > >carriers may not want to go and reimplement in an ENUM
> > database in the
> > >short term.  These carriers have spent a lot of money on
> > their SCPs and
> > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > be front-ended
> > >and conversion can be automated but this draft provides an
> > >alternative.  So, to answer the first question, the SIP
> > endpoint formats
> > >the correct query in the XML format specified and sends if
> > using an INFO
> > >to a Signaling Gateway (SG).  The SG then converts the query
> > to binary
> > >TCAP and dips the SCP.  The XML format can be templated in the
> > >implementation so the effort is quite minimal on the SIP
> > endpoint.  To
> > >answer the second question, the draft talks about a couple
> > of examples but
> > >the specification encompasses the entire TCAP message set so you can
> > >format the appropriate dip for AR/C.  One caveat is that the
> > draft is
> > >Telcordia based.  It would need to be extended to take into
> > account other
> > >variants.  On the third question, <personal view> I'm a believer in
> > >translation over tunneling, tunneling just puts off work and mixes
> > >messaging from different signaling networks
> > unnecessarily</personal view>.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > >Sent: Tuesday, November 18, 2003 11:27 AM
> > >To: Frank W. Miller; McCandless, Kevin
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > >A couple specific questions:
> > >
> > >What is the recommendation on how a SIP network element can
> > access the
> > >callers' name databases (CNAM in US) in PSTN after the SIP
> > element has
> > >determined that the called parties have subscribed to Caller ID?
> > >
> > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > in ITU?)
> > >procedures?
> > >
> > >Assume TCAP over SIGTRAN is a bit long long term....
> > >
> > >Koan
> > >Koan S.Chong
> > >AT&T
> > >1-732-420-4557
> > >
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Monday, November 17, 2003 6:18 PM
> > >To: 'McCandless, Kevin'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >You mean other than us implementing it?  No, I don't think
> > so.  I think
> > >its considered Rosemary's Baby by most...
> > >
> > >FM
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
> > >McCandless, Kevin
> > >Sent: Monday, November 17, 2003 4:11 PM
> > >To: sip@ietf.org
> > >Subject: [Sip] Sip support for TCAP queries
> > >
> > >Has any progress been taken on the draft by Frank Miller on
> > Carrying TCAP
> > >in SIP messages?  Are there other drafts that address SIP
> > access to SS7
> > >database information through TCAP or another method?
> > >
> > >Thanks,
> > >
> > >Kevin
> >
> >
> >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > NeuStar Inc.
> > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > Fax: +1 815.333.1237
> > <mailto:richard(at)shockey.us> or
> > <mailto:richard.shockey(at)neustar.biz>
> >
> <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 11:15:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23738
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 11:15:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMUz0-0003sO-Ll
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 11:15:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJGFA0A014896
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 11:15:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMUz0-0003sB-II
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 11:15:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23646
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 11:14:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMUyz-0001w9-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 11:15:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMUyz-0001w6-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 11:15:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMUys-0003qz-HR; Wed, 19 Nov 2003 11:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMUyS-0003qQ-C7
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 11:14:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23608
	for <sipping@ietf.org>; Wed, 19 Nov 2003 11:14:23 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMUyR-0001vg-00
	for sipping@ietf.org; Wed, 19 Nov 2003 11:14:35 -0500
Received: from imo-d06.mx.aol.com ([205.188.157.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMUyQ-0001vH-00
	for sipping@ietf.org; Wed, 19 Nov 2003 11:14:35 -0500
Received: from Mpierce1@aol.com
	by imo-d06.mx.aol.com (mail_out_v36_r1.1.) id u.124.27f04014 (4116);
	Wed, 19 Nov 2003 11:13:27 -0500 (EST)
Message-ID: <124.27f04014.2cecf0a6@aol.com>
Date: Wed, 19 Nov 2003 11:13:26 EST
Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
To: asveren@ulticom.com, KMcCandless@verisign.com, richard@shockey.us
CC: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_124.27f04014.2cecf0a6_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


--part1_124.27f04014.2cecf0a6_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/19/2003 10:03:49 AM Eastern Standard Time, 
asveren@ulticom.com writes:


> [TOLGA] I fail to see the reason for statement "SIP needs a formal
> methodology for obtaining TCAP query." Why? SIP is the protocol to
> create/modify sessions. And to do the query, one uses another protocol, TCAP
> or something else. Especially if TCAP is going to be used, IMO there is no
> need to discuss this in SIP/SIPPING list, it just is a different protocol.
> Also for SS7 case, ISUP is used for call control and TCAP for queries. With
> the same logic, one should be asking ISUP to be enhanced to support queries.
> 

I agree completely. SIP and TCAP are two completely separate things.

Besides, I could not see the original point that an endpoint (someone's 
telephone) needs to initiate TCAP queries. I don't think that anyone operating the 
entity at the other end of such a TCAP query would ever agree to such a thing.

Mike Pierce



--part1_124.27f04014.2cecf0a6_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2>In a message dated 11/19/=
2003 10:03:49 AM Eastern Standard Time, asveren@ulticom.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">[TOLGA] I fail to see the r=
eason for statement "SIP needs a formal
<BR>methodology for obtaining TCAP query." Why? SIP is the protocol to
<BR>create/modify sessions. And to do the query, one uses another protocol,=20=
TCAP
<BR>or something else. Especially if TCAP is going to be used, IMO there is=20=
no
<BR>need to discuss this in SIP/SIPPING list, it just is a different protoco=
l.
<BR>Also for SS7 case, ISUP is used for call control and TCAP for queries. W=
ith
<BR>the same logic, one should be asking ISUP to be enhanced to support quer=
ies.
<BR></FONT><FONT  COLOR=3D"#000000" SIZE=3D3 FAMILY=3D"SANSSERIF" FACE=3D"Ar=
ial" LANG=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Ar=
ial" LANG=3D"0">
<BR>I agree completely. SIP and TCAP are two completely separate things.
<BR>
<BR>Besides, I could not see the original point that an endpoint (someone's=20=
telephone) needs to initiate TCAP queries. I don't think that anyone operati=
ng the entity at the other end of such a TCAP query would ever agree to such=
 a thing.
<BR>
<BR>Mike Pierce
<BR>
<BR></FONT></HTML>

--part1_124.27f04014.2cecf0a6_boundary--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 13:25:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01383
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 13:25:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX0p-0005sb-Vv
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 13:25:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJIPBeq022597
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 13:25:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX0p-0005sO-SI
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 13:25:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01366
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 13:24:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX0n-0005sd-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 13:25:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX0n-0005sX-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 13:25:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX0h-0005r9-47; Wed, 19 Nov 2003 13:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX0I-0005py-4Y
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 13:24:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01359
	for <sipping@ietf.org>; Wed, 19 Nov 2003 13:24:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX0G-0005rv-00
	for sipping@ietf.org; Wed, 19 Nov 2003 13:24:36 -0500
Received: from clarepost.cgu.edu ([134.173.237.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX0F-0005qm-00
	for sipping@ietf.org; Wed, 19 Nov 2003 13:24:35 -0500
Received: by clarepost.cgu.edu with Internet Mail Service (5.5.2657.72)
	id <WKZ5SAR7>; Wed, 19 Nov 2003 10:32:30 -0800
Message-ID: <9C6FE1166FC14444811E7AB3B1B6D7E5A3545A@clarepost.cgu.edu>
From: Samir Chatterjee <samir.chatterjee@cgu.edu>
To: sipping@ietf.org
Date: Wed, 19 Nov 2003 10:32:29 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3AECB.7D307E30"
Subject: [Sipping] SIMPLE vs XMPP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3AECB.7D307E30
Content-Type: text/plain

Is anyone aware of a comparison made between SIMPLE and XMPP for instant
messaging/presence services?

Samir

 

Dr. Samir Chatterjee

School of Information Science

Claremont Graduate University

130 East 9th Street

Claremont, CA 91711

 


------_=_NextPart_001_01C3AECB.7D307E30
Content-Type: text/html

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is anyone aware of a comparison made between SIMPLE and XMPP
for instant messaging/presence services?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Samir</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Dr. Samir Chatterjee</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
  font-family:Arial'>School</span></font><font size=2 face=Arial><span
 style='font-size:10.0pt;font-family:Arial'> of </span></font><font size=2
  face=Arial><span style='font-size:10.0pt;font-family:Arial'>Information
  Science</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
  font-family:Arial'>Claremont</span></font><font size=2 face=Arial><span
 style='font-size:10.0pt;font-family:Arial'> </span></font><font size=2
  face=Arial><span style='font-size:10.0pt;font-family:Arial'>Graduate</span></font><font
 size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> </span></font><font
  size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>University</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
  font-family:Arial'>130 East 9th Street</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
  font-family:Arial'>Claremont</span></font><font size=2 face=Arial><span
 style='font-size:10.0pt;font-family:Arial'>, </span></font><font size=2
  face=Arial><span style='font-size:10.0pt;font-family:Arial'>CA</span></font><font
 size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> </span></font><font
  size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>91711</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C3AECB.7D307E30--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 13:33:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01824
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 13:33:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX8U-0006ag-C0
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 13:33:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJIX66H025328
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 13:33:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX8U-0006aR-7X
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 13:33:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01791
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 13:32:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX8O-00068i-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 13:33:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX8O-00068f-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 13:33:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX8P-0006Wt-36; Wed, 19 Nov 2003 13:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMX7g-0006WK-Ck
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 13:32:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01759
	for <sipping@ietf.org>; Wed, 19 Nov 2003 13:32:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX7e-00067C-00
	for sipping@ietf.org; Wed, 19 Nov 2003 13:32:14 -0500
Received: from jalapeno.cc.columbia.edu ([128.59.59.238] ident=cu41754)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMX7d-000679-00
	for sipping@ietf.org; Wed, 19 Nov 2003 13:32:13 -0500
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	(user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.12.10/8.12.10) with ESMTP id hAJIVt9U006032
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 19 Nov 2003 13:31:55 -0500 (EST)
Message-ID: <3FBBB71B.70603@cs.columbia.edu>
Date: Wed, 19 Nov 2003 13:31:55 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Samir Chatterjee <samir.chatterjee@cgu.edu>
CC: sipping@ietf.org
Subject: Re: [Sipping] SIMPLE vs XMPP
References: <9C6FE1166FC14444811E7AB3B1B6D7E5A3545A@clarepost.cgu.edu>
In-Reply-To: <9C6FE1166FC14444811E7AB3B1B6D7E5A3545A@clarepost.cgu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.35
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Great - all the people who are well-rested from writing comparisons 
between H.323 and SIP can now step forward and again talk about vague 
generalities like scaling, formats and security :-) Given how 
enlightening the comparisons were last time, I'm sure we'll enjoy the 
repeat performance :-)

[Disclaimer: I contributed to one of those earlier comparison papers.]

Samir Chatterjee wrote:

> Is anyone aware of a comparison made between SIMPLE and XMPP for instant 
> messaging/presence services?
> 
> Samir
> 
>  
> 
> Dr. Samir Chatterjee
> 
> School of Information Science
> 
> Claremont Graduate University
> 
> 130 East 9th Street
> 
> Claremont, CA 91711
> 
>  
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 14:03:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03782
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 14:03:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXba-0007zS-6g
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:03:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJJ3AiP030708
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:03:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXbY-0007zC-KE
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 14:03:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03768
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 14:02:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXbW-00074r-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:03:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXbV-00074o-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:03:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXbR-0007xz-AS; Wed, 19 Nov 2003 14:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXb6-0007xl-M1
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 14:02:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03762
	for <sipping@ietf.org>; Wed, 19 Nov 2003 14:02:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXb4-00074k-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:02:38 -0500
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXb3-000744-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:02:37 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAJJ13m01563
	for <sipping@ietf.org>; Wed, 19 Nov 2003 13:01:19 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2656.59)
	id <4M3XH459>; Wed, 19 Nov 2003 19:01:01 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EF0F@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'McCandless, Kevin'" <KMcCandless@verisign.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 19:01:00 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I dont see any justification here.

The only sense I can make of the proposal so far is that SIP is used as a means of transporting TCAP from one place to another. It is not a case the protocol being used to make a SIP request, and the TCAP information enhancing that request.

The IETF will not extend SIP so it is just another transport protocol, transaction protocol or whatever. There are other IETF defined solutions in this space.

So while the original author never progressed his original request, in that he never asked for it to become a WG item or proposed that it should go forward as an individual draft (and it died because the author failed to refresh it), it would probably fail to progress (I daren't say never as they will then prove me wrong), the former because the charter of the WG would never be extended to cover it, and the latter at the IESG review stage.

If there is any reason for progressing this, then the proponents need to clearly distinguish a reason for putting it in SIP that relates to SIP as a Session Initiation Protocol.

regards

Keith



> -----Original Message-----
> From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> Sent: 19 November 2003 14:47
> To: 'Richard Shockey'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> 
> Ignorance awakens in the dawn of reality.
> 
> SIP needs a formal methodology for obtaining a TCAP query.  
> Whether the SS7 providers does this with their signaling 
> gateway or not is not the issue.  A formalized approach that 
> a vendor can implement is the point that is being raised.
> 
> 
> 
> > -----Original Message-----
> > From: Richard Shockey [mailto:richard@shockey.us] 
> > Sent: Tuesday, November 18, 2003 3:09 PM
> > To: sipping@ietf.org
> > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > 
> > 
> > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > 
> > As the distributor of the NO TCAP buttons on generous display 
> > at IETF 59 
> > and fine trade shows nationwide , let me comment that this is 
> > one of the 
> > silliest ideas I have yet seen cross the SIPPING landscape.
> > 
> > Why ..why on earth would you want to do this ..any query 
> > response mechanism 
> > can get you the data points necessary without the baggage 
> > TCAP puts you 
> > through.
> > 
> > Talk to your SS7 vendor and demand better service or fire 
> > them. Get them to 
> > support SIP itself  query response mechanism. Send an INVITE 
> > expect a 302 
> > MOVE in response and encapsulate SS7 the data as part of a 
> > TEL URL in the 
> > response.
> > 
> > This is a "bad idea" tm worthy of the big gong and hook.
> > 
> > 
> > >
> > >Aiieee, a cross is raised!!  ;)
> > >
> > >Anyway, you're right, the format doesn't matter at all, 
> > except for one 
> > >thing.  Expedience.  The essence of the argument against 
> > this type of 
> > >draft in general, i.e. one that uses INFO to carry anything, 
> > is usually 
> > >based on the fact that the content is application specific 
> > and so doesn't 
> > >fit with the base SIP protocol.  I can understand that and 
> > accept it, it 
> > >really doesn't matter to me.  I'm an implementor, not a protocol 
> > >specifier.  Unfortunately, the protocol doesn't do 
> > everything I need it to 
> > >do so I have to add stuff to fill in the holes when I take 
> > it into the 
> > >real world.  The other draft in this area 
> > draft-miller-sip-isup-annex is 
> > >another example of augmentation, the addition of ISUP 
> > maintenance commands 
> > >to the ISUP translation now RFC.  I could write/buy an SS7 
> > implementation 
> > >and template the messages and hook that into my 
> > CNAME/LNP/whatever at the 
> > >call control layer and to SCTP/UDP/whatever on the network 
> > side but why, 
> > >to keep the SIP implementation "beautiful"?  The bottom line 
> > is I'm not 
> > >going to pass the cost of the SS7 stack on to my customers 
> > if I can make a 
> > >simple addition to the SIP stuff and do exactly the same 
> > thing basically 
> > >for free.
> > >
> > >Now with respect to the specifics of the encoding, we can 
> > certainly talk 
> > >about anything.  That was the whole reason for publishing 
> > the work in the 
> > >IETF to begin with.  On 6.1.1.1 specifically, this is 
> simply a field 
> > >required in the QWP message.  The actual digits are 
> > specified in a string 
> > >not in BCD binary.  The Signaling 
> > Gateway/Softswitch/whatever just picks 
> > >up BCD from the Encoding field and fills in the appropriate 
> > value in the 
> > >actual TCAP binary message when the translation is done.  
> > The digits in 
> > >the ASCII string are converted similarly to BCD format in 
> > the TCAP binary 
> > >message also at that time.  The <Encoding  > field doesn't 
> > change and is 
> > >therefore a perfect candidate for being templated.  The only real 
> > >information that needs to be handled per query here is the 
> > actual number.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > >Sent: Tuesday, November 18, 2003 3:14 PM
> > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >  [Moving this thread to SIPPING, where it belongs]
> > >
> > >Leaving aside the question of whether or not ENUM supports 
> > all of the 
> > >functions of TCAP, the main issue is whether or not SIP is 
> > the right sort 
> > >of protocol to handle this function. A query-response 
> protocol that 
> > >carries XML documents from a client to a server? Does SIP 
> > INFO really seem 
> > >to map onto that well? Aren't there other protocols that 
> are tooled 
> > >specifically to that purpose?
> > >
> > >Furthermore, is the encoding really the issue? XML vs. 
> > binary doesn't seem 
> > >that significant to me - if a SIP endpoint can template the 
> > XML format, it 
> > >could template the binary format as well. Regardless of the 
> > syntax, should 
> > >we expect SIP endpoints to understand the semantics of TCAP? 
> > Do we expect 
> > >a SIP user agent to understand and implement the concept of, 
> > say, a code 
> > >gap? That isn't "translation" in any sense that I recognize 
> > - it is closer 
> > >to saying that SIP user agents have to run a dual stack (SIP 
> > and TCAP). 
> > >Just look at the <Digits> stanza of the example in 6.1.1.1 
> > of the draft: 
> > >what sorts of SIP elements are going to understand binary 
> > coded decimal, 
> > >recognize numbering plans, and the like? If the answer is 
> > "only PSTN-SIP 
> > >gateways with that already have SS7 links and could 
> > therefore just send 
> > >TCAP queries over SS7", then I think there is a design issue here.
> > >
> > >Jon Peterson
> > >NeuStar, Inc.
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Tuesday, November 18, 2003 8:50 AM
> > >To: 'Chong, Koan S, ALABS'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >The main idea of this draft was to provide a capability for 
> > SIP endpoints 
> > >to do TCAP queries without having to implement the binary TCAP 
> > >protocol.  The motivation is that there are a lot of TCAP 
> > queries that 
> > >take place (800, LNP, CNAME) that are really simple and that major 
> > >carriers may not want to go and reimplement in an ENUM 
> > database in the 
> > >short term.  These carriers have spent a lot of money on 
> > their SCPs and 
> > >converting the to ENUM is non-trivial.  Now, the SCPs could 
> > be front-ended 
> > >and conversion can be automated but this draft provides an 
> > >alternative.  So, to answer the first question, the SIP 
> > endpoint formats 
> > >the correct query in the XML format specified and sends if 
> > using an INFO 
> > >to a Signaling Gateway (SG).  The SG then converts the query 
> > to binary 
> > >TCAP and dips the SCP.  The XML format can be templated in the 
> > >implementation so the effort is quite minimal on the SIP 
> > endpoint.  To 
> > >answer the second question, the draft talks about a couple 
> > of examples but 
> > >the specification encompasses the entire TCAP message set 
> so you can 
> > >format the appropriate dip for AR/C.  One caveat is that the 
> > draft is 
> > >Telcordia based.  It would need to be extended to take into 
> > account other 
> > >variants.  On the third question, <personal view> I'm a 
> believer in 
> > >translation over tunneling, tunneling just puts off work and mixes 
> > >messaging from different signaling networks 
> > unnecessarily</personal view>.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > >Sent: Tuesday, November 18, 2003 11:27 AM
> > >To: Frank W. Miller; McCandless, Kevin
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > >A couple specific questions:
> > >
> > >What is the recommendation on how a SIP network element can 
> > access the 
> > >callers' name databases (CNAM in US) in PSTN after the SIP 
> > element has 
> > >determined that the called parties have subscribed to Caller ID?
> > >
> > >How about interworking with CLASS Auto-Recall/Callback (CCBS 
> > in ITU?) 
> > >procedures?
> > >
> > >Assume TCAP over SIGTRAN is a bit long long term....
> > >
> > >Koan
> > >Koan S.Chong
> > >AT&T
> > >1-732-420-4557
> > >
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Monday, November 17, 2003 6:18 PM
> > >To: 'McCandless, Kevin'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >You mean other than us implementing it?  No, I don't think 
> > so.  I think 
> > >its considered Rosemary's Baby by most...
> > >
> > >FM
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of 
> > >McCandless, Kevin
> > >Sent: Monday, November 17, 2003 4:11 PM
> > >To: sip@ietf.org
> > >Subject: [Sip] Sip support for TCAP queries
> > >
> > >Has any progress been taken on the draft by Frank Miller on 
> > Carrying TCAP 
> > >in SIP messages?  Are there other drafts that address SIP 
> > access to SS7 
> > >database information through TCAP or another method?
> > >
> > >Thanks,
> > >
> > >Kevin
> > 
> > 
> >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > NeuStar Inc.
> > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  
> > Fax: +1 815.333.1237
> > <mailto:richard(at)shockey.us> or 
> > <mailto:richard.shockey(at)neustar.biz>
> > 
> <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 14:12:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04403
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 14:12:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXkB-0000CY-OM
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:12:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJJC3gu000768
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:12:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXkB-0000CJ-Ie
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 14:12:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04369
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 14:11:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXk9-0007I2-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:12:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXk8-0007Hz-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:12:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXk9-0000BA-6z; Wed, 19 Nov 2003 14:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMXk3-0000AP-Ug
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 14:11:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04361
	for <sipping@ietf.org>; Wed, 19 Nov 2003 14:11:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXk1-0007Hm-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:11:53 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMXk0-0007Gk-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:11:52 -0500
Received: from stntimc1.va.neustar.com (stntimc1.neustar.com [10.31.13.11])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hAJJBKb9001550;
	Wed, 19 Nov 2003 19:11:21 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <WAAP0N9W>; Wed, 19 Nov 2003 14:11:20 -0500
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56469@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Samir Chatterjee'" <samir.chatterjee@cgu.edu>, sipping@ietf.org
Subject: RE: [Sipping] SIMPLE vs XMPP
Date: Wed, 19 Nov 2003 14:11:19 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3AED0.E9E95740"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3AED0.E9E95740
Content-Type: text/plain;
	charset="ISO-8859-1"

As far as I know, existing comparisons have been written only as propaganda,
so I'm afraid I can't point you to anything useful. If you find one, caveat
emptor - there is some remarkably specious analysis in circulation.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Samir Chatterjee [mailto:samir.chatterjee@cgu.edu]
Sent: Wednesday, November 19, 2003 10:32 AM
To: sipping@ietf.org
Subject: [Sipping] SIMPLE vs XMPP



Is anyone aware of a comparison made between SIMPLE and XMPP for instant
messaging/presence services?

Samir

 

Dr. Samir Chatterjee

School of Information Science

Claremont Graduate University

130 East 9th Street

Claremont, CA 91711

 


------_=_NextPart_001_01C3AED0.E9E95740
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">


<META content="MSHTML 6.00.2800.1226" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=425055318-19112003><FONT face=Arial color=#0000ff size=2>As far 
as I know, existing comparisons have been written only as propaganda, so I'm 
afraid I can't point you to anything useful.&nbsp;If you find one, caveat emptor 
- there is some remarkably specious analysis in circulation.</FONT></SPAN></DIV>
<DIV><SPAN class=425055318-19112003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=425055318-19112003><FONT face=Arial color=#0000ff size=2>Jon 
Peterson</FONT></SPAN></DIV>
<DIV><SPAN class=425055318-19112003><FONT face=Arial color=#0000ff 
size=2>NeuStar, Inc.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Samir Chatterjee 
  [mailto:samir.chatterjee@cgu.edu]<BR><B>Sent:</B> Wednesday, November 19, 2003 
  10:32 AM<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> [Sipping] SIMPLE vs 
  XMPP<BR><BR></FONT></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is anyone aware of a comparison 
  made between SIMPLE and XMPP for instant messaging/presence 
  services?</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Samir</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Dr. Samir 
  Chatterjee</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">School</SPAN></FONT><FONT 
  face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> of 
  </SPAN></FONT><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Information 
  Science</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claremont</SPAN></FONT><FONT 
  face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 
  </SPAN></FONT><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Graduate</SPAN></FONT><FONT 
  face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 
  </SPAN></FONT><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">University</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">130 East 9th 
  Street</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Claremont</SPAN></FONT><FONT 
  face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">, 
  </SPAN></FONT><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">CA</SPAN></FONT><FONT face=Arial 
  size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><FONT 
  face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">91711</SPAN></FONT></P>
  <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
  style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3AED0.E9E95740--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 14:40:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05812
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 14:40:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYBQ-0001wt-39
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:40:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJJeBYq007485
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:40:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYBO-0001we-Ua
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 14:40:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05787
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 14:39:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYBM-0000Jo-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:40:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYBL-0000Jl-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:40:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYBI-0001vX-3u; Wed, 19 Nov 2003 14:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYAl-0001ui-D0
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 14:39:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05757
	for <sipping@ietf.org>; Wed, 19 Nov 2003 14:39:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYAi-0000Iv-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:39:28 -0500
Received: from airwolf.sentito.com ([65.202.222.11])
	by ietf-mx with smtp (Exim 4.12)
	id 1AMYAi-0000IL-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:39:28 -0500
Received: (qmail 38103 invoked from network); 19 Nov 2003 19:40:14 -0000
Received: from unknown (HELO frankgks0u6mmz) (relay@65.202.222.2)
  by airwolf.sentito.com with SMTP; 19 Nov 2003 19:40:14 -0000
From: "Frank W. Miller" <fmiller@sentito.com>
To: "'Drage, Keith \(Keith\)'" <drage@lucent.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 14:38:57 -0500
Message-ID: <004101c3aed4$c5f826a0$9100000a@frankgks0u6mmz>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <475FF955A05DD411980D00508B6D5FB00439EF0F@en0033exch001u.uk.lucent.com>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


With all due respect, the reason I didn't ask to have it considered was =
I
knew that it would never be accepted, so why waste my breath.  My =
purpose
was to solve a problem that needs addressing.

It cannot be ignored that SIP is making major inroads into the big =
carriers
and dealing with ISUP and TCAP in a complete way within the context of =
SIP
is something that needs to happen.  Now, if INFO as transport for XML =
isn't
palatable, whatever.

Let me be very plain, RFC 3398 is not sufficient.  It lacks support for =
ISUP
maintenance commands and access to SCPs via TCAP.  These are functions =
that
are required by vendors and carriers integrating SIP with the existing =
PSTN.

I happen to be associated with one of the vendors addressing these needs =
at
the implementation level.  If the protocol does not serve all my needs, =
I
will extend it.  If you as protocol specifiers don't like the way I =
extend
it then put something else in place that I can use.

Hoping to be constructive,
FM
=20

Frank W. Miller, Ph.D.
Chief Technical Officer
sentitO Networks, Inc.
fmiller@sentito.com


-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf =
Of
Drage, Keith (Keith)
Sent: Wednesday, November 19, 2003 2:01 PM
To: 'McCandless, Kevin'
Cc: sipping@ietf.org
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries

I dont see any justification here.

The only sense I can make of the proposal so far is that SIP is used as =
a
means of transporting TCAP from one place to another. It is not a case =
the
protocol being used to make a SIP request, and the TCAP information
enhancing that request.

The IETF will not extend SIP so it is just another transport protocol,
transaction protocol or whatever. There are other IETF defined solutions =
in
this space.

So while the original author never progressed his original request, in =
that
he never asked for it to become a WG item or proposed that it should go
forward as an individual draft (and it died because the author failed to
refresh it), it would probably fail to progress (I daren't say never as =
they
will then prove me wrong), the former because the charter of the WG =
would
never be extended to cover it, and the latter at the IESG review stage.

If there is any reason for progressing this, then the proponents need to
clearly distinguish a reason for putting it in SIP that relates to SIP =
as a
Session Initiation Protocol.

regards

Keith



> -----Original Message-----
> From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> Sent: 19 November 2003 14:47
> To: 'Richard Shockey'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>=20
>=20
> Ignorance awakens in the dawn of reality.
>=20
> SIP needs a formal methodology for obtaining a TCAP query. =20
> Whether the SS7 providers does this with their signaling=20
> gateway or not is not the issue.  A formalized approach that=20
> a vendor can implement is the point that is being raised.
>=20
>=20
>=20
> > -----Original Message-----
> > From: Richard Shockey [mailto:richard@shockey.us]=20
> > Sent: Tuesday, November 18, 2003 3:09 PM
> > To: sipping@ietf.org
> > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> >=20
> >=20
> > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> >=20
> > As the distributor of the NO TCAP buttons on generous display=20
> > at IETF 59=20
> > and fine trade shows nationwide , let me comment that this is=20
> > one of the=20
> > silliest ideas I have yet seen cross the SIPPING landscape.
> >=20
> > Why ..why on earth would you want to do this ..any query=20
> > response mechanism=20
> > can get you the data points necessary without the baggage=20
> > TCAP puts you=20
> > through.
> >=20
> > Talk to your SS7 vendor and demand better service or fire=20
> > them. Get them to=20
> > support SIP itself  query response mechanism. Send an INVITE=20
> > expect a 302=20
> > MOVE in response and encapsulate SS7 the data as part of a=20
> > TEL URL in the=20
> > response.
> >=20
> > This is a "bad idea" tm worthy of the big gong and hook.
> >=20
> >=20
> > >
> > >Aiieee, a cross is raised!!  ;)
> > >
> > >Anyway, you're right, the format doesn't matter at all,=20
> > except for one=20
> > >thing.  Expedience.  The essence of the argument against=20
> > this type of=20
> > >draft in general, i.e. one that uses INFO to carry anything,=20
> > is usually=20
> > >based on the fact that the content is application specific=20
> > and so doesn't=20
> > >fit with the base SIP protocol.  I can understand that and=20
> > accept it, it=20
> > >really doesn't matter to me.  I'm an implementor, not a protocol=20
> > >specifier.  Unfortunately, the protocol doesn't do=20
> > everything I need it to=20
> > >do so I have to add stuff to fill in the holes when I take=20
> > it into the=20
> > >real world.  The other draft in this area=20
> > draft-miller-sip-isup-annex is=20
> > >another example of augmentation, the addition of ISUP=20
> > maintenance commands=20
> > >to the ISUP translation now RFC.  I could write/buy an SS7=20
> > implementation=20
> > >and template the messages and hook that into my=20
> > CNAME/LNP/whatever at the=20
> > >call control layer and to SCTP/UDP/whatever on the network=20
> > side but why,=20
> > >to keep the SIP implementation "beautiful"?  The bottom line=20
> > is I'm not=20
> > >going to pass the cost of the SS7 stack on to my customers=20
> > if I can make a=20
> > >simple addition to the SIP stuff and do exactly the same=20
> > thing basically=20
> > >for free.
> > >
> > >Now with respect to the specifics of the encoding, we can=20
> > certainly talk=20
> > >about anything.  That was the whole reason for publishing=20
> > the work in the=20
> > >IETF to begin with.  On 6.1.1.1 specifically, this is=20
> simply a field=20
> > >required in the QWP message.  The actual digits are=20
> > specified in a string=20
> > >not in BCD binary.  The Signaling=20
> > Gateway/Softswitch/whatever just picks=20
> > >up BCD from the Encoding field and fills in the appropriate=20
> > value in the=20
> > >actual TCAP binary message when the translation is done. =20
> > The digits in=20
> > >the ASCII string are converted similarly to BCD format in=20
> > the TCAP binary=20
> > >message also at that time.  The <Encoding  > field doesn't=20
> > change and is=20
> > >therefore a perfect candidate for being templated.  The only real=20
> > >information that needs to be handled per query here is the=20
> > actual number.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > >Sent: Tuesday, November 18, 2003 3:14 PM
> > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >  [Moving this thread to SIPPING, where it belongs]
> > >
> > >Leaving aside the question of whether or not ENUM supports=20
> > all of the=20
> > >functions of TCAP, the main issue is whether or not SIP is=20
> > the right sort=20
> > >of protocol to handle this function. A query-response=20
> protocol that=20
> > >carries XML documents from a client to a server? Does SIP=20
> > INFO really seem=20
> > >to map onto that well? Aren't there other protocols that=20
> are tooled=20
> > >specifically to that purpose?
> > >
> > >Furthermore, is the encoding really the issue? XML vs.=20
> > binary doesn't seem=20
> > >that significant to me - if a SIP endpoint can template the=20
> > XML format, it=20
> > >could template the binary format as well. Regardless of the=20
> > syntax, should=20
> > >we expect SIP endpoints to understand the semantics of TCAP?=20
> > Do we expect=20
> > >a SIP user agent to understand and implement the concept of,=20
> > say, a code=20
> > >gap? That isn't "translation" in any sense that I recognize=20
> > - it is closer=20
> > >to saying that SIP user agents have to run a dual stack (SIP=20
> > and TCAP).=20
> > >Just look at the <Digits> stanza of the example in 6.1.1.1=20
> > of the draft:=20
> > >what sorts of SIP elements are going to understand binary=20
> > coded decimal,=20
> > >recognize numbering plans, and the like? If the answer is=20
> > "only PSTN-SIP=20
> > >gateways with that already have SS7 links and could=20
> > therefore just send=20
> > >TCAP queries over SS7", then I think there is a design issue here.
> > >
> > >Jon Peterson
> > >NeuStar, Inc.
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Tuesday, November 18, 2003 8:50 AM
> > >To: 'Chong, Koan S, ALABS'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >The main idea of this draft was to provide a capability for=20
> > SIP endpoints=20
> > >to do TCAP queries without having to implement the binary TCAP=20
> > >protocol.  The motivation is that there are a lot of TCAP=20
> > queries that=20
> > >take place (800, LNP, CNAME) that are really simple and that major=20
> > >carriers may not want to go and reimplement in an ENUM=20
> > database in the=20
> > >short term.  These carriers have spent a lot of money on=20
> > their SCPs and=20
> > >converting the to ENUM is non-trivial.  Now, the SCPs could=20
> > be front-ended=20
> > >and conversion can be automated but this draft provides an=20
> > >alternative.  So, to answer the first question, the SIP=20
> > endpoint formats=20
> > >the correct query in the XML format specified and sends if=20
> > using an INFO=20
> > >to a Signaling Gateway (SG).  The SG then converts the query=20
> > to binary=20
> > >TCAP and dips the SCP.  The XML format can be templated in the=20
> > >implementation so the effort is quite minimal on the SIP=20
> > endpoint.  To=20
> > >answer the second question, the draft talks about a couple=20
> > of examples but=20
> > >the specification encompasses the entire TCAP message set=20
> so you can=20
> > >format the appropriate dip for AR/C.  One caveat is that the=20
> > draft is=20
> > >Telcordia based.  It would need to be extended to take into=20
> > account other=20
> > >variants.  On the third question, <personal view> I'm a=20
> believer in=20
> > >translation over tunneling, tunneling just puts off work and mixes=20
> > >messaging from different signaling networks=20
> > unnecessarily</personal view>.
> > >
> > >FM
> > >
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > >Sent: Tuesday, November 18, 2003 11:27 AM
> > >To: Frank W. Miller; McCandless, Kevin
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > >A couple specific questions:
> > >
> > >What is the recommendation on how a SIP network element can=20
> > access the=20
> > >callers' name databases (CNAM in US) in PSTN after the SIP=20
> > element has=20
> > >determined that the called parties have subscribed to Caller ID?
> > >
> > >How about interworking with CLASS Auto-Recall/Callback (CCBS=20
> > in ITU?)=20
> > >procedures?
> > >
> > >Assume TCAP over SIGTRAN is a bit long long term....
> > >
> > >Koan
> > >Koan S.Chong
> > >AT&T
> > >1-732-420-4557
> > >
> > >-----Original Message-----
> > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > >Sent: Monday, November 17, 2003 6:18 PM
> > >To: 'McCandless, Kevin'
> > >Cc: sip@ietf.org
> > >Subject: RE: [Sip] Sip support for TCAP queries
> > >
> > >You mean other than us implementing it?  No, I don't think=20
> > so.  I think=20
> > >its considered Rosemary's Baby by most...
> > >
> > >FM
> > >
> > >
> > >Frank W. Miller, Ph.D.
> > >Chief Technical Officer
> > >sentitO Networks, Inc.
> > >fmiller@sentito.com
> > >
> > >-----Original Message-----
> > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of=20
> > >McCandless, Kevin
> > >Sent: Monday, November 17, 2003 4:11 PM
> > >To: sip@ietf.org
> > >Subject: [Sip] Sip support for TCAP queries
> > >
> > >Has any progress been taken on the draft by Frank Miller on=20
> > Carrying TCAP=20
> > >in SIP messages?  Are there other drafts that address SIP=20
> > access to SS7=20
> > >database information through TCAP or another method?
> > >
> > >Thanks,
> > >
> > >Kevin
> >=20
> >=20
> >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > NeuStar Inc.
> > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, =20
> > Fax: +1 815.333.1237
> > <mailto:richard(at)shockey.us> or=20
> > <mailto:richard.shockey(at)neustar.biz>
> >=20
> <http://www.neustar.biz> ; <http://www.enum.org>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 14:52:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06292
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 14:52:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYMv-0002gV-Js
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:52:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJJq5H8010313
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 14:52:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYMv-0002gG-Fv
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 14:52:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06265
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 14:51:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYMs-0000cq-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:52:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYMs-0000cn-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 14:52:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYMr-0002f5-97; Wed, 19 Nov 2003 14:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYMF-0002eJ-2i
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 14:51:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06250
	for <sipping@ietf.org>; Wed, 19 Nov 2003 14:51:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYMC-0000bh-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:51:20 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYMB-0000at-00
	for sipping@ietf.org; Wed, 19 Nov 2003 14:51:19 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hAJJokDM017810;
	Wed, 19 Nov 2003 14:50:46 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AUP14697;
	Wed, 19 Nov 2003 11:50:45 -0800 (PST)
Message-Id: <4.3.2.7.2.20031119143000.00b527b0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 19 Nov 2003 14:50:05 -0500
To: "Drage, Keith (Keith)" <drage@lucent.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Cc: "'McCandless, Kevin'" <KMcCandless@verisign.com>, sipping@ietf.org
In-Reply-To: <475FF955A05DD411980D00508B6D5FB00439EF0F@en0033exch001u.uk
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Keith,

This is not to support the current suggestion but to get more clarification 
taking a long-range view of (Internet/PSTN) network(s) evolution.

Two cases in point:
1) TCAP carried registration messages for mobile systems, yet the 
equivalent is now done by SIP REGISTER method, which may eventually 
displace the former TCAP-carried methods.
2) Camp-on indications currently carried by TCAP that translate (partially) 
into SUBSCRIBE/NOTIFY.  Recall the previous request to expand SIP to carry 
some additional CCBS indications.

I see TCAP as being more like the transport protocols that underlies SIP, 
so am not sure that all of that functionality needs to survive (carried 
over) into the IP world.

The question I have is whether the stuff inside of TCAP messages evolves 
from an SS7-world application to an IETF application?

Put another way, if the TCAP and above stuff is migrated to 
TCAP/SUA/SCTP/IP, and the SS7 network as we know it today eventually fades 
away, does that make the TCAP and above stuff Internet protocols?

Mike


At 07:01 PM 11/19/2003 +0000, Drage, Keith (Keith) wrote:
>I dont see any justification here.
>
>The only sense I can make of the proposal so far is that SIP is used as a 
>means of transporting TCAP from one place to another. It is not a case the 
>protocol being used to make a SIP request, and the TCAP information 
>enhancing that request.
>
>The IETF will not extend SIP so it is just another transport protocol, 
>transaction protocol or whatever. There are other IETF defined solutions 
>in this space.
>
>So while the original author never progressed his original request, in 
>that he never asked for it to become a WG item or proposed that it should 
>go forward as an individual draft (and it died because the author failed 
>to refresh it), it would probably fail to progress (I daren't say never as 
>they will then prove me wrong), the former because the charter of the WG 
>would never be extended to cover it, and the latter at the IESG review stage.
>
>If there is any reason for progressing this, then the proponents need to 
>clearly distinguish a reason for putting it in SIP that relates to SIP as 
>a Session Initiation Protocol.
>
>regards
>
>Keith
>
>
>
> > -----Original Message-----
> > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > Sent: 19 November 2003 14:47
> > To: 'Richard Shockey'
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> >
> >
> > Ignorance awakens in the dawn of reality.
> >
> > SIP needs a formal methodology for obtaining a TCAP query.
> > Whether the SS7 providers does this with their signaling
> > gateway or not is not the issue.  A formalized approach that
> > a vendor can implement is the point that is being raised.
> >
> >
> >
> > > -----Original Message-----
> > > From: Richard Shockey [mailto:richard@shockey.us]
> > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > To: sipping@ietf.org
> > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > >
> > > As the distributor of the NO TCAP buttons on generous display
> > > at IETF 59
> > > and fine trade shows nationwide , let me comment that this is
> > > one of the
> > > silliest ideas I have yet seen cross the SIPPING landscape.
> > >
> > > Why ..why on earth would you want to do this ..any query
> > > response mechanism
> > > can get you the data points necessary without the baggage
> > > TCAP puts you
> > > through.
> > >
> > > Talk to your SS7 vendor and demand better service or fire
> > > them. Get them to
> > > support SIP itself  query response mechanism. Send an INVITE
> > > expect a 302
> > > MOVE in response and encapsulate SS7 the data as part of a
> > > TEL URL in the
> > > response.
> > >
> > > This is a "bad idea" tm worthy of the big gong and hook.
> > >
> > >
> > > >
> > > >Aiieee, a cross is raised!!  ;)
> > > >
> > > >Anyway, you're right, the format doesn't matter at all,
> > > except for one
> > > >thing.  Expedience.  The essence of the argument against
> > > this type of
> > > >draft in general, i.e. one that uses INFO to carry anything,
> > > is usually
> > > >based on the fact that the content is application specific
> > > and so doesn't
> > > >fit with the base SIP protocol.  I can understand that and
> > > accept it, it
> > > >really doesn't matter to me.  I'm an implementor, not a protocol
> > > >specifier.  Unfortunately, the protocol doesn't do
> > > everything I need it to
> > > >do so I have to add stuff to fill in the holes when I take
> > > it into the
> > > >real world.  The other draft in this area
> > > draft-miller-sip-isup-annex is
> > > >another example of augmentation, the addition of ISUP
> > > maintenance commands
> > > >to the ISUP translation now RFC.  I could write/buy an SS7
> > > implementation
> > > >and template the messages and hook that into my
> > > CNAME/LNP/whatever at the
> > > >call control layer and to SCTP/UDP/whatever on the network
> > > side but why,
> > > >to keep the SIP implementation "beautiful"?  The bottom line
> > > is I'm not
> > > >going to pass the cost of the SS7 stack on to my customers
> > > if I can make a
> > > >simple addition to the SIP stuff and do exactly the same
> > > thing basically
> > > >for free.
> > > >
> > > >Now with respect to the specifics of the encoding, we can
> > > certainly talk
> > > >about anything.  That was the whole reason for publishing
> > > the work in the
> > > >IETF to begin with.  On 6.1.1.1 specifically, this is
> > simply a field
> > > >required in the QWP message.  The actual digits are
> > > specified in a string
> > > >not in BCD binary.  The Signaling
> > > Gateway/Softswitch/whatever just picks
> > > >up BCD from the Encoding field and fills in the appropriate
> > > value in the
> > > >actual TCAP binary message when the translation is done.
> > > The digits in
> > > >the ASCII string are converted similarly to BCD format in
> > > the TCAP binary
> > > >message also at that time.  The <Encoding  > field doesn't
> > > change and is
> > > >therefore a perfect candidate for being templated.  The only real
> > > >information that needs to be handled per query here is the
> > > actual number.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >  [Moving this thread to SIPPING, where it belongs]
> > > >
> > > >Leaving aside the question of whether or not ENUM supports
> > > all of the
> > > >functions of TCAP, the main issue is whether or not SIP is
> > > the right sort
> > > >of protocol to handle this function. A query-response
> > protocol that
> > > >carries XML documents from a client to a server? Does SIP
> > > INFO really seem
> > > >to map onto that well? Aren't there other protocols that
> > are tooled
> > > >specifically to that purpose?
> > > >
> > > >Furthermore, is the encoding really the issue? XML vs.
> > > binary doesn't seem
> > > >that significant to me - if a SIP endpoint can template the
> > > XML format, it
> > > >could template the binary format as well. Regardless of the
> > > syntax, should
> > > >we expect SIP endpoints to understand the semantics of TCAP?
> > > Do we expect
> > > >a SIP user agent to understand and implement the concept of,
> > > say, a code
> > > >gap? That isn't "translation" in any sense that I recognize
> > > - it is closer
> > > >to saying that SIP user agents have to run a dual stack (SIP
> > > and TCAP).
> > > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > > of the draft:
> > > >what sorts of SIP elements are going to understand binary
> > > coded decimal,
> > > >recognize numbering plans, and the like? If the answer is
> > > "only PSTN-SIP
> > > >gateways with that already have SS7 links and could
> > > therefore just send
> > > >TCAP queries over SS7", then I think there is a design issue here.
> > > >
> > > >Jon Peterson
> > > >NeuStar, Inc.
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > >To: 'Chong, Koan S, ALABS'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >The main idea of this draft was to provide a capability for
> > > SIP endpoints
> > > >to do TCAP queries without having to implement the binary TCAP
> > > >protocol.  The motivation is that there are a lot of TCAP
> > > queries that
> > > >take place (800, LNP, CNAME) that are really simple and that major
> > > >carriers may not want to go and reimplement in an ENUM
> > > database in the
> > > >short term.  These carriers have spent a lot of money on
> > > their SCPs and
> > > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > > be front-ended
> > > >and conversion can be automated but this draft provides an
> > > >alternative.  So, to answer the first question, the SIP
> > > endpoint formats
> > > >the correct query in the XML format specified and sends if
> > > using an INFO
> > > >to a Signaling Gateway (SG).  The SG then converts the query
> > > to binary
> > > >TCAP and dips the SCP.  The XML format can be templated in the
> > > >implementation so the effort is quite minimal on the SIP
> > > endpoint.  To
> > > >answer the second question, the draft talks about a couple
> > > of examples but
> > > >the specification encompasses the entire TCAP message set
> > so you can
> > > >format the appropriate dip for AR/C.  One caveat is that the
> > > draft is
> > > >Telcordia based.  It would need to be extended to take into
> > > account other
> > > >variants.  On the third question, <personal view> I'm a
> > believer in
> > > >translation over tunneling, tunneling just puts off work and mixes
> > > >messaging from different signaling networks
> > > unnecessarily</personal view>.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > >To: Frank W. Miller; McCandless, Kevin
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >
> > > >A couple specific questions:
> > > >
> > > >What is the recommendation on how a SIP network element can
> > > access the
> > > >callers' name databases (CNAM in US) in PSTN after the SIP
> > > element has
> > > >determined that the called parties have subscribed to Caller ID?
> > > >
> > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > > in ITU?)
> > > >procedures?
> > > >
> > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > >
> > > >Koan
> > > >Koan S.Chong
> > > >AT&T
> > > >1-732-420-4557
> > > >
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Monday, November 17, 2003 6:18 PM
> > > >To: 'McCandless, Kevin'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >You mean other than us implementing it?  No, I don't think
> > > so.  I think
> > > >its considered Rosemary's Baby by most...
> > > >
> > > >FM
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
> > > >McCandless, Kevin
> > > >Sent: Monday, November 17, 2003 4:11 PM
> > > >To: sip@ietf.org
> > > >Subject: [Sip] Sip support for TCAP queries
> > > >
> > > >Has any progress been taken on the draft by Frank Miller on
> > > Carrying TCAP
> > > >in SIP messages?  Are there other drafts that address SIP
> > > access to SS7
> > > >database information through TCAP or another method?
> > > >
> > > >Thanks,
> > > >
> > > >Kevin
> > >
> > >
> > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > > NeuStar Inc.
> > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > > Fax: +1 815.333.1237
> > > <mailto:richard(at)shockey.us> or
> > > <mailto:richard.shockey(at)neustar.biz>
> > >
> > <http://www.neustar.biz> ; <http://www.enum.org>
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 15:17:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08660
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 15:17:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYlA-000499-UO
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:17:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKH8DA015933
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:17:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYlA-00048u-QQ
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 15:17:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08607
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 15:16:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYl9-0001LU-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:17:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYl8-0001LB-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:17:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYl3-00047n-IW; Wed, 19 Nov 2003 15:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYk9-00042j-W0
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 15:16:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08500
	for <sipping@ietf.org>; Wed, 19 Nov 2003 15:15:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYk8-0001Hy-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:16:04 -0500
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYk7-0001HS-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:16:03 -0500
Received: from zcard307.ca.nortel.com (americasm03.nt.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAJKFVJ12230;
	Wed, 19 Nov 2003 15:15:31 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XCDCP70P; Wed, 19 Nov 2003 15:15:31 -0500
Received: from nortelnetworks.com (acart1c0.ca.nortel.com [47.129.129.43]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5N359; Wed, 19 Nov 2003 15:15:30 -0500
Message-ID: <3FBBCF61.6040508@nortelnetworks.com>
Date: Wed, 19 Nov 2003 15:15:29 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Frank W. Miller" <fmiller@sentito.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
References: <004101c3aed4$c5f826a0$9100000a@frankgks0u6mmz>
In-Reply-To: <004101c3aed4$c5f826a0$9100000a@frankgks0u6mmz>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Let me ask: why do you need support for ISUP maintenance messages?  Are 
you using SIP to control circuits?

Frank W. Miller wrote:

> With all due respect, the reason I didn't ask to have it considered was I
> knew that it would never be accepted, so why waste my breath.  My purpose
> was to solve a problem that needs addressing.
> 
> It cannot be ignored that SIP is making major inroads into the big carriers
> and dealing with ISUP and TCAP in a complete way within the context of SIP
> is something that needs to happen.  Now, if INFO as transport for XML isn't
> palatable, whatever.
> 
> Let me be very plain, RFC 3398 is not sufficient.  It lacks support for ISUP
> maintenance commands and access to SCPs via TCAP.  These are functions that
> are required by vendors and carriers integrating SIP with the existing PSTN.
> 
> I happen to be associated with one of the vendors addressing these needs at
> the implementation level.  If the protocol does not serve all my needs, I
> will extend it.  If you as protocol specifiers don't like the way I extend
> it then put something else in place that I can use.
> 
> Hoping to be constructive,
> FM
>  
> 
> Frank W. Miller, Ph.D.
> Chief Technical Officer
> sentitO Networks, Inc.
> fmiller@sentito.com
> 
> 
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf Of
> Drage, Keith (Keith)
> Sent: Wednesday, November 19, 2003 2:01 PM
> To: 'McCandless, Kevin'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> I dont see any justification here.
> 
> The only sense I can make of the proposal so far is that SIP is used as a
> means of transporting TCAP from one place to another. It is not a case the
> protocol being used to make a SIP request, and the TCAP information
> enhancing that request.
> 
> The IETF will not extend SIP so it is just another transport protocol,
> transaction protocol or whatever. There are other IETF defined solutions in
> this space.
> 
> So while the original author never progressed his original request, in that
> he never asked for it to become a WG item or proposed that it should go
> forward as an individual draft (and it died because the author failed to
> refresh it), it would probably fail to progress (I daren't say never as they
> will then prove me wrong), the former because the charter of the WG would
> never be extended to cover it, and the latter at the IESG review stage.
> 
> If there is any reason for progressing this, then the proponents need to
> clearly distinguish a reason for putting it in SIP that relates to SIP as a
> Session Initiation Protocol.
> 
> regards
> 
> Keith
> 
> 
> 
> 
>>-----Original Message-----
>>From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
>>Sent: 19 November 2003 14:47
>>To: 'Richard Shockey'
>>Cc: sipping@ietf.org
>>Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>>
>>
>>Ignorance awakens in the dawn of reality.
>>
>>SIP needs a formal methodology for obtaining a TCAP query.  
>>Whether the SS7 providers does this with their signaling 
>>gateway or not is not the issue.  A formalized approach that 
>>a vendor can implement is the point that is being raised.
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: Richard Shockey [mailto:richard@shockey.us] 
>>>Sent: Tuesday, November 18, 2003 3:09 PM
>>>To: sipping@ietf.org
>>>Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
>>>
>>>
>>>At 03:50 PM 11/18/2003, Frank W. Miller wrote:
>>>
>>>As the distributor of the NO TCAP buttons on generous display 
>>>at IETF 59 
>>>and fine trade shows nationwide , let me comment that this is 
>>>one of the 
>>>silliest ideas I have yet seen cross the SIPPING landscape.
>>>
>>>Why ..why on earth would you want to do this ..any query 
>>>response mechanism 
>>>can get you the data points necessary without the baggage 
>>>TCAP puts you 
>>>through.
>>>
>>>Talk to your SS7 vendor and demand better service or fire 
>>>them. Get them to 
>>>support SIP itself  query response mechanism. Send an INVITE 
>>>expect a 302 
>>>MOVE in response and encapsulate SS7 the data as part of a 
>>>TEL URL in the 
>>>response.
>>>
>>>This is a "bad idea" tm worthy of the big gong and hook.
>>>
>>>
>>>
>>>>Aiieee, a cross is raised!!  ;)
>>>>
>>>>Anyway, you're right, the format doesn't matter at all, 
>>>
>>>except for one 
>>>
>>>>thing.  Expedience.  The essence of the argument against 
>>>
>>>this type of 
>>>
>>>>draft in general, i.e. one that uses INFO to carry anything, 
>>>
>>>is usually 
>>>
>>>>based on the fact that the content is application specific 
>>>
>>>and so doesn't 
>>>
>>>>fit with the base SIP protocol.  I can understand that and 
>>>
>>>accept it, it 
>>>
>>>>really doesn't matter to me.  I'm an implementor, not a protocol 
>>>>specifier.  Unfortunately, the protocol doesn't do 
>>>
>>>everything I need it to 
>>>
>>>>do so I have to add stuff to fill in the holes when I take 
>>>
>>>it into the 
>>>
>>>>real world.  The other draft in this area 
>>>
>>>draft-miller-sip-isup-annex is 
>>>
>>>>another example of augmentation, the addition of ISUP 
>>>
>>>maintenance commands 
>>>
>>>>to the ISUP translation now RFC.  I could write/buy an SS7 
>>>
>>>implementation 
>>>
>>>>and template the messages and hook that into my 
>>>
>>>CNAME/LNP/whatever at the 
>>>
>>>>call control layer and to SCTP/UDP/whatever on the network 
>>>
>>>side but why, 
>>>
>>>>to keep the SIP implementation "beautiful"?  The bottom line 
>>>
>>>is I'm not 
>>>
>>>>going to pass the cost of the SS7 stack on to my customers 
>>>
>>>if I can make a 
>>>
>>>>simple addition to the SIP stuff and do exactly the same 
>>>
>>>thing basically 
>>>
>>>>for free.
>>>>
>>>>Now with respect to the specifics of the encoding, we can 
>>>
>>>certainly talk 
>>>
>>>>about anything.  That was the whole reason for publishing 
>>>
>>>the work in the 
>>>
>>>>IETF to begin with.  On 6.1.1.1 specifically, this is 
>>
>>simply a field 
>>
>>>>required in the QWP message.  The actual digits are 
>>>
>>>specified in a string 
>>>
>>>>not in BCD binary.  The Signaling 
>>>
>>>Gateway/Softswitch/whatever just picks 
>>>
>>>>up BCD from the Encoding field and fills in the appropriate 
>>>
>>>value in the 
>>>
>>>>actual TCAP binary message when the translation is done.  
>>>
>>>The digits in 
>>>
>>>>the ASCII string are converted similarly to BCD format in 
>>>
>>>the TCAP binary 
>>>
>>>>message also at that time.  The <Encoding  > field doesn't 
>>>
>>>change and is 
>>>
>>>>therefore a perfect candidate for being templated.  The only real 
>>>>information that needs to be handled per query here is the 
>>>
>>>actual number.
>>>
>>>>FM
>>>>
>>>>
>>>>
>>>>Frank W. Miller, Ph.D.
>>>>Chief Technical Officer
>>>>sentitO Networks, Inc.
>>>>fmiller@sentito.com
>>>>
>>>>-----Original Message-----
>>>>From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
>>>>Sent: Tuesday, November 18, 2003 3:14 PM
>>>>To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
>>>>Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
>>>>Subject: RE: [Sip] Sip support for TCAP queries
>>>>
>>>> [Moving this thread to SIPPING, where it belongs]
>>>>
>>>>Leaving aside the question of whether or not ENUM supports 
>>>
>>>all of the 
>>>
>>>>functions of TCAP, the main issue is whether or not SIP is 
>>>
>>>the right sort 
>>>
>>>>of protocol to handle this function. A query-response 
>>
>>protocol that 
>>
>>>>carries XML documents from a client to a server? Does SIP 
>>>
>>>INFO really seem 
>>>
>>>>to map onto that well? Aren't there other protocols that 
>>
>>are tooled 
>>
>>>>specifically to that purpose?
>>>>
>>>>Furthermore, is the encoding really the issue? XML vs. 
>>>
>>>binary doesn't seem 
>>>
>>>>that significant to me - if a SIP endpoint can template the 
>>>
>>>XML format, it 
>>>
>>>>could template the binary format as well. Regardless of the 
>>>
>>>syntax, should 
>>>
>>>>we expect SIP endpoints to understand the semantics of TCAP? 
>>>
>>>Do we expect 
>>>
>>>>a SIP user agent to understand and implement the concept of, 
>>>
>>>say, a code 
>>>
>>>>gap? That isn't "translation" in any sense that I recognize 
>>>
>>>- it is closer 
>>>
>>>>to saying that SIP user agents have to run a dual stack (SIP 
>>>
>>>and TCAP). 
>>>
>>>>Just look at the <Digits> stanza of the example in 6.1.1.1 
>>>
>>>of the draft: 
>>>
>>>>what sorts of SIP elements are going to understand binary 
>>>
>>>coded decimal, 
>>>
>>>>recognize numbering plans, and the like? If the answer is 
>>>
>>>"only PSTN-SIP 
>>>
>>>>gateways with that already have SS7 links and could 
>>>
>>>therefore just send 
>>>
>>>>TCAP queries over SS7", then I think there is a design issue here.
>>>>
>>>>Jon Peterson
>>>>NeuStar, Inc.
>>>>-----Original Message-----
>>>>From: Frank W. Miller [mailto:fmiller@sentito.com]
>>>>Sent: Tuesday, November 18, 2003 8:50 AM
>>>>To: 'Chong, Koan S, ALABS'
>>>>Cc: sip@ietf.org
>>>>Subject: RE: [Sip] Sip support for TCAP queries
>>>>
>>>>The main idea of this draft was to provide a capability for 
>>>
>>>SIP endpoints 
>>>
>>>>to do TCAP queries without having to implement the binary TCAP 
>>>>protocol.  The motivation is that there are a lot of TCAP 
>>>
>>>queries that 
>>>
>>>>take place (800, LNP, CNAME) that are really simple and that major 
>>>>carriers may not want to go and reimplement in an ENUM 
>>>
>>>database in the 
>>>
>>>>short term.  These carriers have spent a lot of money on 
>>>
>>>their SCPs and 
>>>
>>>>converting the to ENUM is non-trivial.  Now, the SCPs could 
>>>
>>>be front-ended 
>>>
>>>>and conversion can be automated but this draft provides an 
>>>>alternative.  So, to answer the first question, the SIP 
>>>
>>>endpoint formats 
>>>
>>>>the correct query in the XML format specified and sends if 
>>>
>>>using an INFO 
>>>
>>>>to a Signaling Gateway (SG).  The SG then converts the query 
>>>
>>>to binary 
>>>
>>>>TCAP and dips the SCP.  The XML format can be templated in the 
>>>>implementation so the effort is quite minimal on the SIP 
>>>
>>>endpoint.  To 
>>>
>>>>answer the second question, the draft talks about a couple 
>>>
>>>of examples but 
>>>
>>>>the specification encompasses the entire TCAP message set 
>>
>>so you can 
>>
>>>>format the appropriate dip for AR/C.  One caveat is that the 
>>>
>>>draft is 
>>>
>>>>Telcordia based.  It would need to be extended to take into 
>>>
>>>account other 
>>>
>>>>variants.  On the third question, <personal view> I'm a 
>>
>>believer in 
>>
>>>>translation over tunneling, tunneling just puts off work and mixes 
>>>>messaging from different signaling networks 
>>>
>>>unnecessarily</personal view>.
>>>
>>>>FM
>>>>
>>>>
>>>>
>>>>Frank W. Miller, Ph.D.
>>>>Chief Technical Officer
>>>>sentitO Networks, Inc.
>>>>fmiller@sentito.com
>>>>
>>>>-----Original Message-----
>>>>From: Chong, Koan S, ALABS [mailto:kschong@att.com]
>>>>Sent: Tuesday, November 18, 2003 11:27 AM
>>>>To: Frank W. Miller; McCandless, Kevin
>>>>Cc: sip@ietf.org
>>>>Subject: RE: [Sip] Sip support for TCAP queries
>>>>
>>>>
>>>>A couple specific questions:
>>>>
>>>>What is the recommendation on how a SIP network element can 
>>>
>>>access the 
>>>
>>>>callers' name databases (CNAM in US) in PSTN after the SIP 
>>>
>>>element has 
>>>
>>>>determined that the called parties have subscribed to Caller ID?
>>>>
>>>>How about interworking with CLASS Auto-Recall/Callback (CCBS 
>>>
>>>in ITU?) 
>>>
>>>>procedures?
>>>>
>>>>Assume TCAP over SIGTRAN is a bit long long term....
>>>>
>>>>Koan
>>>>Koan S.Chong
>>>>AT&T
>>>>1-732-420-4557
>>>>
>>>>-----Original Message-----
>>>>From: Frank W. Miller [mailto:fmiller@sentito.com]
>>>>Sent: Monday, November 17, 2003 6:18 PM
>>>>To: 'McCandless, Kevin'
>>>>Cc: sip@ietf.org
>>>>Subject: RE: [Sip] Sip support for TCAP queries
>>>>
>>>>You mean other than us implementing it?  No, I don't think 
>>>
>>>so.  I think 
>>>
>>>>its considered Rosemary's Baby by most...
>>>>
>>>>FM
>>>>
>>>>
>>>>Frank W. Miller, Ph.D.
>>>>Chief Technical Officer
>>>>sentitO Networks, Inc.
>>>>fmiller@sentito.com
>>>>
>>>>-----Original Message-----
>>>>From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of 
>>>>McCandless, Kevin
>>>>Sent: Monday, November 17, 2003 4:11 PM
>>>>To: sip@ietf.org
>>>>Subject: [Sip] Sip support for TCAP queries
>>>>
>>>>Has any progress been taken on the draft by Frank Miller on 
>>>
>>>Carrying TCAP 
>>>
>>>>in SIP messages?  Are there other drafts that address SIP 
>>>
>>>access to SS7 
>>>
>>>>database information through TCAP or another method?
>>>>
>>>>Thanks,
>>>>
>>>>Kevin
>>>
>>>
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>Richard Shockey, Senior Manager, Strategic Technology Initiatives
>>>NeuStar Inc.
>>>46000 Center Oak Plaza  -   Sterling, VA  20166
>>>sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
>>>PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  
>>>Fax: +1 815.333.1237
>>><mailto:richard(at)shockey.us> or 
>>><mailto:richard.shockey(at)neustar.biz>
>>>
>><http://www.neustar.biz> ; <http://www.enum.org>
>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 15:19:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08931
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 15:19:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYn1-0004Js-Og
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:19:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKJ3IH016598
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:19:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYn1-0004Jd-HU
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 15:19:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08829
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 15:18:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYn0-0001MZ-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:19:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYmz-0001MW-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYn0-0004IT-4K; Wed, 19 Nov 2003 15:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYma-0004I7-QO
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 15:18:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08762
	for <sipping@ietf.org>; Wed, 19 Nov 2003 15:18:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYmX-0001MI-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:18:33 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYmW-0001MF-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:18:32 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id PAA25848;
	Wed, 19 Nov 2003 15:16:40 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Frank W. Miller" <fmiller@sentito.com>,
        "'Drage, Keith \(Keith\)'" <drage@lucent.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 15:16:25 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMMEFICCAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <004101c3aed4$c5f826a0$9100000a@frankgks0u6mmz>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Please see below fpor some questions/comments....
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Frank W. Miller
> Sent: Wednesday, November 19, 2003 2:39 PM
> To: 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>
>
>
> With all due respect, the reason I didn't ask to have it considered was I
> knew that it would never be accepted, so why waste my breath.  My purpose
> was to solve a problem that needs addressing.
>
> It cannot be ignored that SIP is making major inroads into the
> big carriers
> and dealing with ISUP and TCAP in a complete way within the context of SIP
> is something that needs to happen.  Now, if INFO as transport for
> XML isn't
> palatable, whatever.
>
> Let me be very plain, RFC 3398 is not sufficient.  It lacks
> support for ISUP
> maintenance commands and access to SCPs via TCAP.  These are
> functions that
> are required by vendors and carriers integrating SIP with the
> existing PSTN.
[TOLGA]Why do you need those maintanence messages? Your voice trunks
terminate at the gateway and it is the gateway, which is interested in them,
and which receives them via ISUP. Why do you need to propogate them to a
pure SIP entity in the network? Why should they care about management of
circuits, which are physically terminated at the gateway?
And again for SCP access, if one wants to speak TCAP to them, one needs
TCAP(over SCCP or over a SIGTRAN protocol like M3UA/SUA etc...). If SCP
understands it -or if one introduces a TCAP gateway for it-, one also might
use something (HTML, SOAP, XML-RPC etc...) over HTTP. I believe, the point
is, SIP is not a transport protocol.
>
> I happen to be associated with one of the vendors addressing
> these needs at
> the implementation level.  If the protocol does not serve all my needs, I
> will extend it.  If you as protocol specifiers don't like the way I extend
> it then put something else in place that I can use.
>
> Hoping to be constructive,
> FM
>
>
> Frank W. Miller, Ph.D.
> Chief Technical Officer
> sentitO Networks, Inc.
> fmiller@sentito.com
>
>
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf Of
> Drage, Keith (Keith)
> Sent: Wednesday, November 19, 2003 2:01 PM
> To: 'McCandless, Kevin'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>
> I dont see any justification here.
>
> The only sense I can make of the proposal so far is that SIP is used as a
> means of transporting TCAP from one place to another. It is not a case the
> protocol being used to make a SIP request, and the TCAP information
> enhancing that request.
>
> The IETF will not extend SIP so it is just another transport protocol,
> transaction protocol or whatever. There are other IETF defined
> solutions in
> this space.
>
> So while the original author never progressed his original
> request, in that
> he never asked for it to become a WG item or proposed that it should go
> forward as an individual draft (and it died because the author failed to
> refresh it), it would probably fail to progress (I daren't say
> never as they
> will then prove me wrong), the former because the charter of the WG would
> never be extended to cover it, and the latter at the IESG review stage.
>
> If there is any reason for progressing this, then the proponents need to
> clearly distinguish a reason for putting it in SIP that relates
> to SIP as a
> Session Initiation Protocol.
>
> regards
>
> Keith
>
>
>
> > -----Original Message-----
> > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > Sent: 19 November 2003 14:47
> > To: 'Richard Shockey'
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> >
> >
> > Ignorance awakens in the dawn of reality.
> >
> > SIP needs a formal methodology for obtaining a TCAP query.
> > Whether the SS7 providers does this with their signaling
> > gateway or not is not the issue.  A formalized approach that
> > a vendor can implement is the point that is being raised.
> >
> >
> >
> > > -----Original Message-----
> > > From: Richard Shockey [mailto:richard@shockey.us]
> > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > To: sipping@ietf.org
> > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > >
> > > As the distributor of the NO TCAP buttons on generous display
> > > at IETF 59
> > > and fine trade shows nationwide , let me comment that this is
> > > one of the
> > > silliest ideas I have yet seen cross the SIPPING landscape.
> > >
> > > Why ..why on earth would you want to do this ..any query
> > > response mechanism
> > > can get you the data points necessary without the baggage
> > > TCAP puts you
> > > through.
> > >
> > > Talk to your SS7 vendor and demand better service or fire
> > > them. Get them to
> > > support SIP itself  query response mechanism. Send an INVITE
> > > expect a 302
> > > MOVE in response and encapsulate SS7 the data as part of a
> > > TEL URL in the
> > > response.
> > >
> > > This is a "bad idea" tm worthy of the big gong and hook.
> > >
> > >
> > > >
> > > >Aiieee, a cross is raised!!  ;)
> > > >
> > > >Anyway, you're right, the format doesn't matter at all,
> > > except for one
> > > >thing.  Expedience.  The essence of the argument against
> > > this type of
> > > >draft in general, i.e. one that uses INFO to carry anything,
> > > is usually
> > > >based on the fact that the content is application specific
> > > and so doesn't
> > > >fit with the base SIP protocol.  I can understand that and
> > > accept it, it
> > > >really doesn't matter to me.  I'm an implementor, not a protocol
> > > >specifier.  Unfortunately, the protocol doesn't do
> > > everything I need it to
> > > >do so I have to add stuff to fill in the holes when I take
> > > it into the
> > > >real world.  The other draft in this area
> > > draft-miller-sip-isup-annex is
> > > >another example of augmentation, the addition of ISUP
> > > maintenance commands
> > > >to the ISUP translation now RFC.  I could write/buy an SS7
> > > implementation
> > > >and template the messages and hook that into my
> > > CNAME/LNP/whatever at the
> > > >call control layer and to SCTP/UDP/whatever on the network
> > > side but why,
> > > >to keep the SIP implementation "beautiful"?  The bottom line
> > > is I'm not
> > > >going to pass the cost of the SS7 stack on to my customers
> > > if I can make a
> > > >simple addition to the SIP stuff and do exactly the same
> > > thing basically
> > > >for free.
> > > >
> > > >Now with respect to the specifics of the encoding, we can
> > > certainly talk
> > > >about anything.  That was the whole reason for publishing
> > > the work in the
> > > >IETF to begin with.  On 6.1.1.1 specifically, this is
> > simply a field
> > > >required in the QWP message.  The actual digits are
> > > specified in a string
> > > >not in BCD binary.  The Signaling
> > > Gateway/Softswitch/whatever just picks
> > > >up BCD from the Encoding field and fills in the appropriate
> > > value in the
> > > >actual TCAP binary message when the translation is done.
> > > The digits in
> > > >the ASCII string are converted similarly to BCD format in
> > > the TCAP binary
> > > >message also at that time.  The <Encoding  > field doesn't
> > > change and is
> > > >therefore a perfect candidate for being templated.  The only real
> > > >information that needs to be handled per query here is the
> > > actual number.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >  [Moving this thread to SIPPING, where it belongs]
> > > >
> > > >Leaving aside the question of whether or not ENUM supports
> > > all of the
> > > >functions of TCAP, the main issue is whether or not SIP is
> > > the right sort
> > > >of protocol to handle this function. A query-response
> > protocol that
> > > >carries XML documents from a client to a server? Does SIP
> > > INFO really seem
> > > >to map onto that well? Aren't there other protocols that
> > are tooled
> > > >specifically to that purpose?
> > > >
> > > >Furthermore, is the encoding really the issue? XML vs.
> > > binary doesn't seem
> > > >that significant to me - if a SIP endpoint can template the
> > > XML format, it
> > > >could template the binary format as well. Regardless of the
> > > syntax, should
> > > >we expect SIP endpoints to understand the semantics of TCAP?
> > > Do we expect
> > > >a SIP user agent to understand and implement the concept of,
> > > say, a code
> > > >gap? That isn't "translation" in any sense that I recognize
> > > - it is closer
> > > >to saying that SIP user agents have to run a dual stack (SIP
> > > and TCAP).
> > > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > > of the draft:
> > > >what sorts of SIP elements are going to understand binary
> > > coded decimal,
> > > >recognize numbering plans, and the like? If the answer is
> > > "only PSTN-SIP
> > > >gateways with that already have SS7 links and could
> > > therefore just send
> > > >TCAP queries over SS7", then I think there is a design issue here.
> > > >
> > > >Jon Peterson
> > > >NeuStar, Inc.
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > >To: 'Chong, Koan S, ALABS'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >The main idea of this draft was to provide a capability for
> > > SIP endpoints
> > > >to do TCAP queries without having to implement the binary TCAP
> > > >protocol.  The motivation is that there are a lot of TCAP
> > > queries that
> > > >take place (800, LNP, CNAME) that are really simple and that major
> > > >carriers may not want to go and reimplement in an ENUM
> > > database in the
> > > >short term.  These carriers have spent a lot of money on
> > > their SCPs and
> > > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > > be front-ended
> > > >and conversion can be automated but this draft provides an
> > > >alternative.  So, to answer the first question, the SIP
> > > endpoint formats
> > > >the correct query in the XML format specified and sends if
> > > using an INFO
> > > >to a Signaling Gateway (SG).  The SG then converts the query
> > > to binary
> > > >TCAP and dips the SCP.  The XML format can be templated in the
> > > >implementation so the effort is quite minimal on the SIP
> > > endpoint.  To
> > > >answer the second question, the draft talks about a couple
> > > of examples but
> > > >the specification encompasses the entire TCAP message set
> > so you can
> > > >format the appropriate dip for AR/C.  One caveat is that the
> > > draft is
> > > >Telcordia based.  It would need to be extended to take into
> > > account other
> > > >variants.  On the third question, <personal view> I'm a
> > believer in
> > > >translation over tunneling, tunneling just puts off work and mixes
> > > >messaging from different signaling networks
> > > unnecessarily</personal view>.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > >To: Frank W. Miller; McCandless, Kevin
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >
> > > >A couple specific questions:
> > > >
> > > >What is the recommendation on how a SIP network element can
> > > access the
> > > >callers' name databases (CNAM in US) in PSTN after the SIP
> > > element has
> > > >determined that the called parties have subscribed to Caller ID?
> > > >
> > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > > in ITU?)
> > > >procedures?
> > > >
> > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > >
> > > >Koan
> > > >Koan S.Chong
> > > >AT&T
> > > >1-732-420-4557
> > > >
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Monday, November 17, 2003 6:18 PM
> > > >To: 'McCandless, Kevin'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >You mean other than us implementing it?  No, I don't think
> > > so.  I think
> > > >its considered Rosemary's Baby by most...
> > > >
> > > >FM
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
> > > >McCandless, Kevin
> > > >Sent: Monday, November 17, 2003 4:11 PM
> > > >To: sip@ietf.org
> > > >Subject: [Sip] Sip support for TCAP queries
> > > >
> > > >Has any progress been taken on the draft by Frank Miller on
> > > Carrying TCAP
> > > >in SIP messages?  Are there other drafts that address SIP
> > > access to SS7
> > > >database information through TCAP or another method?
> > > >
> > > >Thanks,
> > > >
> > > >Kevin
> > >
> > >
> > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > > NeuStar Inc.
> > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > > Fax: +1 815.333.1237
> > > <mailto:richard(at)shockey.us> or
> > > <mailto:richard.shockey(at)neustar.biz>
> > >
> > <http://www.neustar.biz> ; <http://www.enum.org>
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 15:24:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09478
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 15:24:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYrz-0004wd-Dn
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:24:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKOBEU018998
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:24:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYry-0004t3-Fj
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 15:24:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09456
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 15:23:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYrr-0001Sg-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:24:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYrr-0001Sd-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:24:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYrp-0004qK-LB; Wed, 19 Nov 2003 15:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMYrJ-0004pU-1D
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 15:23:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09432
	for <sipping@ietf.org>; Wed, 19 Nov 2003 15:23:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYrH-0001Rw-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:23:27 -0500
Received: from [198.202.216.4] (helo=fullsail.illuminet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMYrG-0001Rs-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:23:27 -0500
Received: from oly1wnexc01.corp.illuminet.com (oly1wnexc01.corp.illuminet.com [10.55.13.12])
	by fullsail.illuminet.com (8.12.10/8.12.10) with ESMTP id hAJKNMLm028262;
	Wed, 19 Nov 2003 12:23:24 -0800 (PST)
Received: by oly1wnexc01.corp.illuminet.com with Internet Mail Service (5.5.2653.19)
	id <W35GMJY2>; Wed, 19 Nov 2003 12:23:17 -0800
Message-ID: <318266A4431BC549B4C4D6FD3EA6E24D012CED18@ove1wnexm01.corp.illuminet.com>
From: "McCandless, Kevin" <KMcCandless@verisign.com>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>
Cc: sipping@ietf.org, "'Frank W. Miller'" <fmiller@sentito.com>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 12:23:10 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

So, CNAM, LNP, and other SS7 data is relevant to working SIP networks that interconnect with the PSTN.  There is no standard document to define how the SIP protocol obtains the database information.  Each vendor is implementing their own way of doing this with SIP on one side during the Invite message and on the other side launching an SS7 query either with M3UA or standard SS7 TDM links.  VoIP carriers want access to the data so would it not be helpful to have a standard way of implementing this interworking.  This has already done for ISUP.  SS7 is not going away and the interworking between VoIP and PSTN can only help the VoIP initiatives.

> -----Original Message-----
> From: Frank W. Miller [mailto:fmiller@sentito.com] 
> Sent: Wednesday, November 19, 2003 1:39 PM
> To: 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> 
> 
> With all due respect, the reason I didn't ask to have it 
> considered was I
> knew that it would never be accepted, so why waste my breath. 
>  My purpose
> was to solve a problem that needs addressing.
> 
> It cannot be ignored that SIP is making major inroads into 
> the big carriers
> and dealing with ISUP and TCAP in a complete way within the 
> context of SIP
> is something that needs to happen.  Now, if INFO as transport 
> for XML isn't
> palatable, whatever.
> 
> Let me be very plain, RFC 3398 is not sufficient.  It lacks 
> support for ISUP
> maintenance commands and access to SCPs via TCAP.  These are 
> functions that
> are required by vendors and carriers integrating SIP with the 
> existing PSTN.
> 
> I happen to be associated with one of the vendors addressing 
> these needs at
> the implementation level.  If the protocol does not serve all 
> my needs, I
> will extend it.  If you as protocol specifiers don't like the 
> way I extend
> it then put something else in place that I can use.
> 
> Hoping to be constructive,
> FM
>  
> 
> Frank W. Miller, Ph.D.
> Chief Technical Officer
> sentitO Networks, Inc.
> fmiller@sentito.com
> 
> 
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of
> Drage, Keith (Keith)
> Sent: Wednesday, November 19, 2003 2:01 PM
> To: 'McCandless, Kevin'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> I dont see any justification here.
> 
> The only sense I can make of the proposal so far is that SIP 
> is used as a
> means of transporting TCAP from one place to another. It is 
> not a case the
> protocol being used to make a SIP request, and the TCAP information
> enhancing that request.
> 
> The IETF will not extend SIP so it is just another transport protocol,
> transaction protocol or whatever. There are other IETF 
> defined solutions in
> this space.
> 
> So while the original author never progressed his original 
> request, in that
> he never asked for it to become a WG item or proposed that it 
> should go
> forward as an individual draft (and it died because the 
> author failed to
> refresh it), it would probably fail to progress (I daren't 
> say never as they
> will then prove me wrong), the former because the charter of 
> the WG would
> never be extended to cover it, and the latter at the IESG 
> review stage.
> 
> If there is any reason for progressing this, then the 
> proponents need to
> clearly distinguish a reason for putting it in SIP that 
> relates to SIP as a
> Session Initiation Protocol.
> 
> regards
> 
> Keith
> 
> 
> 
> > -----Original Message-----
> > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > Sent: 19 November 2003 14:47
> > To: 'Richard Shockey'
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > 
> > 
> > Ignorance awakens in the dawn of reality.
> > 
> > SIP needs a formal methodology for obtaining a TCAP query.  
> > Whether the SS7 providers does this with their signaling 
> > gateway or not is not the issue.  A formalized approach that 
> > a vendor can implement is the point that is being raised.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Richard Shockey [mailto:richard@shockey.us] 
> > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > To: sipping@ietf.org
> > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > 
> > > 
> > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > 
> > > As the distributor of the NO TCAP buttons on generous display 
> > > at IETF 59 
> > > and fine trade shows nationwide , let me comment that this is 
> > > one of the 
> > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > 
> > > Why ..why on earth would you want to do this ..any query 
> > > response mechanism 
> > > can get you the data points necessary without the baggage 
> > > TCAP puts you 
> > > through.
> > > 
> > > Talk to your SS7 vendor and demand better service or fire 
> > > them. Get them to 
> > > support SIP itself  query response mechanism. Send an INVITE 
> > > expect a 302 
> > > MOVE in response and encapsulate SS7 the data as part of a 
> > > TEL URL in the 
> > > response.
> > > 
> > > This is a "bad idea" tm worthy of the big gong and hook.
> > > 
> > > 
> > > >
> > > >Aiieee, a cross is raised!!  ;)
> > > >
> > > >Anyway, you're right, the format doesn't matter at all, 
> > > except for one 
> > > >thing.  Expedience.  The essence of the argument against 
> > > this type of 
> > > >draft in general, i.e. one that uses INFO to carry anything, 
> > > is usually 
> > > >based on the fact that the content is application specific 
> > > and so doesn't 
> > > >fit with the base SIP protocol.  I can understand that and 
> > > accept it, it 
> > > >really doesn't matter to me.  I'm an implementor, not a protocol 
> > > >specifier.  Unfortunately, the protocol doesn't do 
> > > everything I need it to 
> > > >do so I have to add stuff to fill in the holes when I take 
> > > it into the 
> > > >real world.  The other draft in this area 
> > > draft-miller-sip-isup-annex is 
> > > >another example of augmentation, the addition of ISUP 
> > > maintenance commands 
> > > >to the ISUP translation now RFC.  I could write/buy an SS7 
> > > implementation 
> > > >and template the messages and hook that into my 
> > > CNAME/LNP/whatever at the 
> > > >call control layer and to SCTP/UDP/whatever on the network 
> > > side but why, 
> > > >to keep the SIP implementation "beautiful"?  The bottom line 
> > > is I'm not 
> > > >going to pass the cost of the SS7 stack on to my customers 
> > > if I can make a 
> > > >simple addition to the SIP stuff and do exactly the same 
> > > thing basically 
> > > >for free.
> > > >
> > > >Now with respect to the specifics of the encoding, we can 
> > > certainly talk 
> > > >about anything.  That was the whole reason for publishing 
> > > the work in the 
> > > >IETF to begin with.  On 6.1.1.1 specifically, this is 
> > simply a field 
> > > >required in the QWP message.  The actual digits are 
> > > specified in a string 
> > > >not in BCD binary.  The Signaling 
> > > Gateway/Softswitch/whatever just picks 
> > > >up BCD from the Encoding field and fills in the appropriate 
> > > value in the 
> > > >actual TCAP binary message when the translation is done.  
> > > The digits in 
> > > >the ASCII string are converted similarly to BCD format in 
> > > the TCAP binary 
> > > >message also at that time.  The <Encoding  > field doesn't 
> > > change and is 
> > > >therefore a perfect candidate for being templated.  The 
> only real 
> > > >information that needs to be handled per query here is the 
> > > actual number.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >  [Moving this thread to SIPPING, where it belongs]
> > > >
> > > >Leaving aside the question of whether or not ENUM supports 
> > > all of the 
> > > >functions of TCAP, the main issue is whether or not SIP is 
> > > the right sort 
> > > >of protocol to handle this function. A query-response 
> > protocol that 
> > > >carries XML documents from a client to a server? Does SIP 
> > > INFO really seem 
> > > >to map onto that well? Aren't there other protocols that 
> > are tooled 
> > > >specifically to that purpose?
> > > >
> > > >Furthermore, is the encoding really the issue? XML vs. 
> > > binary doesn't seem 
> > > >that significant to me - if a SIP endpoint can template the 
> > > XML format, it 
> > > >could template the binary format as well. Regardless of the 
> > > syntax, should 
> > > >we expect SIP endpoints to understand the semantics of TCAP? 
> > > Do we expect 
> > > >a SIP user agent to understand and implement the concept of, 
> > > say, a code 
> > > >gap? That isn't "translation" in any sense that I recognize 
> > > - it is closer 
> > > >to saying that SIP user agents have to run a dual stack (SIP 
> > > and TCAP). 
> > > >Just look at the <Digits> stanza of the example in 6.1.1.1 
> > > of the draft: 
> > > >what sorts of SIP elements are going to understand binary 
> > > coded decimal, 
> > > >recognize numbering plans, and the like? If the answer is 
> > > "only PSTN-SIP 
> > > >gateways with that already have SS7 links and could 
> > > therefore just send 
> > > >TCAP queries over SS7", then I think there is a design 
> issue here.
> > > >
> > > >Jon Peterson
> > > >NeuStar, Inc.
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > >To: 'Chong, Koan S, ALABS'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >The main idea of this draft was to provide a capability for 
> > > SIP endpoints 
> > > >to do TCAP queries without having to implement the binary TCAP 
> > > >protocol.  The motivation is that there are a lot of TCAP 
> > > queries that 
> > > >take place (800, LNP, CNAME) that are really simple and 
> that major 
> > > >carriers may not want to go and reimplement in an ENUM 
> > > database in the 
> > > >short term.  These carriers have spent a lot of money on 
> > > their SCPs and 
> > > >converting the to ENUM is non-trivial.  Now, the SCPs could 
> > > be front-ended 
> > > >and conversion can be automated but this draft provides an 
> > > >alternative.  So, to answer the first question, the SIP 
> > > endpoint formats 
> > > >the correct query in the XML format specified and sends if 
> > > using an INFO 
> > > >to a Signaling Gateway (SG).  The SG then converts the query 
> > > to binary 
> > > >TCAP and dips the SCP.  The XML format can be templated in the 
> > > >implementation so the effort is quite minimal on the SIP 
> > > endpoint.  To 
> > > >answer the second question, the draft talks about a couple 
> > > of examples but 
> > > >the specification encompasses the entire TCAP message set 
> > so you can 
> > > >format the appropriate dip for AR/C.  One caveat is that the 
> > > draft is 
> > > >Telcordia based.  It would need to be extended to take into 
> > > account other 
> > > >variants.  On the third question, <personal view> I'm a 
> > believer in 
> > > >translation over tunneling, tunneling just puts off work 
> and mixes 
> > > >messaging from different signaling networks 
> > > unnecessarily</personal view>.
> > > >
> > > >FM
> > > >
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > >To: Frank W. Miller; McCandless, Kevin
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >
> > > >A couple specific questions:
> > > >
> > > >What is the recommendation on how a SIP network element can 
> > > access the 
> > > >callers' name databases (CNAM in US) in PSTN after the SIP 
> > > element has 
> > > >determined that the called parties have subscribed to Caller ID?
> > > >
> > > >How about interworking with CLASS Auto-Recall/Callback (CCBS 
> > > in ITU?) 
> > > >procedures?
> > > >
> > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > >
> > > >Koan
> > > >Koan S.Chong
> > > >AT&T
> > > >1-732-420-4557
> > > >
> > > >-----Original Message-----
> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > >Sent: Monday, November 17, 2003 6:18 PM
> > > >To: 'McCandless, Kevin'
> > > >Cc: sip@ietf.org
> > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > >
> > > >You mean other than us implementing it?  No, I don't think 
> > > so.  I think 
> > > >its considered Rosemary's Baby by most...
> > > >
> > > >FM
> > > >
> > > >
> > > >Frank W. Miller, Ph.D.
> > > >Chief Technical Officer
> > > >sentitO Networks, Inc.
> > > >fmiller@sentito.com
> > > >
> > > >-----Original Message-----
> > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of 
> > > >McCandless, Kevin
> > > >Sent: Monday, November 17, 2003 4:11 PM
> > > >To: sip@ietf.org
> > > >Subject: [Sip] Sip support for TCAP queries
> > > >
> > > >Has any progress been taken on the draft by Frank Miller on 
> > > Carrying TCAP 
> > > >in SIP messages?  Are there other drafts that address SIP 
> > > access to SS7 
> > > >database information through TCAP or another method?
> > > >
> > > >Thanks,
> > > >
> > > >Kevin
> > > 
> > > 
> > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > > NeuStar Inc.
> > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  
> > > Fax: +1 815.333.1237
> > > <mailto:richard(at)shockey.us> or 
> > > <mailto:richard.shockey(at)neustar.biz>
> > > 
> > <http://www.neustar.biz> ; <http://www.enum.org>
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 15:39:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10710
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 15:39:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZ6R-00078P-0L
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:39:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKd6Sj027419
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:39:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZ6Q-00078A-Ro
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 15:39:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10698
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 15:38:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZ6P-0001nh-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:39:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZ6O-0001ne-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZ6L-00076y-9t; Wed, 19 Nov 2003 15:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZ6I-00076l-Dt
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 15:38:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10683
	for <sipping@ietf.org>; Wed, 19 Nov 2003 15:38:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZ6G-0001na-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:38:56 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZ6F-0001nX-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:38:56 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id PAA01523;
	Wed, 19 Nov 2003 15:36:41 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Michael Hammer" <mhammer@cisco.com>,
        "Drage, Keith \(Keith\)" <drage@lucent.com>
Cc: "'McCandless, Kevin'" <KMcCandless@verisign.com>, <sipping@ietf.org>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 15:36:26 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMCEFKCCAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20031119143000.00b527b0@cia.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Michael Hammer
> Sent: Wednesday, November 19, 2003 2:50 PM
> To: Drage, Keith (Keith)
> Cc: 'McCandless, Kevin'; sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>
>
> Keith,
>
> This is not to support the current suggestion but to get more
> clarification
> taking a long-range view of (Internet/PSTN) network(s) evolution.
>
> Two cases in point:
> 1) TCAP carried registration messages for mobile systems, yet the
> equivalent is now done by SIP REGISTER method, which may eventually
> displace the former TCAP-carried methods.
> 2) Camp-on indications currently carried by TCAP that translate
> (partially)
> into SUBSCRIBE/NOTIFY.  Recall the previous request to expand SIP
> to carry
> some additional CCBS indications.
>
> I see TCAP as being more like the transport protocols that underlies SIP,
> so am not sure that all of that functionality needs to survive (carried
> over) into the IP world.
[TOLGA]In fact it is SCCP, which is the transport protocol for such messages
in SS7 world. TCAP is more like an asynchronous RPC mechanism (for example
similar to SOAP over HTTP), and does not have direct application semantic.
>
> The question I have is whether the stuff inside of TCAP messages evolves
> from an SS7-world application to an IETF application?
[TOLGA]Personally I don't think so, because SIP is really a totally
different paradigm. For example, do we foresee to have a call model similar
to BCSM for SIP, which would make INAP/AIN meaningfull for SIP?
>
> Put another way, if the TCAP and above stuff is migrated to
> TCAP/SUA/SCTP/IP, and the SS7 network as we know it today
> eventually fades
> away, does that make the TCAP and above stuff Internet protocols?
[TOLGA] Again my personal opinion, "Internet protocols" probably
yes -afterall Internet is not just SIP- , but I would think, when SS7 fades
away, there won't be need for the stuff above TCAP in the pure SIP network.
IMO, even today, they are mostly necessary just for gateways, because SS7
concepts are still present at them -they are a node in SS7 network-.
>
> Mike
>
>
> At 07:01 PM 11/19/2003 +0000, Drage, Keith (Keith) wrote:
> >I dont see any justification here.
> >
> >The only sense I can make of the proposal so far is that SIP is
> used as a
> >means of transporting TCAP from one place to another. It is not
> a case the
> >protocol being used to make a SIP request, and the TCAP information
> >enhancing that request.
> >
> >The IETF will not extend SIP so it is just another transport protocol,
> >transaction protocol or whatever. There are other IETF defined solutions
> >in this space.
> >
> >So while the original author never progressed his original request, in
> >that he never asked for it to become a WG item or proposed that
> it should
> >go forward as an individual draft (and it died because the author failed
> >to refresh it), it would probably fail to progress (I daren't
> say never as
> >they will then prove me wrong), the former because the charter of the WG
> >would never be extended to cover it, and the latter at the IESG
> review stage.
> >
> >If there is any reason for progressing this, then the proponents need to
> >clearly distinguish a reason for putting it in SIP that relates
> to SIP as
> >a Session Initiation Protocol.
> >
> >regards
> >
> >Keith
> >
> >
> >
> > > -----Original Message-----
> > > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > > Sent: 19 November 2003 14:47
> > > To: 'Richard Shockey'
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > > Ignorance awakens in the dawn of reality.
> > >
> > > SIP needs a formal methodology for obtaining a TCAP query.
> > > Whether the SS7 providers does this with their signaling
> > > gateway or not is not the issue.  A formalized approach that
> > > a vendor can implement is the point that is being raised.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Richard Shockey [mailto:richard@shockey.us]
> > > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > > To: sipping@ietf.org
> > > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > >
> > > >
> > > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > >
> > > > As the distributor of the NO TCAP buttons on generous display
> > > > at IETF 59
> > > > and fine trade shows nationwide , let me comment that this is
> > > > one of the
> > > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > >
> > > > Why ..why on earth would you want to do this ..any query
> > > > response mechanism
> > > > can get you the data points necessary without the baggage
> > > > TCAP puts you
> > > > through.
> > > >
> > > > Talk to your SS7 vendor and demand better service or fire
> > > > them. Get them to
> > > > support SIP itself  query response mechanism. Send an INVITE
> > > > expect a 302
> > > > MOVE in response and encapsulate SS7 the data as part of a
> > > > TEL URL in the
> > > > response.
> > > >
> > > > This is a "bad idea" tm worthy of the big gong and hook.
> > > >
> > > >
> > > > >
> > > > >Aiieee, a cross is raised!!  ;)
> > > > >
> > > > >Anyway, you're right, the format doesn't matter at all,
> > > > except for one
> > > > >thing.  Expedience.  The essence of the argument against
> > > > this type of
> > > > >draft in general, i.e. one that uses INFO to carry anything,
> > > > is usually
> > > > >based on the fact that the content is application specific
> > > > and so doesn't
> > > > >fit with the base SIP protocol.  I can understand that and
> > > > accept it, it
> > > > >really doesn't matter to me.  I'm an implementor, not a protocol
> > > > >specifier.  Unfortunately, the protocol doesn't do
> > > > everything I need it to
> > > > >do so I have to add stuff to fill in the holes when I take
> > > > it into the
> > > > >real world.  The other draft in this area
> > > > draft-miller-sip-isup-annex is
> > > > >another example of augmentation, the addition of ISUP
> > > > maintenance commands
> > > > >to the ISUP translation now RFC.  I could write/buy an SS7
> > > > implementation
> > > > >and template the messages and hook that into my
> > > > CNAME/LNP/whatever at the
> > > > >call control layer and to SCTP/UDP/whatever on the network
> > > > side but why,
> > > > >to keep the SIP implementation "beautiful"?  The bottom line
> > > > is I'm not
> > > > >going to pass the cost of the SS7 stack on to my customers
> > > > if I can make a
> > > > >simple addition to the SIP stuff and do exactly the same
> > > > thing basically
> > > > >for free.
> > > > >
> > > > >Now with respect to the specifics of the encoding, we can
> > > > certainly talk
> > > > >about anything.  That was the whole reason for publishing
> > > > the work in the
> > > > >IETF to begin with.  On 6.1.1.1 specifically, this is
> > > simply a field
> > > > >required in the QWP message.  The actual digits are
> > > > specified in a string
> > > > >not in BCD binary.  The Signaling
> > > > Gateway/Softswitch/whatever just picks
> > > > >up BCD from the Encoding field and fills in the appropriate
> > > > value in the
> > > > >actual TCAP binary message when the translation is done.
> > > > The digits in
> > > > >the ASCII string are converted similarly to BCD format in
> > > > the TCAP binary
> > > > >message also at that time.  The <Encoding  > field doesn't
> > > > change and is
> > > > >therefore a perfect candidate for being templated.  The only real
> > > > >information that needs to be handled per query here is the
> > > > actual number.
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >  [Moving this thread to SIPPING, where it belongs]
> > > > >
> > > > >Leaving aside the question of whether or not ENUM supports
> > > > all of the
> > > > >functions of TCAP, the main issue is whether or not SIP is
> > > > the right sort
> > > > >of protocol to handle this function. A query-response
> > > protocol that
> > > > >carries XML documents from a client to a server? Does SIP
> > > > INFO really seem
> > > > >to map onto that well? Aren't there other protocols that
> > > are tooled
> > > > >specifically to that purpose?
> > > > >
> > > > >Furthermore, is the encoding really the issue? XML vs.
> > > > binary doesn't seem
> > > > >that significant to me - if a SIP endpoint can template the
> > > > XML format, it
> > > > >could template the binary format as well. Regardless of the
> > > > syntax, should
> > > > >we expect SIP endpoints to understand the semantics of TCAP?
> > > > Do we expect
> > > > >a SIP user agent to understand and implement the concept of,
> > > > say, a code
> > > > >gap? That isn't "translation" in any sense that I recognize
> > > > - it is closer
> > > > >to saying that SIP user agents have to run a dual stack (SIP
> > > > and TCAP).
> > > > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > > > of the draft:
> > > > >what sorts of SIP elements are going to understand binary
> > > > coded decimal,
> > > > >recognize numbering plans, and the like? If the answer is
> > > > "only PSTN-SIP
> > > > >gateways with that already have SS7 links and could
> > > > therefore just send
> > > > >TCAP queries over SS7", then I think there is a design issue here.
> > > > >
> > > > >Jon Peterson
> > > > >NeuStar, Inc.
> > > > >-----Original Message-----
> > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > > >To: 'Chong, Koan S, ALABS'
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >The main idea of this draft was to provide a capability for
> > > > SIP endpoints
> > > > >to do TCAP queries without having to implement the binary TCAP
> > > > >protocol.  The motivation is that there are a lot of TCAP
> > > > queries that
> > > > >take place (800, LNP, CNAME) that are really simple and that major
> > > > >carriers may not want to go and reimplement in an ENUM
> > > > database in the
> > > > >short term.  These carriers have spent a lot of money on
> > > > their SCPs and
> > > > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > > > be front-ended
> > > > >and conversion can be automated but this draft provides an
> > > > >alternative.  So, to answer the first question, the SIP
> > > > endpoint formats
> > > > >the correct query in the XML format specified and sends if
> > > > using an INFO
> > > > >to a Signaling Gateway (SG).  The SG then converts the query
> > > > to binary
> > > > >TCAP and dips the SCP.  The XML format can be templated in the
> > > > >implementation so the effort is quite minimal on the SIP
> > > > endpoint.  To
> > > > >answer the second question, the draft talks about a couple
> > > > of examples but
> > > > >the specification encompasses the entire TCAP message set
> > > so you can
> > > > >format the appropriate dip for AR/C.  One caveat is that the
> > > > draft is
> > > > >Telcordia based.  It would need to be extended to take into
> > > > account other
> > > > >variants.  On the third question, <personal view> I'm a
> > > believer in
> > > > >translation over tunneling, tunneling just puts off work and mixes
> > > > >messaging from different signaling networks
> > > > unnecessarily</personal view>.
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > > >To: Frank W. Miller; McCandless, Kevin
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >
> > > > >A couple specific questions:
> > > > >
> > > > >What is the recommendation on how a SIP network element can
> > > > access the
> > > > >callers' name databases (CNAM in US) in PSTN after the SIP
> > > > element has
> > > > >determined that the called parties have subscribed to Caller ID?
> > > > >
> > > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > > > in ITU?)
> > > > >procedures?
> > > > >
> > > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > > >
> > > > >Koan
> > > > >Koan S.Chong
> > > > >AT&T
> > > > >1-732-420-4557
> > > > >
> > > > >-----Original Message-----
> > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > >Sent: Monday, November 17, 2003 6:18 PM
> > > > >To: 'McCandless, Kevin'
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >You mean other than us implementing it?  No, I don't think
> > > > so.  I think
> > > > >its considered Rosemary's Baby by most...
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
> > > > >McCandless, Kevin
> > > > >Sent: Monday, November 17, 2003 4:11 PM
> > > > >To: sip@ietf.org
> > > > >Subject: [Sip] Sip support for TCAP queries
> > > > >
> > > > >Has any progress been taken on the draft by Frank Miller on
> > > > Carrying TCAP
> > > > >in SIP messages?  Are there other drafts that address SIP
> > > > access to SS7
> > > > >database information through TCAP or another method?
> > > > >
> > > > >Thanks,
> > > > >
> > > > >Kevin
> > > >
> > > >
> > > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > > > NeuStar Inc.
> > > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > > > Fax: +1 815.333.1237
> > > > <mailto:richard(at)shockey.us> or
> > > > <mailto:richard.shockey(at)neustar.biz>
> > > >
> > > <http://www.neustar.biz> ; <http://www.enum.org>
> > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the application of SIP
> >Use sip-implementors@cs.columbia.edu for questions on current sip
> >Use sip@ietf.org for new developments of core SIP
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 15:44:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11008
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 15:44:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZBE-0007Tq-Bg
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:44:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKi4XS028748
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 15:44:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZBD-0007Tb-NF
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 15:44:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10971
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 15:43:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZBC-0001rU-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:44:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZBB-0001rQ-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 15:44:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZBB-0007SL-18; Wed, 19 Nov 2003 15:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZB4-0007S5-2m
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 15:43:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10925
	for <sipping@ietf.org>; Wed, 19 Nov 2003 15:43:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZB2-0001r0-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:43:52 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZB1-0001qZ-00
	for sipping@ietf.org; Wed, 19 Nov 2003 15:43:51 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAJKg8A05580;
	Wed, 19 Nov 2003 15:42:09 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id W3H9ABH5; Wed, 19 Nov 2003 15:42:09 -0500
Received: from nortelnetworks.com (acart1c0.ca.nortel.com [47.129.129.43]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SZW5N36P; Wed, 19 Nov 2003 15:42:08 -0500
Message-ID: <3FBBD59E.8080900@nortelnetworks.com>
Date: Wed, 19 Nov 2003 15:42:06 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Hammer <mhammer@cisco.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
References: <4.3.2.7.2.20031119143000.00b527b0@cia.cisco.com>
In-Reply-To: <4.3.2.7.2.20031119143000.00b527b0@cia.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

You make a good point.  Architecturally we should allow ISUP and related 
signalling to invade SIP only in ways that are easy to remove as we 
migrate away from SS7.  This means for one thing that ISUP encapsulation 
is a temporary measure, used to carry ISUP between well-defined gateway 
points rather than spread it around the network for various SIP entities 
to work on.  Similarly, transport of TCAP over SUA/SCTP/IP is for IP 
bridging between two SS7 networks or between an SS7 network and an 
interworking point -- it's not meant to be used between SIP elements.

The end goal is services.  TCAP messages get replaced by whatever 
provides equivalent services in the Internet (your point).  ISUP 
services get mapped into the equivalent SIP services.  The ISUP may 
eventually go away, but the services will remain.

Michael Hammer wrote:

> Keith,
> 
> This is not to support the current suggestion but to get more 
> clarification taking a long-range view of (Internet/PSTN) network(s) 
> evolution.
> 
> Two cases in point:
> 1) TCAP carried registration messages for mobile systems, yet the 
> equivalent is now done by SIP REGISTER method, which may eventually 
> displace the former TCAP-carried methods.
> 2) Camp-on indications currently carried by TCAP that translate 
> (partially) into SUBSCRIBE/NOTIFY.  Recall the previous request to 
> expand SIP to carry some additional CCBS indications.
> 
> I see TCAP as being more like the transport protocols that underlies 
> SIP, so am not sure that all of that functionality needs to survive 
> (carried over) into the IP world.
> 
> The question I have is whether the stuff inside of TCAP messages evolves 
> from an SS7-world application to an IETF application?
> 
> Put another way, if the TCAP and above stuff is migrated to 
> TCAP/SUA/SCTP/IP, and the SS7 network as we know it today eventually 
> fades away, does that make the TCAP and above stuff Internet protocols?
> 
> Mike
> 
> 
> At 07:01 PM 11/19/2003 +0000, Drage, Keith (Keith) wrote:
> 
>> I dont see any justification here.
>>
>> The only sense I can make of the proposal so far is that SIP is used 
>> as a means of transporting TCAP from one place to another. It is not a 
>> case the protocol being used to make a SIP request, and the TCAP 
>> information enhancing that request.
>>
>> The IETF will not extend SIP so it is just another transport protocol, 
>> transaction protocol or whatever. There are other IETF defined 
>> solutions in this space.
>>
>> So while the original author never progressed his original request, in 
>> that he never asked for it to become a WG item or proposed that it 
>> should go forward as an individual draft (and it died because the 
>> author failed to refresh it), it would probably fail to progress (I 
>> daren't say never as they will then prove me wrong), the former 
>> because the charter of the WG would never be extended to cover it, and 
>> the latter at the IESG review stage.
>>
>> If there is any reason for progressing this, then the proponents need 
>> to clearly distinguish a reason for putting it in SIP that relates to 
>> SIP as a Session Initiation Protocol.
>>
>> regards
>>
>> Keith
>>
>>
>>
>> > -----Original Message-----
>> > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
>> > Sent: 19 November 2003 14:47
>> > To: 'Richard Shockey'
>> > Cc: sipping@ietf.org
>> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>> >
>> >
>> > Ignorance awakens in the dawn of reality.
>> >
>> > SIP needs a formal methodology for obtaining a TCAP query.
>> > Whether the SS7 providers does this with their signaling
>> > gateway or not is not the issue.  A formalized approach that
>> > a vendor can implement is the point that is being raised.
>> >
>> >
>> >
>> > > -----Original Message-----
>> > > From: Richard Shockey [mailto:richard@shockey.us]
>> > > Sent: Tuesday, November 18, 2003 3:09 PM
>> > > To: sipping@ietf.org
>> > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
>> > >
>> > >
>> > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
>> > >
>> > > As the distributor of the NO TCAP buttons on generous display
>> > > at IETF 59
>> > > and fine trade shows nationwide , let me comment that this is
>> > > one of the
>> > > silliest ideas I have yet seen cross the SIPPING landscape.
>> > >
>> > > Why ..why on earth would you want to do this ..any query
>> > > response mechanism
>> > > can get you the data points necessary without the baggage
>> > > TCAP puts you
>> > > through.
>> > >
>> > > Talk to your SS7 vendor and demand better service or fire
>> > > them. Get them to
>> > > support SIP itself  query response mechanism. Send an INVITE
>> > > expect a 302
>> > > MOVE in response and encapsulate SS7 the data as part of a
>> > > TEL URL in the
>> > > response.
>> > >
>> > > This is a "bad idea" tm worthy of the big gong and hook.
>> > >
>> > >
>> > > >
>> > > >Aiieee, a cross is raised!!  ;)
>> > > >
>> > > >Anyway, you're right, the format doesn't matter at all,
>> > > except for one
>> > > >thing.  Expedience.  The essence of the argument against
>> > > this type of
>> > > >draft in general, i.e. one that uses INFO to carry anything,
>> > > is usually
>> > > >based on the fact that the content is application specific
>> > > and so doesn't
>> > > >fit with the base SIP protocol.  I can understand that and
>> > > accept it, it
>> > > >really doesn't matter to me.  I'm an implementor, not a protocol
>> > > >specifier.  Unfortunately, the protocol doesn't do
>> > > everything I need it to
>> > > >do so I have to add stuff to fill in the holes when I take
>> > > it into the
>> > > >real world.  The other draft in this area
>> > > draft-miller-sip-isup-annex is
>> > > >another example of augmentation, the addition of ISUP
>> > > maintenance commands
>> > > >to the ISUP translation now RFC.  I could write/buy an SS7
>> > > implementation
>> > > >and template the messages and hook that into my
>> > > CNAME/LNP/whatever at the
>> > > >call control layer and to SCTP/UDP/whatever on the network
>> > > side but why,
>> > > >to keep the SIP implementation "beautiful"?  The bottom line
>> > > is I'm not
>> > > >going to pass the cost of the SS7 stack on to my customers
>> > > if I can make a
>> > > >simple addition to the SIP stuff and do exactly the same
>> > > thing basically
>> > > >for free.
>> > > >
>> > > >Now with respect to the specifics of the encoding, we can
>> > > certainly talk
>> > > >about anything.  That was the whole reason for publishing
>> > > the work in the
>> > > >IETF to begin with.  On 6.1.1.1 specifically, this is
>> > simply a field
>> > > >required in the QWP message.  The actual digits are
>> > > specified in a string
>> > > >not in BCD binary.  The Signaling
>> > > Gateway/Softswitch/whatever just picks
>> > > >up BCD from the Encoding field and fills in the appropriate
>> > > value in the
>> > > >actual TCAP binary message when the translation is done.
>> > > The digits in
>> > > >the ASCII string are converted similarly to BCD format in
>> > > the TCAP binary
>> > > >message also at that time.  The <Encoding  > field doesn't
>> > > change and is
>> > > >therefore a perfect candidate for being templated.  The only real
>> > > >information that needs to be handled per query here is the
>> > > actual number.
>> > > >
>> > > >FM
>> > > >
>> > > >
>> > > >
>> > > >Frank W. Miller, Ph.D.
>> > > >Chief Technical Officer
>> > > >sentitO Networks, Inc.
>> > > >fmiller@sentito.com
>> > > >
>> > > >-----Original Message-----
>> > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
>> > > >Sent: Tuesday, November 18, 2003 3:14 PM
>> > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
>> > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
>> > > >Subject: RE: [Sip] Sip support for TCAP queries
>> > > >
>> > > >  [Moving this thread to SIPPING, where it belongs]
>> > > >
>> > > >Leaving aside the question of whether or not ENUM supports
>> > > all of the
>> > > >functions of TCAP, the main issue is whether or not SIP is
>> > > the right sort
>> > > >of protocol to handle this function. A query-response
>> > protocol that
>> > > >carries XML documents from a client to a server? Does SIP
>> > > INFO really seem
>> > > >to map onto that well? Aren't there other protocols that
>> > are tooled
>> > > >specifically to that purpose?
>> > > >
>> > > >Furthermore, is the encoding really the issue? XML vs.
>> > > binary doesn't seem
>> > > >that significant to me - if a SIP endpoint can template the
>> > > XML format, it
>> > > >could template the binary format as well. Regardless of the
>> > > syntax, should
>> > > >we expect SIP endpoints to understand the semantics of TCAP?
>> > > Do we expect
>> > > >a SIP user agent to understand and implement the concept of,
>> > > say, a code
>> > > >gap? That isn't "translation" in any sense that I recognize
>> > > - it is closer
>> > > >to saying that SIP user agents have to run a dual stack (SIP
>> > > and TCAP).
>> > > >Just look at the <Digits> stanza of the example in 6.1.1.1
>> > > of the draft:
>> > > >what sorts of SIP elements are going to understand binary
>> > > coded decimal,
>> > > >recognize numbering plans, and the like? If the answer is
>> > > "only PSTN-SIP
>> > > >gateways with that already have SS7 links and could
>> > > therefore just send
>> > > >TCAP queries over SS7", then I think there is a design issue here.
>> > > >
>> > > >Jon Peterson
>> > > >NeuStar, Inc.
>> > > >-----Original Message-----
>> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
>> > > >Sent: Tuesday, November 18, 2003 8:50 AM
>> > > >To: 'Chong, Koan S, ALABS'
>> > > >Cc: sip@ietf.org
>> > > >Subject: RE: [Sip] Sip support for TCAP queries
>> > > >
>> > > >The main idea of this draft was to provide a capability for
>> > > SIP endpoints
>> > > >to do TCAP queries without having to implement the binary TCAP
>> > > >protocol.  The motivation is that there are a lot of TCAP
>> > > queries that
>> > > >take place (800, LNP, CNAME) that are really simple and that major
>> > > >carriers may not want to go and reimplement in an ENUM
>> > > database in the
>> > > >short term.  These carriers have spent a lot of money on
>> > > their SCPs and
>> > > >converting the to ENUM is non-trivial.  Now, the SCPs could
>> > > be front-ended
>> > > >and conversion can be automated but this draft provides an
>> > > >alternative.  So, to answer the first question, the SIP
>> > > endpoint formats
>> > > >the correct query in the XML format specified and sends if
>> > > using an INFO
>> > > >to a Signaling Gateway (SG).  The SG then converts the query
>> > > to binary
>> > > >TCAP and dips the SCP.  The XML format can be templated in the
>> > > >implementation so the effort is quite minimal on the SIP
>> > > endpoint.  To
>> > > >answer the second question, the draft talks about a couple
>> > > of examples but
>> > > >the specification encompasses the entire TCAP message set
>> > so you can
>> > > >format the appropriate dip for AR/C.  One caveat is that the
>> > > draft is
>> > > >Telcordia based.  It would need to be extended to take into
>> > > account other
>> > > >variants.  On the third question, <personal view> I'm a
>> > believer in
>> > > >translation over tunneling, tunneling just puts off work and mixes
>> > > >messaging from different signaling networks
>> > > unnecessarily</personal view>.
>> > > >
>> > > >FM
>> > > >
>> > > >
>> > > >
>> > > >Frank W. Miller, Ph.D.
>> > > >Chief Technical Officer
>> > > >sentitO Networks, Inc.
>> > > >fmiller@sentito.com
>> > > >
>> > > >-----Original Message-----
>> > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
>> > > >Sent: Tuesday, November 18, 2003 11:27 AM
>> > > >To: Frank W. Miller; McCandless, Kevin
>> > > >Cc: sip@ietf.org
>> > > >Subject: RE: [Sip] Sip support for TCAP queries
>> > > >
>> > > >
>> > > >A couple specific questions:
>> > > >
>> > > >What is the recommendation on how a SIP network element can
>> > > access the
>> > > >callers' name databases (CNAM in US) in PSTN after the SIP
>> > > element has
>> > > >determined that the called parties have subscribed to Caller ID?
>> > > >
>> > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
>> > > in ITU?)
>> > > >procedures?
>> > > >
>> > > >Assume TCAP over SIGTRAN is a bit long long term....
>> > > >
>> > > >Koan
>> > > >Koan S.Chong
>> > > >AT&T
>> > > >1-732-420-4557
>> > > >
>> > > >-----Original Message-----
>> > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
>> > > >Sent: Monday, November 17, 2003 6:18 PM
>> > > >To: 'McCandless, Kevin'
>> > > >Cc: sip@ietf.org
>> > > >Subject: RE: [Sip] Sip support for TCAP queries
>> > > >
>> > > >You mean other than us implementing it?  No, I don't think
>> > > so.  I think
>> > > >its considered Rosemary's Baby by most...
>> > > >
>> > > >FM
>> > > >
>> > > >
>> > > >Frank W. Miller, Ph.D.
>> > > >Chief Technical Officer
>> > > >sentitO Networks, Inc.
>> > > >fmiller@sentito.com
>> > > >
>> > > >-----Original Message-----
>> > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
>> > > >McCandless, Kevin
>> > > >Sent: Monday, November 17, 2003 4:11 PM
>> > > >To: sip@ietf.org
>> > > >Subject: [Sip] Sip support for TCAP queries
>> > > >
>> > > >Has any progress been taken on the draft by Frank Miller on
>> > > Carrying TCAP
>> > > >in SIP messages?  Are there other drafts that address SIP
>> > > access to SS7
>> > > >database information through TCAP or another method?
>> > > >
>> > > >Thanks,
>> > > >
>> > > >Kevin
>> > >
>> > >
>> > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
>> > > NeuStar Inc.
>> > > 46000 Center Oak Plaza  -   Sterling, VA  20166
>> > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
>> > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
>> > > Fax: +1 815.333.1237
>> > > <mailto:richard(at)shockey.us> or
>> > > <mailto:richard.shockey(at)neustar.biz>
>> > >
>> > <http://www.neustar.biz> ; <http://www.enum.org>
>> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>> >
>> >
>> > _______________________________________________
>> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> > This list is for NEW development of the application of SIP
>> > Use sip-implementors@cs.columbia.edu for questions on current sip
>> > Use sip@ietf.org for new developments of core SIP
>> >
>> > _______________________________________________
>> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> > This list is for NEW development of the application of SIP
>> > Use sip-implementors@cs.columbia.edu for questions on current sip
>> > Use sip@ietf.org for new developments of core SIP
>> >
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 16:23:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13066
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 16:23:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZn8-0000WA-Gm
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 16:23:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJLNEu3001987
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 16:23:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZn8-0000Vy-7c
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 16:23:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13045
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 16:23:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZn6-0002dX-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 16:23:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZn5-0002dU-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 16:23:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZmv-0000Uq-GH; Wed, 19 Nov 2003 16:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMZmK-0000UK-2q
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 16:22:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13016
	for <sipping@ietf.org>; Wed, 19 Nov 2003 16:22:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZmI-0002cs-00
	for sipping@ietf.org; Wed, 19 Nov 2003 16:22:22 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMZmH-0002bs-00
	for sipping@ietf.org; Wed, 19 Nov 2003 16:22:21 -0500
Received: from cisco.com (64.102.124.12)
  by sj-iport-5.cisco.com with ESMTP; 19 Nov 2003 13:22:26 -0800
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAJLLlxg015825;
	Wed, 19 Nov 2003 16:21:47 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AUP39310;
	Wed, 19 Nov 2003 13:21:46 -0800 (PST)
Message-Id: <4.3.2.7.2.20031119160920.0304bea0@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 19 Nov 2003 16:21:46 -0500
To: "Tolga Asveren" <asveren@ulticom.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Cc: "Drage, Keith \(Keith\)" <drage@lucent.com>,
        "'McCandless, Kevin'" <KMcCandless@verisign.com>, <sipping@ietf.org>
In-Reply-To: <GBEBKGPKHGPAOFCLBNAMCEFKCCAA.asveren@ulticom.com>
References: <4.3.2.7.2.20031119143000.00b527b0@cia.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Tolga,

Your point about RPC semantic is well taken, but I was glossing over that 
to get to the heart of the matter, which is what is being carried that we 
would still care about in a SIP network.  The "call models" are different, 
so I don't expect such things to survive as they currently exist.  But, are 
there other things there needed to support end-user services that would be 
gaps in the current Internet architectural scheme.  Or put another way, 
will the SS7 network be kept around because access to SS7-based SCPs will 
still be needed because equivalent service capabilities can't be done in 
SIP?  I don't like the Frankenstein approach to building services.

Mike


At 03:36 PM 11/19/2003 -0500, Tolga Asveren wrote:
> > -----Original Message-----
> > From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> > Michael Hammer
> > Sent: Wednesday, November 19, 2003 2:50 PM
> > To: Drage, Keith (Keith)
> > Cc: 'McCandless, Kevin'; sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> >
> >
> > Keith,
> >
> > This is not to support the current suggestion but to get more
> > clarification
> > taking a long-range view of (Internet/PSTN) network(s) evolution.
> >
> > Two cases in point:
> > 1) TCAP carried registration messages for mobile systems, yet the
> > equivalent is now done by SIP REGISTER method, which may eventually
> > displace the former TCAP-carried methods.
> > 2) Camp-on indications currently carried by TCAP that translate
> > (partially)
> > into SUBSCRIBE/NOTIFY.  Recall the previous request to expand SIP
> > to carry
> > some additional CCBS indications.
> >
> > I see TCAP as being more like the transport protocols that underlies SIP,
> > so am not sure that all of that functionality needs to survive (carried
> > over) into the IP world.
>[TOLGA]In fact it is SCCP, which is the transport protocol for such messages
>in SS7 world. TCAP is more like an asynchronous RPC mechanism (for example
>similar to SOAP over HTTP), and does not have direct application semantic.
> >
> > The question I have is whether the stuff inside of TCAP messages evolves
> > from an SS7-world application to an IETF application?
>[TOLGA]Personally I don't think so, because SIP is really a totally
>different paradigm. For example, do we foresee to have a call model similar
>to BCSM for SIP, which would make INAP/AIN meaningfull for SIP?
> >
> > Put another way, if the TCAP and above stuff is migrated to
> > TCAP/SUA/SCTP/IP, and the SS7 network as we know it today
> > eventually fades
> > away, does that make the TCAP and above stuff Internet protocols?
>[TOLGA] Again my personal opinion, "Internet protocols" probably
>yes -afterall Internet is not just SIP- , but I would think, when SS7 fades
>away, there won't be need for the stuff above TCAP in the pure SIP network.
>IMO, even today, they are mostly necessary just for gateways, because SS7
>concepts are still present at them -they are a node in SS7 network-.
> >
> > Mike
> >
> >
> > At 07:01 PM 11/19/2003 +0000, Drage, Keith (Keith) wrote:
> > >I dont see any justification here.
> > >
> > >The only sense I can make of the proposal so far is that SIP is
> > used as a
> > >means of transporting TCAP from one place to another. It is not
> > a case the
> > >protocol being used to make a SIP request, and the TCAP information
> > >enhancing that request.
> > >
> > >The IETF will not extend SIP so it is just another transport protocol,
> > >transaction protocol or whatever. There are other IETF defined solutions
> > >in this space.
> > >
> > >So while the original author never progressed his original request, in
> > >that he never asked for it to become a WG item or proposed that
> > it should
> > >go forward as an individual draft (and it died because the author failed
> > >to refresh it), it would probably fail to progress (I daren't
> > say never as
> > >they will then prove me wrong), the former because the charter of the WG
> > >would never be extended to cover it, and the latter at the IESG
> > review stage.
> > >
> > >If there is any reason for progressing this, then the proponents need to
> > >clearly distinguish a reason for putting it in SIP that relates
> > to SIP as
> > >a Session Initiation Protocol.
> > >
> > >regards
> > >
> > >Keith
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > > > Sent: 19 November 2003 14:47
> > > > To: 'Richard Shockey'
> > > > Cc: sipping@ietf.org
> > > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > >
> > > >
> > > > Ignorance awakens in the dawn of reality.
> > > >
> > > > SIP needs a formal methodology for obtaining a TCAP query.
> > > > Whether the SS7 providers does this with their signaling
> > > > gateway or not is not the issue.  A formalized approach that
> > > > a vendor can implement is the point that is being raised.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Richard Shockey [mailto:richard@shockey.us]
> > > > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > > > To: sipping@ietf.org
> > > > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >
> > > > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > > >
> > > > > As the distributor of the NO TCAP buttons on generous display
> > > > > at IETF 59
> > > > > and fine trade shows nationwide , let me comment that this is
> > > > > one of the
> > > > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > > >
> > > > > Why ..why on earth would you want to do this ..any query
> > > > > response mechanism
> > > > > can get you the data points necessary without the baggage
> > > > > TCAP puts you
> > > > > through.
> > > > >
> > > > > Talk to your SS7 vendor and demand better service or fire
> > > > > them. Get them to
> > > > > support SIP itself  query response mechanism. Send an INVITE
> > > > > expect a 302
> > > > > MOVE in response and encapsulate SS7 the data as part of a
> > > > > TEL URL in the
> > > > > response.
> > > > >
> > > > > This is a "bad idea" tm worthy of the big gong and hook.
> > > > >
> > > > >
> > > > > >
> > > > > >Aiieee, a cross is raised!!  ;)
> > > > > >
> > > > > >Anyway, you're right, the format doesn't matter at all,
> > > > > except for one
> > > > > >thing.  Expedience.  The essence of the argument against
> > > > > this type of
> > > > > >draft in general, i.e. one that uses INFO to carry anything,
> > > > > is usually
> > > > > >based on the fact that the content is application specific
> > > > > and so doesn't
> > > > > >fit with the base SIP protocol.  I can understand that and
> > > > > accept it, it
> > > > > >really doesn't matter to me.  I'm an implementor, not a protocol
> > > > > >specifier.  Unfortunately, the protocol doesn't do
> > > > > everything I need it to
> > > > > >do so I have to add stuff to fill in the holes when I take
> > > > > it into the
> > > > > >real world.  The other draft in this area
> > > > > draft-miller-sip-isup-annex is
> > > > > >another example of augmentation, the addition of ISUP
> > > > > maintenance commands
> > > > > >to the ISUP translation now RFC.  I could write/buy an SS7
> > > > > implementation
> > > > > >and template the messages and hook that into my
> > > > > CNAME/LNP/whatever at the
> > > > > >call control layer and to SCTP/UDP/whatever on the network
> > > > > side but why,
> > > > > >to keep the SIP implementation "beautiful"?  The bottom line
> > > > > is I'm not
> > > > > >going to pass the cost of the SS7 stack on to my customers
> > > > > if I can make a
> > > > > >simple addition to the SIP stuff and do exactly the same
> > > > > thing basically
> > > > > >for free.
> > > > > >
> > > > > >Now with respect to the specifics of the encoding, we can
> > > > > certainly talk
> > > > > >about anything.  That was the whole reason for publishing
> > > > > the work in the
> > > > > >IETF to begin with.  On 6.1.1.1 specifically, this is
> > > > simply a field
> > > > > >required in the QWP message.  The actual digits are
> > > > > specified in a string
> > > > > >not in BCD binary.  The Signaling
> > > > > Gateway/Softswitch/whatever just picks
> > > > > >up BCD from the Encoding field and fills in the appropriate
> > > > > value in the
> > > > > >actual TCAP binary message when the translation is done.
> > > > > The digits in
> > > > > >the ASCII string are converted similarly to BCD format in
> > > > > the TCAP binary
> > > > > >message also at that time.  The <Encoding  > field doesn't
> > > > > change and is
> > > > > >therefore a perfect candidate for being templated.  The only real
> > > > > >information that needs to be handled per query here is the
> > > > > actual number.
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >  [Moving this thread to SIPPING, where it belongs]
> > > > > >
> > > > > >Leaving aside the question of whether or not ENUM supports
> > > > > all of the
> > > > > >functions of TCAP, the main issue is whether or not SIP is
> > > > > the right sort
> > > > > >of protocol to handle this function. A query-response
> > > > protocol that
> > > > > >carries XML documents from a client to a server? Does SIP
> > > > > INFO really seem
> > > > > >to map onto that well? Aren't there other protocols that
> > > > are tooled
> > > > > >specifically to that purpose?
> > > > > >
> > > > > >Furthermore, is the encoding really the issue? XML vs.
> > > > > binary doesn't seem
> > > > > >that significant to me - if a SIP endpoint can template the
> > > > > XML format, it
> > > > > >could template the binary format as well. Regardless of the
> > > > > syntax, should
> > > > > >we expect SIP endpoints to understand the semantics of TCAP?
> > > > > Do we expect
> > > > > >a SIP user agent to understand and implement the concept of,
> > > > > say, a code
> > > > > >gap? That isn't "translation" in any sense that I recognize
> > > > > - it is closer
> > > > > >to saying that SIP user agents have to run a dual stack (SIP
> > > > > and TCAP).
> > > > > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > > > > of the draft:
> > > > > >what sorts of SIP elements are going to understand binary
> > > > > coded decimal,
> > > > > >recognize numbering plans, and the like? If the answer is
> > > > > "only PSTN-SIP
> > > > > >gateways with that already have SS7 links and could
> > > > > therefore just send
> > > > > >TCAP queries over SS7", then I think there is a design issue here.
> > > > > >
> > > > > >Jon Peterson
> > > > > >NeuStar, Inc.
> > > > > >-----Original Message-----
> > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > > > >To: 'Chong, Koan S, ALABS'
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >The main idea of this draft was to provide a capability for
> > > > > SIP endpoints
> > > > > >to do TCAP queries without having to implement the binary TCAP
> > > > > >protocol.  The motivation is that there are a lot of TCAP
> > > > > queries that
> > > > > >take place (800, LNP, CNAME) that are really simple and that major
> > > > > >carriers may not want to go and reimplement in an ENUM
> > > > > database in the
> > > > > >short term.  These carriers have spent a lot of money on
> > > > > their SCPs and
> > > > > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > > > > be front-ended
> > > > > >and conversion can be automated but this draft provides an
> > > > > >alternative.  So, to answer the first question, the SIP
> > > > > endpoint formats
> > > > > >the correct query in the XML format specified and sends if
> > > > > using an INFO
> > > > > >to a Signaling Gateway (SG).  The SG then converts the query
> > > > > to binary
> > > > > >TCAP and dips the SCP.  The XML format can be templated in the
> > > > > >implementation so the effort is quite minimal on the SIP
> > > > > endpoint.  To
> > > > > >answer the second question, the draft talks about a couple
> > > > > of examples but
> > > > > >the specification encompasses the entire TCAP message set
> > > > so you can
> > > > > >format the appropriate dip for AR/C.  One caveat is that the
> > > > > draft is
> > > > > >Telcordia based.  It would need to be extended to take into
> > > > > account other
> > > > > >variants.  On the third question, <personal view> I'm a
> > > > believer in
> > > > > >translation over tunneling, tunneling just puts off work and mixes
> > > > > >messaging from different signaling networks
> > > > > unnecessarily</personal view>.
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > > > >To: Frank W. Miller; McCandless, Kevin
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >
> > > > > >A couple specific questions:
> > > > > >
> > > > > >What is the recommendation on how a SIP network element can
> > > > > access the
> > > > > >callers' name databases (CNAM in US) in PSTN after the SIP
> > > > > element has
> > > > > >determined that the called parties have subscribed to Caller ID?
> > > > > >
> > > > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > > > > in ITU?)
> > > > > >procedures?
> > > > > >
> > > > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > > > >
> > > > > >Koan
> > > > > >Koan S.Chong
> > > > > >AT&T
> > > > > >1-732-420-4557
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > >Sent: Monday, November 17, 2003 6:18 PM
> > > > > >To: 'McCandless, Kevin'
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >You mean other than us implementing it?  No, I don't think
> > > > > so.  I think
> > > > > >its considered Rosemary's Baby by most...
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of
> > > > > >McCandless, Kevin
> > > > > >Sent: Monday, November 17, 2003 4:11 PM
> > > > > >To: sip@ietf.org
> > > > > >Subject: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >Has any progress been taken on the draft by Frank Miller on
> > > > > Carrying TCAP
> > > > > >in SIP messages?  Are there other drafts that address SIP
> > > > > access to SS7
> > > > > >database information through TCAP or another method?
> > > > > >
> > > > > >Thanks,
> > > > > >
> > > > > >Kevin
> > > > >
> > > > >
> > > > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > > > Richard Shockey, Senior Manager, Strategic Technology Initiatives
> > > > > NeuStar Inc.
> > > > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > > > > Fax: +1 815.333.1237
> > > > > <mailto:richard(at)shockey.us> or
> > > > > <mailto:richard.shockey(at)neustar.biz>
> > > > >
> > > > <http://www.neustar.biz> ; <http://www.enum.org>
> > > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > >
> > >_______________________________________________
> > >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > >This list is for NEW development of the application of SIP
> > >Use sip-implementors@cs.columbia.edu for questions on current sip
> > >Use sip@ietf.org for new developments of core SIP
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 16:44:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14712
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 16:44:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMa7L-0001dp-9F
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 16:44:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJLi75f006303
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 16:44:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMa7L-0001da-4Q
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 16:44:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14699
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 16:43:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMa7I-0003E4-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 16:44:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMa7I-0003E1-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 16:44:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMa7F-0001cJ-BM; Wed, 19 Nov 2003 16:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMa6K-0001aC-A8
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 16:43:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14659
	for <sipping@ietf.org>; Wed, 19 Nov 2003 16:42:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMa6I-0003DF-00
	for sipping@ietf.org; Wed, 19 Nov 2003 16:43:02 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMa6H-0003D6-00
	for sipping@ietf.org; Wed, 19 Nov 2003 16:43:01 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id QAA17667;
	Wed, 19 Nov 2003 16:41:37 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Michael Hammer" <mhammer@cisco.com>
Cc: "Drage, Keith \(Keith\)" <drage@lucent.com>,
        "'McCandless, Kevin'" <KMcCandless@verisign.com>, <sipping@ietf.org>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 16:41:21 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMGEFLCCAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20031119160920.0304bea0@cia.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Michael Hammer
> Sent: Wednesday, November 19, 2003 4:22 PM
> To: Tolga Asveren
> Cc: Drage, Keith (Keith); 'McCandless, Kevin'; sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>
>
> Tolga,
>
> Your point about RPC semantic is well taken, but I was glossing over that
> to get to the heart of the matter, which is what is being carried that we
> would still care about in a SIP network.  The "call models" are
> different,
> so I don't expect such things to survive as they currently exist.
>  But, are
> there other things there needed to support end-user services that
> would be
> gaps in the current Internet architectural scheme.  Or put another way,
> will the SS7 network be kept around because access to SS7-based SCPs will
> still be needed because equivalent service capabilities can't be done in
> SIP?  I don't like the Frankenstein approach to building services.
[TOLGA]Maybe not just with SIP, but I would think with SIP + other Internet
protocols, one can implement existing PSTN services (I am not saying I am
sure, I did not go throught the whole list yet :) )  And to reuse existing
equipment during transition period(for example existing SCP database), I
would think one has to use the protocol supported by that equipment.
>
> Mike
>
>
> At 03:36 PM 11/19/2003 -0500, Tolga Asveren wrote:
> > > -----Original Message-----
> > > From: sipping-admin@ietf.org
> [mailto:sipping-admin@ietf.org]On Behalf Of
> > > Michael Hammer
> > > Sent: Wednesday, November 19, 2003 2:50 PM
> > > To: Drage, Keith (Keith)
> > > Cc: 'McCandless, Kevin'; sipping@ietf.org
> > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >
> > >
> > > Keith,
> > >
> > > This is not to support the current suggestion but to get more
> > > clarification
> > > taking a long-range view of (Internet/PSTN) network(s) evolution.
> > >
> > > Two cases in point:
> > > 1) TCAP carried registration messages for mobile systems, yet the
> > > equivalent is now done by SIP REGISTER method, which may eventually
> > > displace the former TCAP-carried methods.
> > > 2) Camp-on indications currently carried by TCAP that translate
> > > (partially)
> > > into SUBSCRIBE/NOTIFY.  Recall the previous request to expand SIP
> > > to carry
> > > some additional CCBS indications.
> > >
> > > I see TCAP as being more like the transport protocols that
> underlies SIP,
> > > so am not sure that all of that functionality needs to
> survive (carried
> > > over) into the IP world.
> >[TOLGA]In fact it is SCCP, which is the transport protocol for
> such messages
> >in SS7 world. TCAP is more like an asynchronous RPC mechanism
> (for example
> >similar to SOAP over HTTP), and does not have direct application
> semantic.
> > >
> > > The question I have is whether the stuff inside of TCAP
> messages evolves
> > > from an SS7-world application to an IETF application?
> >[TOLGA]Personally I don't think so, because SIP is really a totally
> >different paradigm. For example, do we foresee to have a call
> model similar
> >to BCSM for SIP, which would make INAP/AIN meaningfull for SIP?
> > >
> > > Put another way, if the TCAP and above stuff is migrated to
> > > TCAP/SUA/SCTP/IP, and the SS7 network as we know it today
> > > eventually fades
> > > away, does that make the TCAP and above stuff Internet protocols?
> >[TOLGA] Again my personal opinion, "Internet protocols" probably
> >yes -afterall Internet is not just SIP- , but I would think,
> when SS7 fades
> >away, there won't be need for the stuff above TCAP in the pure
> SIP network.
> >IMO, even today, they are mostly necessary just for gateways, because SS7
> >concepts are still present at them -they are a node in SS7 network-.
> > >
> > > Mike
> > >
> > >
> > > At 07:01 PM 11/19/2003 +0000, Drage, Keith (Keith) wrote:
> > > >I dont see any justification here.
> > > >
> > > >The only sense I can make of the proposal so far is that SIP is
> > > used as a
> > > >means of transporting TCAP from one place to another. It is not
> > > a case the
> > > >protocol being used to make a SIP request, and the TCAP information
> > > >enhancing that request.
> > > >
> > > >The IETF will not extend SIP so it is just another transport
> protocol,
> > > >transaction protocol or whatever. There are other IETF
> defined solutions
> > > >in this space.
> > > >
> > > >So while the original author never progressed his original
> request, in
> > > >that he never asked for it to become a WG item or proposed that
> > > it should
> > > >go forward as an individual draft (and it died because the
> author failed
> > > >to refresh it), it would probably fail to progress (I daren't
> > > say never as
> > > >they will then prove me wrong), the former because the
> charter of the WG
> > > >would never be extended to cover it, and the latter at the IESG
> > > review stage.
> > > >
> > > >If there is any reason for progressing this, then the
> proponents need to
> > > >clearly distinguish a reason for putting it in SIP that relates
> > > to SIP as
> > > >a Session Initiation Protocol.
> > > >
> > > >regards
> > > >
> > > >Keith
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > > > > Sent: 19 November 2003 14:47
> > > > > To: 'Richard Shockey'
> > > > > Cc: sipping@ietf.org
> > > > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >
> > > > > Ignorance awakens in the dawn of reality.
> > > > >
> > > > > SIP needs a formal methodology for obtaining a TCAP query.
> > > > > Whether the SS7 providers does this with their signaling
> > > > > gateway or not is not the issue.  A formalized approach that
> > > > > a vendor can implement is the point that is being raised.
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Richard Shockey [mailto:richard@shockey.us]
> > > > > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > > > > To: sipping@ietf.org
> > > > > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >
> > > > > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > > > >
> > > > > > As the distributor of the NO TCAP buttons on generous display
> > > > > > at IETF 59
> > > > > > and fine trade shows nationwide , let me comment that this is
> > > > > > one of the
> > > > > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > > > >
> > > > > > Why ..why on earth would you want to do this ..any query
> > > > > > response mechanism
> > > > > > can get you the data points necessary without the baggage
> > > > > > TCAP puts you
> > > > > > through.
> > > > > >
> > > > > > Talk to your SS7 vendor and demand better service or fire
> > > > > > them. Get them to
> > > > > > support SIP itself  query response mechanism. Send an INVITE
> > > > > > expect a 302
> > > > > > MOVE in response and encapsulate SS7 the data as part of a
> > > > > > TEL URL in the
> > > > > > response.
> > > > > >
> > > > > > This is a "bad idea" tm worthy of the big gong and hook.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >Aiieee, a cross is raised!!  ;)
> > > > > > >
> > > > > > >Anyway, you're right, the format doesn't matter at all,
> > > > > > except for one
> > > > > > >thing.  Expedience.  The essence of the argument against
> > > > > > this type of
> > > > > > >draft in general, i.e. one that uses INFO to carry anything,
> > > > > > is usually
> > > > > > >based on the fact that the content is application specific
> > > > > > and so doesn't
> > > > > > >fit with the base SIP protocol.  I can understand that and
> > > > > > accept it, it
> > > > > > >really doesn't matter to me.  I'm an implementor, not
> a protocol
> > > > > > >specifier.  Unfortunately, the protocol doesn't do
> > > > > > everything I need it to
> > > > > > >do so I have to add stuff to fill in the holes when I take
> > > > > > it into the
> > > > > > >real world.  The other draft in this area
> > > > > > draft-miller-sip-isup-annex is
> > > > > > >another example of augmentation, the addition of ISUP
> > > > > > maintenance commands
> > > > > > >to the ISUP translation now RFC.  I could write/buy an SS7
> > > > > > implementation
> > > > > > >and template the messages and hook that into my
> > > > > > CNAME/LNP/whatever at the
> > > > > > >call control layer and to SCTP/UDP/whatever on the network
> > > > > > side but why,
> > > > > > >to keep the SIP implementation "beautiful"?  The bottom line
> > > > > > is I'm not
> > > > > > >going to pass the cost of the SS7 stack on to my customers
> > > > > > if I can make a
> > > > > > >simple addition to the SIP stuff and do exactly the same
> > > > > > thing basically
> > > > > > >for free.
> > > > > > >
> > > > > > >Now with respect to the specifics of the encoding, we can
> > > > > > certainly talk
> > > > > > >about anything.  That was the whole reason for publishing
> > > > > > the work in the
> > > > > > >IETF to begin with.  On 6.1.1.1 specifically, this is
> > > > > simply a field
> > > > > > >required in the QWP message.  The actual digits are
> > > > > > specified in a string
> > > > > > >not in BCD binary.  The Signaling
> > > > > > Gateway/Softswitch/whatever just picks
> > > > > > >up BCD from the Encoding field and fills in the appropriate
> > > > > > value in the
> > > > > > >actual TCAP binary message when the translation is done.
> > > > > > The digits in
> > > > > > >the ASCII string are converted similarly to BCD format in
> > > > > > the TCAP binary
> > > > > > >message also at that time.  The <Encoding  > field doesn't
> > > > > > change and is
> > > > > > >therefore a perfect candidate for being templated.
> The only real
> > > > > > >information that needs to be handled per query here is the
> > > > > > actual number.
> > > > > > >
> > > > > > >FM
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >Frank W. Miller, Ph.D.
> > > > > > >Chief Technical Officer
> > > > > > >sentitO Networks, Inc.
> > > > > > >fmiller@sentito.com
> > > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > > > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > > > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > > > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > > >
> > > > > > >  [Moving this thread to SIPPING, where it belongs]
> > > > > > >
> > > > > > >Leaving aside the question of whether or not ENUM supports
> > > > > > all of the
> > > > > > >functions of TCAP, the main issue is whether or not SIP is
> > > > > > the right sort
> > > > > > >of protocol to handle this function. A query-response
> > > > > protocol that
> > > > > > >carries XML documents from a client to a server? Does SIP
> > > > > > INFO really seem
> > > > > > >to map onto that well? Aren't there other protocols that
> > > > > are tooled
> > > > > > >specifically to that purpose?
> > > > > > >
> > > > > > >Furthermore, is the encoding really the issue? XML vs.
> > > > > > binary doesn't seem
> > > > > > >that significant to me - if a SIP endpoint can template the
> > > > > > XML format, it
> > > > > > >could template the binary format as well. Regardless of the
> > > > > > syntax, should
> > > > > > >we expect SIP endpoints to understand the semantics of TCAP?
> > > > > > Do we expect
> > > > > > >a SIP user agent to understand and implement the concept of,
> > > > > > say, a code
> > > > > > >gap? That isn't "translation" in any sense that I recognize
> > > > > > - it is closer
> > > > > > >to saying that SIP user agents have to run a dual stack (SIP
> > > > > > and TCAP).
> > > > > > >Just look at the <Digits> stanza of the example in 6.1.1.1
> > > > > > of the draft:
> > > > > > >what sorts of SIP elements are going to understand binary
> > > > > > coded decimal,
> > > > > > >recognize numbering plans, and the like? If the answer is
> > > > > > "only PSTN-SIP
> > > > > > >gateways with that already have SS7 links and could
> > > > > > therefore just send
> > > > > > >TCAP queries over SS7", then I think there is a design
> issue here.
> > > > > > >
> > > > > > >Jon Peterson
> > > > > > >NeuStar, Inc.
> > > > > > >-----Original Message-----
> > > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > > > > >To: 'Chong, Koan S, ALABS'
> > > > > > >Cc: sip@ietf.org
> > > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > > >
> > > > > > >The main idea of this draft was to provide a capability for
> > > > > > SIP endpoints
> > > > > > >to do TCAP queries without having to implement the binary TCAP
> > > > > > >protocol.  The motivation is that there are a lot of TCAP
> > > > > > queries that
> > > > > > >take place (800, LNP, CNAME) that are really simple
> and that major
> > > > > > >carriers may not want to go and reimplement in an ENUM
> > > > > > database in the
> > > > > > >short term.  These carriers have spent a lot of money on
> > > > > > their SCPs and
> > > > > > >converting the to ENUM is non-trivial.  Now, the SCPs could
> > > > > > be front-ended
> > > > > > >and conversion can be automated but this draft provides an
> > > > > > >alternative.  So, to answer the first question, the SIP
> > > > > > endpoint formats
> > > > > > >the correct query in the XML format specified and sends if
> > > > > > using an INFO
> > > > > > >to a Signaling Gateway (SG).  The SG then converts the query
> > > > > > to binary
> > > > > > >TCAP and dips the SCP.  The XML format can be templated in the
> > > > > > >implementation so the effort is quite minimal on the SIP
> > > > > > endpoint.  To
> > > > > > >answer the second question, the draft talks about a couple
> > > > > > of examples but
> > > > > > >the specification encompasses the entire TCAP message set
> > > > > so you can
> > > > > > >format the appropriate dip for AR/C.  One caveat is that the
> > > > > > draft is
> > > > > > >Telcordia based.  It would need to be extended to take into
> > > > > > account other
> > > > > > >variants.  On the third question, <personal view> I'm a
> > > > > believer in
> > > > > > >translation over tunneling, tunneling just puts off
> work and mixes
> > > > > > >messaging from different signaling networks
> > > > > > unnecessarily</personal view>.
> > > > > > >
> > > > > > >FM
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >Frank W. Miller, Ph.D.
> > > > > > >Chief Technical Officer
> > > > > > >sentitO Networks, Inc.
> > > > > > >fmiller@sentito.com
> > > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > > > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > > > > >To: Frank W. Miller; McCandless, Kevin
> > > > > > >Cc: sip@ietf.org
> > > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > > >
> > > > > > >
> > > > > > >A couple specific questions:
> > > > > > >
> > > > > > >What is the recommendation on how a SIP network element can
> > > > > > access the
> > > > > > >callers' name databases (CNAM in US) in PSTN after the SIP
> > > > > > element has
> > > > > > >determined that the called parties have subscribed to
> Caller ID?
> > > > > > >
> > > > > > >How about interworking with CLASS Auto-Recall/Callback (CCBS
> > > > > > in ITU?)
> > > > > > >procedures?
> > > > > > >
> > > > > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > > > > >
> > > > > > >Koan
> > > > > > >Koan S.Chong
> > > > > > >AT&T
> > > > > > >1-732-420-4557
> > > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > > >Sent: Monday, November 17, 2003 6:18 PM
> > > > > > >To: 'McCandless, Kevin'
> > > > > > >Cc: sip@ietf.org
> > > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > > >
> > > > > > >You mean other than us implementing it?  No, I don't think
> > > > > > so.  I think
> > > > > > >its considered Rosemary's Baby by most...
> > > > > > >
> > > > > > >FM
> > > > > > >
> > > > > > >
> > > > > > >Frank W. Miller, Ph.D.
> > > > > > >Chief Technical Officer
> > > > > > >sentitO Networks, Inc.
> > > > > > >fmiller@sentito.com
> > > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]
> On Behalf Of
> > > > > > >McCandless, Kevin
> > > > > > >Sent: Monday, November 17, 2003 4:11 PM
> > > > > > >To: sip@ietf.org
> > > > > > >Subject: [Sip] Sip support for TCAP queries
> > > > > > >
> > > > > > >Has any progress been taken on the draft by Frank Miller on
> > > > > > Carrying TCAP
> > > > > > >in SIP messages?  Are there other drafts that address SIP
> > > > > > access to SS7
> > > > > > >database information through TCAP or another method?
> > > > > > >
> > > > > > >Thanks,
> > > > > > >
> > > > > > >Kevin
> > > > > >
> > > > > >
> > > > > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > > > > Richard Shockey, Senior Manager, Strategic Technology
> Initiatives
> > > > > > NeuStar Inc.
> > > > > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > > > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > > > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,
> > > > > > Fax: +1 815.333.1237
> > > > > > <mailto:richard(at)shockey.us> or
> > > > > > <mailto:richard.shockey(at)neustar.biz>
> > > > > >
> > > > > <http://www.neustar.biz> ; <http://www.enum.org>
> > > > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sipping mailing list
https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >
> > >
> > >_______________________________________________
> > >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > >This list is for NEW development of the application of SIP
> > >Use sip-implementors@cs.columbia.edu for questions on current sip
> > >Use sip@ietf.org for new developments of core SIP
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 17:25:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18563
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 17:25:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMal9-0003RY-HB
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 17:25:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJMPFJv013233
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 17:25:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMal9-0003RM-Ba
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 17:25:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18531
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 17:24:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMal3-0004li-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 17:25:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMal3-0004lf-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 17:25:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMakx-0003Pk-IV; Wed, 19 Nov 2003 17:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMakW-0003NP-W1
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 17:24:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18474
	for <sipping@ietf.org>; Wed, 19 Nov 2003 17:24:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMakR-0004kK-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:24:31 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMakQ-0004k7-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:24:30 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hAJMNwb9005530;
	Wed, 19 Nov 2003 22:23:58 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHL18Q>; Wed, 19 Nov 2003 16:23:59 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56470@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Tolga Asveren'" <asveren@ulticom.com>,
        "Frank W. Miller"
	 <fmiller@sentito.com>,
        "'Drage, Keith (Keith)'" <drage@lucent.com>
Cc: sipping@ietf.org
Subject: isup maintenance msgs (was RE: [Sipping] RE: [Sip] Sip support fo
	r TCAP queries)
Date: Wed, 19 Nov 2003 16:23:59 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Just to be even more explicit about this point - there are no CICs between
gateways that reside on the Internet. Separate calls between these gateways
are differentiated by the transport-layer (i.e. UDP) port over which RTP is
sent. ISUP maintenance messages (like BLO, say) refer to a particular CIC or
set of CICs. Those indications are necessarily hop-by-hop - they are only
meaningful between the origination and destination point codes for which
they are sent, since the bindings between these CICs and their corresponding
circuits is a matter of arbitrary hop-by-hop convention established by the
switches.

The necessary guidance for translating applicable maintenance conditions
into SIP messages is already given in RFC3398, Section 11, so this was not
overlooked by that document entirely. But what could possibly be the meaning
of sending (via encapsulation) the BLO received by a gateway to some other
gateway on the Internet? Transposing this question to the PSTN, what would
be the meaning of, say, a tandem forwarding a BLO that it received to
another switch? Even if we proceed on the (misguided but least implausble)
assumption that a remote gateway would use these sorts of maintenance
messages as rough indicators of the capacity of its peers, this would still
entail that every gateway has a rough idea of the total number of CICs
supported by every other gateway to which it might connect, which in turn
entails a nightmare of n^2 provision and bilateral associations between
gateways that is, ultimately, redundant with capacity management
capabilities that SIP already possesses.

I would be very interested to hear how a requirement for encapsulating ISUP
maintenance messages in SIP is motivated. The omission of these messages
from our encapsulation strategy was not an oversight, or a "to do" flag.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Tolga Asveren [mailto:asveren@ulticom.com]
> Sent: Wednesday, November 19, 2003 12:16 PM
> To: Frank W. Miller; 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
[snip]
> >
> > Let me be very plain, RFC 3398 is not sufficient.  It lacks support for
ISUP
> > maintenance commands and access to SCPs via TCAP.  These are functions
that
> > are required by vendors and carriers integrating SIP with the existing
PSTN.
> [TOLGA]Why do you need those maintanence messages? Your voice trunks
> terminate at the gateway and it is the gateway, which is interested in
them,
> and which receives them via ISUP. Why do you need to propogate them to a
> pure SIP entity in the network? Why should they care about management of
> circuits, which are physically terminated at the gateway?
> And again for SCP access, if one wants to speak TCAP to them, one needs
> TCAP(over SCCP or over a SIGTRAN protocol like M3UA/SUA etc...). If SCP
> understands it -or if one introduces a TCAP gateway for it-, one also
might
> use something (HTML, SOAP, XML-RPC etc...) over HTTP. I believe, the point
> is, SIP is not a transport protocol.
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 17:40:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18954
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 17:40:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMazZ-0004Kb-DK
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 17:40:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJMe9hO016497
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 17:40:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMazW-0004Hz-Vp
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 17:40:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18943
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 17:39:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMazU-0004yU-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 17:40:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMazU-0004yR-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 17:40:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMazS-0004GZ-K2; Wed, 19 Nov 2003 17:40:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMayg-0004A8-96
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 17:39:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18929
	for <sipping@ietf.org>; Wed, 19 Nov 2003 17:38:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMayd-0004y5-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:39:11 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMayd-0004xs-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:39:11 -0500
Received: from stntimc1.va.neustar.com (stntimc1.neustar.com [10.31.13.11])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hAJMcfb9005768;
	Wed, 19 Nov 2003 22:38:41 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19)
	id <WAAP0QSY>; Wed, 19 Nov 2003 17:38:41 -0500
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD56471@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'McCandless, Kevin'" <KMcCandless@verisign.com>,
        "'Drage, Keith (Keith)'" <drage@lucent.com>
Cc: sipping@ietf.org, "'Frank W. Miller'" <fmiller@sentito.com>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 17:38:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


Relevant - yes, by all means. But in order for these functions to work for
VoIP solutions of which SIP is only a part, there is no requirement for the
SIP protocol itself to obtain this sort of database information. There are
obviously alternatives (one being something like ENUM, another being some
sort of web services architecture).

For trivial applications like number translation (or CNAM), I can understand
why some might insist that this is a feasible thing to do with SIP. As my
colleague Mr. Shockey suggested earlier in this thread,it would be perfectly
reasonable for a SIP redirect server to act as a SIP-TCAP gateway. One might
send an INVITE with a tel URL Request-URI to the gateway and receive a 3xx
reponse with a Contact header containing the translated number. In fact,
this architecture was documented in a now-expired ID, which can still be
found here:

http://www.watersprings.org/pub/id/draft-yu-sip-np-01.txt

At the time, there was not sufficient interest in the WG to push this draft
forward. I got the sense that most people believed it was too obvious to
even require documentation. 

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> Sent: Wednesday, November 19, 2003 12:23 PM
> To: 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org; 'Frank W. Miller'
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> 
> So, CNAM, LNP, and other SS7 data is relevant to working SIP 
> networks that interconnect with the PSTN.  There is no 
> standard document to define how the SIP protocol obtains the 
> database information.  Each vendor is implementing their own 
> way of doing this with SIP on one side during the Invite 
> message and on the other side launching an SS7 query either 
> with M3UA or standard SS7 TDM links.  VoIP carriers want 
> access to the data so would it not be helpful to have a 
> standard way of implementing this interworking.  This has 
> already done for ISUP.  SS7 is not going away and the 
> interworking between VoIP and PSTN can only help the VoIP initiatives.
> 
> > -----Original Message-----
> > From: Frank W. Miller [mailto:fmiller@sentito.com] 
> > Sent: Wednesday, November 19, 2003 1:39 PM
> > To: 'Drage, Keith (Keith)'
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > 
> > 
> > 
> > With all due respect, the reason I didn't ask to have it 
> > considered was I
> > knew that it would never be accepted, so why waste my breath. 
> >  My purpose
> > was to solve a problem that needs addressing.
> > 
> > It cannot be ignored that SIP is making major inroads into 
> > the big carriers
> > and dealing with ISUP and TCAP in a complete way within the 
> > context of SIP
> > is something that needs to happen.  Now, if INFO as transport 
> > for XML isn't
> > palatable, whatever.
> > 
> > Let me be very plain, RFC 3398 is not sufficient.  It lacks 
> > support for ISUP
> > maintenance commands and access to SCPs via TCAP.  These are 
> > functions that
> > are required by vendors and carriers integrating SIP with the 
> > existing PSTN.
> > 
> > I happen to be associated with one of the vendors addressing 
> > these needs at
> > the implementation level.  If the protocol does not serve all 
> > my needs, I
> > will extend it.  If you as protocol specifiers don't like the 
> > way I extend
> > it then put something else in place that I can use.
> > 
> > Hoping to be constructive,
> > FM
> >  
> > 
> > Frank W. Miller, Ph.D.
> > Chief Technical Officer
> > sentitO Networks, Inc.
> > fmiller@sentito.com
> > 
> > 
> > -----Original Message-----
> > From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> > On Behalf Of
> > Drage, Keith (Keith)
> > Sent: Wednesday, November 19, 2003 2:01 PM
> > To: 'McCandless, Kevin'
> > Cc: sipping@ietf.org
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > 
> > I dont see any justification here.
> > 
> > The only sense I can make of the proposal so far is that SIP 
> > is used as a
> > means of transporting TCAP from one place to another. It is 
> > not a case the
> > protocol being used to make a SIP request, and the TCAP information
> > enhancing that request.
> > 
> > The IETF will not extend SIP so it is just another 
> transport protocol,
> > transaction protocol or whatever. There are other IETF 
> > defined solutions in
> > this space.
> > 
> > So while the original author never progressed his original 
> > request, in that
> > he never asked for it to become a WG item or proposed that it 
> > should go
> > forward as an individual draft (and it died because the 
> > author failed to
> > refresh it), it would probably fail to progress (I daren't 
> > say never as they
> > will then prove me wrong), the former because the charter of 
> > the WG would
> > never be extended to cover it, and the latter at the IESG 
> > review stage.
> > 
> > If there is any reason for progressing this, then the 
> > proponents need to
> > clearly distinguish a reason for putting it in SIP that 
> > relates to SIP as a
> > Session Initiation Protocol.
> > 
> > regards
> > 
> > Keith
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > > Sent: 19 November 2003 14:47
> > > To: 'Richard Shockey'
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > 
> > > 
> > > Ignorance awakens in the dawn of reality.
> > > 
> > > SIP needs a formal methodology for obtaining a TCAP query.  
> > > Whether the SS7 providers does this with their signaling 
> > > gateway or not is not the issue.  A formalized approach that 
> > > a vendor can implement is the point that is being raised.
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Richard Shockey [mailto:richard@shockey.us] 
> > > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > > To: sipping@ietf.org
> > > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > > 
> > > > 
> > > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > > 
> > > > As the distributor of the NO TCAP buttons on generous display 
> > > > at IETF 59 
> > > > and fine trade shows nationwide , let me comment that this is 
> > > > one of the 
> > > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > > 
> > > > Why ..why on earth would you want to do this ..any query 
> > > > response mechanism 
> > > > can get you the data points necessary without the baggage 
> > > > TCAP puts you 
> > > > through.
> > > > 
> > > > Talk to your SS7 vendor and demand better service or fire 
> > > > them. Get them to 
> > > > support SIP itself  query response mechanism. Send an INVITE 
> > > > expect a 302 
> > > > MOVE in response and encapsulate SS7 the data as part of a 
> > > > TEL URL in the 
> > > > response.
> > > > 
> > > > This is a "bad idea" tm worthy of the big gong and hook.
> > > > 
> > > > 
> > > > >
> > > > >Aiieee, a cross is raised!!  ;)
> > > > >
> > > > >Anyway, you're right, the format doesn't matter at all, 
> > > > except for one 
> > > > >thing.  Expedience.  The essence of the argument against 
> > > > this type of 
> > > > >draft in general, i.e. one that uses INFO to carry anything, 
> > > > is usually 
> > > > >based on the fact that the content is application specific 
> > > > and so doesn't 
> > > > >fit with the base SIP protocol.  I can understand that and 
> > > > accept it, it 
> > > > >really doesn't matter to me.  I'm an implementor, not 
> a protocol 
> > > > >specifier.  Unfortunately, the protocol doesn't do 
> > > > everything I need it to 
> > > > >do so I have to add stuff to fill in the holes when I take 
> > > > it into the 
> > > > >real world.  The other draft in this area 
> > > > draft-miller-sip-isup-annex is 
> > > > >another example of augmentation, the addition of ISUP 
> > > > maintenance commands 
> > > > >to the ISUP translation now RFC.  I could write/buy an SS7 
> > > > implementation 
> > > > >and template the messages and hook that into my 
> > > > CNAME/LNP/whatever at the 
> > > > >call control layer and to SCTP/UDP/whatever on the network 
> > > > side but why, 
> > > > >to keep the SIP implementation "beautiful"?  The bottom line 
> > > > is I'm not 
> > > > >going to pass the cost of the SS7 stack on to my customers 
> > > > if I can make a 
> > > > >simple addition to the SIP stuff and do exactly the same 
> > > > thing basically 
> > > > >for free.
> > > > >
> > > > >Now with respect to the specifics of the encoding, we can 
> > > > certainly talk 
> > > > >about anything.  That was the whole reason for publishing 
> > > > the work in the 
> > > > >IETF to begin with.  On 6.1.1.1 specifically, this is 
> > > simply a field 
> > > > >required in the QWP message.  The actual digits are 
> > > > specified in a string 
> > > > >not in BCD binary.  The Signaling 
> > > > Gateway/Softswitch/whatever just picks 
> > > > >up BCD from the Encoding field and fills in the appropriate 
> > > > value in the 
> > > > >actual TCAP binary message when the translation is done.  
> > > > The digits in 
> > > > >the ASCII string are converted similarly to BCD format in 
> > > > the TCAP binary 
> > > > >message also at that time.  The <Encoding  > field doesn't 
> > > > change and is 
> > > > >therefore a perfect candidate for being templated.  The 
> > only real 
> > > > >information that needs to be handled per query here is the 
> > > > actual number.
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >  [Moving this thread to SIPPING, where it belongs]
> > > > >
> > > > >Leaving aside the question of whether or not ENUM supports 
> > > > all of the 
> > > > >functions of TCAP, the main issue is whether or not SIP is 
> > > > the right sort 
> > > > >of protocol to handle this function. A query-response 
> > > protocol that 
> > > > >carries XML documents from a client to a server? Does SIP 
> > > > INFO really seem 
> > > > >to map onto that well? Aren't there other protocols that 
> > > are tooled 
> > > > >specifically to that purpose?
> > > > >
> > > > >Furthermore, is the encoding really the issue? XML vs. 
> > > > binary doesn't seem 
> > > > >that significant to me - if a SIP endpoint can template the 
> > > > XML format, it 
> > > > >could template the binary format as well. Regardless of the 
> > > > syntax, should 
> > > > >we expect SIP endpoints to understand the semantics of TCAP? 
> > > > Do we expect 
> > > > >a SIP user agent to understand and implement the concept of, 
> > > > say, a code 
> > > > >gap? That isn't "translation" in any sense that I recognize 
> > > > - it is closer 
> > > > >to saying that SIP user agents have to run a dual stack (SIP 
> > > > and TCAP). 
> > > > >Just look at the <Digits> stanza of the example in 6.1.1.1 
> > > > of the draft: 
> > > > >what sorts of SIP elements are going to understand binary 
> > > > coded decimal, 
> > > > >recognize numbering plans, and the like? If the answer is 
> > > > "only PSTN-SIP 
> > > > >gateways with that already have SS7 links and could 
> > > > therefore just send 
> > > > >TCAP queries over SS7", then I think there is a design 
> > issue here.
> > > > >
> > > > >Jon Peterson
> > > > >NeuStar, Inc.
> > > > >-----Original Message-----
> > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > > >To: 'Chong, Koan S, ALABS'
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >The main idea of this draft was to provide a capability for 
> > > > SIP endpoints 
> > > > >to do TCAP queries without having to implement the binary TCAP 
> > > > >protocol.  The motivation is that there are a lot of TCAP 
> > > > queries that 
> > > > >take place (800, LNP, CNAME) that are really simple and 
> > that major 
> > > > >carriers may not want to go and reimplement in an ENUM 
> > > > database in the 
> > > > >short term.  These carriers have spent a lot of money on 
> > > > their SCPs and 
> > > > >converting the to ENUM is non-trivial.  Now, the SCPs could 
> > > > be front-ended 
> > > > >and conversion can be automated but this draft provides an 
> > > > >alternative.  So, to answer the first question, the SIP 
> > > > endpoint formats 
> > > > >the correct query in the XML format specified and sends if 
> > > > using an INFO 
> > > > >to a Signaling Gateway (SG).  The SG then converts the query 
> > > > to binary 
> > > > >TCAP and dips the SCP.  The XML format can be templated in the 
> > > > >implementation so the effort is quite minimal on the SIP 
> > > > endpoint.  To 
> > > > >answer the second question, the draft talks about a couple 
> > > > of examples but 
> > > > >the specification encompasses the entire TCAP message set 
> > > so you can 
> > > > >format the appropriate dip for AR/C.  One caveat is that the 
> > > > draft is 
> > > > >Telcordia based.  It would need to be extended to take into 
> > > > account other 
> > > > >variants.  On the third question, <personal view> I'm a 
> > > believer in 
> > > > >translation over tunneling, tunneling just puts off work 
> > and mixes 
> > > > >messaging from different signaling networks 
> > > > unnecessarily</personal view>.
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > > >To: Frank W. Miller; McCandless, Kevin
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >
> > > > >A couple specific questions:
> > > > >
> > > > >What is the recommendation on how a SIP network element can 
> > > > access the 
> > > > >callers' name databases (CNAM in US) in PSTN after the SIP 
> > > > element has 
> > > > >determined that the called parties have subscribed to 
> Caller ID?
> > > > >
> > > > >How about interworking with CLASS Auto-Recall/Callback (CCBS 
> > > > in ITU?) 
> > > > >procedures?
> > > > >
> > > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > > >
> > > > >Koan
> > > > >Koan S.Chong
> > > > >AT&T
> > > > >1-732-420-4557
> > > > >
> > > > >-----Original Message-----
> > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > >Sent: Monday, November 17, 2003 6:18 PM
> > > > >To: 'McCandless, Kevin'
> > > > >Cc: sip@ietf.org
> > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > >
> > > > >You mean other than us implementing it?  No, I don't think 
> > > > so.  I think 
> > > > >its considered Rosemary's Baby by most...
> > > > >
> > > > >FM
> > > > >
> > > > >
> > > > >Frank W. Miller, Ph.D.
> > > > >Chief Technical Officer
> > > > >sentitO Networks, Inc.
> > > > >fmiller@sentito.com
> > > > >
> > > > >-----Original Message-----
> > > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> > Behalf Of 
> > > > >McCandless, Kevin
> > > > >Sent: Monday, November 17, 2003 4:11 PM
> > > > >To: sip@ietf.org
> > > > >Subject: [Sip] Sip support for TCAP queries
> > > > >
> > > > >Has any progress been taken on the draft by Frank Miller on 
> > > > Carrying TCAP 
> > > > >in SIP messages?  Are there other drafts that address SIP 
> > > > access to SS7 
> > > > >database information through TCAP or another method?
> > > > >
> > > > >Thanks,
> > > > >
> > > > >Kevin
> > > > 
> > > > 
> > > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > > Richard Shockey, Senior Manager, Strategic Technology 
> Initiatives
> > > > NeuStar Inc.
> > > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  
> > > > Fax: +1 815.333.1237
> > > > <mailto:richard(at)shockey.us> or 
> > > > <mailto:richard.shockey(at)neustar.biz>
> > > > 
> > > <http://www.neustar.biz> ; <http://www.enum.org>
> > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > > 
> > > 
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > > 
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 18:00:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20488
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 18:00:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMbJ3-00050n-Gd
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 18:00:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJN0HEm019265
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 18:00:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMbJ3-00050e-0n
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 18:00:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20452
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 18:00:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMbJ0-0005ar-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 18:00:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMbIz-0005ao-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 18:00:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMbIq-0004z2-Uj; Wed, 19 Nov 2003 18:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMbHo-0004xE-S2
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 17:59:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20331
	for <sipping@ietf.org>; Wed, 19 Nov 2003 17:58:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMbHZ-0005Y2-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:58:46 -0500
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMbHY-0005Xy-00
	for sipping@ietf.org; Wed, 19 Nov 2003 17:58:45 -0500
Received: from txdwillis (dhcp225.dfw.dynamicsoft.com [63.110.3.225])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id hAJN0Juc014734
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Wed, 19 Nov 2003 17:00:20 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'McCandless, Kevin'" <KMcCandless@verisign.com>,
        "'Drage, Keith \(Keith\)'" <drage@lucent.com>
Cc: <sipping@ietf.org>, "'Frank W. Miller'" <fmiller@sentito.com>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 16:57:49 -0600
Message-ID: <001601c3aef0$8ec11b30$e1036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513CD56471@stntexch03.va.neustar.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Jon said:
> Relevant - yes, by all means. But in order for these=20
> functions to work for VoIP solutions of which SIP is only a=20
> part, there is no requirement for the SIP protocol itself to=20
> obtain this sort of database information. There are obviously=20
> alternatives (one being something like ENUM, another being=20
> some sort of web services architecture).
>=20
> For trivial applications like number translation (or CNAM), I=20
> can understand why some might insist that this is a feasible=20
> thing to do with SIP. As my colleague Mr. Shockey suggested=20
> earlier in this thread,it would be perfectly reasonable for a=20
> SIP redirect server to act as a SIP-TCAP gateway.=20

In fact, I once worked on something very much like this. In our network =
at
that time, incoming tel:URI calls might be to a translatable (800 or =
LNP)
number. But the translation database was on a legacy SCP-like device
implementing a legacy TCAP-like protocol which happened to support IP
datagram access.

Rather than modifying the old SCP-like device, we fronted it with a SIP
proxy that would use the legacy TCAP-like protocol to dip the SCP, then
apply standard SIP proxy request-URI rewriting to adjust the request =
URI. We
even used a phone-context to indicate that the translation dip had =
already
occurred, thereby preventing redundant lookups.

Now if one were to replace that legacy TCAP-like IP protocol with a nice
smooth web-services interface, that would be really cool. Eventually, I
could see that translation database jettisoning its IN interfaces =
entirely.
One might even imagine that it would gain a SIP interface, displacing =
the
proxy as well. But neither this application nor the evolution path =
proposed
here justifies any changes to the SIP protocol as I understand it. And =
most
especially, it does not require a general semantic mapping between SIP =
and
TCAP to operate.

--
Dean


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 20:44:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28919
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 20:44:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMdre-0004Qn-FV
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 20:44:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK1iAPJ017027
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 20:44:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMdre-0004QY-BT
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 20:44:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28912
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 20:43:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMdrb-0000wU-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 20:44:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMdrb-0000wR-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 20:44:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMdrV-0004PF-Vu; Wed, 19 Nov 2003 20:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMdqz-0004Os-Mx
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 20:43:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28884
	for <sipping@ietf.org>; Wed, 19 Nov 2003 20:43:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMdqs-0000vl-00
	for sipping@ietf.org; Wed, 19 Nov 2003 20:43:22 -0500
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMdqr-0000vY-00
	for sipping@ietf.org; Wed, 19 Nov 2003 20:43:21 -0500
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id hAK1aUPR019954
	for <sipping@ietf.org>; Wed, 19 Nov 2003 20:42:51 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3FBBC62E0002655C; Wed, 19 Nov 2003 20:42:30 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Wed, 19 Nov 2003 19:42:52 -0600
Message-ID: <73656AE8EE4C9C4D9FFF9DBFEAE9A00F0B1C47@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: [Sipping] RE: [Sip] Sip support for TCAP queries
Thread-Index: AcOu7k9A9K80FaFZR3+1SHSeXO4pAAACCfBQ
From: "Chong, Koan S, ALABS" <kschong@att.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "McCandless, Kevin" <KMcCandless@verisign.com>,
        "Drage, Keith (Keith)" <drage@lucent.com>
Cc: <sipping@ietf.org>, "Frank W. Miller" <fmiller@sentito.com>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


	I understand James Yu's ID on using the redirect server to interwork =
with number translation services like LNP and ITFDB. And I have =
communicated to him on our support/need for and our dependency on his =
draft to be incorporated into the new RFC of tel url.

	My earlier question is more specific. I am interested to know if there =
is any industry standard solution for interworking with CNAM. Is CNAM a =
trivial number translation that can be treated with redirect response =
like LNP or ITFDB?

	Another specific question is about interworking with the CLASS =
Auto-Recall & Callback.

	If existing solution for specific services is not available, are we =
looking for a general problem statement and a more universal solution? I =
agree that TCAP over SIGTRAN will solve this type of problem to =
interwork with TCAP-based PSTN services. Is this the recommended =
solution taken by SIPPING & SIGTRAN?

Koan
AT&T

... whether a cat is black or white so long as it catches mice. And =
super cat is not needed if only a couple mice need to be caught....



> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: Wednesday, November 19, 2003 5:39 PM
> To: 'McCandless, Kevin'; 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org; 'Frank W. Miller'
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
>=20
>=20
>=20
> Relevant - yes, by all means. But in order for these=20
> functions to work for
> VoIP solutions of which SIP is only a part, there is no=20
> requirement for the
> SIP protocol itself to obtain this sort of database=20
> information. There are
> obviously alternatives (one being something like ENUM,=20
> another being some
> sort of web services architecture).
>=20
> For trivial applications like number translation (or CNAM), I=20
> can understand
> why some might insist that this is a feasible thing to do=20
> with SIP. As my
> colleague Mr. Shockey suggested earlier in this thread,it=20
> would be perfectly
> reasonable for a SIP redirect server to act as a SIP-TCAP=20
> gateway. One might
> send an INVITE with a tel URL Request-URI to the gateway and=20
> receive a 3xx
> reponse with a Contact header containing the translated=20
> number. In fact,
> this architecture was documented in a now-expired ID, which=20
> can still be
> found here:
>=20
> http://www.watersprings.org/pub/id/draft-yu-sip-np-01.txt
>=20
> At the time, there was not sufficient interest in the WG to=20
> push this draft
> forward. I got the sense that most people believed it was too=20
> obvious to
> even require documentation.=20
>=20
> Jon Peterson
> NeuStar, Inc.
>=20
> > -----Original Message-----
> > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > Sent: Wednesday, November 19, 2003 12:23 PM
> > To: 'Drage, Keith (Keith)'
> > Cc: sipping@ietf.org; 'Frank W. Miller'
> > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> >=20
> >=20
> > So, CNAM, LNP, and other SS7 data is relevant to working SIP=20
> > networks that interconnect with the PSTN.  There is no=20
> > standard document to define how the SIP protocol obtains the=20
> > database information.  Each vendor is implementing their own=20
> > way of doing this with SIP on one side during the Invite=20
> > message and on the other side launching an SS7 query either=20
> > with M3UA or standard SS7 TDM links.  VoIP carriers want=20
> > access to the data so would it not be helpful to have a=20
> > standard way of implementing this interworking.  This has=20
> > already done for ISUP.  SS7 is not going away and the=20
> > interworking between VoIP and PSTN can only help the VoIP=20
> initiatives.
> >=20
> > > -----Original Message-----
> > > From: Frank W. Miller [mailto:fmiller@sentito.com]=20
> > > Sent: Wednesday, November 19, 2003 1:39 PM
> > > To: 'Drage, Keith (Keith)'
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >=20
> > >=20
> > >=20
> > > With all due respect, the reason I didn't ask to have it=20
> > > considered was I
> > > knew that it would never be accepted, so why waste my breath.=20
> > >  My purpose
> > > was to solve a problem that needs addressing.
> > >=20
> > > It cannot be ignored that SIP is making major inroads into=20
> > > the big carriers
> > > and dealing with ISUP and TCAP in a complete way within the=20
> > > context of SIP
> > > is something that needs to happen.  Now, if INFO as transport=20
> > > for XML isn't
> > > palatable, whatever.
> > >=20
> > > Let me be very plain, RFC 3398 is not sufficient.  It lacks=20
> > > support for ISUP
> > > maintenance commands and access to SCPs via TCAP.  These are=20
> > > functions that
> > > are required by vendors and carriers integrating SIP with the=20
> > > existing PSTN.
> > >=20
> > > I happen to be associated with one of the vendors addressing=20
> > > these needs at
> > > the implementation level.  If the protocol does not serve all=20
> > > my needs, I
> > > will extend it.  If you as protocol specifiers don't like the=20
> > > way I extend
> > > it then put something else in place that I can use.
> > >=20
> > > Hoping to be constructive,
> > > FM
> > > =20
> > >=20
> > > Frank W. Miller, Ph.D.
> > > Chief Technical Officer
> > > sentitO Networks, Inc.
> > > fmiller@sentito.com
> > >=20
> > >=20
> > > -----Original Message-----
> > > From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]=20
> > > On Behalf Of
> > > Drage, Keith (Keith)
> > > Sent: Wednesday, November 19, 2003 2:01 PM
> > > To: 'McCandless, Kevin'
> > > Cc: sipping@ietf.org
> > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > >=20
> > > I dont see any justification here.
> > >=20
> > > The only sense I can make of the proposal so far is that SIP=20
> > > is used as a
> > > means of transporting TCAP from one place to another. It is=20
> > > not a case the
> > > protocol being used to make a SIP request, and the TCAP=20
> information
> > > enhancing that request.
> > >=20
> > > The IETF will not extend SIP so it is just another=20
> > transport protocol,
> > > transaction protocol or whatever. There are other IETF=20
> > > defined solutions in
> > > this space.
> > >=20
> > > So while the original author never progressed his original=20
> > > request, in that
> > > he never asked for it to become a WG item or proposed that it=20
> > > should go
> > > forward as an individual draft (and it died because the=20
> > > author failed to
> > > refresh it), it would probably fail to progress (I daren't=20
> > > say never as they
> > > will then prove me wrong), the former because the charter of=20
> > > the WG would
> > > never be extended to cover it, and the latter at the IESG=20
> > > review stage.
> > >=20
> > > If there is any reason for progressing this, then the=20
> > > proponents need to
> > > clearly distinguish a reason for putting it in SIP that=20
> > > relates to SIP as a
> > > Session Initiation Protocol.
> > >=20
> > > regards
> > >=20
> > > Keith
> > >=20
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> > > > Sent: 19 November 2003 14:47
> > > > To: 'Richard Shockey'
> > > > Cc: sipping@ietf.org
> > > > Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > >=20
> > > >=20
> > > > Ignorance awakens in the dawn of reality.
> > > >=20
> > > > SIP needs a formal methodology for obtaining a TCAP query. =20
> > > > Whether the SS7 providers does this with their signaling=20
> > > > gateway or not is not the issue.  A formalized approach that=20
> > > > a vendor can implement is the point that is being raised.
> > > >=20
> > > >=20
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Richard Shockey [mailto:richard@shockey.us]=20
> > > > > Sent: Tuesday, November 18, 2003 3:09 PM
> > > > > To: sipping@ietf.org
> > > > > Subject: Re: [Sipping] RE: [Sip] Sip support for TCAP queries
> > > > >=20
> > > > >=20
> > > > > At 03:50 PM 11/18/2003, Frank W. Miller wrote:
> > > > >=20
> > > > > As the distributor of the NO TCAP buttons on generous display=20
> > > > > at IETF 59=20
> > > > > and fine trade shows nationwide , let me comment that this is=20
> > > > > one of the=20
> > > > > silliest ideas I have yet seen cross the SIPPING landscape.
> > > > >=20
> > > > > Why ..why on earth would you want to do this ..any query=20
> > > > > response mechanism=20
> > > > > can get you the data points necessary without the baggage=20
> > > > > TCAP puts you=20
> > > > > through.
> > > > >=20
> > > > > Talk to your SS7 vendor and demand better service or fire=20
> > > > > them. Get them to=20
> > > > > support SIP itself  query response mechanism. Send an INVITE=20
> > > > > expect a 302=20
> > > > > MOVE in response and encapsulate SS7 the data as part of a=20
> > > > > TEL URL in the=20
> > > > > response.
> > > > >=20
> > > > > This is a "bad idea" tm worthy of the big gong and hook.
> > > > >=20
> > > > >=20
> > > > > >
> > > > > >Aiieee, a cross is raised!!  ;)
> > > > > >
> > > > > >Anyway, you're right, the format doesn't matter at all,=20
> > > > > except for one=20
> > > > > >thing.  Expedience.  The essence of the argument against=20
> > > > > this type of=20
> > > > > >draft in general, i.e. one that uses INFO to carry anything,=20
> > > > > is usually=20
> > > > > >based on the fact that the content is application specific=20
> > > > > and so doesn't=20
> > > > > >fit with the base SIP protocol.  I can understand that and=20
> > > > > accept it, it=20
> > > > > >really doesn't matter to me.  I'm an implementor, not=20
> > a protocol=20
> > > > > >specifier.  Unfortunately, the protocol doesn't do=20
> > > > > everything I need it to=20
> > > > > >do so I have to add stuff to fill in the holes when I take=20
> > > > > it into the=20
> > > > > >real world.  The other draft in this area=20
> > > > > draft-miller-sip-isup-annex is=20
> > > > > >another example of augmentation, the addition of ISUP=20
> > > > > maintenance commands=20
> > > > > >to the ISUP translation now RFC.  I could write/buy an SS7=20
> > > > > implementation=20
> > > > > >and template the messages and hook that into my=20
> > > > > CNAME/LNP/whatever at the=20
> > > > > >call control layer and to SCTP/UDP/whatever on the network=20
> > > > > side but why,=20
> > > > > >to keep the SIP implementation "beautiful"?  The bottom line=20
> > > > > is I'm not=20
> > > > > >going to pass the cost of the SS7 stack on to my customers=20
> > > > > if I can make a=20
> > > > > >simple addition to the SIP stuff and do exactly the same=20
> > > > > thing basically=20
> > > > > >for free.
> > > > > >
> > > > > >Now with respect to the specifics of the encoding, we can=20
> > > > > certainly talk=20
> > > > > >about anything.  That was the whole reason for publishing=20
> > > > > the work in the=20
> > > > > >IETF to begin with.  On 6.1.1.1 specifically, this is=20
> > > > simply a field=20
> > > > > >required in the QWP message.  The actual digits are=20
> > > > > specified in a string=20
> > > > > >not in BCD binary.  The Signaling=20
> > > > > Gateway/Softswitch/whatever just picks=20
> > > > > >up BCD from the Encoding field and fills in the appropriate=20
> > > > > value in the=20
> > > > > >actual TCAP binary message when the translation is done. =20
> > > > > The digits in=20
> > > > > >the ASCII string are converted similarly to BCD format in=20
> > > > > the TCAP binary=20
> > > > > >message also at that time.  The <Encoding  > field doesn't=20
> > > > > change and is=20
> > > > > >therefore a perfect candidate for being templated.  The=20
> > > only real=20
> > > > > >information that needs to be handled per query here is the=20
> > > > > actual number.
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> > > > > >Sent: Tuesday, November 18, 2003 3:14 PM
> > > > > >To: 'Frank W. Miller'; 'Chong, Koan S, ALABS'
> > > > > >Cc: 'sipping@ietf.org'; 'McCandless, Kevin'
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >  [Moving this thread to SIPPING, where it belongs]
> > > > > >
> > > > > >Leaving aside the question of whether or not ENUM supports=20
> > > > > all of the=20
> > > > > >functions of TCAP, the main issue is whether or not SIP is=20
> > > > > the right sort=20
> > > > > >of protocol to handle this function. A query-response=20
> > > > protocol that=20
> > > > > >carries XML documents from a client to a server? Does SIP=20
> > > > > INFO really seem=20
> > > > > >to map onto that well? Aren't there other protocols that=20
> > > > are tooled=20
> > > > > >specifically to that purpose?
> > > > > >
> > > > > >Furthermore, is the encoding really the issue? XML vs.=20
> > > > > binary doesn't seem=20
> > > > > >that significant to me - if a SIP endpoint can template the=20
> > > > > XML format, it=20
> > > > > >could template the binary format as well. Regardless of the=20
> > > > > syntax, should=20
> > > > > >we expect SIP endpoints to understand the semantics of TCAP?=20
> > > > > Do we expect=20
> > > > > >a SIP user agent to understand and implement the concept of,=20
> > > > > say, a code=20
> > > > > >gap? That isn't "translation" in any sense that I recognize=20
> > > > > - it is closer=20
> > > > > >to saying that SIP user agents have to run a dual stack (SIP=20
> > > > > and TCAP).=20
> > > > > >Just look at the <Digits> stanza of the example in 6.1.1.1=20
> > > > > of the draft:=20
> > > > > >what sorts of SIP elements are going to understand binary=20
> > > > > coded decimal,=20
> > > > > >recognize numbering plans, and the like? If the answer is=20
> > > > > "only PSTN-SIP=20
> > > > > >gateways with that already have SS7 links and could=20
> > > > > therefore just send=20
> > > > > >TCAP queries over SS7", then I think there is a design=20
> > > issue here.
> > > > > >
> > > > > >Jon Peterson
> > > > > >NeuStar, Inc.
> > > > > >-----Original Message-----
> > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > >Sent: Tuesday, November 18, 2003 8:50 AM
> > > > > >To: 'Chong, Koan S, ALABS'
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >The main idea of this draft was to provide a capability for=20
> > > > > SIP endpoints=20
> > > > > >to do TCAP queries without having to implement the=20
> binary TCAP=20
> > > > > >protocol.  The motivation is that there are a lot of TCAP=20
> > > > > queries that=20
> > > > > >take place (800, LNP, CNAME) that are really simple and=20
> > > that major=20
> > > > > >carriers may not want to go and reimplement in an ENUM=20
> > > > > database in the=20
> > > > > >short term.  These carriers have spent a lot of money on=20
> > > > > their SCPs and=20
> > > > > >converting the to ENUM is non-trivial.  Now, the SCPs could=20
> > > > > be front-ended=20
> > > > > >and conversion can be automated but this draft provides an=20
> > > > > >alternative.  So, to answer the first question, the SIP=20
> > > > > endpoint formats=20
> > > > > >the correct query in the XML format specified and sends if=20
> > > > > using an INFO=20
> > > > > >to a Signaling Gateway (SG).  The SG then converts the query=20
> > > > > to binary=20
> > > > > >TCAP and dips the SCP.  The XML format can be=20
> templated in the=20
> > > > > >implementation so the effort is quite minimal on the SIP=20
> > > > > endpoint.  To=20
> > > > > >answer the second question, the draft talks about a couple=20
> > > > > of examples but=20
> > > > > >the specification encompasses the entire TCAP message set=20
> > > > so you can=20
> > > > > >format the appropriate dip for AR/C.  One caveat is that the=20
> > > > > draft is=20
> > > > > >Telcordia based.  It would need to be extended to take into=20
> > > > > account other=20
> > > > > >variants.  On the third question, <personal view> I'm a=20
> > > > believer in=20
> > > > > >translation over tunneling, tunneling just puts off work=20
> > > and mixes=20
> > > > > >messaging from different signaling networks=20
> > > > > unnecessarily</personal view>.
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Chong, Koan S, ALABS [mailto:kschong@att.com]
> > > > > >Sent: Tuesday, November 18, 2003 11:27 AM
> > > > > >To: Frank W. Miller; McCandless, Kevin
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >
> > > > > >A couple specific questions:
> > > > > >
> > > > > >What is the recommendation on how a SIP network element can=20
> > > > > access the=20
> > > > > >callers' name databases (CNAM in US) in PSTN after the SIP=20
> > > > > element has=20
> > > > > >determined that the called parties have subscribed to=20
> > Caller ID?
> > > > > >
> > > > > >How about interworking with CLASS Auto-Recall/Callback (CCBS=20
> > > > > in ITU?)=20
> > > > > >procedures?
> > > > > >
> > > > > >Assume TCAP over SIGTRAN is a bit long long term....
> > > > > >
> > > > > >Koan
> > > > > >Koan S.Chong
> > > > > >AT&T
> > > > > >1-732-420-4557
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: Frank W. Miller [mailto:fmiller@sentito.com]
> > > > > >Sent: Monday, November 17, 2003 6:18 PM
> > > > > >To: 'McCandless, Kevin'
> > > > > >Cc: sip@ietf.org
> > > > > >Subject: RE: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >You mean other than us implementing it?  No, I don't think=20
> > > > > so.  I think=20
> > > > > >its considered Rosemary's Baby by most...
> > > > > >
> > > > > >FM
> > > > > >
> > > > > >
> > > > > >Frank W. Miller, Ph.D.
> > > > > >Chief Technical Officer
> > > > > >sentitO Networks, Inc.
> > > > > >fmiller@sentito.com
> > > > > >
> > > > > >-----Original Message-----
> > > > > >From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On=20
> > > Behalf Of=20
> > > > > >McCandless, Kevin
> > > > > >Sent: Monday, November 17, 2003 4:11 PM
> > > > > >To: sip@ietf.org
> > > > > >Subject: [Sip] Sip support for TCAP queries
> > > > > >
> > > > > >Has any progress been taken on the draft by Frank Miller on=20
> > > > > Carrying TCAP=20
> > > > > >in SIP messages?  Are there other drafts that address SIP=20
> > > > > access to SS7=20
> > > > > >database information through TCAP or another method?
> > > > > >
> > > > > >Thanks,
> > > > > >
> > > > > >Kevin
> > > > >=20
> > > > >=20
> > > > >  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > > > > Richard Shockey, Senior Manager, Strategic Technology=20
> > Initiatives
> > > > > NeuStar Inc.
> > > > > 46000 Center Oak Plaza  -   Sterling, VA  20166
> > > > > sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
> > > > > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, =20
> > > > > Fax: +1 815.333.1237
> > > > > <mailto:richard(at)shockey.us> or=20
> > > > > <mailto:richard.shockey(at)neustar.biz>
> > > > >=20
> > > > <http://www.neustar.biz> ; <http://www.enum.org>
> > > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sipping mailing list =20
> > https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on=20
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >=20
> > > > _______________________________________________
> > > > Sipping mailing list =20
> > https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP
> > > > Use sip-implementors@cs.columbia.edu for questions on=20
> current sip
> > > > Use sip@ietf.org for new developments of core SIP
> > > >=20
> > >=20
> > > _______________________________________________
> > > Sipping mailing list =20
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 19 20:59:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29224
	for <sipping-archive@odin.ietf.org>; Wed, 19 Nov 2003 20:59:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMe67-000525-Lq
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 20:59:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK1x7lu019339
	for sipping-archive@odin.ietf.org; Wed, 19 Nov 2003 20:59:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMe67-00051m-Bq
	for sipping-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 20:59:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29213
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 20:58:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMe64-00017s-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 20:59:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMe64-00017n-00
	for sipping-web-archive@ietf.org; Wed, 19 Nov 2003 20:59:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMe62-00050X-2S; Wed, 19 Nov 2003 20:59:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMe55-000503-Mh
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 20:58:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29185
	for <sipping@ietf.org>; Wed, 19 Nov 2003 20:57:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMe53-00016y-00
	for sipping@ietf.org; Wed, 19 Nov 2003 20:58:01 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMe52-00016L-00
	for sipping@ietf.org; Wed, 19 Nov 2003 20:58:00 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (h-68-165-240-34.MCLNVA23.covad.net [68.165.240.34])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hAK22nf32118;
	Wed, 19 Nov 2003 18:02:49 -0800
Message-Id: <6.0.0.22.2.20031119205307.03698468@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Wed, 19 Nov 2003 20:56:05 -0500
To: "Dean Willis" <dean.willis@softarmor.com>,
        "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'McCandless, Kevin'" <KMcCandless@verisign.com>,
        "'Drage, Keith \(Keith\)'" <drage@lucent.com>
From: Richard Shockey <richard@shockey.us>
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Cc: <sipping@ietf.org>, "'Frank W. Miller'" <fmiller@sentito.com>
In-Reply-To: <001601c3aef0$8ec11b30$e1036e3f@txdwillis>
References: <A9DECB0B8A01A54DBECC03B25D29513CD56471@stntexch03.va.neustar.com>
 <001601c3aef0$8ec11b30$e1036e3f@txdwillis>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

At 05:57 PM 11/19/2003, Dean Willis wrote:

>In fact, I once worked on something very much like this. In our network at
>that time, incoming tel:URI calls might be to a translatable (800 or LNP)
>number. But the translation database was on a legacy SCP-like device
>implementing a legacy TCAP-like protocol which happened to support IP
>datagram access.
>
>Rather than modifying the old SCP-like device, we fronted it with a SIP
>proxy that would use the legacy TCAP-like protocol to dip the SCP, then
>apply standard SIP proxy request-URI rewriting to adjust the request URI. We
>even used a phone-context to indicate that the translation dip had already
>occurred, thereby preventing redundant lookups.

clever.. very clever


>Now if one were to replace that legacy TCAP-like IP protocol with a nice
>smooth web-services interface, that would be really cool.

yes . that is the point here the query/response mechanism to retrieve the 
data is only relevant to the specifics of the network architecture deployed

>  Eventually, I
>could see that translation database jettisoning its IN interfaces entirely.

and such a day will come ..

>One might even imagine that it would gain a SIP interface, displacing the
>proxy as well. But neither this application nor the evolution path proposed
>here justifies any changes to the SIP protocol as I understand it. And most
>especially, it does not require a general semantic mapping between SIP and
>TCAP to operate.
>
>-

well spoken..



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 00:00:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03808
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 00:00:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMgvK-0003vH-5Q
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 00:00:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK5096l015073
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 00:00:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMgvJ-0003v2-E0
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 00:00:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03763
	for <sipping-web-archive@ietf.org>; Wed, 19 Nov 2003 23:59:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMgvG-0003OG-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 00:00:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMgvG-0003OD-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 00:00:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMgvC-0003su-9w; Thu, 20 Nov 2003 00:00:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMguY-0003mm-Ra
	for sipping@optimus.ietf.org; Wed, 19 Nov 2003 23:59:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03733
	for <sipping@ietf.org>; Wed, 19 Nov 2003 23:59:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMguW-0003Mv-00
	for sipping@ietf.org; Wed, 19 Nov 2003 23:59:20 -0500
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMguV-0003Lz-00
	for sipping@ietf.org; Wed, 19 Nov 2003 23:59:20 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id hAK4wod22646
	for <sipping@ietf.org>; Wed, 19 Nov 2003 22:58:50 -0600
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sipping@ietf.org
Content-Type: text/plain
Message-Id: <1069304329.973.69.camel@RjS.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Wed, 19 Nov 2003 22:58:49 -0600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Torture test update
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I've just submitted
http://www.nostrum.com/~rjsparks/draft-ietf-sipping-torture-tests-02.txt
to the I-D respository.

This update reflects production bug fixes to -01.

Specifically:

 - The <hex> expansion errors in the bit-accurate archive previously 
   reported to this list have been corrected.
 - The "Message Detail" line for each message now indicates the filename
   of that message in the bit-accurate archive.

RjS


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 03:20:45 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24365
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 03:20:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMk37-0008R8-Th
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 03:20:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAK8KPWw032427
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 03:20:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMk36-0008Qt-BG
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 03:20:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24342
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 03:20:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMk34-0006TY-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 03:20:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMk34-0006TV-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 03:20:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMk2m-0008P6-JX; Thu, 20 Nov 2003 03:20:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMk20-0008Mu-L3
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 03:19:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24279
	for <sipping@ietf.org>; Thu, 20 Nov 2003 03:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMk1z-0006S5-00
	for sipping@ietf.org; Thu, 20 Nov 2003 03:19:15 -0500
Received: from inet11.jrc.co.jp ([203.180.124.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMk1y-0006RP-00
	for sipping@ietf.org; Thu, 20 Nov 2003 03:19:14 -0500
Received: from vscan.jrc.co.jp by inet11.jrc.co.jp (8.9.3/3.7W)
	id RAA23154; Thu, 20 Nov 2003 17:18:26 +0900 (JST)
Received: from jrcgw1.noc.jrc.co.jp(10.8.1.31) by vscan.jrc.co.jp via csmap 
	 id 27902; Thu, 20 Nov 2003 17:18:26 +0900 (JST)
Received: from labgw1.lab.jrc.co.jp by jrcgw1.noc.jrc.co.jp (8.9.3/3.7WSaTaMa99081014)
	id RAA10768; Thu, 20 Nov 2003 17:17:05 +0900 (JST)
Received: from [10.38.58.12] (sakai.lab.jrc.co.jp [10.38.58.12])
	by labgw1.lab.jrc.co.jp (8.9.3+3.2W/3.7W-labgw1) with ESMTP id RAA04462;
	Thu, 20 Nov 2003 17:17:05 +0900 (JST)
Date: Thu, 20 Nov 2003 17:16:51 +0900
From: Yutaka SAKAI <sakai@lab.jrc.co.jp>
To: samir.chatterjee@cgu.edu
Cc: sipping@ietf.org
In-Reply-To: <9C6FE1166FC14444811E7AB3B1B6D7E5A3545A@clarepost.cgu.edu>
References: <9C6FE1166FC14444811E7AB3B1B6D7E5A3545A@clarepost.cgu.edu>
Message-Id: <20031120162729.573F.SAKAI@lab.jrc.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.07.02
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: SIMPLE vs XMPP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

FYI : this is from point of view of XMPP/Jabber side ;-)

  The Instant Messaging Standards Race:
    Comparing XMPP/Jabber and SIP/SIMPLE
  May 2003  Version 1.0
  http://www.jabber.com/media/1_The_IM_Standards_Race_v1.0.pdf

thanks,
yutaka

Samir Chatterjee wrote:
> Is anyone aware of a comparison made between SIMPLE and XMPP 
> for instant messaging/presence services?



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 05:24:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27833
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 05:24:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlyx-0007Fl-FP
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 05:24:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKAOFeB027875
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 05:24:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlyx-0007FW-7l
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 05:24:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27808
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 05:24:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlyu-0000Ex-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 05:24:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlyu-0000Eu-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 05:24:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlyl-0007DN-9Q; Thu, 20 Nov 2003 05:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMlyh-0007Co-Qm
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 05:23:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27801
	for <sipping@ietf.org>; Thu, 20 Nov 2003 05:23:45 -0500 (EST)
From: aki.niemi@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlyf-0000Ek-00
	for sipping@ietf.org; Thu, 20 Nov 2003 05:23:57 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMlye-0000Eh-00
	for sipping@ietf.org; Thu, 20 Nov 2003 05:23:56 -0500
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAKANu612810
	for <sipping@ietf.org>; Thu, 20 Nov 2003 12:23:56 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66058175d1ac158f23077@esvir03nok.nokia.com>;
 Thu, 20 Nov 2003 12:23:54 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 20 Nov 2003 12:23:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] How to control drop algorithms for throttling
Date: Thu, 20 Nov 2003 12:23:55 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592BC@esebe013.ntc.nokia.com>
Thread-Topic: [Sipping] How to control drop algorithms for throttling
Thread-Index: AcOqPmLMwtTnptiuREaxDmPMWbqReQFD9/BA
To: <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 20 Nov 2003 10:23:55.0982 (UTC) FILETIME=[672E06E0:01C3AF50]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Jonathan,

Inline.

 > -----Original Message-----
 > From: sipping-admin@ietf.org=20
 > [mailto:sipping-admin@ietf.org]On Behalf Of
 > ext Jonathan Rosenberg
 > Sent: 14 November, 2003 01:30
 > To: sipping
 > Subject: [Sipping] How to control drop algorithms for throttling
 >=20
 >=20
 > This mail is a followup to some comments I made during sipping today=20
 > on the event throttling work.
 >=20
 > Once we add throttling capabilities to the SIP event=20
 > framework, we end=20
 > up with a lossy system. Some notifications will be dropped,=20
 > and others=20
 > will be transmitted. The problem is that all notifications are not=20
 > created equally. If the notififer drops notifications at=20
 > random, will=20
 > the resulting stream of notifications meet the needs of the watcher?=20
 > Can we do better than simply dropping notifications randomly?

I think dropping notifications randomly is almost always what we don't =
want. The notifications generally have ordering, so having for example a =
simple FIFO buffer with like a tail drop packet treatment would really =
mess up the state.
=20
 > Some possible things we might do:
 >=20
 > 1. instead of dropping notifications, the notifier buffers=20
 > them. If it=20
 > receives another notification within the next M seconds, it=20
 > drops the=20
 > older one, and sends the newer one. This would allow you to control=20
 > the rate through delays. I suspect that many applications=20
 > will have a=20
 > better sense of the utility of the presence data as a=20
 > function of age.=20
 > Do we want the mechanism to support this?

This is exactly the sort of treatment I can see value in. And my =
assumption is that many notifiers today implement something close to =
this. So if I fall asleep on top of my keyboard and start making =
presence updates in 10ms intervals, the notifier can cope and not exceed =
its rate limits by mirroring this activity to the watchers.

In practice, this would mean that a notification arriving in the buffer =
replaces any notification still there (a LIFO with buffer size of 1). =
For those events that support partial state notifications, it is a bit =
more complicated, because the notifier would have to resolve the =
interdependency of the buffered notifications, e.g., by merging their =
state.
=20
 > 2. the watcher could provide a filter type of document in the=20
 > subscription. This filter could indicate that certain=20
 > transitions are=20
 > more important than others. For example, in the case of presence, it=20
 > might say that transitions of the <basic> status are more important=20
 > than transitions of the <placetype> from RPID. The notifier=20
 > could use=20
 > these to preferentially drop certain notifications over=20
 > others. Do we=20
 > want the mechanism to support this?

It really seems to me that this falls into the filtering work more than =
throttling. And even there, while this is quite interesting, I don't =
think it is a first order of priority. I think we could live without it =
in the first phases.
=20
 > 3. If we don't use the concepts of (1) and (2), is there any=20
 > value in=20
 > applying algorithms like RED to the systems (I dont think=20
 > so, but its=20
 > worth considering).

This is an interesting idea, but I suspect applying things like the RED =
algorithm to the notifier buffer would need to take into ocnsideration =
the ordering of notifications. And in partial notification case, also =
the interdependency of notifications.=20

At least in the first phase of throttling, this might not be such a high =
priority.
=20
 > 4. Do we want to specify that each package should have a=20
 > considerations section about how to use throttling? In particular,=20
 > what will be the typical impact on service for various loss=20
 > rates? Or,=20
 >   which components of a document should a client ask to have dropped=20
 > (assuming the filtering of (2)).

I think this is worth having.=20

Cheers,
Aki
=20
 >=20
 > Thanks,
 > Jonathan R.
 > --=20
 > Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
 > Chief Technology Officer                    Parsippany, NJ 07054-2711
 > dynamicsoft
 > jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
 > http://www.jdrosen.net                      PHONE: (973) 952-5000
 > http://www.dynamicsoft.com
 >=20
 >=20
 >=20
 > _______________________________________________
 > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
 > This list is for NEW development of the application of SIP
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sip@ietf.org for new developments of core SIP
 >=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 05:31:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28028
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 05:31:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMm5X-0007dl-TD
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 05:31:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKAV35C029363
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 05:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMm5X-0007dW-PX
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 05:31:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28002
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 05:30:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMm5V-0000KG-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 05:31:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMm5U-0000KD-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 05:31:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMm5W-0007cF-5B; Thu, 20 Nov 2003 05:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMm5S-0007br-DK
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 05:30:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27999
	for <sipping@ietf.org>; Thu, 20 Nov 2003 05:30:44 -0500 (EST)
From: aki.niemi@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMm5P-0000KA-00
	for sipping@ietf.org; Thu, 20 Nov 2003 05:30:55 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMm5O-0000K7-00
	for sipping@ietf.org; Thu, 20 Nov 2003 05:30:55 -0500
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAKAUrA17471
	for <sipping@ietf.org>; Thu, 20 Nov 2003 12:30:53 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T660587d838ac158f21082@esvir01nok.ntc.nokia.com>;
 Thu, 20 Nov 2003 12:30:52 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Thu, 20 Nov 2003 12:30:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] How to control drop algorithms for throttling
Date: Thu, 20 Nov 2003 12:30:52 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592BB@esebe013.ntc.nokia.com>
Thread-Topic: [Sipping] How to control drop algorithms for throttling
Thread-Index: AcOqYqlURp5KoAs9QjeflBRcOjlyrAE64i8Q
To: <hgs@cs.columbia.edu>, <pkyzivat@cisco.com>
Cc: <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 20 Nov 2003 10:30:52.0743 (UTC) FILETIME=[5F96B570:01C3AF51]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Henning,

Inline.

 > Indeed, I wonder if users will really want to get continuous=20
 > updates on=20
 > their buddy list members. I may want some general sense of=20
 > how many of=20
 > my colleagues are around and I may want to quickly determine=20
 > whether a=20
 > particular colleague is around right now, but clicking on=20
 > the name seems=20
 > perfectly fine for that, without getting the detailed updates on the=20
 > person's cell phone idle time every five minutes.

I think you just spelled out a key use case for filtering. If I have 500 =
buddies in my buddy list, plus restricted screen real estate, there =
might only be room for a simple icon to show per buddy. However, without =
being able to control the content of notifications, I would still get =
the full presence of each buddy at all times.=20

Throttling would be able to lower the aggregate rate of those 500 =
subscriptions, but what you really want to do is control the amount of =
content, focusing on the key things you can show to the user in this =
buddy list view. The mechanism for that is filtering.

Cheers,
Aki
=20
 > Paul Kyzivat wrote:
 >=20
 > > Jonathan,
 > >=20
 > > I pretty much agree with you - especially on the need for=20
 > a throttling=20
 > > considerations section. Ultimately, I think this means=20
 > that the notifier=20
 > > application must participate in the throttling in order to=20
 > ensure that=20
 > > the right thing is done.
 > >=20
 > > In some cases it might make the most sense to simply terminate the=20
 > > subscription rather than provide a deceptive view. (So=20
 > that when an=20
 > > event was discarded, at the next permissible time the server would=20
 > > simply send a notification terminating the subscription.)
 > >=20
 > >     Paul
 > >=20
 > > Jonathan Rosenberg wrote:
 > >=20
 > >> This mail is a followup to some comments I made during=20
 > sipping today=20
 > >> on the event throttling work.
 > >>
 > >> Once we add throttling capabilities to the SIP event=20
 > framework, we end=20
 > >> up with a lossy system. Some notifications will be=20
 > dropped, and others=20
 > >> will be transmitted. The problem is that all=20
 > notifications are not=20
 > >> created equally. If the notififer drops notifications at=20
 > random, will=20
 > >> the resulting stream of notifications meet the needs of=20
 > the watcher?=20
 > >> Can we do better than simply dropping notifications randomly?
 > >>
 > >> Some possible things we might do:
 > >>
 > >> 1. instead of dropping notifications, the notifier=20
 > buffers them. If it=20
 > >> receives another notification within the next M seconds,=20
 > it drops the=20
 > >> older one, and sends the newer one. This would allow you=20
 > to control=20
 > >> the rate through delays. I suspect that many applications=20
 > will have a=20
 > >> better sense of the utility of the presence data as a=20
 > function of age.=20
 > >> Do we want the mechanism to support this?
 > >>
 > >> 2. the watcher could provide a filter type of document in the=20
 > >> subscription. This filter could indicate that certain=20
 > transitions are=20
 > >> more important than others. For example, in the case of=20
 > presence, it=20
 > >> might say that transitions of the <basic> status are more=20
 > important=20
 > >> than transitions of the <placetype> from RPID. The=20
 > notifier could use=20
 > >> these to preferentially drop certain notifications over=20
 > others. Do we=20
 > >> want the mechanism to support this?
 > >>
 > >> 3. If we don't use the concepts of (1) and (2), is there=20
 > any value in=20
 > >> applying algorithms like RED to the systems (I dont think=20
 > so, but its=20
 > >> worth considering).
 > >>
 > >> 4. Do we want to specify that each package should have a=20
 > >> considerations section about how to use throttling? In=20
 > particular,=20
 > >> what will be the typical impact on service for various=20
 > loss rates?=20
 > >> Or,  which components of a document should a client ask to have=20
 > >> dropped (assuming the filtering of (2)).
 > >>
 > >>
 > >> Thanks,
 > >> Jonathan R.
 > >=20
 > >=20
 > >=20
 > > _______________________________________________
 > > Sipping mailing list =20
 > https://www1.ietf.org/mailman/listinfo/sipping
 > > This list is for NEW development of the application of SIP
 > > Use sip-implementors@cs.columbia.edu for questions on current sip
 > > Use sip@ietf.org for new developments of core SIP
 >=20
 > _______________________________________________
 > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
 > This list is for NEW development of the application of SIP
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sip@ietf.org for new developments of core SIP
 >=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 06:55:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00077
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 06:55:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMnOt-0002hz-1V
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 06:55:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKBt6LI010404
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 06:55:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMnOs-0002hj-Tw
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 06:55:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00062
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 06:54:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMnOp-0001JT-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 06:55:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMnOp-0001JQ-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 06:55:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMnOn-0002gT-O7; Thu, 20 Nov 2003 06:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMnO2-0002et-RL
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 06:54:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00035
	for <sipping@ietf.org>; Thu, 20 Nov 2003 06:53:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMnNz-0001Ij-00
	for sipping@ietf.org; Thu, 20 Nov 2003 06:54:11 -0500
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMnNy-0001IQ-00
	for sipping@ietf.org; Thu, 20 Nov 2003 06:54:11 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAKBrbh18152
	for <sipping@ietf.org>; Thu, 20 Nov 2003 05:53:38 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2656.59)
	id <4M3X2FN3>; Thu, 20 Nov 2003 11:53:36 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EF11@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'McCandless, Kevin'" <KMcCandless@verisign.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
Date: Thu, 20 Nov 2003 11:53:33 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

You seem to be assuming that the entire protocol space on the IP side is occupied by SIP. SIP is just one of a number of protocols that coexist to provide a solution to a problem.

Therefore, just because something exists in some form in SS7, does not mean that has to automatically have a SIP equivalent. IETF is very strong on smaller protocols working together to provide an end result (unfortunately SIP got out of hand). Therefore it is perfectly acceptable that elements within the scope of SIP are carried in, or mapped to, SIP, but other elements that are in the scope of some other IETF protocol are dealt with by that protocol.

Any requirement for protocol extensions in the IETF space need therefore to answer the question: "Is this the appropriate protocol to extend to carry my functionality?" That is therefore the question I would like to see input to. 

regards

Keith

> -----Original Message-----
> From: McCandless, Kevin [mailto:KMcCandless@verisign.com]
> Sent: 19 November 2003 20:23
> To: 'Drage, Keith (Keith)'
> Cc: sipping@ietf.org; 'Frank W. Miller'
> Subject: RE: [Sipping] RE: [Sip] Sip support for TCAP queries
> 
> 
> So, CNAM, LNP, and other SS7 data is relevant to working SIP 
> networks that interconnect with the PSTN.  There is no 
> standard document to define how the SIP protocol obtains the 
> database information.  Each vendor is implementing their own 
> way of doing this with SIP on one side during the Invite 
> message and on the other side launching an SS7 query either 
> with M3UA or standard SS7 TDM links.  VoIP carriers want 
> access to the data so would it not be helpful to have a 
> standard way of implementing this interworking.  This has 
> already done for ISUP.  SS7 is not going away and the 
> interworking between VoIP and PSTN can only help the VoIP initiatives.
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 07:11:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00874
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 07:11:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMneL-00041m-Rm
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 07:11:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKCB5Ng015476
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 07:11:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMneL-00041X-OQ
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 07:11:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00845
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 07:10:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMneI-0001cc-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 07:11:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMneH-0001cZ-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 07:11:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMneI-00040M-8h; Thu, 20 Nov 2003 07:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMne3-0003zL-Ow
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 07:10:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00830
	for <sipping@ietf.org>; Thu, 20 Nov 2003 07:10:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMne0-0001cS-00
	for sipping@ietf.org; Thu, 20 Nov 2003 07:10:44 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMndz-0001cP-00
	for sipping@ietf.org; Thu, 20 Nov 2003 07:10:43 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAKCAhA05500
	for <sipping@ietf.org>; Thu, 20 Nov 2003 14:10:43 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6605e33d0eac158f2546f@esvir05nok.ntc.nokia.com> for <sipping@ietf.org>;
 Thu, 20 Nov 2003 14:10:42 +0200
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 20 Nov 2003 14:10:41 +0200
Received: from localhost.localdomain (hed042-227.research.nokia.com [172.21.42.227])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id OAA10624;
	Thu, 20 Nov 2003 14:10:44 +0200 (EET)
Received: from localhost.localdomain (localhost [127.0.0.1])
	by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hAKEAXiZ020027;
	Thu, 20 Nov 2003 16:10:33 +0200
Received: (from ppessi@localhost)
	by localhost.localdomain (8.12.8/8.12.5/Submit) id hAKEAXET020026;
	Thu, 20 Nov 2003 16:10:33 +0200
X-Authentication-Warning: localhost.localdomain: ppessi set sender to Pekka.Pessi@nokia.com using -f
To: sipping@ietf.org
Cc: <hisham.khartabil@nokia.com>
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB70118B0FA@esebe019.ntc.nokia.com> ("hisham.khartabil@nokia.com"'s
 message of "Thu, 20 Nov 2003 09:39:39 +0200")
References: <2038BCC78B1AD641891A0D1AE133DBB70118B0FA@esebe019.ntc.nokia.com>
Date: Thu, 20 Nov 2003 16:01:29 +0200
Message-ID: <pvvfpf6sw6.fsf@nokia.com>
User-Agent: Gnus/5.09001 (Oort Gnus v0.10) XEmacs/21.4 (Honest Recruiter,
 i386-redhat-linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 20 Nov 2003 12:10:41.0197 (UTC) FILETIME=[50FC45D0:01C3AF5F]
Subject: [Sipping] Exploders (was: [Simple] ad-hoc list subscriptions)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

"hisham.khartabil@nokia.com" <hisham.khartabil@nokia.com> writes:
>As I said on the mike in the SIMPLE meeting, this issue is not just
>limited to SUBSCRIBE, but the problem also includes MESSAGE, INVITE,
>etc.

>There are already requirements documented in
>http://www.ietf.org/internet-drafts/draft-camarillo-sipping-exploders-00.txt

>Should we discuss those in sipping?

Whatever. ;)

It looks like there are at least three kinds of exploders with
slightly different semantics:

1) (subscription) session exploders, like event lists

2) request exploders, like sending IM to a group 

3) forking exploders, where client defines the target locations 

1 - Session exploders establish session with all resources on
the list, and deliver the combined results from sessions to the
originator. I think this kind of exploders include event lists
(SUBSCRIBE) and group calls (INVITE, REFER).

2 - Request exploders send one request to each list members,
combine results from requests, and send combined result to
originator. This include MESSAGE and other MESSAGE-like request.

3 - Forking exploders fork request and send the best result to
orginator. They work jsut like proxies work today, but the
target location list is provided by client. 

If we define a nice mechanism to deliver combined status of an
exploded request for case 2, I would be tempted to to use the
same mechanisms to deliver combined results of ordinary request
that just got forked.

Now, back to the case 2. It looks like REFER on stereoids, at
least if REFER is your favorite SIP remote control method. In
plain REFER, originator sends a REFER request to server, server
sends a request on its own to the final destination and forwards
the response it got back to orinator within NOTIFY. In order to
do explosion, we just put cid uri in the Refer-To header, send
REFER to exploder then let a exploder server do the magic and
send the combined results in NOTIFY. No SIP-level extension
needed, plain old RFC 3515 stuff (with fancy mime types,
however).

BR,
				Pekka

>> -----Original Message-----
>> From: simple-admin@ietf.org [mailto:simple-admin@ietf.org]On Behalf Of
>> ext Orit Levin
>> Sent: 20.November.2003 03:34
>> To: Adam Roach; simple@ietf.org
>> Subject: RE: [Simple] ad-hoc list subscriptions


>> First of all, I am glad that I am not alone :-)

>> As a direct outcome of the discussion around the ad-hoc list topic in
>> the SIMPLE session, I identified to myself a clear AI to come 
>> up with a
>> requirements draft for how we distribute the dynamic 
>> information, vital
>> for building scalable and interoperable SIMPLE infrastructures.

>> The user's "subscribe list" - is one simple example.
>> - "Single transaction mechanism" is an important requirement to me as
>> well. - Ability to send deltas of a list is also crucial (apropos the
>> discussed exploders' syntax).

>> I also see requirements for exchanging highly dynamic information
>> between/among "Presence Servers" in optimized (e.g. compact) way.

>> When doing all this, I will love to reuse as many basic XML presence
>> schemas as possible.

>> Creation of the requirements draft is a very high priority on 
>> my list. I
>> suggest that we join our efforts and create a taskforce in 
>> order to come
>> up with suggestions/conclusions/directions... faster than usually.

>> I believe that we are in shortage of time here in order for the
>> standards to be adopted by the industry.

>> Orit. 

>> -----Original Message-----
>> From: Adam Roach [mailto:adam@dynamicsoft.com] 
>> Sent: Wednesday, November 19, 2003 3:54 PM
>> To: Orit Levin; simple@ietf.org
>> Subject: RE: [Simple] ad-hoc list subscriptions

>> Orit Levin [mailto:oritl@microsoft.com] writes:

>> > Are we planning to automatically distribute the dynamic lists 
>> > across the network using XCAP?

>> To my understanding, that was the original plan.

>> That said, companies working in the wireless space have
>> been promoting a requirement that devices that use
>> short-lived lists must be able to send the list and the
>> operation that uses the list in a single transaction.

>> I understand this requirement, and think we need some
>> specification to address it. I plan to submit an internet
>> draft that expands on the ideas I have championed in this
>> thread as soon as I have time.

>> Your recent draft makes it clear that using XCAP for these
>> temporary lists doesn't meet your requirements either --
>> but it doesn't clarify what requirements you have on short-
>> lived lists. What I would like to know from you is: is this
>> requirement (a single transaction to specify and use a list)
>> the same as what you need, or do you have additional and/or
>> different requirements?

>> /a



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


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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 09:48:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06740
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 09:48:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMq6M-00085T-6X
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 09:48:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKEmArY031081
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 09:48:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMq6M-00085E-3E
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 09:48:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06724
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 09:47:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMq6J-00047H-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 09:48:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMq6J-00047E-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 09:48:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMq6D-00083r-Sr; Thu, 20 Nov 2003 09:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMq5a-00081k-Jl
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 09:47:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06706
	for <sipping@ietf.org>; Thu, 20 Nov 2003 09:47:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMq5W-00046e-00
	for sipping@ietf.org; Thu, 20 Nov 2003 09:47:18 -0500
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMq5W-00046b-00
	for sipping@ietf.org; Thu, 20 Nov 2003 09:47:18 -0500
Received: from razor.cs.columbia.edu (IDENT:root@razor.cs.columbia.edu [128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hAKEkuU6027972;
	Thu, 20 Nov 2003 09:46:56 -0500 (EST)
Received: from cs.columbia.edu (IDENT:root@localhost [127.0.0.1])
	by razor.cs.columbia.edu (8.11.6/8.9.3) with ESMTP id hAKEksf19828;
	Thu, 20 Nov 2003 09:46:55 -0500
Message-ID: <3FBCD3DF.60507@cs.columbia.edu>
Date: Thu, 20 Nov 2003 09:46:55 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: aki.niemi@nokia.com
CC: pkyzivat@cisco.com, jdrosen@dynamicsoft.com, sipping@ietf.org
Subject: Re: [Sipping] How to control drop algorithms for throttling
References: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592BB@esebe013.ntc.nokia.com>
In-Reply-To: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592BB@esebe013.ntc.nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



aki.niemi@nokia.com wrote:

> Hi Henning,
> 
> Inline.
> 
>> Indeed, I wonder if users will really want to get continuous 
>> updates on their buddy list members. I may want some general sense
>> of how many of my colleagues are around and I may want to quickly
>> determine whether a particular colleague is around right now, but
>> clicking on the name seems perfectly fine for that, without getting
>> the detailed updates on the person's cell phone idle time every
>> five minutes.
> 
> I think you just spelled out a key use case for filtering. If I have
> 500 buddies in my buddy list, plus restricted screen real estate,
> there might only be room for a simple icon to show per buddy.
> However, without being able to control the content of notifications,
> I would still get the full presence of each buddy at all times.

My earlier message goes further than that: in many cases, even filtered 
delivery is too much useless information. Having a quick 
SUBSCRIBE/unsubscribe on demand will work better, with no additional 
filtering effort.

This obviously does not negate the need for filtering.

We do seem to agree that pure blind notification dropping according to 
some arbitrary rate threshold is probably the method least likely to be 
useful in practice, except for the continuous-update cases that I 
mentioned before.

> 
> Throttling would be able to lower the aggregate rate of those 500
> subscriptions, but what you really want to do is control the amount
> of content, focusing on the key things you can show to the user in
> this buddy list view. The mechanism for that is filtering.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Thu Nov 20 19:00:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09212
	for <sipping-archive@odin.ietf.org>; Thu, 20 Nov 2003 19:00:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMyiq-0007fj-DA
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 19:00:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL00SF8029485
	for sipping-archive@odin.ietf.org; Thu, 20 Nov 2003 19:00:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMyio-0007fI-OI
	for sipping-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 19:00:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09188
	for <sipping-web-archive@ietf.org>; Thu, 20 Nov 2003 19:00:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMyik-0007Es-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 19:00:22 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMyiZ-0007Eg-00
	for sipping-web-archive@ietf.org; Thu, 20 Nov 2003 19:00:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMyiR-0007du-Sf; Thu, 20 Nov 2003 19:00:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMyhV-0007TN-7Z
	for sipping@optimus.ietf.org; Thu, 20 Nov 2003 18:59:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09135
	for <sipping@ietf.org>; Thu, 20 Nov 2003 18:58:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMyhR-0007DY-00
	for sipping@ietf.org; Thu, 20 Nov 2003 18:59:02 -0500
Received: from inet11.jrc.co.jp ([203.180.124.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMyhR-0007DJ-00
	for sipping@ietf.org; Thu, 20 Nov 2003 18:59:01 -0500
Received: from vscan.jrc.co.jp by inet11.jrc.co.jp (8.9.3/3.7W)
	id IAA08215; Fri, 21 Nov 2003 08:58:24 +0900 (JST)
Received: from jrcgw1.noc.jrc.co.jp(10.8.1.31) by vscan.jrc.co.jp via csmap 
	 id 6d2ea6b8_1bb5_11d8_9ecb_0002b3c81b92_27585;
	Fri, 21 Nov 2003 08:58:24 +0900 (JST)
Received: from labgw1.lab.jrc.co.jp by jrcgw1.noc.jrc.co.jp (8.9.3/3.7WSaTaMa99081014)
	id IAA15529; Fri, 21 Nov 2003 08:58:23 +0900 (JST)
Received: from [10.38.58.12] (sakai.lab.jrc.co.jp [10.38.58.12])
	by labgw1.lab.jrc.co.jp (8.9.3+3.2W/3.7W-labgw1) with ESMTP id IAA29694;
	Fri, 21 Nov 2003 08:58:23 +0900 (JST)
Date: Fri, 21 Nov 2003 08:58:10 +0900
From: Yutaka SAKAI <sakai@lab.jrc.co.jp>
To: adam@dynamicsoft.com
Cc: sipping@ietf.org
In-Reply-To: <9BF66EBF6BEFD942915B4D4D45C051F3E86641@dyn-tx-exch-001.dynamicsoft.com>
References: <9BF66EBF6BEFD942915B4D4D45C051F3E86641@dyn-tx-exch-001.dynamicsoft.com>
Message-Id: <20031121083934.9282.SAKAI@lab.jrc.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.07.02
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re[2]: Re: SIMPLE vs XMPP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yes, you are correct.
To be sure, some claims lack in the fairness.
Therefore, this is just one of information.
I apologize for having caused misapprehension.

regards,
yutaka

Adam Roach wrote:
> To reinforce Jon's warning: this document in particular
> makes some demonstrably false assertions about SIP/SIMPLE
> that are so specious as to be not worth the effort of
> rebutting.
> 
> It also confounds Jabber with XMPP in a very misleading way.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 12:46:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24137
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 12:46:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANFM7-0007ZC-VN
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 12:46:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALHk72A029080
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 12:46:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANFM7-0007Yx-Q8
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 12:46:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24088
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 12:45:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANFM6-0005yy-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 12:46:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANFM5-0005yv-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 12:46:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANFM2-0007Wj-At; Fri, 21 Nov 2003 12:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANFLn-0007Vx-Jq
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 12:45:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24072
	for <sipping@ietf.org>; Fri, 21 Nov 2003 12:45:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANFLl-0005yU-00
	for sipping@ietf.org; Fri, 21 Nov 2003 12:45:46 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANFLl-0005yQ-00
	for sipping@ietf.org; Fri, 21 Nov 2003 12:45:45 -0500
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hALHjWI2023997;
	Fri, 21 Nov 2003 18:45:32 +0100 (MET)
Received: from ericsson.com (rvi2-92-168.sw.ericsson.se [153.88.92.168]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XF1726FC; Fri, 21 Nov 2003 18:45:39 +0100
Message-ID: <3FBE4F3B.2070403@ericsson.com>
Date: Fri, 21 Nov 2003 19:45:31 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Dean Willis <dean.willis@softarmor.com>, Rohan Mahy <rohan@cisco.com>,
        John Loughney <john.loughney@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Update on SIP-AAA reqs
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

the IESG has sent us some comments regarding the SIP-AAA requirements 
draft. We will be working with people involved in the RADIUS extensions 
work to analyze whether or not all our requirements make sense to them 
as well.

We'll keep you updated on this one. In any case, the draft seems to be 
in a pretty good shape.

Gonzalo


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 14:16:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27350
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 14:16:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANGlD-0005Qd-17
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 14:16:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALJG68o020861
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 14:16:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANGlC-0005QO-T5
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 14:16:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27333
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 14:15:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANGlA-0007Dt-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 14:16:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANGlA-0007Dq-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 14:16:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANGl8-0005PE-6k; Fri, 21 Nov 2003 14:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANGl0-0005Ov-OF
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 14:15:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27330
	for <sipping@ietf.org>; Fri, 21 Nov 2003 14:15:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANGky-0007Dm-00
	for sipping@ietf.org; Fri, 21 Nov 2003 14:15:52 -0500
Received: from mailgw1a.lmco.com ([192.31.106.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANGkx-0007Dj-00
	for sipping@ietf.org; Fri, 21 Nov 2003 14:15:51 -0500
Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [166.29.2.54])
	by mailgw1a.lmco.com (8.12.10/8.12.10) with ESMTP id hALJFUNK000567;
	Fri, 21 Nov 2003 12:15:30 -0700 (MST)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30760) id <0HOP00E01UTP4Z@lmco.com>; Fri,
 21 Nov 2003 12:15:27 -0700 (MST)
Received: from EMSS09I00.us.lmco.com ([158.183.26.31]) by lmco.com (PMDF V6.1-1X6 #30760)
 with ESMTP id <0HOP00ICWUTMNB@lmco.com>; Fri, 21 Nov 2003 12:15:22 -0700 (MST)
Date: Fri, 21 Nov 2003 14:15:13 -0500
From: "Eagan, Christopher" <christopher.eagan@lmco.com>
To: jon.peterson@neustar.biz, jmpolk@cisco.com, douglas.sicker@colorado.edu
Cc: sipping@ietf.org
Message-id: <3F2F205501D3D411878C0008C7E6459410CFECAF@emss09m06.ems.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-Topic: comments on draft-peterson-sipping-role-authz-01
thread-index: AcOwY/FqcF6hvPnSTnKPpRLBBOkjFw==
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7BIT
Subject: [Sipping] comments on draft-peterson-sipping-role-authz-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

I think this draft as a whole is great, and I think a scheme that meets these requirements will be helpful in extending SIP to more applications.  The only issues I have it....

--------------------
Requirement #6: "Proxy servers should have a way to inspect assertions..."

Why not "must have a way..."?  Or "there must be a mechanism for proxy servers to inspect assertions (that may or may not have to be activated, depending on the specific network).

-----------------------
Requirement #7: "The mechanism must have a single baseline mandatory-to-implement authorization assertion scheme".

Why not just have a toolkit that UA's can implement on a needs basis, along the ability to query/answer questions about their capabilities w/ regards to trait based authorization?  There are different levels of security requirements for different examples of where this scheme could be used.  For example, the scenario of asserting the trait of professor in the chemistry department versus asserting the trait that one is a commander in a police department.  Is this a trade-off of requiring more work for implementors at the benefit of more reliable interoperability?  (or am I way off and reading the requirement wrong?)

-----------------------
Requirement #11: "An assertion must have security properties that can prevent unauthorized parties from viewing the contents of the assertion."

I think you mean this as a requirement for the scheme but possibly optional to activate but I think it could be clearer.  Securing the contents of an authorization seems like it may be unecessary in some cases (like possibly asserting you're a professor in the chemistry department).  Possible alt verbage for #11:  "The scheme must provide a mechanism that can prevent unauthorized parties from viewing the contents of the assertion".

------------------------
Requirement #15: "It must be possible for a UAS or proxy server to reject a request that lacks an authorization assertion..."

I'm not reconciling this with #6, that says proxy servers >>should<< have a way to inspect assertions.  Is this a requirement that the proxy server makes sure an assertion is present in a message? or that it is both present and valid?  I would normally assume the latter, except for requirement #6.

Thanks!

Chris

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 15:14:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00330
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 15:14:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANHfM-0000jD-5z
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 15:14:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALKE8Vk002792
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 15:14:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANHfL-0000ix-Uf
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 15:14:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00272
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 15:13:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANHfK-00008w-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 15:14:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANHfK-00008t-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 15:14:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANHfF-0000ho-C4; Fri, 21 Nov 2003 15:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANHer-0000ha-Uc
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 15:13:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00217
	for <sipping@ietf.org>; Fri, 21 Nov 2003 15:13:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANHeq-00008f-00
	for sipping@ietf.org; Fri, 21 Nov 2003 15:13:36 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANHeq-00008S-00
	for sipping@ietf.org; Fri, 21 Nov 2003 15:13:36 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hALKCib9009074;
	Fri, 21 Nov 2003 20:12:44 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHLH6D>; Fri, 21 Nov 2003 14:12:46 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD5648D@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Eagan, Christopher'" <christopher.eagan@lmco.com>, jmpolk@cisco.com,
        douglas.sicker@colorado.edu
Cc: sipping@ietf.org
Date: Fri, 21 Nov 2003 14:12:44 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] RE: comments on draft-peterson-sipping-role-authz-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


> I think this draft as a whole is great, and I think a scheme 
> that meets these requirements will be helpful in extending 
> SIP to more applications.  

Great, thanks!

> The only issues I have it....
> 
> --------------------
> Requirement #6: "Proxy servers should have a way to inspect 
> assertions..."
> 
> Why not "must have a way..."?  Or "there must be a mechanism 
> for proxy servers to inspect assertions (that may or may not 
> have to be activated, depending on the specific network).
> 

Agreed that must is better, and that this requirement could use some
rewording. We aren't really using RFC2119 language in this draft, and
perhaps we should, just to be more specific about these matters.

> -----------------------
> Requirement #7: "The mechanism must have a single baseline 
> mandatory-to-implement authorization assertion scheme".
> 
> Why not just have a toolkit that UA's can implement on a 
> needs basis, along the ability to query/answer questions 
> about their capabilities w/ regards to trait based 
> authorization?  There are different levels of security 
> requirements for different examples of where this scheme 
> could be used.  For example, the scenario of asserting the 
> trait of professor in the chemistry department versus 
> asserting the trait that one is a commander in a police 
> department.  Is this a trade-off of requiring more work for 
> implementors at the benefit of more reliable 
> interoperability?  (or am I way off and reading the 
> requirement wrong?)
> 

The requirement isn't that we accept some particular set of traits (like
'academic' versus 'military' or something), but rather that there be one
format for assertions that all implementations support. SAML is given in the
draft is an example - any number of trait sets can be supported by SAML. The
issue is that if some implementations use SAML, and others use (I don't
know) attribute certificates, or something, to express these traits, then
they won't be interoperable.

> -----------------------
> Requirement #11: "An assertion must have security properties 
> that can prevent unauthorized parties from viewing the 
> contents of the assertion."
> 
> I think you mean this as a requirement for the scheme but 
> possibly optional to activate but I think it could be 
> clearer.  Securing the contents of an authorization seems 
> like it may be unecessary in some cases (like possibly 
> asserting you're a professor in the chemistry department).  
> Possible alt verbage for #11:  "The scheme must provide a 
> mechanism that can prevent unauthorized parties from viewing 
> the contents of the assertion".
> 

I'm fine with your suggested wording.

> ------------------------
> Requirement #15: "It must be possible for a UAS or proxy 
> server to reject a request that lacks an authorization assertion..."
> 
> I'm not reconciling this with #6, that says proxy servers 
> >>should<< have a way to inspect assertions.  Is this a 
> requirement that the proxy server makes sure an assertion is 
> present in a message? or that it is both present and valid?  
> I would normally assume the latter, except for requirement #6.
> 

Granted, it is the latter, and we should fix 6 and this one accordingly. It
is possible, of course, that a particular proxy server would not be
authorized to inspect an assertion (I might want only one proxy in a request
path to be able to inspect it), so we don't want to make 6 say "all
assertions must be readable by all proxy servers", but if a proxy server
must inspect the assertion, and cannot do so or finds it to be invalid, then
that may be grounds to reject a SIP request.

Jon Peterson
Neustar, Inc.

> Thanks!
> 
> Chris
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 16:05:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02685
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 16:05:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISh-0003PE-J5
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALL57lK013086
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISh-0003Oy-Ew
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02585
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 16:04:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISf-0000l5-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISf-0000kx-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISf-0003LN-0f; Fri, 21 Nov 2003 16:05:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISU-0003JZ-47
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 16:04:54 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02534;
	Fri, 21 Nov 2003 16:04:40 -0500 (EST)
Message-Id: <200311212104.QAA02534@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 21 Nov 2003 16:04:40 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-torture-tests-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Session Initiation Protocol Torture Test Messages
	Author(s)	: R. Sparks
	Filename	: draft-ietf-sipping-torture-tests-02.txt
	Pages		: 51
	Date		: 2003-11-21
	
This informational document gives examples of Session Initiation
Protocol (SIP) test messages designed to exercise and 'torture' a
parser.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-torture-tests-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-torture-tests-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-torture-tests-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-21162306.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-torture-tests-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-torture-tests-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-21162306.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 16:05:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02713
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 16:05:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISi-0003Ps-NS
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALL58fM013125
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISi-0003Pc-K1
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 16:05:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02593
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 16:04:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISg-0000lG-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISg-0000kw-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISd-0003Kg-PM; Fri, 21 Nov 2003 16:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISO-0003JS-P4
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 16:04:48 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02520;
	Fri, 21 Nov 2003 16:04:35 -0500 (EST)
Message-Id: <200311212104.QAA02520@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 21 Nov 2003 16:04:35 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-early-media-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Early Media and Ringing Tone Generation in the Session Initiation Protocol
	Author(s)	: G. Camarillo, H. Schulzrinne
	Filename	: draft-ietf-sipping-early-media-01.txt
	Pages		: 11
	Date		: 2003-11-21
	
This document describes how to manage early media in SIP using two
models; the gateway model and the application server model. It also
describes the inputs one needs to consider to define local policies
for ringing tone generation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-media-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-early-media-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-early-media-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-21162256.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-early-media-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-early-media-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-21162256.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 16:53:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02686
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 16:05:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISh-0003PV-N7
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALL57AY013101
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISh-0003P2-H1
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 16:05:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02588
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 16:04:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISf-0000l8-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANISf-0000l4-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:05:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISg-0003Nr-Az; Fri, 21 Nov 2003 16:05:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANISZ-0003Jf-DE
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 16:04:59 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02548;
	Fri, 21 Nov 2003 16:04:46 -0500 (EST)
Message-Id: <200311212104.QAA02548@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 21 Nov 2003 16:04:45 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-early-disposition-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: The Early Session Disposition Type for the Session Initiation Protocol (SIP)
	Author(s)	: 
	Filename	: draft-ietf-sipping-early-disposition-00.txt
	Pages		: 10
	Date		: 2003-11-21
	
This document defines a new disposition type (early-session) for the
Content-Disposition header field in SIP. The treatment of
'early-session' bodies is similar to the treatment of 'session'
bodies. That is, they follow the offer/answer model. Their only
difference is that session descriptions whose disposition type is
'early-session' are used to establish early media sessions within
early dialogs, as opposed to regular sessions within regular dialogs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-disposition-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-early-disposition-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-early-disposition-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-21162318.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-early-disposition-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-early-disposition-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-21162318.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 16:53:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05142
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 16:53:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJDH-0007DK-5E
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:53:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALLrFmR027724
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 16:53:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJDH-0007D5-0s
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 16:53:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05089
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 16:53:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJDE-0001hl-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:53:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJDE-0001hi-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 16:53:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJD3-00079y-Gy; Fri, 21 Nov 2003 16:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJCM-00078A-SH
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 16:52:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04990
	for <sipping@ietf.org>; Fri, 21 Nov 2003 16:52:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJCK-0001fH-00
	for sipping@ietf.org; Fri, 21 Nov 2003 16:52:16 -0500
Received: from mailgw1a.lmco.com ([192.31.106.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJCJ-0001ep-00
	for sipping@ietf.org; Fri, 21 Nov 2003 16:52:15 -0500
Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [166.29.2.54])
	by mailgw1a.lmco.com (8.12.10/8.12.10) with ESMTP id hALLmYNK028822;
	Fri, 21 Nov 2003 14:48:34 -0700 (MST)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30760) id <0HOQ009011WP8A@lmco.com>; Fri,
 21 Nov 2003 14:48:25 -0700 (MST)
Received: from EMSS09I00.us.lmco.com ([158.183.26.31]) by lmco.com (PMDF V6.1-1X6 #30760)
 with ESMTP id <0HOQ00BWB1WLPQ@lmco.com>; Fri, 21 Nov 2003 14:48:22 -0700 (MST)
Date: Fri, 21 Nov 2003 16:48:16 -0500
From: "Eagan, Christopher" <christopher.eagan@lmco.com>
Subject: [Sipping] Resource-Priority header decisions at IETF 58?
To: sipping@ietf.org
Cc: jmpolk@cisco.com, schulzrinne@cs.columbia.edu
Message-id: <3F2F205501D3D411878C0008C7E6459410CFECB2@emss09m06.ems.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-Topic: [Sipping] Resource-Priority header decisions at IETF 58?
thread-index: AcOweVMxFHE1VNyTRcud5Fhs2z8IFA==
Content-Class: urn:content-classes:message
Content-Transfer-Encoding: 7BIT
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Was there any movement or decisions on the Resource-Priority header at IETF 58 that someone can summarize?  (missed that session unfortunately)

Thanks!

Chris

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Fri Nov 21 17:15:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07336
	for <sipping-archive@odin.ietf.org>; Fri, 21 Nov 2003 17:15:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJYZ-0001Iy-GG
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 17:15:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALMFFvS005010
	for sipping-archive@odin.ietf.org; Fri, 21 Nov 2003 17:15:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJYZ-0001Ij-Bq
	for sipping-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 17:15:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07307
	for <sipping-web-archive@ietf.org>; Fri, 21 Nov 2003 17:15:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJYW-0002VG-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 17:15:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJYW-0002VD-00
	for sipping-web-archive@ietf.org; Fri, 21 Nov 2003 17:15:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJYM-0001Eq-TG; Fri, 21 Nov 2003 17:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANJXQ-00015B-AA
	for sipping@optimus.ietf.org; Fri, 21 Nov 2003 17:14:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07152
	for <sipping@ietf.org>; Fri, 21 Nov 2003 17:13:49 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJXM-0002ST-00
	for sipping@ietf.org; Fri, 21 Nov 2003 17:14:00 -0500
Received: from imo-m05.mx.aol.com ([64.12.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANJXL-0002QZ-00
	for sipping@ietf.org; Fri, 21 Nov 2003 17:13:59 -0500
Received: from Mpierce1@aol.com
	by imo-m05.mx.aol.com (mail_out_v36_r1.1.) id l.a3.4ccf9932 (4222)
	 for <sipping@ietf.org>; Fri, 21 Nov 2003 17:12:43 -0500 (EST)
Message-ID: <a3.4ccf9932.2cefe7db@aol.com>
Date: Fri, 21 Nov 2003 17:12:43 EST
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_a3.4ccf9932.2cefe7db_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Subject: [Sipping] User=Phone/DialString and Pause and Wait
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


--part1_a3.4ccf9932.2cefe7db_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Following the discussion in IPTEL (which belongs in SIPPING) concering the 
idea of including "pause" and "wait" in the dial string, I have the following 
comments:

Long before the current revision of RFC2806 was started, it was recognized 
that RFC 2806 was very wrong, and, following my early suggestions on beginning a 
fix, the draft revision came out with these old "AT modem command" functions 
removed. The discussion at last week's meeting about re-adding them is very 
troubling.

The fundamental issue seems to be a lack of agreement on the application, or 
environment, in which the tel:uri or any of its extensions, is to be used. It 
was clear to me from the beginning that the scope of the effort was to provide 
a coding to be used in messages from the end user's terminal (the one 
"dialing") to some other device that might need to interpret those digits for routing 
purposes. As such, it needs to deal with "dial strings" vs "numbers", and 
this has been the main part of the discussion. As stated in the tel:uri draft: 
"the tel:uri describes resources identifed by telephone numbers".

However, at the meeting, this notion of again including "pause" and "wait" 
came up, and when challenged, someone used the example of needing to tell an 
outgoing Gateway how to send the digits into the circuit switched network (PSTN 
or private). I believe this is not in the scope of the effort.

In any case, if someone still thinks it is, some further comments are in 
order:

It should be expected that the interface from a Gateway to the the PSTN would 
use something modern like ISDN, without any notion of pauses or waits.

If a Gateway uses channel associated signaling like DTMF, all modern switches 
only require waiting for dial tone for the first digit, something the Gateway 
must know without it being coded into the digit string. They do not require 
further pauses or waits for dial tone, even if another dial tone is being 
returned to the user (like after dialling "9" in a PBX).

Even with old PSTN switches, the application still is based on sending a 
single string of digits (no pauses or waits).

For the application of telling a Gateway how to send out digits, only the 
"dial string" format, not the "number" format would apply.

Bottom line: the application of coding the digits entered by the originating 
human or agent and the one of telling a Gateway how to send digits are very 
much different and should not be combined into one definition or discussion.

What I find particularly bad about this whole user=phone discussion is that 
this issue was discussed and resolved over 15 years ago for ISDN and documented 
in Q.931 for the Called Party Number. If that definition in Q.931 had been 
used as the base for SIP (with possible deletion of some values that don't 
apply), this whole issue would have been much easier and resolved a long time ago.

Mike Pierce
Artel




--part1_a3.4ccf9932.2cefe7db_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2>Following the discussion=20=
in IPTEL (which belongs in SIPPING) concering the idea of including "pause"=20=
and "wait" in the dial string, I have the following comments:
<BR>
<BR>Long before the current revision of RFC2806 was started, it was recogniz=
ed that RFC 2806 was very wrong, and, following my early suggestions on begi=
nning a fix, the draft revision came out with these old "AT modem command" f=
unctions removed. The discussion at last week's meeting about re-adding them=
 is very troubling.
<BR>
<BR>The fundamental issue seems to be a lack of agreement on the application=
, or environment, in which the tel:uri or any of its extensions, is to be us=
ed. It was clear to me from the beginning that the scope of the effort was t=
o provide a coding to be used in messages from the end user's terminal (the=20=
one "dialing") to some other device that might need to interpret those digit=
s for routing purposes. As such, it needs to deal with "dial strings" vs "nu=
mbers", and this has been the main part of the discussion. As stated in the=20=
tel:uri draft: "the tel:uri describes resources identifed by telephone numbe=
rs".
<BR>
<BR>However, at the meeting, this notion of again including "pause" and "wai=
t" came up, and when challenged, someone used the example of needing to tell=
 an outgoing Gateway how to send the digits into the circuit switched networ=
k (PSTN or private). I believe this is not in the scope of the effort.
<BR>
<BR>In any case, if someone still thinks it is, some further comments are in=
 order:
<BR>
<BR>It should be expected that the interface from a Gateway to the the PSTN=20=
would use something modern like ISDN, without any notion of pauses or waits.
<BR>
<BR>If a Gateway uses channel associated signaling like DTMF, all modern swi=
tches only require waiting for dial tone for the first digit, something the=20=
Gateway must know without it being coded into the digit string. They do not=20=
require further pauses or waits for dial tone, even if another dial tone is=20=
being returned to the user (like after dialling "9" in a PBX).
<BR>
<BR>Even with old PSTN switches, the application still is based on sending a=
 single string of digits (no pauses or waits).
<BR>
<BR>For the application of telling a Gateway how to send out digits, only th=
e "dial string" format, not the "number" format would apply.
<BR>
<BR>Bottom line: the application of coding the digits entered by the origina=
ting human or agent and the one of telling a Gateway how to send digits are=20=
very much different and should not be combined into one definition or discus=
sion.
<BR>
<BR>What I find particularly bad about this whole user=3Dphone discussion is=
 that this issue was discussed and resolved over 15 years ago for ISDN and d=
ocumented in Q.931 for the Called Party Number. If that definition in Q.931=20=
had been used as the base for SIP (with possible deletion of some values tha=
t don't apply), this whole issue would have been much easier and resolved a=20=
long time ago.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR>
<BR></FONT></HTML>

--part1_a3.4ccf9932.2cefe7db_boundary--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov 22 08:56:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11551
	for <sipping-archive@odin.ietf.org>; Sat, 22 Nov 2003 08:56:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYFE-00028f-1i
	for sipping-archive@odin.ietf.org; Sat, 22 Nov 2003 08:56:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAMDuGKW008217
	for sipping-archive@odin.ietf.org; Sat, 22 Nov 2003 08:56:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYFD-00028S-T4
	for sipping-web-archive@optimus.ietf.org; Sat, 22 Nov 2003 08:56:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11545
	for <sipping-web-archive@ietf.org>; Sat, 22 Nov 2003 08:56:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYFC-0004yf-00
	for sipping-web-archive@ietf.org; Sat, 22 Nov 2003 08:56:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYFC-0004yc-00
	for sipping-web-archive@ietf.org; Sat, 22 Nov 2003 08:56:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYF0-00027M-Tm; Sat, 22 Nov 2003 08:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYEh-00026p-91
	for sipping@optimus.ietf.org; Sat, 22 Nov 2003 08:55:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11539
	for <sipping@ietf.org>; Sat, 22 Nov 2003 08:55:30 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYEf-0004yI-00
	for sipping@ietf.org; Sat, 22 Nov 2003 08:55:41 -0500
Received: from imo-d03.mx.aol.com ([205.188.157.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYEf-0004y1-00
	for sipping@ietf.org; Sat, 22 Nov 2003 08:55:41 -0500
Received: from Mpierce1@aol.com
	by imo-d03.mx.aol.com (mail_out_v36_r1.1.) id l.117.2bf49d88 (4592)
	 for <sipping@ietf.org>; Sat, 22 Nov 2003 08:55:05 -0500 (EST)
Message-ID: <117.2bf49d88.2cf0c4b8@aol.com>
Date: Sat, 22 Nov 2003 08:55:04 EST
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_117.2bf49d88.2cf0c4b8_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Subject: [Sipping] Comments on Reason Header for Preemption Events
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


--part1_117.2bf49d88.2cf0c4b8_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Following the discussion in the meeting, I have the following comments on:

draft-polk-sipping-reason-header-for-preemption-00

The current Reason Header provides for coding either a SIP response code or a 
Q.850 ISDN cause code. Since the Q.850 codes are sufficient to support MLPP 
in the existing network, they shoud be sufficient in a SIP controlled network, 
so I am not convinced of the need for this extension.

If this is to published as an Informational RFC, since SIP is to do the 
actual protocol work, Section 4 needs to be deleted.

If not deleted, I understand that it was agreed in the meeting to change 
"preempted_network" to "preempted_resource". This would also require an extensive 
rewrite of section 3, since it specifically describes "Network Preemption".

From the point of view of the "Assured Service" I have been documenting in 
various drafts, the following requirement related to these new Reason Header 
values is the following:

When a user's call (session) is preempted due to either a resource preemption 
(in the network) or an access preemption at the other end of the call 
(session), it MUST NOT be possible for that preempted user to know which of these two 
events occurred.

(In other words, the final sentence in Section 2.0 of the draft is incorrect.)

The result of this requirement is that the reason sent back to UA1 in Figure 
4 cannot be "preempted_UA". It must be "preempted_resource", where it is 
intentionally obscure about which resource was preempted (as shown in Figure 1). 
"Preempted_UA" would only be sent to the UA that is being preempted for a new 
call (UA2 in Figure 4) if 3PCC or a proxy were involved.


Mike Pierce



--part1_117.2bf49d88.2cf0c4b8_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2>Following the discussion=20=
in the meeting, I have the following comments on:
<BR>
<BR>draft-polk-sipping-reason-header-for-preemption-00
<BR>
<BR>The current Reason Header provides for coding either a SIP response code=
 or a Q.850 ISDN cause code. Since the Q.850 codes are sufficient to support=
 MLPP in the existing network, they shoud be sufficient in a SIP controlled=20=
network, so I am not convinced of the need for this extension.
<BR>
<BR>If this is to published as an Informational RFC, since SIP is to do the=20=
actual protocol work, Section 4 needs to be deleted.
<BR>
<BR>If not deleted, I understand that it was agreed in the meeting to change=
 "preempted_network" to "preempted_resource". This would also require an ext=
ensive rewrite of section 3, since it specifically describes "Network Preemp=
tion".
<BR>
<BR>From the point of view of the "Assured Service" I have been documenting=20=
in various drafts, the following requirement related to these new Reason Hea=
der values is the following:
<BR>
<BR>When a user's call (session) is preempted due to either a resource preem=
ption (in the network) or an access preemption at the other end of the call=20=
(session), it MUST NOT be possible for that preempted user to know which of=20=
these two events occurred.
<BR>
<BR>(In other words, the final sentence in Section 2.0 of the draft is incor=
rect.)
<BR>
<BR>The result of this requirement is that the reason sent back to UA1 in Fi=
gure 4 cannot be "preempted_UA". It must be "preempted_resource", where it i=
s intentionally obscure about which resource was preempted (as shown in Figu=
re 1). "Preempted_UA" would only be sent to the UA that is being preempted f=
or a new call (UA2 in Figure 4) if 3PCC or a proxy were involved.
<BR>
<BR>
<BR>Mike Pierce
<BR>
<BR></FONT></HTML>

--part1_117.2bf49d88.2cf0c4b8_boundary--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov 22 08:58:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11612
	for <sipping-archive@odin.ietf.org>; Sat, 22 Nov 2003 08:58:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYGw-0002K4-Uc
	for sipping-archive@odin.ietf.org; Sat, 22 Nov 2003 08:58:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAMDw2cT008922
	for sipping-archive@odin.ietf.org; Sat, 22 Nov 2003 08:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYGw-0002Jp-RK
	for sipping-web-archive@optimus.ietf.org; Sat, 22 Nov 2003 08:58:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11602
	for <sipping-web-archive@ietf.org>; Sat, 22 Nov 2003 08:57:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYGv-00050O-00
	for sipping-web-archive@ietf.org; Sat, 22 Nov 2003 08:58:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYGv-00050J-00
	for sipping-web-archive@ietf.org; Sat, 22 Nov 2003 08:58:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYGv-0002Ib-7I; Sat, 22 Nov 2003 08:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANYGN-0002I5-5U
	for sipping@optimus.ietf.org; Sat, 22 Nov 2003 08:57:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11584
	for <sipping@ietf.org>; Sat, 22 Nov 2003 08:57:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANYGL-0004zn-00
	for sipping@ietf.org; Sat, 22 Nov 2003 08:57:25 -0500
Received: from mail.oefeg.at ([62.47.121.5])
	by ietf-mx with smtp (Exim 4.12)
	id 1ANYGL-0004z6-00
	for sipping@ietf.org; Sat, 22 Nov 2003 08:57:25 -0500
content-class: urn:content-classes:message
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
Date: Sat, 22 Nov 2003 15:02:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <06CF906FE3998C4E944213062009F1622339C3@oefeg-s02.oefeg.loc>
Thread-Topic: [Sipping] User=Phone/DialString and Pause and Wait
Thread-Index: AcOwfcVF5HwvBi4MQXeWYgkBwAfOLgAgyWcR
From: "Stastny Richard" <Richard.Stastny@oefeg.at>
To: <Mpierce1@aol.com>, <sipping@ietf.org>
Content-Transfer-Encoding: base64
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

QW1lbi4NCkkgYWxzbyByZW1lbWJlciBIZW5uaW5nIHNheWluZyB0aGF0IHRoZSB0ZWw6IFVSSSBp
cyBtb3JlIGxpa2UgYW4gVVJOLg0KSSBjYW5ub25vdCBpbWFnaW5lIGFuIFVSTiB3aXRoIGEgcGF1
c2UuDQpSaWNoYXJkDQoNCgktLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tIA0KCVZv
bjogTXBpZXJjZTFAYW9sLmNvbSBbbWFpbHRvOk1waWVyY2UxQGFvbC5jb21dIA0KCUdlc2VuZGV0
OiBGciAyMS4xMS4yMDAzIDIzOjEyIA0KCUFuOiBzaXBwaW5nQGlldGYub3JnIA0KCUNjOiANCglC
ZXRyZWZmOiBbU2lwcGluZ10gVXNlcj1QaG9uZS9EaWFsU3RyaW5nIGFuZCBQYXVzZSBhbmQgV2Fp
dA0KCQ0KCQ0KCUZvbGxvd2luZyB0aGUgZGlzY3Vzc2lvbiBpbiBJUFRFTCAod2hpY2ggYmVsb25n
cyBpbiBTSVBQSU5HKSBjb25jZXJpbmcgdGhlIGlkZWEgb2YgaW5jbHVkaW5nICJwYXVzZSIgYW5k
ICJ3YWl0IiBpbiB0aGUgZGlhbCBzdHJpbmcsIEkgaGF2ZSB0aGUgZm9sbG93aW5nIGNvbW1lbnRz
OiANCgkNCglMb25nIGJlZm9yZSB0aGUgY3VycmVudCByZXZpc2lvbiBvZiBSRkMyODA2IHdhcyBz
dGFydGVkLCBpdCB3YXMgcmVjb2duaXplZCB0aGF0IFJGQyAyODA2IHdhcyB2ZXJ5IHdyb25nLCBh
bmQsIGZvbGxvd2luZyBteSBlYXJseSBzdWdnZXN0aW9ucyBvbiBiZWdpbm5pbmcgYSBmaXgsIHRo
ZSBkcmFmdCByZXZpc2lvbiBjYW1lIG91dCB3aXRoIHRoZXNlIG9sZCAiQVQgbW9kZW0gY29tbWFu
ZCIgZnVuY3Rpb25zIHJlbW92ZWQuIFRoZSBkaXNjdXNzaW9uIGF0IGxhc3Qgd2VlaydzIG1lZXRp
bmcgYWJvdXQgcmUtYWRkaW5nIHRoZW0gaXMgdmVyeSB0cm91YmxpbmcuIA0KCQ0KCVRoZSBmdW5k
YW1lbnRhbCBpc3N1ZSBzZWVtcyB0byBiZSBhIGxhY2sgb2YgYWdyZWVtZW50IG9uIHRoZSBhcHBs
aWNhdGlvbiwgb3IgZW52aXJvbm1lbnQsIGluIHdoaWNoIHRoZSB0ZWw6dXJpIG9yIGFueSBvZiBp
dHMgZXh0ZW5zaW9ucywgaXMgdG8gYmUgdXNlZC4gSXQgd2FzIGNsZWFyIHRvIG1lIGZyb20gdGhl
IGJlZ2lubmluZyB0aGF0IHRoZSBzY29wZSBvZiB0aGUgZWZmb3J0IHdhcyB0byBwcm92aWRlIGEg
Y29kaW5nIHRvIGJlIHVzZWQgaW4gbWVzc2FnZXMgZnJvbSB0aGUgZW5kIHVzZXIncyB0ZXJtaW5h
bCAodGhlIG9uZSAiZGlhbGluZyIpIHRvIHNvbWUgb3RoZXIgZGV2aWNlIHRoYXQgbWlnaHQgbmVl
ZCB0byBpbnRlcnByZXQgdGhvc2UgZGlnaXRzIGZvciByb3V0aW5nIHB1cnBvc2VzLiBBcyBzdWNo
LCBpdCBuZWVkcyB0byBkZWFsIHdpdGggImRpYWwgc3RyaW5ncyIgdnMgIm51bWJlcnMiLCBhbmQg
dGhpcyBoYXMgYmVlbiB0aGUgbWFpbiBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uLiBBcyBzdGF0ZWQg
aW4gdGhlIHRlbDp1cmkgZHJhZnQ6ICJ0aGUgdGVsOnVyaSBkZXNjcmliZXMgcmVzb3VyY2VzIGlk
ZW50aWZlZCBieSB0ZWxlcGhvbmUgbnVtYmVycyIuIA0KCQ0KCUhvd2V2ZXIsIGF0IHRoZSBtZWV0
aW5nLCB0aGlzIG5vdGlvbiBvZiBhZ2FpbiBpbmNsdWRpbmcgInBhdXNlIiBhbmQgIndhaXQiIGNh
bWUgdXAsIGFuZCB3aGVuIGNoYWxsZW5nZWQsIHNvbWVvbmUgdXNlZCB0aGUgZXhhbXBsZSBvZiBu
ZWVkaW5nIHRvIHRlbGwgYW4gb3V0Z29pbmcgR2F0ZXdheSBob3cgdG8gc2VuZCB0aGUgZGlnaXRz
IGludG8gdGhlIGNpcmN1aXQgc3dpdGNoZWQgbmV0d29yayAoUFNUTiBvciBwcml2YXRlKS4gSSBi
ZWxpZXZlIHRoaXMgaXMgbm90IGluIHRoZSBzY29wZSBvZiB0aGUgZWZmb3J0LiANCgkNCglJbiBh
bnkgY2FzZSwgaWYgc29tZW9uZSBzdGlsbCB0aGlua3MgaXQgaXMsIHNvbWUgZnVydGhlciBjb21t
ZW50cyBhcmUgaW4gb3JkZXI6IA0KCQ0KCUl0IHNob3VsZCBiZSBleHBlY3RlZCB0aGF0IHRoZSBp
bnRlcmZhY2UgZnJvbSBhIEdhdGV3YXkgdG8gdGhlIHRoZSBQU1ROIHdvdWxkIHVzZSBzb21ldGhp
bmcgbW9kZXJuIGxpa2UgSVNETiwgd2l0aG91dCBhbnkgbm90aW9uIG9mIHBhdXNlcyBvciB3YWl0
cy4gDQoJDQoJSWYgYSBHYXRld2F5IHVzZXMgY2hhbm5lbCBhc3NvY2lhdGVkIHNpZ25hbGluZyBs
aWtlIERUTUYsIGFsbCBtb2Rlcm4gc3dpdGNoZXMgb25seSByZXF1aXJlIHdhaXRpbmcgZm9yIGRp
YWwgdG9uZSBmb3IgdGhlIGZpcnN0IGRpZ2l0LCBzb21ldGhpbmcgdGhlIEdhdGV3YXkgbXVzdCBr
bm93IHdpdGhvdXQgaXQgYmVpbmcgY29kZWQgaW50byB0aGUgZGlnaXQgc3RyaW5nLiBUaGV5IGRv
IG5vdCByZXF1aXJlIGZ1cnRoZXIgcGF1c2VzIG9yIHdhaXRzIGZvciBkaWFsIHRvbmUsIGV2ZW4g
aWYgYW5vdGhlciBkaWFsIHRvbmUgaXMgYmVpbmcgcmV0dXJuZWQgdG8gdGhlIHVzZXIgKGxpa2Ug
YWZ0ZXIgZGlhbGxpbmcgIjkiIGluIGEgUEJYKS4gDQoJDQoJRXZlbiB3aXRoIG9sZCBQU1ROIHN3
aXRjaGVzLCB0aGUgYXBwbGljYXRpb24gc3RpbGwgaXMgYmFzZWQgb24gc2VuZGluZyBhIHNpbmds
ZSBzdHJpbmcgb2YgZGlnaXRzIChubyBwYXVzZXMgb3Igd2FpdHMpLiANCgkNCglGb3IgdGhlIGFw
cGxpY2F0aW9uIG9mIHRlbGxpbmcgYSBHYXRld2F5IGhvdyB0byBzZW5kIG91dCBkaWdpdHMsIG9u
bHkgdGhlICJkaWFsIHN0cmluZyIgZm9ybWF0LCBub3QgdGhlICJudW1iZXIiIGZvcm1hdCB3b3Vs
ZCBhcHBseS4gDQoJDQoJQm90dG9tIGxpbmU6IHRoZSBhcHBsaWNhdGlvbiBvZiBjb2RpbmcgdGhl
IGRpZ2l0cyBlbnRlcmVkIGJ5IHRoZSBvcmlnaW5hdGluZyBodW1hbiBvciBhZ2VudCBhbmQgdGhl
IG9uZSBvZiB0ZWxsaW5nIGEgR2F0ZXdheSBob3cgdG8gc2VuZCBkaWdpdHMgYXJlIHZlcnkgbXVj
aCBkaWZmZXJlbnQgYW5kIHNob3VsZCBub3QgYmUgY29tYmluZWQgaW50byBvbmUgZGVmaW5pdGlv
biBvciBkaXNjdXNzaW9uLiANCgkNCglXaGF0IEkgZmluZCBwYXJ0aWN1bGFybHkgYmFkIGFib3V0
IHRoaXMgd2hvbGUgdXNlcj1waG9uZSBkaXNjdXNzaW9uIGlzIHRoYXQgdGhpcyBpc3N1ZSB3YXMg
ZGlzY3Vzc2VkIGFuZCByZXNvbHZlZCBvdmVyIDE1IHllYXJzIGFnbyBmb3IgSVNETiBhbmQgZG9j
dW1lbnRlZCBpbiBRLjkzMSBmb3IgdGhlIENhbGxlZCBQYXJ0eSBOdW1iZXIuIElmIHRoYXQgZGVm
aW5pdGlvbiBpbiBRLjkzMSBoYWQgYmVlbiB1c2VkIGFzIHRoZSBiYXNlIGZvciBTSVAgKHdpdGgg
cG9zc2libGUgZGVsZXRpb24gb2Ygc29tZSB2YWx1ZXMgdGhhdCBkb24ndCBhcHBseSksIHRoaXMg
d2hvbGUgaXNzdWUgd291bGQgaGF2ZSBiZWVuIG11Y2ggZWFzaWVyIGFuZCByZXNvbHZlZCBhIGxv
bmcgdGltZSBhZ28uIA0KCQ0KCU1pa2UgUGllcmNlIA0KCUFydGVsIA0KCQ0KCQ0KCQ0KDQo=

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 23 09:37:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21606
	for <sipping-archive@odin.ietf.org>; Sun, 23 Nov 2003 09:37:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANvMN-0006nC-1x
	for sipping-archive@odin.ietf.org; Sun, 23 Nov 2003 09:37:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hANEbAWI026104
	for sipping-archive@odin.ietf.org; Sun, 23 Nov 2003 09:37:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANvML-0006mx-PA
	for sipping-web-archive@optimus.ietf.org; Sun, 23 Nov 2003 09:37:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21603
	for <sipping-web-archive@ietf.org>; Sun, 23 Nov 2003 09:36:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANvMJ-0003NS-00
	for sipping-web-archive@ietf.org; Sun, 23 Nov 2003 09:37:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANvMJ-0003NO-00
	for sipping-web-archive@ietf.org; Sun, 23 Nov 2003 09:37:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANvME-0006jj-17; Sun, 23 Nov 2003 09:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANvLm-0006ix-1P
	for sipping@optimus.ietf.org; Sun, 23 Nov 2003 09:36:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21587
	for <sipping@ietf.org>; Sun, 23 Nov 2003 09:36:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANvLk-0003Mv-00
	for sipping@ietf.org; Sun, 23 Nov 2003 09:36:32 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANvLj-0003Mh-00
	for sipping@ietf.org; Sun, 23 Nov 2003 09:36:31 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hANEZxjq016263;
	Sun, 23 Nov 2003 06:35:59 -0800 (PST)
Received: from [10.32.245.146] (stealth-10-32-245-146.cisco.com [10.32.245.146])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AKE79716;
	Sun, 23 Nov 2003 06:35:58 -0800 (PST)
Date: Sun, 23 Nov 2003 09:35:55 -0500
From: "David R. Oran" <oran@cisco.com>
To: Mpierce1@aol.com, sipping@ietf.org
Subject: Re: [Sipping] Comments on Reason Header for Preemption Events
Message-ID: <603141671.1069580155@[10.32.245.146]>
In-Reply-To: <117.2bf49d88.2cf0c4b8@aol.com>
References:  <117.2bf49d88.2cf0c4b8@aol.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========E326474ABF7E8899F904=========="
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

--==========E326474ABF7E8899F904==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

--On Saturday, November 22, 2003 8:55 AM -0500 Mpierce1@aol.com wrote:

> Following the discussion in the meeting, I have the following comments
> on:
>
> draft-polk-sipping-reason-header-for-preemption-00
>
> The current Reason Header provides for coding either a SIP response code
> or a Q.850 ISDN cause code. Since the Q.850 codes are sufficient to
> support MLPP in the existing network, they shoud be sufficient in a SIP
> controlled network, so I am not convinced of the need for this extension.
>
I might be willing to buy your conclusion, but your logic escapes me. Just=20
because the methods for preempting space at the water trough for pony=20
express horses is demonstrably adequate for the western mail system, does=20
not mean they are adequate for preempting traffic flow on today's roads for =

ambulances.

> If this is to published as an Informational RFC, since SIP is to do the
> actual protocol work, Section 4 needs to be deleted.
>
> If not deleted, I understand that it was agreed in the meeting to change
> "preempted_network" to "preempted_resource". This would also require an
> extensive rewrite of section 3, since it specifically describes "Network
> Preemption".
>
You seem to have a very narrow and politicized view of what constitutes a=20
"network". What precisely concerns you with the use of this term?

> From the point of view of the "Assured Service" I have been documenting
> in various drafts, the following requirement related to these new Reason
> Header values is the following:
>
> When a user's call (session) is preempted due to either a resource
> preemption (in the network) or an access preemption at the other end of
> the call (session), it MUST NOT be possible for that preempted user to
> know which of these two events occurred.
>
Huh? Why? I think you're still living in TDM-land, or at least in the land=20
with some kind of regulatory hard boundary between "the network" and "the=20
user" where somehow letting the user know which happened opens up some kind =

of opportunity for abuse, or a wedge through which the lawyers enter. Could =

you give some justification in the environment of the Internet for=20
introducing this kind of information hiding?

> (In other words, the final sentence in Section 2.0 of the draft is
> incorrect.)
>
> The result of this requirement is that the reason sent back to UA1 in
> Figure 4 cannot be "preempted_UA". It must be "preempted_resource", where
> it is intentionally obscure about which resource was preempted (as shown
> in Figure 1). "Preempted_UA" would only be sent to the UA that is being
> preempted for a new call (UA2 in Figure 4) if 3PCC or a proxy were
> involved.
>
I disagree with all of the above, but my disagreement may of course be=20
based on misunderstanding or poor logic, so please convince me that I'm=20
wrong here.

Dave.

>
> Mike Pierce
>



------------------------
David R. Oran
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720
Office: +1 978 264 2048
VoIP: +1 408 571 4576
Email: oran@cisco.com
--==========E326474ABF7E8899F904==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: Mulberry PGP Plugin v3.0
Comment: processed by Mulberry PGP Plugin

iQA/AwUBP8DFzI1mhLZU3SrmEQLJLwCgtuaFquKIm6TSvuYbdQfjsmL38DMAmQFh
6N9DO47L7MInrC3AtKlT1l5g
=fZSs
-----END PGP SIGNATURE-----

--==========E326474ABF7E8899F904==========--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 23 22:01:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08659
	for <sipping-archive@odin.ietf.org>; Sun, 23 Nov 2003 22:01:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6yK-0007fT-IG
	for sipping-archive@odin.ietf.org; Sun, 23 Nov 2003 22:01:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO318DM029471
	for sipping-archive@odin.ietf.org; Sun, 23 Nov 2003 22:01:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6yK-0007fF-CJ
	for sipping-web-archive@optimus.ietf.org; Sun, 23 Nov 2003 22:01:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08633
	for <sipping-web-archive@ietf.org>; Sun, 23 Nov 2003 22:00:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6yH-0003Nx-00
	for sipping-web-archive@ietf.org; Sun, 23 Nov 2003 22:01:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6yG-0003Nu-00
	for sipping-web-archive@ietf.org; Sun, 23 Nov 2003 22:01:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6yE-0007d4-Ie; Sun, 23 Nov 2003 22:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AO6y9-0007cD-P4
	for sipping@optimus.ietf.org; Sun, 23 Nov 2003 22:00:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08619
	for <sipping@ietf.org>; Sun, 23 Nov 2003 22:00:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AO6y6-0003NY-00
	for sipping@ietf.org; Sun, 23 Nov 2003 22:00:54 -0500
Received: from goalie.snowshore.com ([216.57.133.4] helo=webshield.office.snowshore.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AO6y6-0003N9-00
	for sipping@ietf.org; Sun, 23 Nov 2003 22:00:54 -0500
Received: from zoe.office.snowshore.com(192.168.1.172) by webshield.office.snowshore.com via csmap 
	 id 6040; Sun, 23 Nov 2003 22:06:31 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] How to control drop algorithms for throttling
Date: Sun, 23 Nov 2003 22:00:24 -0500
Message-ID: <4A3384433CE2AB46A63468CB207E209D4F6A3F@zoe.office.snowshore.com>
Thread-Topic: [Sipping] How to control drop algorithms for throttling
Thread-Index: AcOvdWbwQC5Ln7UiTxOX1qdjqUwBLACwVchA
From: "Eric Burger" <eburger@snowshore.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, <aki.niemi@nokia.com>
Cc: <pkyzivat@cisco.com>, <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I said it before, and I'll say it again:

    Rate limiting / throttling is a function of the semantics of the=20
    event package.  There CANNOT be a sensible, generic rate limiting
    method.

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Thu, November 20, 2003 9:47 AM
> To: aki.niemi@nokia.com
> Cc: pkyzivat@cisco.com; jdrosen@dynamicsoft.com; sipping@ietf.org
> Subject: Re: [Sipping] How to control drop algorithms for throttling
>=20
>=20
>=20
>=20
> aki.niemi@nokia.com wrote:
>=20
> > Hi Henning,
> >=20
> > Inline.
> >=20
> >> Indeed, I wonder if users will really want to get continuous=20
> >> updates on their buddy list members. I may want some general sense
> >> of how many of my colleagues are around and I may want to quickly
> >> determine whether a particular colleague is around right now, but
> >> clicking on the name seems perfectly fine for that, without getting
> >> the detailed updates on the person's cell phone idle time every
> >> five minutes.
> >=20
> > I think you just spelled out a key use case for filtering. If I have
> > 500 buddies in my buddy list, plus restricted screen real estate,
> > there might only be room for a simple icon to show per buddy.
> > However, without being able to control the content of notifications,
> > I would still get the full presence of each buddy at all times.
>=20
> My earlier message goes further than that: in many cases,=20
> even filtered=20
> delivery is too much useless information. Having a quick=20
> SUBSCRIBE/unsubscribe on demand will work better, with no additional=20
> filtering effort.
>=20
> This obviously does not negate the need for filtering.
>=20
> We do seem to agree that pure blind notification dropping=20
> according to=20
> some arbitrary rate threshold is probably the method least=20
> likely to be=20
> useful in practice, except for the continuous-update cases that I=20
> mentioned before.
>=20
> >=20
> > Throttling would be able to lower the aggregate rate of those 500
> > subscriptions, but what you really want to do is control the amount
> > of content, focusing on the key things you can show to the user in
> > this buddy list view. The mechanism for that is filtering.
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20
>=20


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 01:38:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14310
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 01:38:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOAMK-00011n-1T
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 01:38:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO6c7Hi003945
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 01:38:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOAMJ-00011Y-SF
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 01:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14299
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 01:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOAMG-0006rs-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 01:38:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOAMG-0006rp-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 01:38:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOAME-0000zW-SB; Mon, 24 Nov 2003 01:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOALr-0000qZ-O5
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 01:37:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14256
	for <sipping@ietf.org>; Mon, 24 Nov 2003 01:37:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOALo-0006rU-00
	for sipping@ietf.org; Mon, 24 Nov 2003 01:37:36 -0500
Received: from [202.96.122.72] (helo=mail1.eastcom.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AOALn-0006qx-00
	for sipping@ietf.org; Mon, 24 Nov 2003 01:37:36 -0500
Received: from zfzhao ([10.8.18.89]) by mail1.eastcom.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 24 Nov 2003 14:36:38 +0800
Message-ID: <00ae01c3b254$c8139770$5912080a@rd.eastcom>
From: "jeff zhao" <zhaozf@eastcom.com>
To: <sipping@ietf.org>
Date: Mon, 24 Nov 2003 14:32:49 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 24 Nov 2003 06:36:38.0816 (UTC) FILETIME=[5072A200:01C3B255]
Content-Transfer-Encoding: base64
Subject: [Sipping] whiteboard and application sharing with SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

RGVhciBhbGw6DQoNCiAgICAgICBJbiBILjMyMyB2aWRlbyBjb25mZXJlbmNlIHN5c3RlbSwgdGhl
cmUgaXMgVC4xMjAgc2VyaWVzIHByb3RvY29sIGZvciB3aGl0ZWJvYXJkKFQuMTI2KSBhbmQgYXBw
bGljYXRpb24gc2hhcmluZyhULjEyOCkuDQoNCiAgICAgIElmIHdlIHVzZSBTSVAgdG8gYnVpbGlk
IGEgdmlkZW8gY29uZmVyZW5jZSBzeXN0ZW0sIGhvdyBjYW4gd2UgaW1wbGVtZW50IHdoaXRlYm9h
cmQgYW5kIGFwcGxpY2F0aW9uIHNoYXJpbmc/IElzIHRoZXJlIGFueQ0Kc3RhbmRhcmRzIG9yIGRy
YWZ0cyBmb3IgaXQ/DQoNCiAgICAgVGhhbmsgeW91Lg0KICANCkplZmYgemhhbw==



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 03:29:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29580
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 03:29:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOC5k-0000TR-Ns
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 03:29:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAO8T8JW001817
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 03:29:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOC5k-0000TD-5i
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 03:29:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29558
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 03:28:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOC5h-0000Nf-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 03:29:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOC5h-0000Nc-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 03:29:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOC5e-0000Rx-0M; Mon, 24 Nov 2003 03:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOC4i-0000QD-56
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 03:28:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29540
	for <sipping@ietf.org>; Mon, 24 Nov 2003 03:27:49 -0500 (EST)
From: aki.niemi@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOC4f-0000N1-00
	for sipping@ietf.org; Mon, 24 Nov 2003 03:28:01 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOC4e-0000Ms-00
	for sipping@ietf.org; Mon, 24 Nov 2003 03:28:00 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAO8OoA26590
	for <sipping@ietf.org>; Mon, 24 Nov 2003 10:27:32 +0200 (EET)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6619ad6fe7ac158f25048@esvir05nok.ntc.nokia.com>;
 Mon, 24 Nov 2003 10:24:20 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 24 Nov 2003 10:24:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Subject: RE: [Sipping] How to control drop algorithms for throttling
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Nov 2003 10:24:20 +0200
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD902D592C0@esebe013.ntc.nokia.com>
Thread-Topic: [Sipping] How to control drop algorithms for throttling
Thread-Index: AcOvdWbwQC5Ln7UiTxOX1qdjqUwBLACwVchAAArXDDA=
To: <eburger@snowshore.com>, <hgs@cs.columbia.edu>
Cc: <pkyzivat@cisco.com>, <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 24 Nov 2003 08:24:21.0338 (UTC) FILETIME=[5C693BA0:01C3B264]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Eric,

 > I said it before, and I'll say it again:
 >=20
 >     Rate limiting / throttling is a function of the semantics of the=20
 >     event package.  There CANNOT be a sensible, generic rate limiting
 >     method.

I remember you saying this about filtering. Can you explain a bit =
further how you see a generic throttling method go against the semantics =
of an event package? Do you not agree with the model in:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-event-throttle-req=
s-00.txt ?

Jonathan pointed out that a throttled system is a lossy one, and that we =
should look at how notifications are dropped. Since there is possibility =
for a wide variety of different event packets carrying different types =
of event state, the drop algorithm of the notifier should be well =
defined, or even configurable by the watcher, or specified event package =
respectively.

My argument has been that an event system is inherently a lossy one, and =
that the drop algorithms that are applied to notifications occurring =
more frequent than the default notification rate of the event package =
are no different from the ones applied when notifications occur more =
frequent than the throttled rate limit.

What the throttle ultimately does is increase the loss probability of =
the system.=20

Regards,
Aki

 >=20
 > > -----Original Message-----
 > > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
 > > Sent: Thu, November 20, 2003 9:47 AM
 > > To: aki.niemi@nokia.com
 > > Cc: pkyzivat@cisco.com; jdrosen@dynamicsoft.com; sipping@ietf.org
 > > Subject: Re: [Sipping] How to control drop algorithms for=20
 > throttling
 > >=20
 > >=20
 > >=20
 > >=20
 > > aki.niemi@nokia.com wrote:
 > >=20
 > > > Hi Henning,
 > > >=20
 > > > Inline.
 > > >=20
 > > >> Indeed, I wonder if users will really want to get continuous=20
 > > >> updates on their buddy list members. I may want some=20
 > general sense
 > > >> of how many of my colleagues are around and I may want=20
 > to quickly
 > > >> determine whether a particular colleague is around=20
 > right now, but
 > > >> clicking on the name seems perfectly fine for that,=20
 > without getting
 > > >> the detailed updates on the person's cell phone idle time every
 > > >> five minutes.
 > > >=20
 > > > I think you just spelled out a key use case for=20
 > filtering. If I have
 > > > 500 buddies in my buddy list, plus restricted screen real estate,
 > > > there might only be room for a simple icon to show per buddy.
 > > > However, without being able to control the content of=20
 > notifications,
 > > > I would still get the full presence of each buddy at all times.
 > >=20
 > > My earlier message goes further than that: in many cases,=20
 > > even filtered=20
 > > delivery is too much useless information. Having a quick=20
 > > SUBSCRIBE/unsubscribe on demand will work better, with no=20
 > additional=20
 > > filtering effort.
 > >=20
 > > This obviously does not negate the need for filtering.
 > >=20
 > > We do seem to agree that pure blind notification dropping=20
 > > according to=20
 > > some arbitrary rate threshold is probably the method least=20
 > > likely to be=20
 > > useful in practice, except for the continuous-update cases that I=20
 > > mentioned before.
 > >=20
 > > >=20
 > > > Throttling would be able to lower the aggregate rate of those 500
 > > > subscriptions, but what you really want to do is control=20
 > the amount
 > > > of content, focusing on the key things you can show to=20
 > the user in
 > > > this buddy list view. The mechanism for that is filtering.
 > >=20
 > >=20
 > > _______________________________________________
 > > Sipping mailing list =20
 > https://www1.ietf.org/mailman/listinfo/sipping
 > > This list is for NEW development of the application of SIP
 > > Use sip-implementors@cs.columbia.edu for questions on current sip
 > > Use sip@ietf.org for new developments of core SIP
 > >=20
 > >=20
 >=20
 >=20

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 08:41:08 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07722
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 08:41:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOGxQ-0001WL-9j
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAODeqGx005842
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 08:40:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOGxO-0001W2-Mx
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 08:40:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07602
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 08:40:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOGxN-0004wE-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:49 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOGxM-0004vi-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:48 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AOGwj-0002Hr-8z
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 08:40:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOGwb-0001PW-SE; Mon, 24 Nov 2003 08:40:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOGwP-0001Oo-Ss
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 08:39:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07580
	for <sipping@ietf.org>; Mon, 24 Nov 2003 08:39:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOGwO-0004vR-00
	for sipping@ietf.org; Mon, 24 Nov 2003 08:39:48 -0500
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOGwO-0004us-00
	for sipping@ietf.org; Mon, 24 Nov 2003 08:39:48 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr2.ericy.com (8.12.10/8.12.10) with ESMTP id hAODdBYb004167;
	Mon, 24 Nov 2003 07:39:12 -0600 (CST)
Received: from ericsson.com (rvi2-92-57.sw.ericsson.se [153.88.92.57]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XH3Y0VCA; Mon, 24 Nov 2003 07:39:04 -0600
Message-ID: <3FC209FA.6030004@ericsson.com>
Date: Mon, 24 Nov 2003 15:39:06 +0200
X-Sybari-Trust: 884f54fc 6fa56f4d 0641cb9c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Adam Roach <adam@dynamicsoft.com>, Aki.Niemi@nokia.com,
        Hisham.Khartabil@nokia.com, Markus.Isomaki@nokia.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Exploders anad ad-hoc lists
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

we have just submitted three drafts about exploders and ad-hoc lists.

We have added more requirements to the following draft. The new 
requirements were mainly discussed in the SIMPLE mailing list.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exploders-01.txt

The following draft describes how to carry lists of URIs in SIP 
requests. It is not a finished draft. It is intended to trigger 
discussions on this topic to see whether this is a step the right direction.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri-list-00.txt

The following draft defines a new method called EXPLODE. EXPLODE does 
the same as REFER. That is, it tells a UA to send a request somewhere. 
The differences are that EXPLODE accepts more than one destination 
(REFER carries a single Refer-To header field) and that EXPLODE does not 
establish implicit subscriptions of any type. This draft is also 
intended to trigger discussions within the WG.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-explode-method-00.txt

Let's try to keep discussions about this topic in the SIPPING mailing 
list. I will forward this mail to the SIMPLE mailing list to let them know.

Comments are welcome,

Gonzalo



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 10:48:14 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13595
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 10:48:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIwR-0003kl-N5
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 10:48:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOFlxSg014421
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 10:47:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIwR-0003kW-Ht
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 10:47:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13514
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 10:47:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIwP-0007An-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 10:47:57 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIwO-0007AN-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 10:47:56 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AOIpD-0006Gx-DZ
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 10:40:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIom-000360-0C; Mon, 24 Nov 2003 10:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOInz-00034q-5p
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 10:39:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13090
	for <sipping@ietf.org>; Mon, 24 Nov 2003 10:38:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOInw-00070x-00
	for sipping@ietf.org; Mon, 24 Nov 2003 10:39:12 -0500
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOInv-00070t-00
	for sipping@ietf.org; Mon, 24 Nov 2003 10:39:12 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr2.ericy.com (8.12.10/8.12.10) with ESMTP id hAOFcVYb004632;
	Mon, 24 Nov 2003 09:38:31 -0600 (CST)
Received: from ericsson.com (rvi2-92-57.sw.ericsson.se [153.88.92.57]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id XH3ZAGSN; Mon, 24 Nov 2003 09:38:24 -0600
Message-ID: <3FC225F3.4070801@ericsson.com>
Date: Mon, 24 Nov 2003 17:38:27 +0200
X-Sybari-Trust: 916525ca 6fa56f4d 0641cb9c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: Dean Willis <dean.willis@softarmor.com>, Rohan Mahy <rohan@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Early media drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I have submitted the two following drafts on early media. I believe I 
have addressed all the comments I have received during the last months. 
So, I intend to request a WGLC from the chairs fairly soon. If anybody 
has further comments before I do that, please let me know.

http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-disposition-00.txt

http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-media-01.txt

Thanks,

Gonzalo


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 11:48:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15453
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 11:48:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJse-00072Z-0t
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 11:48:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOGm7Ei027057
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 11:48:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJsd-00072K-TS
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 11:48:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15445
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 11:47:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJsc-0000AS-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 11:48:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJsc-0000AP-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 11:48:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJsX-00070X-FI; Mon, 24 Nov 2003 11:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJrh-0006yJ-DX
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 11:47:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15380
	for <sipping@ietf.org>; Mon, 24 Nov 2003 11:46:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJrf-00009F-00
	for sipping@ietf.org; Mon, 24 Nov 2003 11:47:07 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJrf-00008e-00
	for sipping@ietf.org; Mon, 24 Nov 2003 11:47:07 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA18491;
	Mon, 24 Nov 2003 11:46:34 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA28904;
	Mon, 24 Nov 2003 11:46:35 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7W2X7>; Mon, 24 Nov 2003 11:46:35 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B610E@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Mon, 24 Nov 2003 11:46:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Rumors are always fascinating to watch form and spread.

Contrary to what you may have heard, no one has proposed modifying
a tel uri to carry a dial string, nor to permit pause/wait in a tel uri.

What was proposed was a new option for the user parameter of a sip uri,
so that you could have a uri of the form:

sip:6000w6826@example.com;user=dialstring

We all agreed that a tel uri, which is also convertible to a sip uri
with the user=phone convention, remained a way to express local or global
phone numbers, and not dial strings.

>It should be expected that the interface from a Gateway to the 
>PSTN would use something modern like ISDN, without any notion of pauses 
>or waits. 
Sorry that the world does not meet your expectations, but there are tens
of thousands of analog gateways out there that use DTMF

>If a Gateway uses channel associated signaling like DTMF, all modern 
>switches only require waiting for dial tone for the first digit, 
>something the Gateway must know without it being coded into the digit 
>string. They do not require further pauses or waits for dial tone, 
>even if another dial tone is being returned to the user (like after 
>dialing "9" in a PBX).
Again, the world does not meet your expectations.  If you were to dial
6000 on my local PBX from any station, you would discover that if
you waited for a dial tone, and entered a 4 digit extension, you would
find yourself depositing a voice mail in the extension's voicemailbox.
If you choose not to wait, you would find that you would often get an
error.

The gateway can insert the pause/wait.  Not all analog gateways do, but
those that do need a standardize way to send a dialstring to it.

We actually use this in our "call forward, no answer" behavior.  We
store a URI like the above in a database, and when the proxy server
handles the call forwarding behavior, it forwards the call to the
gateway with a uri not much different than the example above (the
host is the gateway, rather than the local proxy server, so it's
really something like sip:6000w6826@gw1.example.com 

>What I find particularly bad about this whole user=phone discussion 
>is that this issue was discussed and resolved over 15 years ago for 
>ISDN and documented in Q.931 for the Called Party Number. If that 
>definition in Q.931 had been used as the base for SIP (with possible 
>deletion of some values that don't apply), this whole issue would have
>been much easier and resolved a long time ago.
Well, once again, surprise, the world doesn't meet your expectations,
nor that of the ITU.  Q.931 has not taken over, even today, for UNI
dialing.  In fact, here in North America, backwards that we are,
Q.931 basically went pffft, except the last 5 or 6 years on T1s.  
Certainly at the station level, there is still a ton of DTMF, and we have
to be able to deal with it, because there are two ends (a gateway and
a UA/proxy server), and they need a standardized way to communicate.
Dialstrings are a fact of life in the real world.

But, we didn't change the tel uri, because there is no need to.

Brian 


-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Friday, November 21, 2003 5:13 PM
To: sipping@ietf.org
Subject: [Sipping] User=Phone/DialString and Pause and Wait


Following the discussion in IPTEL (which belongs in SIPPING) concering the
idea of including "pause" and "wait" in the dial string, I have the
following comments: 

Long before the current revision of RFC2806 was started, it was recognized
that RFC 2806 was very wrong, and, following my early suggestions on
beginning a fix, the draft revision came out with these old "AT modem
command" functions removed. The discussion at last week's meeting about
re-adding them is very troubling. 

The fundamental issue seems to be a lack of agreement on the application, or
environment, in which the tel:uri or any of its extensions, is to be used.
It was clear to me from the beginning that the scope of the effort was to
provide a coding to be used in messages from the end user's terminal (the
one "dialing") to some other device that might need to interpret those
digits for routing purposes. As such, it needs to deal with "dial strings"
vs "numbers", and this has been the main part of the discussion. As stated
in the tel:uri draft: "the tel:uri describes resources identifed by
telephone numbers". 

However, at the meeting, this notion of again including "pause" and "wait"
came up, and when challenged, someone used the example of needing to tell an
outgoing Gateway how to send the digits into the circuit switched network
(PSTN or private). I believe this is not in the scope of the effort. 

In any case, if someone still thinks it is, some further comments are in
order: 

It should be expected that the interface from a Gateway to the the PSTN
would use something modern like ISDN, without any notion of pauses or waits.


If a Gateway uses channel associated signaling like DTMF, all modern
switches only require waiting for dial tone for the first digit, something
the Gateway must know without it being coded into the digit string. They do
not require further pauses or waits for dial tone, even if another dial tone
is being returned to the user (like after dialling "9" in a PBX). 

Even with old PSTN switches, the application still is based on sending a
single string of digits (no pauses or waits). 

For the application of telling a Gateway how to send out digits, only the
"dial string" format, not the "number" format would apply. 

Bottom line: the application of coding the digits entered by the originating
human or agent and the one of telling a Gateway how to send digits are very
much different and should not be combined into one definition or discussion.


What I find particularly bad about this whole user=phone discussion is that
this issue was discussed and resolved over 15 years ago for ISDN and
documented in Q.931 for the Called Party Number. If that definition in Q.931
had been used as the base for SIP (with possible deletion of some values
that don't apply), this whole issue would have been much easier and resolved
a long time ago. 

Mike Pierce 
Artel 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 13:30:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20060
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 13:30:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOLTR-00063W-O5
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 13:30:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOIUDsw023272
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 13:30:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOLTR-00063G-Im
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 13:30:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20038
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 13:29:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOLTP-0001pD-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 13:30:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOLTO-0001p9-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 13:30:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOLTH-00061x-C1; Mon, 24 Nov 2003 13:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOLTB-00061J-NO
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 13:29:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20032
	for <sipping@ietf.org>; Mon, 24 Nov 2003 13:29:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOLT8-0001oy-00
	for sipping@ietf.org; Mon, 24 Nov 2003 13:29:54 -0500
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOLT7-0001ov-00
	for sipping@ietf.org; Mon, 24 Nov 2003 13:29:53 -0500
Received: from bdsl.greycouncil.com (www.softarmor.com [127.0.0.1])
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id hAOIVrud012242
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 24 Nov 2003 12:31:53 -0600
Received: (from dwillis@localhost)
	by bdsl.greycouncil.com (8.12.8/8.12.8/Submit) id hAOIVrO3012240;
	Mon, 24 Nov 2003 12:31:53 -0600
X-Authentication-Warning: bdsl.greycouncil.com: dwillis set sender to dean.willis@softarmor.com using -f
From: Dean Willis <dean.willis@softarmor.com>
To: sipping@ietf.org
Cc: Tyler_Johnson@unc.edu
In-Reply-To: <4297DD64C36B80448637DC966CB492AE60459E@UABEXMB1.ad.uab.edu>
References: <4297DD64C36B80448637DC966CB492AE60459E@UABEXMB1.ad.uab.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1069698712.11916.91.camel@bdsl.greycouncil.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Mon, 24 Nov 2003 12:31:52 -0600
Content-Transfer-Encoding: 7bit
Subject: [Sipping] ITU H.350-related Directory Services Internet Draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


If you are interested in integrating directory services with SIP, please
review:

http://www.ietf.org/internet-drafts/draft-h350-directory-services-00.txt


Thanks!

--
Dean

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 17:02:05 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05333
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 17:02:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOOmE-0005ZR-4M
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 17:01:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOM1oHU021407
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 17:01:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOOmD-0005ZB-Vu
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 17:01:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05227
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 17:01:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOOmB-0006au-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 17:01:47 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOOhA-0006CS-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 16:56:37 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AOOXa-0008UX-8i
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 16:46:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOOWw-0003uy-Vh; Mon, 24 Nov 2003 16:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOOWX-0003tM-GQ
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 16:45:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03260
	for <sipping@ietf.org>; Mon, 24 Nov 2003 16:45:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOOWV-0005oT-00
	for sipping@ietf.org; Mon, 24 Nov 2003 16:45:35 -0500
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOOWU-0005mG-00
	for sipping@ietf.org; Mon, 24 Nov 2003 16:45:35 -0500
Received: from mail5.microsoft.com ([157.54.6.156]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 24 Nov 2003 13:45:02 -0800
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039);
	 Mon, 24 Nov 2003 13:45:05 -0800
Received: from 157.54.6.150 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Nov 2003 13:45:01 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 24 Nov 2003 13:44:59 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Exploders anad ad-hoc lists
Date: Mon, 24 Nov 2003 13:44:54 -0800
Message-ID: <DD07841287D0AD428833021705E0D14ED37899@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Exploders anad ad-hoc lists
Thread-Index: AcOykF3dmBGL72V7SmuIrhIkNRz13gAQBHEg
From: "Orit Levin" <oritl@microsoft.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
        "sipping" <sipping@ietf.org>
Cc: "Adam Roach" <adam@dynamicsoft.com>, <Aki.Niemi@nokia.com>,
        <Hisham.Khartabil@nokia.com>, <Markus.Isomaki@nokia.com>
X-OriginalArrivalTime: 24 Nov 2003 21:44:59.0012 (UTC) FILETIME=[35189440:01C3B2D4]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I like the direction.

Two questions:
1. How do you propose sending the deltas? (Consistently with the updated
requirements' draft.)
2. How do you propose managing the "entry_name" - especially on a B2BUA
that perform the "explosion" and needs to automatically break up the
received list into different lists and pack them again?

My thinking was to use an XML schema such as in my updated
draft-levin-simple-adhoc-list-01.txt that should appear in the IETF
directory soon:

   <xs:schema targetNamespace=3D"urn:ietf:params:xml:ns:adrl"
              elementFormDefault=3D"qualified"
              xmlns=3D"urn:ietf:params:xml:ns:adrl"
              xmlns:xs=3D"http://www.w3.org/2001/XMLSchema">

     <xs:element name=3D"adhoclist">
       <xs:complexType>

         <xs:sequence>
           <xs:element name=3D"delete" type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:element name=3D"create" type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:element name=3D"add"    type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:any     minOccurs=3D"0" maxOccurs=3D"unbounded" />
         </xs:sequence>

         <xs:attribute name=3D"uri" type=3D"xs:anyURI" use=3D"required" =
/>
         <xs:attribute name=3D"name" type=3D"xs:string" use=3D"required" =
/>
         <xs:anyAttribute />
       </xs:complexType>
     </xs:element>

       <xs:complexType name=3D"roster">
         <xs:sequence>
           <xs:element ref=3D"resource" minOccurs=3D"0"
maxOccurs=3D"unbounded" />
         </xs:sequence>
         <xs:anyAttribute />
       </xs:complexType>

     <xs:element name=3D"resource">
         <xs:attribute name=3D"uri" type=3D"xs:anyURI" use=3D"required" =
/>
         <xs:attribute name=3D"name" type=3D"xs:string" use=3D"optional" =
/>
         <xs:anyAttribute />
     </xs:element>

   </xs:schema>

Orit.

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Monday, November 24, 2003 5:39 AM
To: sipping
Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
Markus.Isomaki@nokia.com
Subject: [Sipping] Exploders anad ad-hoc lists

Folks,

we have just submitted three drafts about exploders and ad-hoc lists.

We have added more requirements to the following draft. The new=20
requirements were mainly discussed in the SIMPLE mailing list.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
loders-01.txt

The following draft describes how to carry lists of URIs in SIP=20
requests. It is not a finished draft. It is intended to trigger=20
discussions on this topic to see whether this is a step the right
direction.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri
-list-00.txt

The following draft defines a new method called EXPLODE. EXPLODE does=20
the same as REFER. That is, it tells a UA to send a request somewhere.=20
The differences are that EXPLODE accepts more than one destination=20
(REFER carries a single Refer-To header field) and that EXPLODE does not

establish implicit subscriptions of any type. This draft is also=20
intended to trigger discussions within the WG.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
lode-method-00.txt

Let's try to keep discussions about this topic in the SIPPING mailing=20
list. I will forward this mail to the SIMPLE mailing list to let them
know.

Comments are welcome,

Gonzalo



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 18:47:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11544
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 18:47:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOQQ6-0003p1-JL
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 18:47:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAONl6dG014687
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 18:47:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOQQ6-0003oo-Fe
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 18:47:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11534
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 18:46:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOQQ3-0000rZ-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 18:47:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOQQ2-0000rW-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 18:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOQQ2-0003nh-0q; Mon, 24 Nov 2003 18:47:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOQPu-0003nS-Po
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 18:46:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11531
	for <sipping@ietf.org>; Mon, 24 Nov 2003 18:46:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOQPr-0000rT-00
	for sipping@ietf.org; Mon, 24 Nov 2003 18:46:51 -0500
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOQPr-0000pV-00
	for sipping@ietf.org; Mon, 24 Nov 2003 18:46:51 -0500
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 24 Nov 2003 15:46:30 -0800
Received: from 157.54.8.155 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Nov 2003 15:46:20 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 24 Nov 2003 15:46:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Exploders anad ad-hoc lists
Date: Mon, 24 Nov 2003 15:46:21 -0800
Message-ID: <DD07841287D0AD428833021705E0D14ED37A59@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Exploders anad ad-hoc lists
Thread-Index: AcOykF3dmBGL72V7SmuIrhIkNRz13gAQBHEgAAUIvAA=
From: "Orit Levin" <oritl@microsoft.com>
To: "Orit Levin" <oritl@microsoft.com>,
        "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
        "sipping" <sipping@ietf.org>
Cc: "Adam Roach" <adam@dynamicsoft.com>, <Aki.Niemi@nokia.com>,
        <Hisham.Khartabil@nokia.com>, <Markus.Isomaki@nokia.com>
X-OriginalArrivalTime: 24 Nov 2003 23:46:20.0943 (UTC) FILETIME=[297711F0:01C3B2E5]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I am removing my second question.
(I re-read the xcap-list-usage-01 and found out that the "name" is the
only required attribute - i.e. the only key which could be the URI
itself.)

Thanks,
Orit.

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Orit Levin
Sent: Monday, November 24, 2003 1:45 PM
To: Gonzalo Camarillo; sipping
Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
Markus.Isomaki@nokia.com
Subject: RE: [Sipping] Exploders anad ad-hoc lists

I like the direction.

Two questions:
1. How do you propose sending the deltas? (Consistently with the updated
requirements' draft.)
2. How do you propose managing the "entry_name" - especially on a B2BUA
that perform the "explosion" and needs to automatically break up the
received list into different lists and pack them again?

My thinking was to use an XML schema such as in my updated
draft-levin-simple-adhoc-list-01.txt that should appear in the IETF
directory soon:

   <xs:schema targetNamespace=3D"urn:ietf:params:xml:ns:adrl"
              elementFormDefault=3D"qualified"
              xmlns=3D"urn:ietf:params:xml:ns:adrl"
              xmlns:xs=3D"http://www.w3.org/2001/XMLSchema">

     <xs:element name=3D"adhoclist">
       <xs:complexType>

         <xs:sequence>
           <xs:element name=3D"delete" type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:element name=3D"create" type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:element name=3D"add"    type=3D"roster" minOccurs=3D"0"
maxOccurs=3D"1"/>
           <xs:any     minOccurs=3D"0" maxOccurs=3D"unbounded" />
         </xs:sequence>

         <xs:attribute name=3D"uri" type=3D"xs:anyURI" use=3D"required" =
/>
         <xs:attribute name=3D"name" type=3D"xs:string" use=3D"required" =
/>
         <xs:anyAttribute />
       </xs:complexType>
     </xs:element>

       <xs:complexType name=3D"roster">
         <xs:sequence>
           <xs:element ref=3D"resource" minOccurs=3D"0"
maxOccurs=3D"unbounded" />
         </xs:sequence>
         <xs:anyAttribute />
       </xs:complexType>

     <xs:element name=3D"resource">
         <xs:attribute name=3D"uri" type=3D"xs:anyURI" use=3D"required" =
/>
         <xs:attribute name=3D"name" type=3D"xs:string" use=3D"optional" =
/>
         <xs:anyAttribute />
     </xs:element>

   </xs:schema>

Orit.

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Monday, November 24, 2003 5:39 AM
To: sipping
Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
Markus.Isomaki@nokia.com
Subject: [Sipping] Exploders anad ad-hoc lists

Folks,

we have just submitted three drafts about exploders and ad-hoc lists.

We have added more requirements to the following draft. The new=20
requirements were mainly discussed in the SIMPLE mailing list.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
loders-01.txt

The following draft describes how to carry lists of URIs in SIP=20
requests. It is not a finished draft. It is intended to trigger=20
discussions on this topic to see whether this is a step the right
direction.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri
-list-00.txt

The following draft defines a new method called EXPLODE. EXPLODE does=20
the same as REFER. That is, it tells a UA to send a request somewhere.=20
The differences are that EXPLODE accepts more than one destination=20
(REFER carries a single Refer-To header field) and that EXPLODE does not

establish implicit subscriptions of any type. This draft is also=20
intended to trigger discussions within the WG.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
lode-method-00.txt

Let's try to keep discussions about this topic in the SIPPING mailing=20
list. I will forward this mail to the SIMPLE mailing list to let them
know.

Comments are welcome,

Gonzalo



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Mon Nov 24 21:07:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16496
	for <sipping-archive@odin.ietf.org>; Mon, 24 Nov 2003 21:07:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOSbf-0002f4-AR
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 21:07:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAP27BIg010222
	for sipping-archive@odin.ietf.org; Mon, 24 Nov 2003 21:07:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOSbe-0002ef-P1
	for sipping-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 21:07:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16492
	for <sipping-web-archive@ietf.org>; Mon, 24 Nov 2003 21:06:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOSbc-00038O-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 21:07:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOSbb-00038L-00
	for sipping-web-archive@ietf.org; Mon, 24 Nov 2003 21:07:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOSbW-0002bK-Hg; Mon, 24 Nov 2003 21:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOSbV-0002av-0T
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 21:07:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16487
	for <sipping@ietf.org>; Mon, 24 Nov 2003 21:06:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOSbS-00037x-00
	for sipping@ietf.org; Mon, 24 Nov 2003 21:06:58 -0500
Received: from [202.96.122.72] (helo=mail1.eastcom.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AOSbR-00037Y-00
	for sipping@ietf.org; Mon, 24 Nov 2003 21:06:58 -0500
Received: from zfzhao ([10.8.18.89]) by mail1.eastcom.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 25 Nov 2003 10:06:15 +0800
Message-ID: <00de01c3b2f8$2cac9fd0$5912080a@rd.eastcom>
From: "jeff zhao" <zhaozf@eastcom.com>
To: <sipping@ietf.org>
Date: Tue, 25 Nov 2003 10:02:26 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 25 Nov 2003 02:06:15.0895 (UTC) FILETIME=[B53F1670:01C3B2F8]
Content-Transfer-Encoding: base64
Subject: [Sipping] whiteboard and application sharing with SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

RGVhciBhbGw6DQoNCiAgICAgICBUaGVyZSBpcyBULjEyMCBzZXJpZXMgcmVjb21tZW5kYXRpb25z
IGZvciB3aGl0ZWJvYXJkKFQuMTI2KSwgZmlsZSBzaGFyaW5nKFQuMTI3KSAgYW5kIGFwcGxpY2F0
aW9uIHNoYXJpbmcoVC4xMjgpIHVuZGVyIEguMzIzIHZpZGVvIGNvbmZlcmVuY2Ugc3lzdGVtLg0K
SWYgd2UgdXNlIFNJUCB0byBidWlsZCBhIHZpZGVvIGNvbmZlcmVuY2Ugc3lzdGVtLCBob3cgY2Fu
IHdlIGltcGxlbWVudCB0aGUgd2hpdGVib2FyZCwgZmlsZSBzaGFyaW5nIGFuZCBhcHBsaWNhaXRv
biBzaGFyaW5nIGZ1bmN0aW9ucz8NCklzIHRoZXJlIGFueSBzdGFuZGFyZHMgYW5kIGRyYWZ0cz8g
Q2FuIFQuMTIwIHNlcmllcyByZWNvbW1lbmRhdGlvbnMgd29yayB3aXRoIFNJUD8NCg0KICAgICAg
V291bGQgeW91IHBsZWFzZSBnaXZlIG1lIGFueSBpbmZvcm1hdGlvbiBhcyB5b3Uga25vdz8NCg0K
VGhha3MgYSBsb3QuDQoNCkJlc3QgUmVnYXJkcw0KDQpKZWZm



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 09:36:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19130
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 09:36:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeIe-0004PY-F9
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 09:36:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPEaKkZ016950
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 09:36:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeIe-0004PJ-BK
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 09:36:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19101
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 09:36:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeIc-0005vX-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 09:36:18 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeIc-0005vU-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 09:36:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeIM-0004HL-Nv; Tue, 25 Nov 2003 09:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeHr-0004Fq-Js
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 09:35:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19025
	for <sipping@ietf.org>; Tue, 25 Nov 2003 09:35:17 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeHp-0005uB-00
	for sipping@ietf.org; Tue, 25 Nov 2003 09:35:29 -0500
Received: from imo-r02.mx.aol.com ([152.163.225.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeHo-0005t7-00
	for sipping@ietf.org; Tue, 25 Nov 2003 09:35:28 -0500
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v36_r1.1.) id e.145.1d42d6b5 (4468);
	Tue, 25 Nov 2003 09:34:48 -0500 (EST)
Message-ID: <145.1d42d6b5.2cf4c287@aol.com>
Date: Tue, 25 Nov 2003 09:34:47 EST
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
To: Brian.Rosen@marconi.com
CC: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_145.1d42d6b5.2cf4c287_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


--part1_145.1d42d6b5.2cf4c287_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 11/24/2003 11:47:54 AM Eastern Standard Time, 
Brian.Rosen@marconi.com writes:


> Rumors are always fascinating to watch form and spread.
> 
> Contrary to what you may have heard, no one has proposed modifying
> a tel uri to carry a dial string, nor to permit pause/wait in a tel uri.
> 


Sorry if I misunderstood the points being made by some. I'm certainly 
relieved that there is no proposal to add pauses and waits to the tel:uri. The 
discussion in IPTEL was about the user=phone parameter in the tel:uri (or so I 
thought) and there were several comments about the need to include pauses and waits.

If the discussion of user=phone and dialstring was not about modifying the 
tel:uri to carry a dial string, why was it reported that the tel:uri draft has 
been held up pending this discussion?

So where and why were the pauses and waits being proposed?

Mike Pierce


--part1_145.1d42d6b5.2cf4c287_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2>In a message dated 11/24/=
2003 11:47:54 AM Eastern Standard Time, Brian.Rosen@marconi.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Rumors are always fascinati=
ng to watch form and spread.
<BR>
<BR>Contrary to what you may have heard, no one has proposed modifying
<BR>a tel uri to carry a dial string, nor to permit pause/wait in a tel uri.
<BR></FONT><FONT  COLOR=3D"#000000" SIZE=3D3 FAMILY=3D"SANSSERIF" FACE=3D"Ar=
ial" LANG=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Ar=
ial" LANG=3D"0">
<BR>
<BR>Sorry if I misunderstood the points being made by some. I'm certainly re=
lieved that there is no proposal to add pauses and waits to the tel:uri. The=
 discussion in IPTEL was about the user=3Dphone parameter in the tel:uri (or=
 so I thought) and there were several comments about the need to include pau=
ses and waits.
<BR>
<BR>If the discussion of user=3Dphone and dialstring was not about modifying=
 the tel:uri to carry a dial string, why was it reported that the tel:uri dr=
aft has been held up pending this discussion?
<BR>
<BR>So where and why were the pauses and waits being proposed?
<BR>
<BR>Mike Pierce
<BR></FONT></HTML>

--part1_145.1d42d6b5.2cf4c287_boundary--

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 09:50:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19530
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 09:50:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeW0-0005Kr-02
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 09:50:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPEo7gP020503
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 09:50:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeVz-0005Kc-S4
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 09:50:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19512
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 09:49:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeVx-000669-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 09:50:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeVx-000665-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 09:50:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeVv-0005Jj-7p; Tue, 25 Nov 2003 09:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOeV2-0005Ih-Fz
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 09:49:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19500
	for <sipping@ietf.org>; Tue, 25 Nov 2003 09:48:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeV0-00065R-00
	for sipping@ietf.org; Tue, 25 Nov 2003 09:49:06 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOeUz-00065G-00
	for sipping@ietf.org; Tue, 25 Nov 2003 09:49:05 -0500
Received: from zcard307.ca.nortel.com (zcard307.ca.nortel.com [47.129.242.67])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hAPEmTD05947;
	Tue, 25 Nov 2003 09:48:29 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLYHVFNY; Tue, 25 Nov 2003 09:48:30 -0500
Received: from nortelnetworks.com (acart1e1.ca.nortel.com [47.129.129.110]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLPWM6N3; Tue, 25 Nov 2003 09:48:29 -0500
Message-ID: <3FC36BBA.9020406@nortelnetworks.com>
Date: Tue, 25 Nov 2003 09:48:26 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mpierce1@aol.com
CC: Brian.Rosen@marconi.com, sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <145.1d42d6b5.2cf4c287@aol.com>
In-Reply-To: <145.1d42d6b5.2cf4c287@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I sent in the IPTEL minutes to the chairs yesterday.  What they record 
is that Brian has volunteered to write a draft documenting a new 
user=dialstring parameter.  People have accepted the need for such a 
parameter, but are not convinced on the pauses and waits.  Brian is 
presumably working to obtain such conviction so he can add the feature 
to his draft.

Mpierce1@aol.com wrote:

> In a message dated 11/24/2003 11:47:54 AM Eastern Standard Time, 
> Brian.Rosen@marconi.com writes:
> 
> 
>> Rumors are always fascinating to watch form and spread.
>>
>> Contrary to what you may have heard, no one has proposed modifying
>> a tel uri to carry a dial string, nor to permit pause/wait in a tel uri.
> 
> 
> 
> 
> Sorry if I misunderstood the points being made by some. I'm certainly 
> relieved that there is no proposal to add pauses and waits to the 
> tel:uri. The discussion in IPTEL was about the user=phone parameter in 
> the tel:uri (or so I thought) and there were several comments about the 
> need to include pauses and waits.
> 
> If the discussion of user=phone and dialstring was not about modifying 
> the tel:uri to carry a dial string, why was it reported that the tel:uri 
> draft has been held up pending this discussion?
> 
> So where and why were the pauses and waits being proposed?
> 
> Mike Pierce


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 10:17:40 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22045
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 10:17:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOewO-0007dx-6i
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 10:17:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPFHOlQ029375
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 10:17:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOewN-0007di-F2
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 10:17:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21979
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 10:17:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOewK-0006ag-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 10:17:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOewJ-0006aF-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 10:17:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOew1-0007WJ-UB; Tue, 25 Nov 2003 10:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOevR-0007Tx-82
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 10:16:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21846
	for <sipping@ietf.org>; Tue, 25 Nov 2003 10:16:10 -0500 (EST)
From: Markus.Isomaki@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOevO-0006XK-00
	for sipping@ietf.org; Tue, 25 Nov 2003 10:16:23 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOevM-0006XD-00
	for sipping@ietf.org; Tue, 25 Nov 2003 10:16:21 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hAPFGI627404
	for <sipping@ietf.org>; Tue, 25 Nov 2003 17:16:19 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66204cf5d1ac158f24115@esvir04nok.ntc.nokia.com>;
 Tue, 25 Nov 2003 17:16:18 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 25 Nov 2003 17:16:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Exploders anad ad-hoc lists
Date: Tue, 25 Nov 2003 17:16:18 +0200
Message-ID: <E392EEA75EC5F54AB75229B693B1B6A707E7A26F@esebe018.ntc.nokia.com>
Thread-Topic: [Sipping] Exploders anad ad-hoc lists
Thread-Index: AcOykF3dmBGL72V7SmuIrhIkNRz13gAQBHEgAAUIvAAAIHWsAA==
To: <oritl@microsoft.com>, <Gonzalo.Camarillo@ericsson.com>,
        <sipping@ietf.org>
Cc: <adam@dynamicsoft.com>, <aki.niemi@nokia.com>,
        <hisham.khartabil@nokia.com>
X-OriginalArrivalTime: 25 Nov 2003 15:16:18.0672 (UTC) FILETIME=[1380D700:01C3B367]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I also like the approach for carrying lists proposed in =
http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-expl=
oders-01.txt

For me the best part is how this aligns with XCAP list usage, since I =
believe that we should be able to do the exactly same things using both =
ad hoc and pre-provisioned lists.=20

Markus=20


> -----Original Message-----
> From: ext Orit Levin [mailto:oritl@microsoft.com]
> Sent: 25 November, 2003 01:46
> To: Orit Levin; Gonzalo Camarillo; sipping
> Cc: Adam Roach; Niemi Aki (NMP/Helsinki); Khartabil Hisham
> (NMP-MSW/Helsinki); Isomaki Markus (NRC/Helsinki)
> Subject: RE: [Sipping] Exploders anad ad-hoc lists
>=20
>=20
> I am removing my second question.
> (I re-read the xcap-list-usage-01 and found out that the "name" is the
> only required attribute - i.e. the only key which could be the URI
> itself.)
>=20
> Thanks,
> Orit.
>=20
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
> Of Orit Levin
> Sent: Monday, November 24, 2003 1:45 PM
> To: Gonzalo Camarillo; sipping
> Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
> Markus.Isomaki@nokia.com
> Subject: RE: [Sipping] Exploders anad ad-hoc lists
>=20
> I like the direction.
>=20
> Two questions:
> 1. How do you propose sending the deltas? (Consistently with=20
> the updated
> requirements' draft.)
> 2. How do you propose managing the "entry_name" - especially=20
> on a B2BUA
> that perform the "explosion" and needs to automatically break up the
> received list into different lists and pack them again?
>=20
> My thinking was to use an XML schema such as in my updated
> draft-levin-simple-adhoc-list-01.txt that should appear in the IETF
> directory soon:
>=20
>    <xs:schema targetNamespace=3D"urn:ietf:params:xml:ns:adrl"
>               elementFormDefault=3D"qualified"
>               xmlns=3D"urn:ietf:params:xml:ns:adrl"
>               xmlns:xs=3D"http://www.w3.org/2001/XMLSchema">
>=20
>      <xs:element name=3D"adhoclist">
>        <xs:complexType>
>=20
>          <xs:sequence>
>            <xs:element name=3D"delete" type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:element name=3D"create" type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:element name=3D"add"    type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:any     minOccurs=3D"0" maxOccurs=3D"unbounded" />
>          </xs:sequence>
>=20
>          <xs:attribute name=3D"uri" type=3D"xs:anyURI" =
use=3D"required" />
>          <xs:attribute name=3D"name" type=3D"xs:string" =
use=3D"required" />
>          <xs:anyAttribute />
>        </xs:complexType>
>      </xs:element>
>=20
>        <xs:complexType name=3D"roster">
>          <xs:sequence>
>            <xs:element ref=3D"resource" minOccurs=3D"0"
> maxOccurs=3D"unbounded" />
>          </xs:sequence>
>          <xs:anyAttribute />
>        </xs:complexType>
>=20
>      <xs:element name=3D"resource">
>          <xs:attribute name=3D"uri" type=3D"xs:anyURI" =
use=3D"required" />
>          <xs:attribute name=3D"name" type=3D"xs:string" =
use=3D"optional" />
>          <xs:anyAttribute />
>      </xs:element>
>=20
>    </xs:schema>
>=20
> Orit.
>=20
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
> Of Gonzalo Camarillo
> Sent: Monday, November 24, 2003 5:39 AM
> To: sipping
> Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
> Markus.Isomaki@nokia.com
> Subject: [Sipping] Exploders anad ad-hoc lists
>=20
> Folks,
>=20
> we have just submitted three drafts about exploders and ad-hoc lists.
>=20
> We have added more requirements to the following draft. The new=20
> requirements were mainly discussed in the SIMPLE mailing list.
>=20
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> ipping-exp
> loders-01.txt
>=20
> The following draft describes how to carry lists of URIs in SIP=20
> requests. It is not a finished draft. It is intended to trigger=20
> discussions on this topic to see whether this is a step the right
> direction.
>=20
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
ipping-uri
-list-00.txt

The following draft defines a new method called EXPLODE. EXPLODE does=20
the same as REFER. That is, it tells a UA to send a request somewhere.=20
The differences are that EXPLODE accepts more than one destination=20
(REFER carries a single Refer-To header field) and that EXPLODE does not

establish implicit subscriptions of any type. This draft is also=20
intended to trigger discussions within the WG.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
lode-method-00.txt

Let's try to keep discussions about this topic in the SIPPING mailing=20
list. I will forward this mail to the SIMPLE mailing list to let them
know.

Comments are welcome,

Gonzalo



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 10:22:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22275
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 10:22:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOf0w-00083X-5f
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 10:22:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPFM6GH030961
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 10:22:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOf0v-00081p-JG
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 10:22:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22221
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 10:21:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOf0t-0006i7-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 10:22:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOf0s-0006i3-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 10:22:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOf0r-0007zP-Lm; Tue, 25 Nov 2003 10:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOf0K-0007yS-Bz
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 10:21:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22197
	for <sipping@ietf.org>; Tue, 25 Nov 2003 10:21:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOf0H-0006gn-00
	for sipping@ietf.org; Tue, 25 Nov 2003 10:21:26 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOf0H-0006gL-00
	for sipping@ietf.org; Tue, 25 Nov 2003 10:21:25 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA23453;
	Tue, 25 Nov 2003 10:20:53 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA28679;
	Tue, 25 Nov 2003 10:20:53 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7XGCH>; Tue, 25 Nov 2003 10:20:53 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6118@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Tue, 25 Nov 2003 10:20:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I am proposing that they be allowed in a SIP URI that includes
a user=dialstring parameter.

To be clear, we agreed in Minneapolis that Rohan's proposal that
user=phone designates a phone number exactly as a tel uri does; 
that is, a sip uri with user=phone is convertible to a tel uri
without change in meaning and vice versa.  I almost typed "without 
a change in destination or routing", but that may not be true, 
because a given proxy could decide to route them differently.  
Don't know why it would, but it could.

Brian

-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Tuesday, November 25, 2003 9:35 AM
To: Brian.Rosen@marconi.com
Cc: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait


In a message dated 11/24/2003 11:47:54 AM Eastern Standard Time,
Brian.Rosen@marconi.com writes: 



Rumors are always fascinating to watch form and spread. 

Contrary to what you may have heard, no one has proposed modifying 
a tel uri to carry a dial string, nor to permit pause/wait in a tel uri. 




Sorry if I misunderstood the points being made by some. I'm certainly
relieved that there is no proposal to add pauses and waits to the tel:uri.
The discussion in IPTEL was about the user=phone parameter in the tel:uri
(or so I thought) and there were several comments about the need to include
pauses and waits. 

If the discussion of user=phone and dialstring was not about modifying the
tel:uri to carry a dial string, why was it reported that the tel:uri draft
has been held up pending this discussion? 

So where and why were the pauses and waits being proposed? 

Mike Pierce 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 15:17:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07216
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 15:17:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOjcR-0005M1-I4
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 15:17:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPKH7lq020577
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 15:17:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOjcR-0005Lo-DR
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 15:17:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07176
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 15:16:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOjcP-0004lH-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 15:17:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOjcP-0004lC-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 15:17:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOjcL-0005Kf-0z; Tue, 25 Nov 2003 15:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOjbr-0005Jz-M0
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 15:16:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07062
	for <sipping@ietf.org>; Tue, 25 Nov 2003 15:16:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOjbe-0004iB-00
	for sipping@ietf.org; Tue, 25 Nov 2003 15:16:18 -0500
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOjbd-0004gq-00
	for sipping@ietf.org; Tue, 25 Nov 2003 15:16:17 -0500
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 25 Nov 2003 12:15:31 -0800
Received: from 157.54.5.25 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 25 Nov 2003 12:15:28 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 25 Nov 2003 12:15:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Exploders anad ad-hoc lists
Date: Tue, 25 Nov 2003 12:15:25 -0800
Message-ID: <DD07841287D0AD428833021705E0D14ED6AE50@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Exploders anad ad-hoc lists
Thread-Index: AcOykF3dmBGL72V7SmuIrhIkNRz13gAQBHEgAAUIvAAAIHWsAAAKYdug
From: "Orit Levin" <oritl@microsoft.com>
To: <Markus.Isomaki@nokia.com>, <Gonzalo.Camarillo@ericsson.com>,
        <sipping@ietf.org>
Cc: <adam@dynamicsoft.com>, <aki.niemi@nokia.com>,
        <hisham.khartabil@nokia.com>
X-OriginalArrivalTime: 25 Nov 2003 20:15:21.0643 (UTC) FILETIME=[DA58EFB0:01C3B390]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Just to clarify:

This specific part (i.e. using XCAP schema alone) does not meet the
delta requirements right now. "Operations" need to be appended to
list/roster XML schema in order to do this.

Orit.

-----Original Message-----
From: Markus.Isomaki@nokia.com [mailto:Markus.Isomaki@nokia.com]=20
Sent: Tuesday, November 25, 2003 7:16 AM
To: Orit Levin; Gonzalo.Camarillo@ericsson.com; sipping@ietf.org
Cc: adam@dynamicsoft.com; aki.niemi@nokia.com;
hisham.khartabil@nokia.com
Subject: RE: [Sipping] Exploders anad ad-hoc lists

Hi,

I also like the approach for carrying lists proposed in
http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
loders-01.txt

For me the best part is how this aligns with XCAP list usage, since I
believe that we should be able to do the exactly same things using both
ad hoc and pre-provisioned lists.=20

Markus=20


> -----Original Message-----
> From: ext Orit Levin [mailto:oritl@microsoft.com]
> Sent: 25 November, 2003 01:46
> To: Orit Levin; Gonzalo Camarillo; sipping
> Cc: Adam Roach; Niemi Aki (NMP/Helsinki); Khartabil Hisham
> (NMP-MSW/Helsinki); Isomaki Markus (NRC/Helsinki)
> Subject: RE: [Sipping] Exploders anad ad-hoc lists
>=20
>=20
> I am removing my second question.
> (I re-read the xcap-list-usage-01 and found out that the "name" is the
> only required attribute - i.e. the only key which could be the URI
> itself.)
>=20
> Thanks,
> Orit.
>=20
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
> Of Orit Levin
> Sent: Monday, November 24, 2003 1:45 PM
> To: Gonzalo Camarillo; sipping
> Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
> Markus.Isomaki@nokia.com
> Subject: RE: [Sipping] Exploders anad ad-hoc lists
>=20
> I like the direction.
>=20
> Two questions:
> 1. How do you propose sending the deltas? (Consistently with=20
> the updated
> requirements' draft.)
> 2. How do you propose managing the "entry_name" - especially=20
> on a B2BUA
> that perform the "explosion" and needs to automatically break up the
> received list into different lists and pack them again?
>=20
> My thinking was to use an XML schema such as in my updated
> draft-levin-simple-adhoc-list-01.txt that should appear in the IETF
> directory soon:
>=20
>    <xs:schema targetNamespace=3D"urn:ietf:params:xml:ns:adrl"
>               elementFormDefault=3D"qualified"
>               xmlns=3D"urn:ietf:params:xml:ns:adrl"
>               xmlns:xs=3D"http://www.w3.org/2001/XMLSchema">
>=20
>      <xs:element name=3D"adhoclist">
>        <xs:complexType>
>=20
>          <xs:sequence>
>            <xs:element name=3D"delete" type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:element name=3D"create" type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:element name=3D"add"    type=3D"roster" minOccurs=3D"0"
> maxOccurs=3D"1"/>
>            <xs:any     minOccurs=3D"0" maxOccurs=3D"unbounded" />
>          </xs:sequence>
>=20
>          <xs:attribute name=3D"uri" type=3D"xs:anyURI" =
use=3D"required" />
>          <xs:attribute name=3D"name" type=3D"xs:string" =
use=3D"required" />
>          <xs:anyAttribute />
>        </xs:complexType>
>      </xs:element>
>=20
>        <xs:complexType name=3D"roster">
>          <xs:sequence>
>            <xs:element ref=3D"resource" minOccurs=3D"0"
> maxOccurs=3D"unbounded" />
>          </xs:sequence>
>          <xs:anyAttribute />
>        </xs:complexType>
>=20
>      <xs:element name=3D"resource">
>          <xs:attribute name=3D"uri" type=3D"xs:anyURI" =
use=3D"required" />
>          <xs:attribute name=3D"name" type=3D"xs:string" =
use=3D"optional" />
>          <xs:anyAttribute />
>      </xs:element>
>=20
>    </xs:schema>
>=20
> Orit.
>=20
> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
> Of Gonzalo Camarillo
> Sent: Monday, November 24, 2003 5:39 AM
> To: sipping
> Cc: Adam Roach; Aki.Niemi@nokia.com; Hisham.Khartabil@nokia.com;
> Markus.Isomaki@nokia.com
> Subject: [Sipping] Exploders anad ad-hoc lists
>=20
> Folks,
>=20
> we have just submitted three drafts about exploders and ad-hoc lists.
>=20
> We have added more requirements to the following draft. The new=20
> requirements were mainly discussed in the SIMPLE mailing list.
>=20
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
> ipping-exp
> loders-01.txt
>=20
> The following draft describes how to carry lists of URIs in SIP=20
> requests. It is not a finished draft. It is intended to trigger=20
> discussions on this topic to see whether this is a step the right
> direction.
>=20
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-s
ipping-uri
-list-00.txt

The following draft defines a new method called EXPLODE. EXPLODE does=20
the same as REFER. That is, it tells a UA to send a request somewhere.=20
The differences are that EXPLODE accepts more than one destination=20
(REFER carries a single Refer-To header field) and that EXPLODE does not

establish implicit subscriptions of any type. This draft is also=20
intended to trigger discussions within the WG.

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exp
lode-method-00.txt

Let's try to keep discussions about this topic in the SIPPING mailing=20
list. I will forward this mail to the SIMPLE mailing list to let them
know.

Comments are welcome,

Gonzalo



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP





_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 16:19:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11198
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 16:19:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOkaX-0001az-47
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 16:19:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPLJDA1006127
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 16:19:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOkaW-0001ak-VA
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 16:19:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11158
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 16:18:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOkaV-0006cl-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 16:19:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOkaU-0006ci-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 16:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOkaM-0001WT-8n; Tue, 25 Nov 2003 16:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOkaD-0001Vx-Li
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 16:18:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11128;
	Tue, 25 Nov 2003 16:18:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOkZz-0006cI-00; Tue, 25 Nov 2003 16:18:39 -0500
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOkZy-0006bm-00; Tue, 25 Nov 2003 16:18:38 -0500
Received: from inet-vrs-01.redmond.corp.microsoft.com ([157.54.8.27]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 25 Nov 2003 13:17:52 -0800
Received: from 157.54.8.109 by inet-vrs-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 25 Nov 2003 13:18:06 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 25 Nov 2003 13:18:11 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Date: Tue, 25 Nov 2003 13:18:03 -0800
Message-ID: <DD07841287D0AD428833021705E0D14ED6AF4E@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: FW: I-D ACTION:draft-levin-simple-adhoc-list-01.txt 
Thread-Index: AcOzmZyvK4uvlGfIQaqcp/ZLgB3Jgw==
From: "Orit Levin" <oritl@microsoft.com>
To: <sipping@ietf.org>, <simple@ietf.org>
X-OriginalArrivalTime: 25 Nov 2003 21:18:11.0118 (UTC) FILETIME=[A1212CE0:01C3B399]
Subject: [Sipping] FW: I-D ACTION:draft-levin-simple-adhoc-list-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3B399.A0FE4560"

------_=_NextPart_001_01C3B399.A0FE4560
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

________________________________

*	To: IETF-Announce: ;=20
*	Subject: I-D ACTION:draft-levin-simple-adhoc-list-01.txt=20
*	From: Internet-Drafts@ietf.org=20
*	Date: Tue, 25 Nov 2003 15:25:13 -0500=20
*	Reply-to: Internet-Drafts@ietf.org=20
*	Sender: owner-ietf-announce@ietf.org=20

________________________________

size=3D2 width=3D"100%" align=3Dcenter>=20
A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
=20
=20
        Title           : Ad-hoc Resource Lists using SUBSCRIBE in =
SIMPLE
        Author(s)      : O. Levin
        Filename       : draft-levin-simple-adhoc-list-01.txt
        Pages          : 14
        Date           : 2003-11-25
       =20
This document presents an extension to the Session Initiation
Protocol (SIP)-Specific Event Notification mechanism for subscribing
to a homogeneous list of resources.  Instead of the subscriber
sending a SUBSCRIBE for each resource individually, the subscriber
can define an ad-hoc resource list, subscribe to it, and maintain it
=FB all within a single SUBSCRIBE dialog. Changes in the state of the
resources are reported using the same dialog in any standard SIMPLE
format for conveying notifications for lists of resources or
individual resources and agreed during the SUBSCRIBE dialog
establishment.
=20
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-levin-simple-adhoc-list-01.txt
=20
To remove yourself from the IETF Announcement list, send a message to=20
ietf-announce-request with the word unsubscribe in the body of the =
message.
=20
Internet-Drafts are also available by anonymous FTP. Login with the =
username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-levin-simple-adhoc-list-01.txt".
=20
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
=20
=20
Internet-Drafts can also be obtained by e-mail.
=20
Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-levin-simple-adhoc-list-01.txt".
       =20
NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail =
readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.
              =20
              =20
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

<ftp://ftp.ietf.org/internet-drafts/draft-levin-simple-adhoc-list-01.txt>=
 =
<ftp://ftp.ietf.org/internet-drafts/draft-levin-simple-adhoc-list-01.txt>=
 =20

=20


------_=_NextPart_001_01C3B399.A0FE4560
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-right:0in;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</span></font></div>

<font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-family:
"Times New Roman"'>

<ul type=3Ddisc>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman"><!--X-Subject-Header-End--><!--X-Head-of-Message-->To</font></i></=
em>:
     IETF-Announce: ; </li>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman">Subject</font></i></em>:
     I-D ACTION:draft-levin-simple-adhoc-list-01.txt </li>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman">From</font></i></em>: <a
     =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> =
</li>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman">Date</font></i></em>:
     Tue, 25 Nov 2003 15:25:13 -0500 </li>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman">Reply-to</font></i></em>:
     <a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> =
</li>
 <li class=3DMsoNormal><em><i><font face=3D"Times New =
Roman">Sender</font></i></em>:
     <a =
href=3D"mailto:owner-ietf-announce@ietf.org">owner-ietf-announce@ietf.org=
</a>
     </li>
</ul>

</span></font>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr<!--X-Head-of-Message-End--><!--X-Head-Body-Sep-Begin--> size=3D2 =
width=3D"100%"
align=3Dcenter>

</span></font></div>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><!--X-Head-Body-Sep-End--><!--X-Body-of-Messag=
e-->A New Internet-Draft is available from the on-line Internet-Drafts =
directories.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 Title=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0 : Ad-hoc Resource Lists using SUBSCRIBE in =
SIMPLE</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
Author(s)=A0=A0=A0=A0=A0 : O. Levin</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
Filename=A0=A0=A0=A0=A0=A0 : =
draft-levin-simple-adhoc-list-01.txt</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
Pages=A0=A0=A0=A0=A0=A0=A0=A0=A0 : 14</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
Date=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 : =
2003-11-25</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This =
document presents an extension to the Session =
Initiation</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Protocol =
(SIP)-Specific Event Notification mechanism for =
subscribing</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>to a =
homogeneous list of resources.=A0 Instead of the =
subscriber</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>sending a =
SUBSCRIBE for each resource individually, the =
subscriber</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>can =
define an ad-hoc resource list, subscribe to it, and maintain =
it</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>=FB all =
within a single SUBSCRIBE dialog. Changes in the state of =
the</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>resources =
are reported using the same dialog in any standard =
SIMPLE</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>format =
for conveying notifications for lists of resources =
or</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>individual resources and agreed during the =
SUBSCRIBE dialog</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>establishment.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>A URL for =
this Internet-Draft is:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><a
href=3D"http://www.ietf.org/internet-drafts/draft-levin-simple-adhoc-list=
-01.txt">http://www.ietf.org/internet-drafts/draft-levin-simple-adhoc-lis=
t-01.txt</a></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>To remove =
yourself from the IETF Announcement list, send a message to =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>ietf-announce-request with the word =
unsubscribe in the body of the message.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Internet-Drafts are also available by =
anonymous FTP. Login with the username</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&quot;anonymous&quot; and a password of your =
e-mail address. After logging in,</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>type =
&quot;cd internet-drafts&quot; and then</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 &quot;get =
draft-levin-simple-adhoc-list-01.txt&quot;.</span></font></pre><pre><font=

size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>A list of =
Internet-Drafts directories can be found =
in</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><a
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html<=
/a> </span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>or <a
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/iet=
f/1shadow-sites.txt</a></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Internet-Drafts can also be obtained by =
e-mail.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Send a =
message to:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
mailserv@ietf.org.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>In the =
body type:</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 &quot;FILE =
/internet-drafts/draft-levin-simple-adhoc-list-01.txt&quot;.</span></font=
></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>NOTE:=A0=A0 The mail server at ietf.org can =
return the document in</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 MIME-encoded form by =
using the &quot;mpack&quot; utility.=A0 To use =
this</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 feature, insert the =
command &quot;ENCODING mime&quot; before the =
&quot;FILE&quot;</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 command.=A0 To decode =
the response(s), you will need &quot;munpack&quot; =
or</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 a MIME-compliant mail =
reader.=A0 Different MIME-compliant mail =
readers</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 exhibit different =
behavior, especially when dealing with</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 &quot;multipart&quot; =
MIME messages (i.e. documents which have been =
split</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 up into multiple =
messages), so check your local documentation =
on</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0 how to manipulate these =
messages.</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Below is =
the data which will enable a MIME compliant mail =
reader</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>implementation to automatically retrieve the =
ASCII version of the</span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Internet-Draft.</span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><a
href=3D"ftp://ftp.ietf.org/internet-drafts/draft-levin-simple-adhoc-list-=
01.txt">&lt;ftp://ftp.ietf.org/internet-drafts/draft-levin-simple-adhoc-l=
ist-01.txt&gt;</a>
</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<!--X-Body-of-Message-End--><!--X-MsgBody-End--><!--X-Follow-Ups--></div>=


</body>

</html>

------_=_NextPart_001_01C3B399.A0FE4560--

--------------InterScan_NT_MIME_Boundary--


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 17:27:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14408
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 17:27:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOleK-0006Gl-3d
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 17:27:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPMRC1E024093
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 17:27:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOleJ-0006GW-Ve
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 17:27:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14382
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 17:26:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOleH-0000dA-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 17:27:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOleH-0000d7-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 17:27:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOleB-0006Cc-9M; Tue, 25 Nov 2003 17:27:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOldy-0006C5-8E
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 17:26:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14374
	for <sipping@ietf.org>; Tue, 25 Nov 2003 17:26:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOldv-0000cx-00
	for sipping@ietf.org; Tue, 25 Nov 2003 17:26:47 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOldv-0000ch-00
	for sipping@ietf.org; Tue, 25 Nov 2003 17:26:47 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAPMQEAt006108;
	Tue, 25 Nov 2003 14:26:15 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEG41662;
	Tue, 25 Nov 2003 17:26:13 -0500 (EST)
Message-ID: <3FC3D704.3090600@cisco.com>
Date: Tue, 25 Nov 2003 17:26:12 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B610E@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Brian - I need to pick some nits in what you say below.

	Paul

Rosen, Brian wrote:
> 
> We all agreed that a tel uri, which is also convertible to a sip uri
> with the user=phone convention, remained a way to express local or global
> phone numbers, and not dial strings.

I wouldn't go quite that far. While we agreed that the sip uri with 
user=dialstring may be used to represent dial strings, I don't believe 
that eliminates the option of using a tel: uri with a local number and a 
context.

Rosen, Brian wrote:
 >
 > To be clear, we agreed in Minneapolis that Rohan's proposal that
 > user=phone designates a phone number exactly as a tel uri does;
 > that is, a sip uri with user=phone is convertible to a tel uri
 > without change in meaning and vice versa.

We have to be very careful about the visa versa part. Sip uris retain 
the rule that the user part is only interpretable within domain of its 
address. So sip:+1-234-567-8901@foo.com;user=phone may be understood to 
be equivalent to tel:+1-234-567-8901 by the foo.com proxy, but not by 
the bar.com proxy.

 > I almost typed "without
 > a change in destination or routing", but that may not be true,
 > because a given proxy could decide to route them differently.
 > Don't know why it would, but it could.

There are good reasons. If the address tel:+1-234-567-8901 is presented 
to both the foo.com and bar.com proxies, they may choose to route it 
differently. Perhaps one routes to a gateway in the US, and the other to 
a gateway in China.

But when both are presented with sip:+1-234-567-8901@foo.com;user=phone,
the bar.com proxy will be compelled to route to the foo.com proxy, and 
from there it will be treated the same as one initially offered to 
foo.com. So both calls will be routed thru the same gateway.

	Paul



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Tue Nov 25 17:48:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15142
	for <sipping-archive@odin.ietf.org>; Tue, 25 Nov 2003 17:48:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOlyc-0008DF-FD
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 17:48:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPMmANN031569
	for sipping-archive@odin.ietf.org; Tue, 25 Nov 2003 17:48:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOlyc-0008D6-5e
	for sipping-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 17:48:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15129
	for <sipping-web-archive@ietf.org>; Tue, 25 Nov 2003 17:47:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOlyZ-0001AU-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 17:48:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOlyZ-0001AQ-00
	for sipping-web-archive@ietf.org; Tue, 25 Nov 2003 17:48:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOlyU-0008Bw-DO; Tue, 25 Nov 2003 17:48:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOlyI-0008A5-JK
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 17:47:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15065
	for <sipping@ietf.org>; Tue, 25 Nov 2003 17:47:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOlyD-00019e-00
	for sipping@ietf.org; Tue, 25 Nov 2003 17:47:45 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOlyD-000194-00
	for sipping@ietf.org; Tue, 25 Nov 2003 17:47:45 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA09859;
	Tue, 25 Nov 2003 17:47:13 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA07473;
	Tue, 25 Nov 2003 17:47:15 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7X4Z4>; Tue, 25 Nov 2003 17:47:14 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B612A@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Tue, 25 Nov 2003 17:47:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Okay, let's pick some nits.

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Tuesday, November 25, 2003 5:26 PM
> To: Rosen, Brian
> Cc: 'Mpierce1@aol.com'; sipping@ietf.org
> Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
> 
> 
> Brian - I need to pick some nits in what you say below.
> 
> 	Paul
> 
> Rosen, Brian wrote:
> > 
> > We all agreed that a tel uri, which is also convertible to a sip uri
> > with the user=phone convention, remained a way to express 
> local or global
> > phone numbers, and not dial strings.
> 
> I wouldn't go quite that far. While we agreed that the sip uri with 
> user=dialstring may be used to represent dial strings, I 
> don't believe 
> that eliminates the option of using a tel: uri with a local 
> number and a 
> context.
I don't understand your concern.
What we agreed was that a local or a global number was expressable
as either a tel uri, or a sip uri with user=phone interchangeably.
So a tel uri can be used for a local number, and a sip uri with
user=phone can be used for a local number.

We confirmed that a tel uri cannot be used with a dial string, and we
decided that a sip uri with user=phone cannot be used with a dial string.

So, 
> 
> Rosen, Brian wrote:
>  >
>  > To be clear, we agreed in Minneapolis that Rohan's proposal that
>  > user=phone designates a phone number exactly as a tel uri does;
>  > that is, a sip uri with user=phone is convertible to a tel uri
>  > without change in meaning and vice versa.
> 
> We have to be very careful about the visa versa part. Sip uris retain 
> the rule that the user part is only interpretable within 
> domain of its 
> address. So sip:+1-234-567-8901@foo.com;user=phone may be 
> understood to 
> be equivalent to tel:+1-234-567-8901 by the foo.com proxy, but not by 
> the bar.com proxy.
Well, I agree with your concern, but not with your example.
Unfortunately, you chose a global number for your example.  They would
refer to the same end terminal in either domain.  What is true
is that the route to that terminal may be different in the foo domain
than the bar domain.

I certainly agree that sip:1234@foo.com;user=phone would probably
be different from sip:1234@bar.com;user=phone

An interesting excercise for the reader would be to decide
whether:
	sip:1234@foo.com;user=phone;phone-context=example.com
is the same destination as
	sip:1234@bar.com;user=phone;phone-contex=example.com
AND THE ANSWER IS
	No, they could be different.  Don't read too much into
	the phone context value.  It's a string.  If foo.com understands
	a context named example.com, great, but nothing guarantees that
	bar.com's view of a context named example.com is the same

Hopefully, you wouldn't ever see something like that, hopefully you
would see:
	sip:1234@example.com;user=phone;phone-context=chicago.example.com

> 
>  > I almost typed "without
>  > a change in destination or routing", but that may not be true,
>  > because a given proxy could decide to route them differently.
>  > Don't know why it would, but it could.
> 
> There are good reasons. If the address tel:+1-234-567-8901 is 
> presented 
> to both the foo.com and bar.com proxies, they may choose to route it 
> differently. Perhaps one routes to a gateway in the US, and 
> the other to 
> a gateway in China.
Note the phrase "a given proxy could decide to route them differently"
I agree that two different proxies could choose to route differently.

> 
> But when both are presented with 
> sip:+1-234-567-8901@foo.com;user=phone,
> the bar.com proxy will be compelled to route to the foo.com 
> proxy, and 
> from there it will be treated the same as one initially offered to 
> foo.com. So both calls will be routed thru the same gateway.
Agree

I was observing that tel:+12345678901 when presented to bar.com would 
probably be routed the same as 
sip:+12345678901@bar.com;user=phone would, but that isn't guaranteed.

Brian

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 04:46:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29821
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 04:46:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOwFb-0007NF-CB
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 04:46:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQ9kNZn028339
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 04:46:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOwFZ-0007Mo-1g
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 04:46:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29672
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 04:46:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOwFV-0002U3-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 04:46:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOwFV-0002U0-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 04:46:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOwFI-0007Kf-2g; Wed, 26 Nov 2003 04:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOwEI-0007JQ-Ib
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 04:45:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29636;
	Wed, 26 Nov 2003 04:44:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOwEF-0002Sv-00; Wed, 26 Nov 2003 04:44:59 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOwEE-0002Ss-00; Wed, 26 Nov 2003 04:44:58 -0500
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hAQ9ipUC006787;
	Wed, 26 Nov 2003 18:44:51 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hAQ9iopo005550;
	Wed, 26 Nov 2003 18:44:51 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hAQ9io8H018032;
	Wed, 26 Nov 2003 18:44:50 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id SAA27756;
	Wed, 26 Nov 2003 18:44:49 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id SAA15517;
	Wed, 26 Nov 2003 18:44:49 +0900 (JST)
Date: Wed, 26 Nov 2003 18:44:40 +0900
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
To: Mark Baugher <mbaugher@cisco.com>, mary.barnes@nortelnetworks.com,
        tachimoto.shinya@lab.ntt.co.jp
Cc: sipping@ietf.org, mmusic@ietf.org, cyrus@ntt-at.com, fandreas@cisco.com,
        dwing@cisco.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.07beta6 (WinNT,501)
In-Reply-To: <6.0.0.22.2.20031125160613.03fd89d8@mira-sjc5-6.cisco.com>
References: <6.0.0.22.2.20031125160613.03fd89d8@mira-sjc5-6.cisco.com>
Message-Id: <2EC3B401E99BAEono.kumiko@lab.ntt.co.jp>
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: e2m, m2m security drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Mark,

Thanks for your comments. Inline-

<mbaugher@cisco.com> wrote:
>1. Section 5.1 of 
>http://www.ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-
>00.txt 
>shows an example of an encrypted SDP in an INVITE but the key to this 
>encrypted SDP is selectively shared with some proxies so they can view the 
>encrypted data.  There is undoubtedly some information in the SDP that a 
>proxy needs to view and some that it does not need to view, such as the 
>end-to-end keying material.  Can we accommodate this requirement in the 
>current proposals?  That is, could we keep the keying material encrypted 
>end-to-end while allowing a proxy to view other parts of the SDP message?

Yes, definitely. 
Section 3.1 of the requirement draft says that 
"The solution MUST work even with  SIP end-to-end encryption for 
confidentiality service enabled".

To clarify this requirement, I would say:
- It MUST work even with end-to-end encryption of some data.
  That is, encrypted data can be shared with the end user and selected 
proxies.
- It MUST NOT violate end-to-end encryption when the encrypted data does 
not need to be shared with any proxies.
  
>2. Have you considered writing a core specification like RFC 1847 and allow 
>for one or more profiles such as S/MIME (today) and PGP MIME (in the 
>future)?  I understand that S/MIME is the designated SIP solution, but it 
>might be wise to allow for future extensions.

Hmm... in the future, such extensions might be needed.
However, I have not considered that yet.
I think there are still more work to use S/MIME practically in SIP.

Thanks a lot,

Kumiko

--
Kumiko Ono
NTT Network Service Systems Labs.
Tel +81 422 59 4508/Fax +81 422 60 4012

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 10:32:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12329
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 10:32:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP1eE-0002e9-T7
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 10:32:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQFWAU1010169
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 10:32:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP1eE-0002dw-Ol
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 10:32:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12265
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 10:31:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP1eC-0007Jl-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 10:32:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP1eC-0007Ji-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 10:32:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP1e6-0002Xj-1i; Wed, 26 Nov 2003 10:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP1dd-0002VN-7A
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 10:31:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12092
	for <sipping@ietf.org>; Wed, 26 Nov 2003 10:31:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP1da-0007F6-00
	for sipping@ietf.org; Wed, 26 Nov 2003 10:31:30 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP1dN-0007Cv-00
	for sipping@ietf.org; Wed, 26 Nov 2003 10:31:17 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 26 Nov 2003 07:32:30 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAQFUhAt006908;
	Wed, 26 Nov 2003 07:30:44 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEG79650;
	Wed, 26 Nov 2003 10:30:42 -0500 (EST)
Message-ID: <3FC4C721.6030206@cisco.com>
Date: Wed, 26 Nov 2003 10:30:41 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B612A@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Rosen, Brian wrote:
> 
>>>We all agreed that a tel uri, which is also convertible to a sip uri
>>>with the user=phone convention, remained a way to express 
>>>local or global phone numbers, and not dial strings.
>>
>>I wouldn't go quite that far. While we agreed that the sip uri with 
>>user=dialstring may be used to represent dial strings, I 
>>>don't believe that eliminates the option of using a tel: uri with a local 
>>>number and a context.
> 
> I don't understand your concern.
> What we agreed was that a local or a global number was expressable
> as either a tel uri, or a sip uri with user=phone interchangeably.
> So a tel uri can be used for a local number, and a sip uri with
> user=phone can be used for a local number.

agreed.

> We confirmed that a tel uri cannot be used with a dial string, and we
> decided that a sip uri with user=phone cannot be used with a dial string.

I think you overstate the case. I think we agreed to define a new value 
"dialstring" that MAY be used with the user= parameter of a sip uri. And 
it MAY be used to represent a dialstring.

It remains demonstrably the case that a dialstring *can* also be 
represented as a tel uri with a local number and context, as has been 
discussed ad nauseum on this list. Of course "can" isn't the same as 
MAY. But AFAIK we *didn't* decide that it MUST NOT.

Which approach is used should really be a local matter between the phone 
and the proxy. It depends both on the features and configurability of 
the phone, and on the translation capabilities of the proxy.

I know you will argue that the definition of the tel uri says it can't 
be used for dial strings. But this still comes down to a fine semantic 
point of whether what is being represented is a dial string or a 
particular form of local number that is closely related to what was 
dialed. The distinction is purely in point of view, so either conclusion 
is valid.

This really is a nit - it perhaps falls into the realm of best practice.

	Paul


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 12:05:46 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17548
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 12:05:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP36Y-00013W-Ik
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 12:05:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQH5UJi004057
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 12:05:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP36Y-00013M-Fl
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 12:05:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17403
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 12:05:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP36X-0001NK-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 12:05:29 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP36W-0001NH-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 12:05:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP366-0000sw-9t; Wed, 26 Nov 2003 12:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP35e-0000rV-M6
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 12:04:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17327
	for <sipping@ietf.org>; Wed, 26 Nov 2003 12:04:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP35d-0001Li-00
	for sipping@ietf.org; Wed, 26 Nov 2003 12:04:33 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP35c-0001L5-00
	for sipping@ietf.org; Wed, 26 Nov 2003 12:04:32 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA04109;
	Wed, 26 Nov 2003 12:03:57 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA24354;
	Wed, 26 Nov 2003 12:03:59 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7Y2M9>; Wed, 26 Nov 2003 12:03:58 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6130@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Wed, 26 Nov 2003 12:03:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

The problem I have with your nit is that I'm big on interoperability.
I think it's important.

Interoperability tends to suffer when you have two ways to do something
and both are optional.  In this case, I think there is so little value
in putting a dialstring in a tel uri or user=phone uri that we should 
just deprecate it.

I think specifications are all about "fine semantic points".  
Specifications strive to be precise.  If the tel uri bis draft is not 
precise enough for you that dialstrings are out of scope, then we should 
make it more precise.

I don't want a UA vendor implementing user=dialstring only to have
a proxy that assumes user=phone.  I really think MUST IMPLEMENT for
both is silly.

I do recognize that the same sequence of digits can be a dial string,
and a local phone number within the "same" context.  That doesn't make 
them the same thing, especially when the recipient doesn't know what he has.
That is why consensus came down to using user=dialstring when you have
a dialstring, and user=phone when you have a phone number.  That way,
a proxy that understands dialstrings can translate, and proxies that 
understand only phone numbers can route appropriately.  Explicit, rather 
than implicit was the reason cited by those in favor of user=dialstring.

Brian

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Wednesday, November 26, 2003 10:31 AM
> To: Rosen, Brian
> Cc: 'Mpierce1@aol.com'; sipping@ietf.org
> Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
> 
> 
> 
> 
> Rosen, Brian wrote:
> > 
> >>>We all agreed that a tel uri, which is also convertible to 
> a sip uri
> >>>with the user=phone convention, remained a way to express 
> >>>local or global phone numbers, and not dial strings.
> >>
> >>I wouldn't go quite that far. While we agreed that the sip uri with 
> >>user=dialstring may be used to represent dial strings, I 
> >>>don't believe that eliminates the option of using a tel: 
> uri with a local 
> >>>number and a context.
> > 
> > I don't understand your concern.
> > What we agreed was that a local or a global number was expressable
> > as either a tel uri, or a sip uri with user=phone interchangeably.
> > So a tel uri can be used for a local number, and a sip uri with
> > user=phone can be used for a local number.
> 
> agreed.
> 
> > We confirmed that a tel uri cannot be used with a dial 
> string, and we
> > decided that a sip uri with user=phone cannot be used with 
> a dial string.
> 
> I think you overstate the case. I think we agreed to define a 
> new value 
> "dialstring" that MAY be used with the user= parameter of a 
> sip uri. And 
> it MAY be used to represent a dialstring.
> 
> It remains demonstrably the case that a dialstring *can* also be 
> represented as a tel uri with a local number and context, as has been 
> discussed ad nauseum on this list. Of course "can" isn't the same as 
> MAY. But AFAIK we *didn't* decide that it MUST NOT.
> 
> Which approach is used should really be a local matter 
> between the phone 
> and the proxy. It depends both on the features and configurability of 
> the phone, and on the translation capabilities of the proxy.
> 
> I know you will argue that the definition of the tel uri says 
> it can't 
> be used for dial strings. But this still comes down to a fine 
> semantic 
> point of whether what is being represented is a dial string or a 
> particular form of local number that is closely related to what was 
> dialed. The distinction is purely in point of view, so either 
> conclusion 
> is valid.
> 
> This really is a nit - it perhaps falls into the realm of 
> best practice.
> 
> 	Paul
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 13:14:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20306
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 13:14:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4Av-0006XY-T4
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 13:14:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQIE53h025134
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 13:14:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4Av-0006XJ-Pi
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 13:14:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20298
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 13:13:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4At-0002Ig-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 13:14:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4At-0002Id-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 13:14:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4Ar-0006W5-5M; Wed, 26 Nov 2003 13:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4AK-0006V9-4v
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 13:13:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20264
	for <sipping@ietf.org>; Wed, 26 Nov 2003 13:13:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4AI-0002Hm-00
	for sipping@ietf.org; Wed, 26 Nov 2003 13:13:26 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4AH-0002HF-00
	for sipping@ietf.org; Wed, 26 Nov 2003 13:13:25 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 26 Nov 2003 10:14:28 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAQICrAt028976;
	Wed, 26 Nov 2003 10:12:53 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEG93240;
	Wed, 26 Nov 2003 13:12:51 -0500 (EST)
Message-ID: <3FC4ED22.3040604@cisco.com>
Date: Wed, 26 Nov 2003 13:12:50 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Exploders anad ad-hoc lists
References: <3FC209FA.6030004@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gonzalo,

I like the concept, but I am troubled by passing the reference to the 
list as a sip/sips url parameter, for the following reasons:

- how does it get there? In your examples, you have the parameter
   in the request uri, but not in the To uri. Normally a UA would
   determine the destination, and put it in both To and request URIs.
   This implies some extra special casing.

- How does it stay there. If the address in the request uri is of
   an AoR, a proxy may replace it with a corresponding registered
   contact. If so, the reference to the list will be lost.

- logically the request is being addressed to the service, and the
   list is a parameter to the service and the particular method the
   service is being asked to perform. Embedding the list in the address
   of the service seems inappropriate.

I think there needs to be a better place to put the reference to the 
list. A new header would seem to be the logical answer.

Regarding draft-camarillo-sipping-exploders-solution-00:

You say the requester should subscribe to a url returned in the response 
to learn the outcome of the exploded requests. But that opens a time 
window when some status may lost. Do you have any thoughts on how to 
close that? (E.g. the first response to a subscription gives all the 
cumulative history of what has happened.)

There are a couple of references to an Explode-To header, but no 
explanation and no examples. It seems redundant to the list, unless it 
is intended as a way to convey the reference to the list.

	Paul

Gonzalo Camarillo wrote:
> Folks,
> 
> we have just submitted three drafts about exploders and ad-hoc lists.
> 
> We have added more requirements to the following draft. The new 
> requirements were mainly discussed in the SIMPLE mailing list.
> 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exploders-01.txt 
> 
> 
> The following draft describes how to carry lists of URIs in SIP 
> requests. It is not a finished draft. It is intended to trigger 
> discussions on this topic to see whether this is a step the right 
> direction.
> 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri-list-00.txt 
> 
> 
> The following draft defines a new method called EXPLODE. EXPLODE does 
> the same as REFER. That is, it tells a UA to send a request somewhere. 
> The differences are that EXPLODE accepts more than one destination 
> (REFER carries a single Refer-To header field) and that EXPLODE does not 
> establish implicit subscriptions of any type. This draft is also 
> intended to trigger discussions within the WG.
> 
> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-explode-method-00.txt 
> 
> 
> Let's try to keep discussions about this topic in the SIPPING mailing 
> list. I will forward this mail to the SIMPLE mailing list to let them know.
> 
> Comments are welcome,
> 
> Gonzalo
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 13:50:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21306
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 13:50:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4jv-00089A-9O
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 13:50:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQIoFAR031310
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 13:50:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4jv-00088v-56
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 13:50:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21283
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 13:49:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4jr-0002gl-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 13:50:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4jr-0002gi-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 13:50:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4jj-00087d-Ek; Wed, 26 Nov 2003 13:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP4jA-00082e-82
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 13:49:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21247
	for <sipping@ietf.org>; Wed, 26 Nov 2003 13:49:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4j7-0002gK-00
	for sipping@ietf.org; Wed, 26 Nov 2003 13:49:25 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP4j7-0002fs-00
	for sipping@ietf.org; Wed, 26 Nov 2003 13:49:25 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id hAQImqjq008863;
	Wed, 26 Nov 2003 10:48:53 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEG96214;
	Wed, 26 Nov 2003 13:48:51 -0500 (EST)
Message-ID: <3FC4F592.2000809@cisco.com>
Date: Wed, 26 Nov 2003 13:48:50 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B6130@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Brian,

I agree that interoperability is important. In the end, unless the phone 
does the entire job of translation there must be some coordination 
between what the phone does and what some proxy downstream does.

To make that work amounts to having at least a minimal dialplan in the 
phone. Minimally this amounts to some substitution rules involving the 
dialstring and some constants configured in the phone.

I gather you have in mind that the phone should have a rule of the form

	url = "sip:" dialstring "@" proxy-address ";user=dialstring"

But that only works when there are no special cases. To support 
dialplans in the phone, it is likely to need to handle a series of 
templates. Often the template of last resort may want to defer to a 
downstream node to sort things out. The template for that could be 
equivalent to the above, but needn't be - it can just as easily make a 
local number with a special context.

We've already discussed reasons why the simple scheme you like has 
problems - like when phones desiring different dialplan expansion share 
a proxy.

It may be more fruitful to explore in more detail what kinds of 
standardized provisioning support ought to be required in phones. I hope 
that is what is most important to you - that it is possible to provision 
any sip phone to work properly with any proxy.

	Paul

Rosen, Brian wrote:
> The problem I have with your nit is that I'm big on interoperability.
> I think it's important.
> 
> Interoperability tends to suffer when you have two ways to do something
> and both are optional.  In this case, I think there is so little value
> in putting a dialstring in a tel uri or user=phone uri that we should 
> just deprecate it.
> 
> I think specifications are all about "fine semantic points".  
> Specifications strive to be precise.  If the tel uri bis draft is not 
> precise enough for you that dialstrings are out of scope, then we should 
> make it more precise.
> 
> I don't want a UA vendor implementing user=dialstring only to have
> a proxy that assumes user=phone.  I really think MUST IMPLEMENT for
> both is silly.
> 
> I do recognize that the same sequence of digits can be a dial string,
> and a local phone number within the "same" context.  That doesn't make 
> them the same thing, especially when the recipient doesn't know what he has.
> That is why consensus came down to using user=dialstring when you have
> a dialstring, and user=phone when you have a phone number.  That way,
> a proxy that understands dialstrings can translate, and proxies that 
> understand only phone numbers can route appropriately.  Explicit, rather 
> than implicit was the reason cited by those in favor of user=dialstring.
> 
> Brian
> 
> 
>>-----Original Message-----
>>From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>Sent: Wednesday, November 26, 2003 10:31 AM
>>To: Rosen, Brian
>>Cc: 'Mpierce1@aol.com'; sipping@ietf.org
>>Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
>>
>>
>>
>>
>>Rosen, Brian wrote:
>>
>>>>>We all agreed that a tel uri, which is also convertible to 
>>>>
>>a sip uri
>>
>>>>>with the user=phone convention, remained a way to express 
>>>>>local or global phone numbers, and not dial strings.
>>>>
>>>>I wouldn't go quite that far. While we agreed that the sip uri with 
>>>>user=dialstring may be used to represent dial strings, I 
>>>>
>>>>>don't believe that eliminates the option of using a tel: 
>>>>
>>uri with a local 
>>
>>>>>number and a context.
>>>>
>>>I don't understand your concern.
>>>What we agreed was that a local or a global number was expressable
>>>as either a tel uri, or a sip uri with user=phone interchangeably.
>>>So a tel uri can be used for a local number, and a sip uri with
>>>user=phone can be used for a local number.
>>
>>agreed.
>>
>>
>>>We confirmed that a tel uri cannot be used with a dial 
>>
>>string, and we
>>
>>>decided that a sip uri with user=phone cannot be used with 
>>
>>a dial string.
>>
>>I think you overstate the case. I think we agreed to define a 
>>new value 
>>"dialstring" that MAY be used with the user= parameter of a 
>>sip uri. And 
>>it MAY be used to represent a dialstring.
>>
>>It remains demonstrably the case that a dialstring *can* also be 
>>represented as a tel uri with a local number and context, as has been 
>>discussed ad nauseum on this list. Of course "can" isn't the same as 
>>MAY. But AFAIK we *didn't* decide that it MUST NOT.
>>
>>Which approach is used should really be a local matter 
>>between the phone 
>>and the proxy. It depends both on the features and configurability of 
>>the phone, and on the translation capabilities of the proxy.
>>
>>I know you will argue that the definition of the tel uri says 
>>it can't 
>>be used for dial strings. But this still comes down to a fine 
>>semantic 
>>point of whether what is being represented is a dial string or a 
>>particular form of local number that is closely related to what was 
>>dialed. The distinction is purely in point of view, so either 
>>conclusion 
>>is valid.
>>
>>This really is a nit - it perhaps falls into the realm of 
>>best practice.
>>
>>	Paul
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 14:12:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22235
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 14:12:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP555-0001cs-7m
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 14:12:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQJC7Sb006247
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 14:12:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP555-0001cg-1S
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 14:12:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22202
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 14:11:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP552-00031m-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 14:12:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP552-00031j-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 14:12:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP54z-0001XZ-D8; Wed, 26 Nov 2003 14:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP54p-0001X9-Ma
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 14:11:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22182
	for <sipping@ietf.org>; Wed, 26 Nov 2003 14:11:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP54m-00031L-00
	for sipping@ietf.org; Wed, 26 Nov 2003 14:11:48 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP54m-00030h-00
	for sipping@ietf.org; Wed, 26 Nov 2003 14:11:48 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA08032;
	Wed, 26 Nov 2003 14:10:41 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA11781;
	Wed, 26 Nov 2003 14:10:37 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7YL9K>; Wed, 26 Nov 2003 14:10:36 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6132@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Wed, 26 Nov 2003 14:10:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Your example does not show a phone context, which it should.
You should always have a context for user=dialstring.
I actually propose that you MUST use a context with user=dialstring.
You need a context for user=phone when you don't a global number.

If your UA implementation does not support dialstring to number
translation (ie downloadable digitmap/regexp), then I propose
that you have a configurable/discoverable context, and the rule
is that you take all the digits, slap the sip: in the front,
your local outgoing proxy in the back, with user=dialstring and
phone=context=<whatever> and send it.

There is no "last resort". it's what a dumb phone always does.

I think that covers all cases of dumb phones.  It might also covers
a case you suggest, which would be an incomplete digitmap that
needed an escape clause.  Digitmap capable phones need more work,
and I agree we need to standardize that, and we both are aware
of the efforts to do that.

None of this is pushback to the argument that user=phone is only
appropriate when the userpart is the address of a terminal (ie
phone number).  I do want a simple rule - if you don't understand 
what the string of digits is, it's a dialstring and send user=dialstring.  
If you can, translate the dialstring to a phone number and send 
user=phone (or tel uri).  There is no third case that I know of.

Brian

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Wednesday, November 26, 2003 1:49 PM
> To: Rosen, Brian
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
> 
> 
> Brian,
> 
> I agree that interoperability is important. In the end, 
> unless the phone 
> does the entire job of translation there must be some coordination 
> between what the phone does and what some proxy downstream does.
> 
> To make that work amounts to having at least a minimal 
> dialplan in the 
> phone. Minimally this amounts to some substitution rules 
> involving the 
> dialstring and some constants configured in the phone.
> 
> I gather you have in mind that the phone should have a rule 
> of the form
> 
> 	url = "sip:" dialstring "@" proxy-address ";user=dialstring"
> 
> But that only works when there are no special cases. To support 
> dialplans in the phone, it is likely to need to handle a series of 
> templates. Often the template of last resort may want to defer to a 
> downstream node to sort things out. The template for that could be 
> equivalent to the above, but needn't be - it can just as 
> easily make a 
> local number with a special context.
> 
> We've already discussed reasons why the simple scheme you like has 
> problems - like when phones desiring different dialplan 
> expansion share 
> a proxy.
> 
> It may be more fruitful to explore in more detail what kinds of 
> standardized provisioning support ought to be required in 
> phones. I hope 
> that is what is most important to you - that it is possible 
> to provision 
> any sip phone to work properly with any proxy.
> 
> 	Paul
> 
> Rosen, Brian wrote:
> > The problem I have with your nit is that I'm big on 
> interoperability.
> > I think it's important.
> > 
> > Interoperability tends to suffer when you have two ways to 
> do something
> > and both are optional.  In this case, I think there is so 
> little value
> > in putting a dialstring in a tel uri or user=phone uri that 
> we should 
> > just deprecate it.
> > 
> > I think specifications are all about "fine semantic points".  
> > Specifications strive to be precise.  If the tel uri bis 
> draft is not 
> > precise enough for you that dialstrings are out of scope, 
> then we should 
> > make it more precise.
> > 
> > I don't want a UA vendor implementing user=dialstring only to have
> > a proxy that assumes user=phone.  I really think MUST IMPLEMENT for
> > both is silly.
> > 
> > I do recognize that the same sequence of digits can be a 
> dial string,
> > and a local phone number within the "same" context.  That 
> doesn't make 
> > them the same thing, especially when the recipient doesn't 
> know what he has.
> > That is why consensus came down to using user=dialstring 
> when you have
> > a dialstring, and user=phone when you have a phone number.  
> That way,
> > a proxy that understands dialstrings can translate, and 
> proxies that 
> > understand only phone numbers can route appropriately.  
> Explicit, rather 
> > than implicit was the reason cited by those in favor of 
> user=dialstring.
> > 
> > Brian
> > 
> > 
> >>-----Original Message-----
> >>From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> >>Sent: Wednesday, November 26, 2003 10:31 AM
> >>To: Rosen, Brian
> >>Cc: 'Mpierce1@aol.com'; sipping@ietf.org
> >>Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
> >>
> >>
> >>
> >>
> >>Rosen, Brian wrote:
> >>
> >>>>>We all agreed that a tel uri, which is also convertible to 
> >>>>
> >>a sip uri
> >>
> >>>>>with the user=phone convention, remained a way to express 
> >>>>>local or global phone numbers, and not dial strings.
> >>>>
> >>>>I wouldn't go quite that far. While we agreed that the 
> sip uri with 
> >>>>user=dialstring may be used to represent dial strings, I 
> >>>>
> >>>>>don't believe that eliminates the option of using a tel: 
> >>>>
> >>uri with a local 
> >>
> >>>>>number and a context.
> >>>>
> >>>I don't understand your concern.
> >>>What we agreed was that a local or a global number was expressable
> >>>as either a tel uri, or a sip uri with user=phone interchangeably.
> >>>So a tel uri can be used for a local number, and a sip uri with
> >>>user=phone can be used for a local number.
> >>
> >>agreed.
> >>
> >>
> >>>We confirmed that a tel uri cannot be used with a dial 
> >>
> >>string, and we
> >>
> >>>decided that a sip uri with user=phone cannot be used with 
> >>
> >>a dial string.
> >>
> >>I think you overstate the case. I think we agreed to define a 
> >>new value 
> >>"dialstring" that MAY be used with the user= parameter of a 
> >>sip uri. And 
> >>it MAY be used to represent a dialstring.
> >>
> >>It remains demonstrably the case that a dialstring *can* also be 
> >>represented as a tel uri with a local number and context, 
> as has been 
> >>discussed ad nauseum on this list. Of course "can" isn't 
> the same as 
> >>MAY. But AFAIK we *didn't* decide that it MUST NOT.
> >>
> >>Which approach is used should really be a local matter 
> >>between the phone 
> >>and the proxy. It depends both on the features and 
> configurability of 
> >>the phone, and on the translation capabilities of the proxy.
> >>
> >>I know you will argue that the definition of the tel uri says 
> >>it can't 
> >>be used for dial strings. But this still comes down to a fine 
> >>semantic 
> >>point of whether what is being represented is a dial string or a 
> >>particular form of local number that is closely related to what was 
> >>dialed. The distinction is purely in point of view, so either 
> >>conclusion 
> >>is valid.
> >>
> >>This really is a nit - it perhaps falls into the realm of 
> >>best practice.
> >>
> >>	Paul
> >>
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> > 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Wed Nov 26 15:19:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26376
	for <sipping-archive@odin.ietf.org>; Wed, 26 Nov 2003 15:19:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP67v-0006S1-Nl
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 15:19:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQKJ7eD024791
	for sipping-archive@odin.ietf.org; Wed, 26 Nov 2003 15:19:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP67v-0006Rm-KH
	for sipping-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 15:19:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26363
	for <sipping-web-archive@ietf.org>; Wed, 26 Nov 2003 15:18:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP67u-0004BL-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 15:19:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP67t-0004BG-00
	for sipping-web-archive@ietf.org; Wed, 26 Nov 2003 15:19:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP67p-0006Qf-5D; Wed, 26 Nov 2003 15:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AP67G-0006PZ-OH
	for sipping@optimus.ietf.org; Wed, 26 Nov 2003 15:18:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26338
	for <sipping@ietf.org>; Wed, 26 Nov 2003 15:18:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP67F-0004Af-00
	for sipping@ietf.org; Wed, 26 Nov 2003 15:18:25 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AP67E-00049z-00
	for sipping@ietf.org; Wed, 26 Nov 2003 15:18:24 -0500
Received: from cisco.com (64.102.124.12)
  by sj-iport-5.cisco.com with ESMTP; 26 Nov 2003 12:17:19 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hAQKHpxg029811;
	Wed, 26 Nov 2003 15:17:52 -0500 (EST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEH03529;
	Wed, 26 Nov 2003 15:17:51 -0500 (EST)
Message-ID: <3FC50A6E.3060707@cisco.com>
Date: Wed, 26 Nov 2003 15:17:50 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B6132@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Rosen, Brian wrote:
> Your example does not show a phone context, which it should.
> You should always have a context for user=dialstring.

OK, I didn't know you intended that requirement. That makes things 
simpler and more clearcut, because it one more piece of 
configurable/discoverable data that even dumb phones need.

> I actually propose that you MUST use a context with user=dialstring.
> You need a context for user=phone when you don't a global number.
> 
> If your UA implementation does not support dialstring to number
> translation (ie downloadable digitmap/regexp), then I propose
> that you have a configurable/discoverable context, and the rule
> is that you take all the digits, slap the sip: in the front,
> your local outgoing proxy in the back, with user=dialstring and
> phone=context=<whatever> and send it.

OK, that is what I thought you had in mind except for the addition of 
the context.

> There is no "last resort". it's what a dumb phone always does.

The way I am thinking of it is that a phone with a dialplan may 
ultimately need an "else" clause. A dumb phone is just a degenerate case 
of that, where the else clause is all there is. It would be nice to be 
consistent in that way between dumb and smart phones.

> I think that covers all cases of dumb phones.  It might also covers
> a case you suggest, which would be an incomplete digitmap that
> needed an escape clause.  Digitmap capable phones need more work,
> and I agree we need to standardize that, and we both are aware
> of the efforts to do that.

It would also be very sensible for the translation that is used by dumb 
phones is of exactly the same form as one entry in a dial map for a 
smart phone. Rather than using the transformation you mention above on 
each dialstring, it would be straightforward to say that a single 
template is either configured, or is created from discoverable data. If 
you can discover a context to use with dialstrings you can just as well 
discover a template.

> None of this is pushback to the argument that user=phone is only
> appropriate when the userpart is the address of a terminal (ie
> phone number).  I do want a simple rule - if you don't understand 
> what the string of digits is, it's a dialstring and send user=dialstring.  
> If you can, translate the dialstring to a phone number and send 
> user=phone (or tel uri).  There is no third case that I know of.

Suppose I had a dial plan that said:

	translate all numbers that start with "8"
	to "tel:" + dialstring + ";phone-context=dial.cisco.com"

I think that should be ok with you. Now instead, suppose I made the rule:

	translate all numbers that start with "0"..."9","*","#"
	to "tel:" + dialstring + ";phone-context=dial.cisco.com"

	translate all other numbers to
	"sip:" + dialstring + ";phone-context=dial.cisco.com"
	       + "@cisco.com;user=dialstring"

Is that still ok with you? Why not?

Its my system, my dial plan, my definition of the "dial.cisco.com" 
phone-context, so I don't see what you have to complain about. You say I 
can only use user=phone (or tel:) when the address is that of a 
terminal. But I get to decide what the addresses of terminals are. I say 
I am using my dialplan to translate dial strings into addresses of 
terminals - it just happens that my terminal addresses look remarkably 
similar to dialstrings.

Of course the last rule isn't needed any more because it can never be 
reached. So my complete dialplan is just:

	translate all numbers that start with "0"..."9","*","#"
	to "tel:" + dialstring + ";phone-context=dial.cisco.com"

What am I doing wrong here?

	Paul


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sat Nov 29 18:30:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01393
	for <sipping-archive@odin.ietf.org>; Sat, 29 Nov 2003 18:30:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQEXZ-0007pB-3y
	for sipping-archive@odin.ietf.org; Sat, 29 Nov 2003 18:30:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hATNUHon030073
	for sipping-archive@odin.ietf.org; Sat, 29 Nov 2003 18:30:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQEXZ-0007oy-0d
	for sipping-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 18:30:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01375
	for <sipping-web-archive@ietf.org>; Sat, 29 Nov 2003 18:30:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQEXV-0004Kh-00
	for sipping-web-archive@ietf.org; Sat, 29 Nov 2003 18:30:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQEXV-0004Kd-00
	for sipping-web-archive@ietf.org; Sat, 29 Nov 2003 18:30:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQEXL-0007nq-An; Sat, 29 Nov 2003 18:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQEXC-0007nK-9y
	for sipping@optimus.ietf.org; Sat, 29 Nov 2003 18:29:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01370
	for <sipping@ietf.org>; Sat, 29 Nov 2003 18:29:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQEX9-0004Ka-00
	for sipping@ietf.org; Sat, 29 Nov 2003 18:29:51 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQEX8-0004KG-00
	for sipping@ietf.org; Sat, 29 Nov 2003 18:29:50 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hATNTIw5007154;
	Sat, 29 Nov 2003 15:29:19 -0800 (PST)
Received: from [192.168.0.2] (sjc-vpn4-71.cisco.com [10.21.80.71])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AKI14906;
	Sat, 29 Nov 2003 15:29:17 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sat, 29 Nov 2003 15:29:15 -0800
Subject: Re: [Sipping] ITU H.350-related Directory Services Internet Draft
From: Cullen Jennings <fluffy@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>, <sipping@ietf.org>
CC: <Tyler_Johnson@unc.edu>
Message-ID: <BBEE6BCB.272A0%fluffy@cisco.com>
In-Reply-To: <1069698712.11916.91.camel@bdsl.greycouncil.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I'm very unclear on what you are trying to do here.

If you are trying to provide configuration information for SIP UA's with
this - I think that approach is really lacking.

If you are trying to create a global LDAP directory with all subscribers in
it as a way of doing rendezvous between different domains, I think that all
you need in the directory is the SIP AOR for the user.

If I have the URL sip:alice@example.com, Why would I want to find out the
address of the registrar?

ProxyAddress - not sure I would want this - again SIP uses DNS.

SIPIdentityAddress - again, isn't this just the URL

SIPIdenityPassword - surely you are joking. If the purpose of this directory
is as described in the draft, you would not need this. If the purpose was
provisioning, this would be a really bad approach.

ServiceLevel - well this is a nice field with no meaning. What would anyone
do with it. If no one does anything with, why is it here.




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 30 07:14:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29570
	for <sipping-archive@odin.ietf.org>; Sun, 30 Nov 2003 07:14:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQQSp-0008NR-HP
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 07:14:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUCEBVD032197
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 07:14:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQQSp-0008NE-BY
	for sipping-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 07:14:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29564
	for <sipping-web-archive@ietf.org>; Sun, 30 Nov 2003 07:13:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQQSo-0004db-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 07:14:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQQSo-0004dY-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 07:14:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQQSf-0008Lz-R7; Sun, 30 Nov 2003 07:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQQRm-0008Dk-Rx
	for sipping@optimus.ietf.org; Sun, 30 Nov 2003 07:13:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29554
	for <sipping@ietf.org>; Sun, 30 Nov 2003 07:12:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQQRm-0004d6-00
	for sipping@ietf.org; Sun, 30 Nov 2003 07:13:06 -0500
Received: from smtpsrv12.isis.unc.edu ([152.2.1.243] helo=smtp.unc.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQQRm-0004d3-00
	for sipping@ietf.org; Sun, 30 Nov 2003 07:13:06 -0500
Received: from email.unc.edu (dhcp26927.vpn.unc.edu [152.23.168.3])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id hAUCCe8Q019981;
	Sun, 30 Nov 2003 07:12:40 -0500 (EST)
Message-ID: <3FC9DEB9.6060504@email.unc.edu>
Date: Sun, 30 Nov 2003 07:12:41 -0500
From: Tyler Johnson <trjohns1@email.unc.edu>
Reply-To: Tyler_Johnson@unc.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 (CK-UNC-CH)
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: sipping@ietf.org, Tyler_Johnson@unc.edu
Subject: Re: [Sipping] ITU H.350-related Directory Services Internet Draft
References: <BBEE6BCB.272A0%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Cullen Jennings wrote:
> I'm very unclear on what you are trying to do here.

The primary reason for the H.350 series is to allow an enterprise, 
carrier, or other service provider to manage primary identity data 
associated with multimedia conferencing in a way that is standardized 
and outside the call servers and endpoints themselves. For example, many 
large universities (like mine) offer SIP, H.323, H.320 as well as 
proprietary conferencing services. It is important that these 
universities be able to centrally manage all of their users, and their 
associated conferencing addresses. It is important that these 
universities be able to manage that data store (LDAP directory) 
independently from the particular call servers they happen to be using, 
so that they can migrate from one product and vendor to another without 
having to rebuild their internal data stores and management structures.

The white pages example you mention is one benefit of standardizing 
conferencing address representations in LDAP. It is important to be able 
to query an LDAP directory and ask the question 'What is the SIP URI for 
this user?' And you correctly point out that SIP URI is probably the 
only attribute (other than the data structures associated with managing 
the object classes themselves) necessary for that.

Using H.350 for endpoint configuration (i.e. provisioning) has been 
demonstrated as an academic exercise and is of interest to some, but the 
base H.350 architecture is not intended to cover the depth of that 
subject, as you correctly point out. To accomplish this in the real 
world would require extension of the object classes, or the use of 
another protocol.

You are correct that for the bulk of SIP applications, only a few of 
these attributes would normally be needed. In particular 
SIPIdentitySIPURI, SIPIdentityUserName, and SIPIdentityPassword. From 
SIPIdentitySIPURI (AOR) white pages can be built, and a user agent can 
determine its registrar using DNS (as you point out). A proxy can access 
SIPIdentityUserName and SIPIdentityPassword to achieve vendor neutrality 
with respect to identity.

The other attributes are there for trivial cases, which I would not 
expect to be used that often. For example, SIPIdentityAddress is 
intended for user agents that are connecting without the benefit of a 
proxy, i.e. dialing directly by IP address (not a common scenario). 
SIPIdentityProxyAddress could be used by user agents that don't support 
the SRV lookup. Sometimes, this information can be used not as a 
provisioning tool, but as a guide for end users, to create web pages 
that assist users in configuring endpoints. For example, a user may have 
access a web interface to ask 'What do I type in my endpoint 
configurations where it asks for proxy address?' Having this information 
in the directory can be an aid to service administrators in creating 
these kinds of tools.

SIPIdentityServiceLevel can be used by service administrators to group 
users (or user agents) into categories based on what services they are 
allowed to access, or other categories deemed useful to the service 
administrator.



> If you are trying to provide configuration information for SIP UA's with
> this - I think that approach is really lacking.
> 
> If you are trying to create a global LDAP directory with all subscribers in
> it as a way of doing rendezvous between different domains, I think that all
> you need in the directory is the SIP AOR for the user.
> 
> If I have the URL sip:alice@example.com, Why would I want to find out the
> address of the registrar?
> 
> ProxyAddress - not sure I would want this - again SIP uses DNS.
> 
> SIPIdentityAddress - again, isn't this just the URL
> 
> SIPIdenityPassword - surely you are joking. If the purpose of this directory
> is as described in the draft, you would not need this. If the purpose was
> provisioning, this would be a really bad approach.
> 
> ServiceLevel - well this is a nice field with no meaning. What would anyone
> do with it. If no one does anything with, why is it here.
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 30 08:40:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01052
	for <sipping-archive@odin.ietf.org>; Sun, 30 Nov 2003 08:40:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQRoB-0004tS-W5
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 08:40:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUDeJSG018803
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 08:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQRoB-0004tC-DH
	for sipping-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 08:40:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01039
	for <sipping-web-archive@ietf.org>; Sun, 30 Nov 2003 08:40:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQRoA-0005RI-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 08:40:18 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQRo9-0005RF-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 08:40:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQRnw-0004rm-6h; Sun, 30 Nov 2003 08:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQRnQ-0004qk-Je
	for sipping@optimus.ietf.org; Sun, 30 Nov 2003 08:39:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01003
	for <sipping@ietf.org>; Sun, 30 Nov 2003 08:39:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQRnP-0005QV-00
	for sipping@ietf.org; Sun, 30 Nov 2003 08:39:31 -0500
Received: from natsmtp01.rzone.de ([81.169.145.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQRnO-0005QS-00
	for sipping@ietf.org; Sun, 30 Nov 2003 08:39:30 -0500
Received: from sip (pD9E6B529.dip.t-dialin.net [217.230.181.41])
	by post.webmailer.de (8.12.10/8.12.10) with ESMTP id hAUDdQq9014425;
	Sun, 30 Nov 2003 14:39:27 +0100 (MET)
From: "Christian Stredicke" <stredicke@snom.de>
To: <sipping@ietf.org>
Cc: <Tyler_Johnson@unc.edu>
Subject: AW: [Sipping] ITU H.350-related Directory Services Internet Draft
Date: Sun, 30 Nov 2003 14:39:31 +0100
Message-ID: <004401c3b747$6284b090$1e02a8c0@sip>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <1069698712.11916.91.camel@bdsl.greycouncil.com>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi!

The problems that I have with LDAP are the following:

- The "lightweight" in LDAP is a euphemism. Implementing LDAP is like
implementing NFS or and other full blown file system. If you have 128 MB
main memory and COM objects it's probably a piece of cake. For an
embedded user agent is unsuitable. Not to mention ASN.1.

- I would like to stay with a simple SIP message exchange. We are
fighting very hard to get SIP through firewalls and people don=92t want =
to
open other ports for LDAP for address book lookup (maybe a tunneling of
the lookup string could be an alternative).

- I am missing call list integration in the LDAP concept. Having an
address book is nice, but customers want to use their last calls as well
(number guessing). I don=92t see how that can be achieved with LDAP.

I would prefer a mechanism that looks like this:

GET number_guessing?user=3D123%40abc.org&number=3Dco&max_hits=3D3 =
HTTP/1.1
Accept: application/number-guessing


HTTP/1.1 200 Ok
Content-Type: application/number-guessing
Content-Length: 35

<sip:conf@abc.org>
<sip:colleagues@bigcompany.org>

Works fine and eats very little additional code if you already have a
web client. The web server can be written for example with PHP as a
student half-time semester task.


Christian

> -----Urspr=FCngliche Nachricht-----
> Von: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] Im Auftrag
von
> Dean Willis
> Gesendet: Montag, 24. November 2003 19:32
> An: sipping@ietf.org
> Cc: Tyler_Johnson@unc.edu
> Betreff: [Sipping] ITU H.350-related Directory Services Internet Draft
>=20
>=20
> If you are interested in integrating directory services with SIP,
please
> review:
>=20
>
http://www.ietf.org/internet-drafts/draft-h350-directory-services-00.txt
>=20
>=20
> Thanks!
>=20
> --
> Dean
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 30 11:41:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04596
	for <sipping-archive@odin.ietf.org>; Sun, 30 Nov 2003 11:41:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQUdH-0007IV-45
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 11:41:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUGfFjV028041
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 11:41:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQUdG-0007Hx-TM
	for sipping-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 11:41:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04576
	for <sipping-web-archive@ietf.org>; Sun, 30 Nov 2003 11:41:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQUdF-0007U8-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 11:41:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQUdF-0007U5-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 11:41:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQUd6-0007Fd-51; Sun, 30 Nov 2003 11:41:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQUcG-00074O-Mo
	for sipping@optimus.ietf.org; Sun, 30 Nov 2003 11:40:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04572
	for <sipping@ietf.org>; Sun, 30 Nov 2003 11:39:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQUcF-0007TA-00
	for sipping@ietf.org; Sun, 30 Nov 2003 11:40:11 -0500
Received: from listserv0.isis.unc.edu ([152.2.0.38] helo=smtp.unc.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQUcF-0007T7-00
	for sipping@ietf.org; Sun, 30 Nov 2003 11:40:11 -0500
Received: from email.unc.edu (rdu26-84-151.nc.rr.com [66.26.84.151])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id hAUGe2bx024021
	for <sipping@ietf.org>; Sun, 30 Nov 2003 11:40:02 -0500 (EST)
Message-ID: <3FCA1D5C.3060505@email.unc.edu>
Date: Sun, 30 Nov 2003 11:39:56 -0500
From: Tyler Johnson <trjohns1@email.unc.edu>
Reply-To: Tyler_Johnson@unc.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 (CK-UNC-CH)
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: sipping@ietf.org
Subject: Re: AW: [Sipping] ITU H.350-related Directory Services Internet Draft
References: <004401c3b747$6284b090$1e02a8c0@sip>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.unc.edu id hAUGe2bx024021
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Christian,

I think what you propose is reasonable. A number of vendors with=20
embedded systems have also considered using a non-LDAP approach to=20
getting address information into the endpoint. This is because they=20
either don't want the footprint/cost of adding LDAP to an embedded=20
device, or they already have a proprietary way of communicating address=20
book information from a management system into endpoints. In these=20
cases, the approach I have seen folks investigate is having the=20
management system (usually a more robust server) do H.350 lookups on=20
behalf of the endpoints, and then transmit that information to the=20
endpoints using a lightweight (no pun intended) or proprietary method.

While LDAP *can* be implemented on the endpoint (and is already in some=20
cases), the goal of H.350 is more about how the enterprise stores,=20
manages, and protects its master data store of endpoint information.

In general, I would say that it is much more desirable that a registrar=20
be able to interface with an enterprise identity service, than an=20
endpoint. At the last Internet2 meeting, we showed an H.350-enabled=20
proxy by HCL handling calls for a variety of SIP user agents that had=20
absolutely no knowledge of H.350. That the endpoints address and=20
authentication information was being managed behind the scenes in=20
accordance with enterprise policy, yet required no modification to the=20
endpoint, was nice to see.

Cheers,
Tyler

Christian Stredicke wrote:
> Hi!
>=20
> The problems that I have with LDAP are the following:
>=20
> - The "lightweight" in LDAP is a euphemism. Implementing LDAP is like
> implementing NFS or and other full blown file system. If you have 128 M=
B
> main memory and COM objects it's probably a piece of cake. For an
> embedded user agent is unsuitable. Not to mention ASN.1.
>=20
> - I would like to stay with a simple SIP message exchange. We are
> fighting very hard to get SIP through firewalls and people don=92t want=
 to
> open other ports for LDAP for address book lookup (maybe a tunneling of
> the lookup string could be an alternative).
>=20
> - I am missing call list integration in the LDAP concept. Having an
> address book is nice, but customers want to use their last calls as wel=
l
> (number guessing). I don=92t see how that can be achieved with LDAP.
>=20
> I would prefer a mechanism that looks like this:
>=20
> GET number_guessing?user=3D123%40abc.org&number=3Dco&max_hits=3D3 HTTP/=
1.1
> Accept: application/number-guessing
>=20
>=20
> HTTP/1.1 200 Ok
> Content-Type: application/number-guessing
> Content-Length: 35
>=20
> <sip:conf@abc.org>
> <sip:colleagues@bigcompany.org>
>=20
> Works fine and eats very little additional code if you already have a
> web client. The web server can be written for example with PHP as a
> student half-time semester task.
>=20
>=20
> Christian
>=20
>=20
>>-----Urspr=FCngliche Nachricht-----
>>Von: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] Im Auftrag
>=20
> von
>=20
>>Dean Willis
>>Gesendet: Montag, 24. November 2003 19:32
>>An: sipping@ietf.org
>>Cc: Tyler_Johnson@unc.edu
>>Betreff: [Sipping] ITU H.350-related Directory Services Internet Draft
>>
>>
>>If you are interested in integrating directory services with SIP,
>=20
> please
>=20
>>review:
>>
>>
>=20
> http://www.ietf.org/internet-drafts/draft-h350-directory-services-00.tx=
t
>=20
>>
>>Thanks!
>>
>>--
>>Dean
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>=20
>=20



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 30 15:03:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11052
	for <sipping-archive@odin.ietf.org>; Sun, 30 Nov 2003 15:03:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQXmr-0003iL-2U
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 15:03:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUK3LKC014271
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 15:03:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQXmq-0003i6-V6
	for sipping-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 15:03:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11022
	for <sipping-web-archive@ietf.org>; Sun, 30 Nov 2003 15:03:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQXmn-0004WX-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 15:03:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQXmn-0004WU-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 15:03:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQXmX-0003gj-17; Sun, 30 Nov 2003 15:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQXlb-0003ZM-3e
	for sipping@optimus.ietf.org; Sun, 30 Nov 2003 15:02:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11001
	for <sipping@ietf.org>; Sun, 30 Nov 2003 15:01:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQXlY-0004Sp-00
	for sipping@ietf.org; Sun, 30 Nov 2003 15:02:00 -0500
Received: from natsmtp01.rzone.de ([81.169.145.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQXlX-0004Sk-00
	for sipping@ietf.org; Sun, 30 Nov 2003 15:01:59 -0500
Received: from sip (pD9E6B529.dip.t-dialin.net [217.230.181.41])
	by post.webmailer.de (8.12.10/8.12.10) with ESMTP id hAUK1ve7025029;
	Sun, 30 Nov 2003 21:01:57 +0100 (MET)
From: "Christian Stredicke" <stredicke@snom.de>
To: <Tyler_Johnson@unc.edu>
Cc: <sipping@ietf.org>
Subject: AW: AW: [Sipping] ITU H.350-related Directory Services Internet Draft
Date: Sun, 30 Nov 2003 21:02:02 +0100
Message-ID: <004d01c3b77c$d2895870$1e02a8c0@sip>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <3FCA1D5C.3060505@email.unc.edu>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Tyler,

I think that is a very good point! The proxy *has* the MB and can act as
an agent for the endpoint. So using H.350 is an option for the proxy or
whatever device needs to access the centralized data in a standardized
way.

Thanks, CS

> -----Urspr=FCngliche Nachricht-----
> Von: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] Im Auftrag
von
> Tyler Johnson
> Gesendet: Sonntag, 30. November 2003 17:40
> Cc: sipping@ietf.org
> Betreff: Re: AW: [Sipping] ITU H.350-related Directory Services
Internet
> Draft
>=20
> Christian,
>=20
> I think what you propose is reasonable. A number of vendors with
> embedded systems have also considered using a non-LDAP approach to
> getting address information into the endpoint. This is because they
> either don't want the footprint/cost of adding LDAP to an embedded
> device, or they already have a proprietary way of communicating
address
> book information from a management system into endpoints. In these
> cases, the approach I have seen folks investigate is having the
> management system (usually a more robust server) do H.350 lookups on
> behalf of the endpoints, and then transmit that information to the
> endpoints using a lightweight (no pun intended) or proprietary method.
>=20
> While LDAP *can* be implemented on the endpoint (and is already in
some
> cases), the goal of H.350 is more about how the enterprise stores,
> manages, and protects its master data store of endpoint information.
>=20
> In general, I would say that it is much more desirable that a
registrar
> be able to interface with an enterprise identity service, than an
> endpoint. At the last Internet2 meeting, we showed an H.350-enabled
> proxy by HCL handling calls for a variety of SIP user agents that had
> absolutely no knowledge of H.350. That the endpoints address and
> authentication information was being managed behind the scenes in
> accordance with enterprise policy, yet required no modification to the
> endpoint, was nice to see.
>=20
> Cheers,
> Tyler
>=20
> Christian Stredicke wrote:
> > Hi!
> >
> > The problems that I have with LDAP are the following:
> >
> > - The "lightweight" in LDAP is a euphemism. Implementing LDAP is
like
> > implementing NFS or and other full blown file system. If you have
128 MB
> > main memory and COM objects it's probably a piece of cake. For an
> > embedded user agent is unsuitable. Not to mention ASN.1.
> >
> > - I would like to stay with a simple SIP message exchange. We are
> > fighting very hard to get SIP through firewalls and people don=92t
want to
> > open other ports for LDAP for address book lookup (maybe a tunneling
of
> > the lookup string could be an alternative).
> >
> > - I am missing call list integration in the LDAP concept. Having an
> > address book is nice, but customers want to use their last calls as
well
> > (number guessing). I don=92t see how that can be achieved with LDAP.
> >
> > I would prefer a mechanism that looks like this:
> >
> > GET number_guessing?user=3D123%40abc.org&number=3Dco&max_hits=3D3 =
HTTP/1.1
> > Accept: application/number-guessing
> >
> >
> > HTTP/1.1 200 Ok
> > Content-Type: application/number-guessing
> > Content-Length: 35
> >
> > <sip:conf@abc.org>
> > <sip:colleagues@bigcompany.org>
> >
> > Works fine and eats very little additional code if you already have
a
> > web client. The web server can be written for example with PHP as a
> > student half-time semester task.
> >
> >
> > Christian
> >
> >
> >>-----Urspr=FCngliche Nachricht-----
> >>Von: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] Im
Auftrag
> >
> > von
> >
> >>Dean Willis
> >>Gesendet: Montag, 24. November 2003 19:32
> >>An: sipping@ietf.org
> >>Cc: Tyler_Johnson@unc.edu
> >>Betreff: [Sipping] ITU H.350-related Directory Services Internet
Draft
> >>
> >>
> >>If you are interested in integrating directory services with SIP,
> >
> > please
> >
> >>review:
> >>
> >>
> >
> >
http://www.ietf.org/internet-drafts/draft-h350-directory-services-00.txt
> >
> >>
> >>Thanks!
> >>
> >>--
> >>Dean
> >>
> >>_______________________________________________
> >>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >>This list is for NEW development of the application of SIP
> >>Use sip-implementors@cs.columbia.edu for questions on current sip
> >>Use sip@ietf.org for new developments of core SIP
> >
> >
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



From exim@www1.ietf.org  Sun Nov 30 15:56:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13106
	for <sipping-archive@odin.ietf.org>; Sun, 30 Nov 2003 15:56:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQYbw-0007J4-8p
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 15:56:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUKu8S5028083
	for sipping-archive@odin.ietf.org; Sun, 30 Nov 2003 15:56:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQYbw-0007Is-2U
	for sipping-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 15:56:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13097
	for <sipping-web-archive@ietf.org>; Sun, 30 Nov 2003 15:55:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQYbu-0005Wp-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 15:56:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQYbu-0005Wm-00
	for sipping-web-archive@ietf.org; Sun, 30 Nov 2003 15:56:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQYbq-0007Hk-4h; Sun, 30 Nov 2003 15:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQYb2-0007HG-W7
	for sipping@optimus.ietf.org; Sun, 30 Nov 2003 15:55:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13085
	for <sipping@ietf.org>; Sun, 30 Nov 2003 15:54:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQYb1-0005WM-00
	for sipping@ietf.org; Sun, 30 Nov 2003 15:55:11 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQYb0-0005W6-00
	for sipping@ietf.org; Sun, 30 Nov 2003 15:55:10 -0500
Received: from ibm-eyjgx9r6nqt.shockey.us (h-68-165-240-35.MCLNVA23.covad.net [68.165.240.35])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id hAUL1Nf30278;
	Sun, 30 Nov 2003 13:01:23 -0800
Message-Id: <6.0.1.1.2.20031130154825.037c5ec0@joy.songbird.com>
X-Sender: richard@joy.songbird.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Sun, 30 Nov 2003 15:54:42 -0500
To: Tyler_Johnson@unc.edu
From: Richard Shockey <richard@shockey.us>
Subject: Re: AW: [Sipping] ITU H.350-related Directory Services
  Internet Draft
Cc: sipping@ietf.org
In-Reply-To: <3FCA1D5C.3060505@email.unc.edu>
References: <004401c3b747$6284b090$1e02a8c0@sip>
 <3FCA1D5C.3060505@email.unc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>



>In general, I would say that it is much more desirable that a registrar be 
>able to interface with an enterprise identity service, than an endpoint. 
>At the last Internet2 meeting, we showed an H.350-enabled proxy by HCL 
>handling calls for a variety of SIP user agents that had absolutely no 
>knowledge of H.350. That the endpoints address and authentication 
>information was being managed behind the scenes in accordance with 
>enterprise policy, yet required no modification to the endpoint, was nice 
>to see.

so how do you plan on solving the Inter-domain issues?


>Cheers,
>Tyler
>
>Christian Stredicke wrote:
>>Hi!
>>The problems that I have with LDAP are the following:
>>- The "lightweight" in LDAP is a euphemism.

more like oxymoron


>>Implementing LDAP is like
>>implementing NFS or and other full blown file system. If you have 128 MB
>>main memory and COM objects it's probably a piece of cake. For an
>>embedded user agent is unsuitable. Not to mention ASN.1.


amen ..whenever anyone asks me  "Why SIP?" I instantly answer .."Its ASCII 
<fill in the blank>"



 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
46000 Center Oak Plaza  -   Sterling, VA  20166
sip:rshockey(at)iptel.org   ENUM +87810-13313-31331
PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683,  Fax: +1 815.333.1237
<mailto:richard(at)shockey.us> or <mailto:richard.shockey(at)neustar.biz>
<http://www.neustar.biz> ; <http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP



