From sipping-bounces@ietf.org  Mon Nov  1 01:21:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11937
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 01:21:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COVoJ-0006XC-8l
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 01:37:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COVXq-0008TO-9p; Mon, 01 Nov 2004 01:19:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COVWS-0008Hq-Rz
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 01:18:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11859
	for <sipping@ietf.org>; Mon, 1 Nov 2004 01:18:32 -0500 (EST)
Received: from g2.sfnat.genesyslab.com ([198.49.180.210]
	helo=g2.genesyslab.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COVlJ-0006U9-GK
	for sipping@ietf.org; Mon, 01 Nov 2004 01:33:53 -0500
Received: from SAURON.us.int.genesyslab.com ([192.168.20.232]) by
	g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 31 Oct 2004 22:18:01 -0800
Received: from aster.us.int.genesyslab.com ([10.10.10.25]) by
	SAURON.us.int.genesyslab.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 31 Oct 2004 22:18:01 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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: Sun, 31 Oct 2004 22:18:00 -0800
Message-ID: <52F49B5A0E5B0F4781C9C8F7159409E40195BE89@aster.us.int.genesyslab.com>
Thread-Topic: Question related to netann draft
Thread-Index: AcS/2ompYpDYXwaRRYmuu/WzXLoM6g==
From: "Rajiv Dharmadhikari" <rajivdh@genesyslab.com>
To: <eburger@brooktrout.com>
X-OriginalArrivalTime: 01 Nov 2004 06:18:01.0414 (UTC)
	FILETIME=[8A1CDE60:01C4BFDA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
Subject: [Sipping] Question related to netann draft
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable

Eric,

This is a resend as I am not sure original email got posted on the =
mailing list.=20

Section 4 of 'netann' draft describes how VoiceXML applications can be =
invoked by an external Application Server. It is also expected that =
results would be posted back to application server via HTTP POST =
mechanism. In true SIP and VoiceXML world this works fine. When it comes =
to legacy IN networks, you may not have a true application server. Even =
if there is some way to launch VoiceXML scripts through 'netann' model, =
posting results is tricky. Would some mid-call signaling method like SIP =
INFO to send results be violating spirit of 'netann'?=20

I am copying this to the mailing list to see if others have opinion on =
this topic.

Thanks,

-Rajiv


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 mailman-bounces@ietf.org  Mon Nov  1 05:38:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13806
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 05:38:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COZoy-0003v5-07
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 05:53:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZ9x-0000Fc-Fo
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 05:11:33 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: sipping-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.3763.1099303433.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:03:53 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

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

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

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

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for sipping-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
sipping@ietf.org                         IsgX      
https://www1.ietf.org/mailman/options/sipping/sipping-web-archive%40ietf.org


From sipping-bounces@ietf.org  Mon Nov  1 11:04:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25853
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 11:04:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COeuS-00029y-IJ
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 11:19:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COdn8-0002aZ-Va; Mon, 01 Nov 2004 10:08:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COar1-0002hW-OG
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 07:00:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21363
	for <sipping@ietf.org>; Mon, 1 Nov 2004 07:00:05 -0500 (EST)
Received: from cms1.etri.re.kr ([129.254.16.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COb5u-0005Jr-4z
	for sipping@ietf.org; Mon, 01 Nov 2004 07:15:31 -0500
Received: by cms1 with Internet Mail Service (5.5.2657.72)
	id <VRH23C4L>; Mon, 1 Nov 2004 20:59:46 +0900
Message-ID: <0957B4ABF486CF4E8494A29B85DEE51016A5AC@cms1>
From: =?euc-kr?B?sK3FwrHU?= <tgkang@etri.re.kr>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: [sipping] Intelligent Transcoding Gateway Model for Transcoding
Date: Mon, 1 Nov 2004 20:59:45 +0900 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4C00A.212F8F6C"
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 94ddbad0060c343c23e74ba9bbebbccf
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0aa23132abbc731e36938583486affe0

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_000_01C4C00A.212F8F6C
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C00A.212F8F6C"


------_=_NextPart_001_01C4C00A.212F8F6C
Content-Type: text/plain;
	charset="ks_c_5601-1987"

I would like to send you my first internet draft.
I submitted it to 'internet-drafts@ietf.org' on 14 of October, but it is
not yet posted.
So, I am sending you the file.
If you have any comment or question for it, please send email to me.

with regards Tae-Gyu Kang

	Title		: Intelligent Transcoding Gateway Model for
Transcoding with the Session Initiation Protocol 
	Author(s)	: Taegyu Kang
	Filename	: draft-taegyukang-sipping-transc-itg-00.txt 
	Pages		: 8
	Date		: 2004-10-27

This document introduces a new model, Intelligent Transcoding 
Gateway, in Framework[6] for transcoding with the Session Initiation 
Protocol. The model might be applied for more general-purpose 
services satisfying the requirements of multimedia applications 
without an additional INVITE, meanwhile the existing two models, The 
third party call control model and The conference bridge model,  
are applied for the specific application requirements in support of 
deaf, hard of hearing and speech-impaired individuals[2].

 <<draft-taegyukang-sipping-transc-itg-00.txt>> 

------_=_NextPart_001_01C4C00A.212F8F6C
Content-Type: text/html;
	charset="ks_c_5601-1987"
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=3Dks_c_5601-1987">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>[sipping] Intelligent Transcoding Gateway Model for =
Transcoding</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I would like to send you my first =
internet draft.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I submitted it to =
'internet-drafts@ietf.org' on 14 of October, but it is not yet =
posted.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">So, I am sending you the file.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">If you have any comment or question =
for it, please send email to me.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">with regards Tae-Gyu Kang</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Title&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :</FONT> <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Intelligent Transcoding Gateway Model for =
Transcoding with the Session Initiation Protocol</FONT>=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
:</FONT> <FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">Taegyu Kang</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 :</FONT> <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">draft-taegyukang-sipping-transc-itg-00.txt</FONT> =

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Pages&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 8</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"=B1=BC=B8=B2">Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2004-10-27</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">This document introduces a new =
model, Intelligent Transcoding </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">Gateway, in Framework[6] for =
transcoding with the Session Initiation </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">Protocol. The model might be =
applied for more general-purpose </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">services satisfying the =
requirements of multimedia applications </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">without an additional INVITE, =
meanwhile the existing two models, The </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">third party call control model =
and The conference bridge model,&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">are applied for the specific =
application requirements in support of </FONT>
<BR><FONT SIZE=3D2 FACE=3D"=B1=BC=B8=B2">deaf, hard of hearing and =
speech-impaired individuals[2].</FONT>
</P>

<P><FONT FACE=3D"=B1=BC=B8=B2" SIZE=3D2 COLOR=3D"#000000"> =
&lt;&lt;draft-taegyukang-sipping-transc-itg-00.txt&gt;&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C00A.212F8F6C--

------_=_NextPart_000_01C4C00A.212F8F6C
Content-Type: text/plain;
	name="draft-taegyukang-sipping-transc-itg-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-taegyukang-sipping-transc-itg-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

                             SIPPING                  November 2004=20


Internet Engineering Task Force                           Sipping WG=20
Internet Draft                                           Taegyu Kang=20
November 11, 2004                                  Doyoung Kim=20
Expires MAY 2005                                    YoungsunKim=20
                                                         ETRI=20
                                                                     =20



         Intelligent Transcoding Gateway Model for Transcoding with the =

                       Session Initiation Protocol=20
                draft-taegyukang-sipping-transc-itg-00.txt=20


Status of this Memo=20


By submitting this Internet-Draft, I certify that any applicable=20
patent or other IPR claims of which I am aware have been disclosed,=20
and any of which I become aware will be disclosed, in accordance with=20
RFC 3668.=20

Internet-Drafts are working documents of the Internet Engineering=20
Task Force (IETF), its areas, and its working groups. Note that other=20
groups may also distribute working documents as Internet-Drafts. =20
                  =20
Internet-Drafts are draft documents valid for a maximum of six months=20
and may be updated, replaced, or obsoleted by other documents at any=20
time. It is inappropriate to use Internet-Drafts as reference=20
material or to cite them other than as "work in progress."=20
                  =20
The list of current Internet-Drafts can be accessed at=20
http://www.ietf.org/1id-abstracts.txt =20
                  =20
The list of Internet-Draft Shadow Directories can be accessed at=20
http://www.ietf.org/shadow.html. =20
                  =20
This Internet-Draft will expire on April 17, 2005.=20
                  =20
Copyright Notice=20
                  =20
Copyright (C) The Internet Society (2004).  All Rights Reserved.=20
                  =20
Abstract=20
                  =20
This document introduces a new model, Intelligent Transcoding=20
Gateway, in Framework[6] for transcoding with the Session Initiation=20
Protocol. The model might be applied for more general-purpose=20
services satisfying the requirements of multimedia applications=20
               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 1]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
without an additional INVITE, meanwhile the existing two models, The=20
third party call control model and The conference bridge model, =20
are applied for the specific application requirements in support of=20
deaf, hard of hearing and speech-impaired individuals[2].=20
                  =20
                  =20











































               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 2]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
                  =20
                  =20
                  =20
                  =20
Table of Contents=20
                  =20
1. Introduction...................................................4=20
2. Background of Intelligent Transcoding Gateway Model............4=20
3. Intelligent Transcoding Gateway Model..........................4=20
4. The Comparison of Models.......................................5=20
5. Security Considerations........................................6=20
6. References.....................................................6=20
Acknowledgment....................................................7 =20
Authors' Addresses................................................7 =20
Intellectual Property Statement...................................7=20
Disclaimer of Validity and Copyright Statement....................8=20
                  =20
































               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 3]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
                  =20
                  =20
1. Introduction=20
                  =20
Simple homogeneous terminals and special purpose terminals are the=20
majority of the existing network terminals. Communication media is=20
getting more diverse in terms of the types of network terminals.=20
However, the era of new communication media types through the several=20
kinds of network terminals such as hardware IP phones(POTS style, PDA=20
style, mobile phone style), software IP phones(special purpose=20
software phone, messenger phone, ITSP phone), POTS phones, ISDN=20
phones and mobile phones is coming.=20
We believe that transcoding services are the key solution for=20
supporting these types of communication in heterogeneous networks and=20
different capability terminals.=20
The transcoding function converges wireline network, wireless network,=20
internet, and broadcasting network with a horizontal structure. We=20
can converge the networks using the Intelligent Transcoding Gateway=20
Model for transcoding with Session Initiation Protocol[1].=20
                  =20
               =20
               =20
               =20
2. Background of Intelligent Transcoding Gateway Model=20
                  =20
                  =20
The IETF sipping WG has been developing two models for transcoding=20
services: Third Party Call Control Transcoding Model[4][7] and=20
Conference Bridge Transcoding Model[5]. The Third Party Call Control=20
Transcoding Model is suitable for advanced end points that are able=20
to perform third party call control. The Conference Bridge=20
Transcoding Model is suitable for a centralized conference. These two=20
models are useful for a specific application invoked rarely to=20
support deaf, hard of hearing and speech-impaired individuals[2]. We=20
need another model that is useful for general applications[8] invoked=20
frequently. The transcoding function is needed in cases of=20
interwoking between different networks with different codecs and=20
communicating between different applications (text and speech). So,=20
the Intelligent Transcoding Gateway(ITG) Model is introduced in this=20
document.=20
                  =20
                  =20
                  =20
3. Intelligent Transcoding Gateway Model=20
                  =20
The Intelligent Transcoding Gateway Model has a transcoding function=20
in a transit node between the calling party and the called party. The=20
Intelligent Transcoding Gateway Model T receives codec information=20

               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 4]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
from A and sends additional codec information to B with SIP/SDP. We=20
assume that T has other codec that is not supported by A or B.=20
                  =20
                  =20
                  =20
+-------+             +-------+             +-------+=20
|       |<----SIP---->|       |<----SIP---->|       |=20
|   A   |             |   T   |             |   B   |=20
|   a   |----Media----|a-b,a-c|----Media----|   c   |=20
+-------+             +-------+             +-------+=20
               =20
Figure 1: Intelligent Transcoding Gateway Model=20
                  =20
We can explain cases where A supports codec a, B supports codec c,=20
and T supports transcoding function with a to b and a to c.=20
A caller party sends an INVITE message with SDP[3] codec a to T.=20
After receiving from A, T sends an INVITE message with SDP=20
A(a)+T(b+c) to called party B. After receiving of the INVITE message=20
from T, called party B responds with an OK message to T with SDP B(c).=20
T sends an OK message with SDP TA(a) to caller party A. This=20
procedure can provide to call setup and media communication between=20
the caller party with codec a and the called party with codec c.=20
                  =20
The Intelligent Transcoding Gateway Model can be used for=20
heterogeneous networks and applications. The examples of=20
heterogeneous networks are ones between PSTN and 3GPP/3GPP2, PSTN and=20
Internet Telephony, or Internet Telephony and 3GPP/3GPP2. The=20
examples of heterogeneous applications are to communicate in real=20
time between voice and text, video/voice and voice, or video/voice=20
and text.=20
                  =20
                  =20
                  =20
4. The Comparison of Models=20
                  =20
The models are compared with signaling traffic overhead. The=20
Conference bridge model and the Third party transcoding server model=20
need an additional signaling procedure for transcoding service=20
whenever they are invoked. The additional signaling procedure=20
includes an additional INVITE procedure with SIP/SDP between invoking=20
point and serving point. Conference bridge model and Third party=20
transcoding server model are useful for environments that rarely=20
occur for the transcoding service.=20
                  =20
The Intelligent Transcoding Gateway Model has an overhead of=20
additional codec information insertion at the INVITE message without=20
an additional INVITE. The overhead for codec information insertion at=20
T is less than that for an additional INVITE signaling procedure. =20
                  =20
               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 5]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
The Intelligent Transcoding Gateway Model is the best solution from=20
the point of ITSP(Internet Telephony Service Provider). In an ITSP=20
environment, all call control messages should be controlled by the=20
ITSP server, ITSP would service to terminals with all kinds of codecs.=20
ITSP's media server has a transcoding function and call control by=20
itself. This model has the advantage of no additional messages=20
between nodes and no modification for call set up standard.=20
               =20
The transcoding technology with the Intelligent Transcoding Gateway=20
Model is one of the solutions for network convergence of PSTN, mobile=20
network, internet telephony, and digital broadcasting TV.=20
                  =20
               =20
5. Security Considerations=20
                  =20
This document does not introduce any new security considerations.=20
                  =20
               =20
6. References=20
                  =20
[1] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. R. Johnston, J.=20
Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP:=20
session initiation protocol," RFC 3261, Internet Engineering=20
Task Force, June 2002.=20

[2] N. Charlton, M. Gasson, G. Gybels, M. Spanner, and A. van Wijk,=20
"User requirements for the session initiation protocol (SIP)=20
in support of deaf, hard of hearing and speech-impaired=20
individuals," RFC 3351, Internet Engineering Task Force, Aug.=20
2002.=20

[3] J. Rosenberg and H. Schulzrinne, "An offer/answer model with=20
session description protocol (SDP)," RFC 3264, Internet=20
Engineering Task Force, June 2002.=20

[4] J. Rosenberg, J. Peterson, H. Schulzrinne, and G. Camarillo,=20
"Best current practices for third party call control in the=20
session initiation protocol," RFC 3725, Internet Engineering=20
Task Force, Jan. 2004. Work in progress.=20

[5] G. Camarillo, "The session initiation protocol conference=20
bridge transcoding model," Internet Draft draft-camarillo-
sipping-transc-b2bua-00, Internet Engineering Task Force, Aug.=20
2003.  Work in progress.=20

[6] G. Camarillo, "Framework for Transcoding with the Session=20
Initiation Protocol," Internet Draft draft-ietf-transc-
framework-00.txt, Internet Engineering Task Force, Feb. 2004. =20
Work in progress.=20

[7] G. Camarillo, E. Burger, H. Schulzrinne, A. van Wijk,=20
"Transcoding Services Invocation in the Session Initiation=20
Protocol (SIP) Using Third Party Call Control (3pcc)," Sep=20
2004 Work in progress.=20

               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 6]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
[8] A. van Wijk, "Framework of requirements for real-time text=20
conversation using SIP," Internet Draft draft-vanwijk-sipping-
toip-00, Internet Engineering Task Force, Jan. 2004.  Work in=20
progress=20
                  =20
               =20
Acknowledgment=20
               =20
               =20
Author's Addresses=20
                  =20
Tae-Gyu Kang=20
ETRI=20
VoIP Service Technology Team=20
161 Kajeong Yousung Taejeon 305-350=20
South Korea=20
Electronic mail: tgkang@etri.re.kr=20
                  =20
Do-Young Kim=20
VoIP Service Technology Team=20
161 Kajeong Yousung Taejeon 305-350=20
South Korea=20
Electronic mail: dyk@etri.re.kr=20
                  =20
Young-Sun Kim=20
Broadband convergence Network Service Research Group=20
161 Kajeong Yousung Taejeon 305-350=20
South Korea=20
Electronic mail: sunkim@etri.re.kr=20
                  =20
                  =20
               =20
               =20
Intellectual Property Statement=20
                  =20
The IETF takes no position regarding the validity or scope of any=20
Intellectual Property Rights or other rights that might be claimed to=20
pertain to the implementation or use of the technology described in=20
this document or the extent to which any license under such rights=20
might or might not be available; nor does it represent that it has=20
made any independent effort to identify any such rights.  Information=20
on the procedures with respect to rights in RFC documents can be=20
found in BCP 78 and BCP 79.=20
                  =20
Copies of IPR disclosures made to the IETF Secretariat and any=20
assurances of licenses to be made available, or the result of an=20
attempt made to obtain a general license or permission for the use of=20
such proprietary rights by implementers or users of this=20

               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 7]=20
=0C                                    SIPPING                  =
November 2004=20
               =20
               =20
specification can be obtained from the IETF on-line IPR repository at=20
http://www.ietf.org/ipr.=20
                  =20
The IETF invites any interested party to bring to its attention any=20
copyrights, patents or patent applications, or other proprietary=20
rights that may cover technology that may be required to implement=20
this standard.  Please address the information to the IETF at ietf-
ipr@ietf.org.=20
                  =20
                  =20
Disclaimer of Validity=20
                  =20
This document and the information contained herein are provided on an=20
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS=20
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET=20
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,=20
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE=20
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED=20
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=20
                  =20
                  =20
Copyright Statement=20
                  =20
Copyright (C) The Internet Society (2004).  This document is subject=20
to the rights, licenses and restrictions contained in BCP 78, and=20
except as set forth therein, the authors retain all their rights.=20
                  =20
                  =20





















               =20
               =20
Taegyu Kang               Expires - May 2005                  [Page 8]=20
=0C

------_=_NextPart_000_01C4C00A.212F8F6C
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
------_=_NextPart_000_01C4C00A.212F8F6C--



From sipping-bounces@ietf.org  Mon Nov  1 11:23:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28206
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 11:23:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COfCa-0002sR-8i
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 11:38:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COePQ-0006ap-RW; Mon, 01 Nov 2004 10:47:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COcjL-0005DL-Er
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 09:00:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04148
	for <sipping@ietf.org>; Mon, 1 Nov 2004 09:00:16 -0500 (EST)
Received: from dirty.research.bell-labs.com ([204.178.16.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COcyF-0007ii-2o
	for sipping@ietf.org; Mon, 01 Nov 2004 09:15:44 -0500
Received: from scummy.research.bell-labs.com
	(H-135-104-2-10.research.bell-labs.com [135.104.2.10])
	by dirty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	iA1E08XJ065141; Mon, 1 Nov 2004 09:00:08 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by scummy.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA1E02U1025172; Mon, 1 Nov 2004 09:00:02 -0500 (EST)
Received: from [135.180.240.186] (volker-hopc [135.180.240.186])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA1E029n028214; Mon, 1 Nov 2004 09:00:02 -0500 (EST)
Message-ID: <4186408D.7040603@bell-labs.com>
Date: Mon, 01 Nov 2004 08:56:29 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, 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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Sipping] Updated session-specific policy draft
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

All,

we have submitted a new version of the session-specific policy draft.

This draft has been almost completely rewritten and is now based on the 
separate channel model. It defines the overall architecture and the 
mechanism for conveying policy channel URIs to the UAs. The main open 
issue is the protocol on the policy channel.

http://www.ietf.org/internet-drafts/draft-hilt-sipping-session-spec-policy-01.txt

Thanks,

Volker


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  1 12:07:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04276
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 12:07:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COft0-0004Sw-28
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 12:22:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COfM5-0008Ru-E2; Mon, 01 Nov 2004 11:48:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COexG-000267-6D
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 11:22:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28123
	for <sipping@ietf.org>; Mon, 1 Nov 2004 11:22:48 -0500 (EST)
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COfCB-0002qt-Ni
	for sipping@ietf.org; Mon, 01 Nov 2004 11:38:16 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA1GMT322406; Mon, 1 Nov 2004 18:22:29 +0200 (EET)
X-Scanned: Mon, 1 Nov 2004 18:22:42 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iA1GMgl4004040;
	Mon, 1 Nov 2004 18:22:42 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00kN902V; Mon, 01 Nov 2004 18:22:41 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA1GMJa09501; Mon, 1 Nov 2004 18:22:19 +0200 (EET)
Received: from [172.21.37.239] ([172.21.37.239]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 1 Nov 2004 18:22:16 +0200
Message-ID: <418662B7.6080301@nokia.com>
Date: Mon, 01 Nov 2004 18:22:15 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>,
        "Orit Levin" <oritl@microsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Nov 2004 16:22:16.0784 (UTC)
	FILETIME=[F3FF4D00:01C4C02E]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 89ebdf268eceaeaf784b3acb625dc20e
Content-Transfer-Encoding: 7bit
Cc: SIPPING mailing list <sipping@ietf.org>
Subject: [Sipping] WGLC: conference-package-06
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3dc828214e948ff35b815af10e94a823
Content-Transfer-Encoding: 7bit

Hi:

I have some questions and comments to 
draft-ietf-sipping-conference-package-06.txt


- General: I noticed that the I-D describes the elements of the 
Conference Info XML document by describing the XML schema, not a real 
XML document. For instance, the I-D describes in section 6.1.1 the 
"Conference-Type", which is a type definition in XML schema, not a real 
element. This is a general comment that applies to the whole document. 
My comment is that the textual description should not describe the bits 
and bytes of the XML schema, but the actual contents of a real 
Conference Info XML document. In short, there shouldn't be any mention 
to "types" in Section 6.

- General: - The document speaks quite a bit about "element with keys". 
It is not clear to me, after trying to understand it a few times, what a 
key is, and how a key is identified. So I guess you should a bit more 
effort in defining keys, and describing their identification.

- General: There are quite a few inconsistencies between the text and 
the XML schema definition (I actually predicted this will happen sooner 
or later). For instance, the following attributes are defined as 
"mandatory" in the text, but they are "optional" in the XML schema:

     version, state (in various subelements), entity

My suggestion is to remove the "mandatory" or "optional" from the text, 
and make sure that things are right in the schema.

- General: There are several instances of a <display-text> element 
(e.g., Sections 6.1.2.1, 6.1.3.1, 6.1.5.1, 6.1.6.1, 6.1.7.1)

While I understand that it makes sense to have some display-text 
information for the conference, the host, or the user, I wonder how this 
can be of benefit for the endpoint or the media type. Further more, how 
can someone set this display type for the endpoint or the media type, or 
how can the conference focus determine it.

- Section 4: After the first paragraph, the URN is missing. Add:

     urn:ietf:params:xml:ns:conference-info

- XML schema: since the 'state' attribute has a default value of "full", 
this should be indicated in the schema. You can do so by replacing all 
the 'state' attribute declarations with the following one, which 
includes the default value:

        <xs:attribute name="state" type="state-type"
                      use="optional" default="full" />

- Section 5, 4th paragraph says:

    If it contains "deleted" state,
    indicated by the value of the "state" attribute in the
    "conference-info" element, it means that the conference ceased to
    exist and the subscriber SHOULD terminate the SUBSCRIBE dialog.

The sentence "the subscriber SHOULD terminate the SUBSCRIBE dialog", 
does it mean the user SHOULD send a SUBSCRIBE with Expires=0 or does it 
mean the user SHOULD consider implicitly the subscription dead? I 
suggest the former, but I would like to explicitly say that the UA 
SHOULD send a SUBSCRIBE with Expires=0 to avoid misunderstandings.
I also think that the misunderstanding is due to "terminate the 
SUBSCRIBE dialog", I guess it should refer to the subscription rather 
than the dialog.

- Section 6.1.1 reads:

    version: This mandatory attribute allows the recipient of conference
       information documents to properly order them.  Versions start at 0
       and increment by one for each new document sent to a subscriber.
       Versions are scoped within a subscription.  Versions MUST be
       represented using a 32 bit integer.

But the XML schema just indicates it is a string:

      <xs:attribute name="version" type="xs:string" use="optional"/>

My suggestion is indicate the valid range (0 to 2^32-1) through the 
schema, something like:

      <xs:attribute name="version" type="version-type" use="required"/>

      <!--
      VERSION TYPE
      -->
      <xs:simpleType name="version-type">
              <xs:restriction base="xs:nonNegativeInteger">
              		<xs:maxInclusive value="4294967295" />
            	</xs:restriction>
      </xs:simpleType>


- Section 6.1.2.4 <keywords> says:

    This element contains a list of keywords which describe the
    conference *topic*.

I disagree. The topic is indicated in the <subject> element. I think you 
want to say that the <keywords> element contains a set of words that can 
be used by automatic search engines to better index the conference.

- Section 6.1.2.6 <conf-uris> says

    This element contains information about additional conference URIs
    that this conference can be accessed by.

This is not correct, the <conf-uris> elements contains one or more 
<entry> elements, each one describing additional info about the 
conference. And that makes me think that the name <conf-uris> is not 
right either, since the URI is hidden in the <entry><uri> element.

This comment is also applicable to <service-uris> (6.1.2.7)

- Section 6.1.2.8 <maximum-user-count> says:

    This element contains a count of the maximum number of users
    permitted in the conference.

Well, the element actually contains one or more <entry> elements, rather 
than a maximum number of users permitted in the conference. The 
definition in the schema is:

     <xs:element name="maximum-user-count"
              type="user-count-type" minOccurs="0"/>

I guess this element should have a nonNegativeInteger type rather than 
user-count-type.

- Section 6.1.3.3 <uris> says

    The "entity" sub-element contains additional URIs relating to the
    user hosting the conference.

Obviously this is not the <entity> subelements, but the <uris> 
sub-element. Also, it can contain one or more <entry> elements, each of 
them contains additional URIs ...

- Section 6.1.4.2  <security-level> says:

    This element contains information about the conference security
    level.  The values can be "none", "low", "medium", or "high".

I don't understand how to map each of these values to something else. So 
what is the "conference security level", where is it described, and how 
can my application determine if the security level is any of the 
mentioned above. In short, I am missing some semantics for this element, 
and some guidance as for how can the focus determine the conference 
security level.

- Section 6.1.5.4 <language> says:

   This element contains the language used by the user.

Does this mean the conference is able to recognize the language I am 
using? I guess not, so perhaps the text should read "This element 
contains the preferred language used by the SIP application. The focus 
can determine its contents from the Accept-Contact header field in SIP".

- Section 6.1.6.7. The title of this section reads:

    disconnection-info of disconnection-type

Although there is not a disconnection-type, but an execution type. 
Nevertheless, I hope this comment becomes not applicable, after my other 
comment indicating that there shouldn't be any "type" mentioned in 
Section 6.

- Section 6.1.6.8 <whispering-to> says:

    If an endpoint is participating in a whisper session with other
    entities, the URIs of these other entities MAY be contained in this
    element.

Absolutely a leak of privacy. If I am whispering to someone might be 
because I don't want the rest of the conference be aware that I am 
having a side-by conversation with someone else. This is the main 
difference between whispering and sidebars.

If there were some mechanism where I could differentiate a "public 
whisper" from an "invisible whisper", I wouldn't mind to have this 
element indicating to who I am whispering. Unfortunately I am not aware 
of such mechanism, so I suggest to delete this element to avoid leaking 
privacy information.

- Section 6.1.7 <media>, speaking about the 'entity' attribute says:

       The value of this element
       SHOULD correspond to the "mid" value in the SDP document as
       defined in Grouping of Media Lines in the SDP [9].

I don't agree with this. So does it mean I cannot join a conference if 
my SIP UA does not support the "mid" attribute? I guess there should be 
some guidelines as for what to do with this attribute if the UA supports 
basic SDP as per RFC 2327.

- Sections 6.1.7.5, 6.1.7.6, 6.1.7.7 and 6.1.7.8

I don't see the need for so many elements. I guess these properties can 
be expressed with just a single element, namely <direction>. This new 
<direction> element can take the values "sendrecv", "sendonly", 
"recvonly", "inactive", and can be mapped from the corresponding SDP 
attributes. Note that I didn't forget the "muted" element, since there 
are no semantics for it, and I don't understand what it means, and I 
believe it is not required.

So please take my consideration into account and arrange these sections 
into one element.

- Section 6.1.7.8 <call>

I don't understand why <call> is of type call-type, and call-type is of 
type dialog-id. I guess <call> should be of type dialog-id. I don't see 
the benefit in so many type indirection.

Also this describes the <call-id>, <to-tag> and <from-tag> subelements. 
You should be associating semantics to the Call-ID header in SIP, the 
tag in the To and From header fields. Such semantics are not assigned in 
the current draft.

- Section 7. XML extensibility. I noticed that you have invented a new 
mechanism to extend an XML schema. It seems that the extensibility is 
provided by an undefined <extended> element. I said undefined because I 
didn't find its description in Section 6. This element may include any 
collection of elements from other namespaces. where the required 
attribute 'namespace' seems to indicate the namespace.

However XML schema already contains a widely used mechanism to allow 
extensibility. To define an extension for an element from other 
namespace, you can add:

<xs:any namespace="##other" processContents="lax" minOccurs="0" 
maxOccurs="unbounded"/>

To define an attribute from another namespace, you can add:

<xs:anyAttribute namespace="##other"/>

The result is the same you are trying to achieve, but the one I am 
proposing is commonly used in XML schemas, and I think we should be 
using the same instead of your invented mechanism.

So can you use the standard extensibility mechanism?

- Section 7, XML schema, <conference-info>

The XML schema indicates that all the child elements of 
<conference-info> are optional. This means that the following document 
is valid:

<?xml version="1.0" encoding="UTF-8"?>
<conference-info xmlns="urn:ietf:params:xml:ns:conference-info" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="urn:ietf:params:xml:ns:conference-info" 
entity="http://www.altova.com" state="full" version="0"/>

And this is a bit weird. I guess there should be something more in 
conference info. As a minimum, the conference has been instantiated, so 
I guess the conference-description and conference state should always be 
present.

- Section 7, XML schema, 'entity' attribute

I noticed that the 'entity' attribute is used by quite a few elements. 
In some cases, the 'entity' attribute can accommodate a URI whereas 
others can accommodate a string. While this is legal, it is really ugly. 
If you browse through the schema, you can see the following two definitions:

     <xs:attribute name="entity" type="xs:anyURI" use="required"/>

     <xs:attribute name="entity" type="xs:string" use="required"/>

I would recommend that you rename the 'entity' that can take a string 
with something else.

- Section 7, XML schema, <label> attribute

The definition of <label> in the schema is:

  <xs:element name="label" type="xs:string" minOccurs="0"/>

However, it is the intention to use this label as a key to discover the 
URI of further services, such as the CPCP URI, and perhaps something 
else. However, the <label> element does not contain a list of possible 
services one can think of, so it is not possible that a SIP UA uses that 
information to, e.g., upload a CPCP document. The problem is that the 
string is not standardized.

I don't know what people think about this, but I believe we either 
standardize a few enumerated values, and provide extensibility, or then 
this <label> attribute looks quite useless.

- Section 13. I think references 12 (RFC 2327) and 19 
(draft-ietf-mmusic-sdp-media-label) can't be informative, since there 
are strong dependencies on those. Further more, RFC 2327 is under 
(eternal) revision, draft-ietf-mmusic-sdp-new-12312.txt or something 
similar. Since there is a dependency on the inactive attribute 
introduced by this new SDP version, we should refer to it, but it would 
be good to find out the status of SDP new and learn if it is going to 
proceed to RFC before the end of the century.




Nits:

- General: I would appreciate if we can refer to elements by enclosing 
the element in brackets rather than quotes. So far, all the document 
refers to elements such as "conference-info" rather than 
<conference-info>. We should refer to attributes by inserting them in 
single quotes, e.g., the 'entity' attribute. Enumerated values should be 
quoted, e.g., the value can be "active" and "inactive".


- Section 4, first paragraph. Include references to "XML document" and 
UTF-8.

    Conference information is an XML document [x]that MUST be well-formed
    and SHOULD be valid.  Dialog information documents MUST be based on
    XML 1.0 and MUST be encoded using UTF-8 [y]. This specification makes

    [x]   Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
          "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C
          REC-xml-20001006, October 2000.

    [y]   Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD
          63, RFC 3629, November 2003.

- Section 4, 5th paragraph. For better readability, I would suggest to 
replace the current paragraph:

    For elements with the optional "state" attribute, if the attribute is
    omitted from the notification for the element, it means that the
    reported element's state is "full".

with this other one:

    Elements can be characterized with an optional 'state' attribute 
that indicates whether a "full", "partial" or "deleted" state is 
indicated. The absence of a 'state' attribute has the same semantics as 
"full".

- Section 5 reads in bullet point 3.1.1: "If a key does not exist in the 
local table, a row is added, and its content is set to the element 
information from the update."
I think it is weird that an element can safely be deleted just because 
it does not provide any content. Imagine an element that can either be 
present or not, hypothetical example, <is-focus/>. I don't think it is 
safe to locally remove those elements.

- Section 6: remove the urn:ietf:params:xml:ns:conference-info
URN from this section.

- Section 6.1.7.3. The last sentence is, for some reason, quoted. 
Action: remove the quotes.

- Section 6.1.7.4., <label>. Replace the sentence:

    The
    value of this element corresponds to the "label" media attribute in
    SDP [12] and defined in [19].

with

    The
    value of this element corresponds to the "label" media attribute in
    [19].

- Section 7. Title. s/Schema/XML Schema

- Section 13, reference 1 is now RFC 3688



Best regards,

     Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  1 14:09:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18688
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 14:09:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COhnD-0008WV-U4
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 14:24:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COhAg-00016o-NT; Mon, 01 Nov 2004 13:44:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COgqc-00088C-ME
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 13:24:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14922
	for <sipping@ietf.org>; Mon, 1 Nov 2004 13:24:04 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COh5Y-0007Rf-2K
	for sipping@ietf.org; Mon, 01 Nov 2004 13:39:33 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 01 Nov 2004 10:33:38 -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.10/8.12.6) with ESMTP id iA1INUcp009101;
	Mon, 1 Nov 2004 10:23:31 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATP89859;
	Mon, 1 Nov 2004 10:23:29 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Mon, 01 Nov 2004 10:23:28 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        Rohan Mahy <rohan@ekabal.com>
Message-ID: <BDABBF20.17E4E%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Things on agenda that don't seem to have made it to the ID
 directory yet 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable



 0905 Real-time Text over IP
 =A0=A0=A0=A0=A0=A0=A0=A0=A0 Arnoud van Wijk
 =A0=A0=A0=A0=A0=A0=A0=A0=A0 draft-ietf-sipping-ToIP-00.txt

and=20

 1025 Direct Transcoding
 =A0=A0=A0=A0=A0=A0=A0=A0=A0 Kang
 =A0=A0=A0=A0=A0=A0=A0=A0=A0 draft-taegyukang-sipping-transc-itg-00.txt



does not seem to be in the ID directory yet



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  1 14:43:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21747
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 14:43:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COiKT-0000ua-GH
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 14:59:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COhnH-0003Bp-3b; Mon, 01 Nov 2004 14:24:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COhay-00042K-5k
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 14:12:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18986
	for <sipping@ietf.org>; Mon, 1 Nov 2004 14:11:57 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COhpu-0000BH-Jq
	for sipping@ietf.org; Mon, 01 Nov 2004 14:27:28 -0500
Received: from [206.176.144.210] (206-176-144-210.waymark.net
	[206.176.144.210] (may be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.12.11/8.12.11) with ESMTP id iA1JC8U0027036
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 1 Nov 2004 13:12:08 -0600
Message-ID: <41868A60.7020707@softarmor.com>
Date: Mon, 01 Nov 2004 13:11:28 -0600
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <BDABBF20.17E4E%fluffy@cisco.com>
In-Reply-To: <BDABBF20.17E4E%fluffy@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, sipping <sipping@ietf.org>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Subject: [Sipping] Re: Things on agenda that don't seem to have made it to
 the ID directory yet
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

Cullen Jennings wrote:
> 
>  0905 Real-time Text over IP
>            Arnoud van Wijk
>            draft-ietf-sipping-ToIP-00.txt
> 
> and 

Caps error above. Correct link is:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-toip-00.txt


>  1025 Direct Transcoding
>            Kang
>            draft-taegyukang-sipping-transc-itg-00.txt
> 
> 
> 
> does not seem to be in the ID directory yet
> 
> 
> 

We don't know what happened here. The draft was submitted to ID on 
November 14.

It is available on the softarmor site:

http://www.softarmor.com/wgdb/docs/draft-taegyukang-sipping-transc-itg-00.txt


I have corrected the links on the posted agenda.

Please note, this agenda is subject to change, and I expect some minor 
changes.

--
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 sipping-bounces@ietf.org  Mon Nov  1 17:39:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14856
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 17:39:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COl56-00071x-0l
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 17:55:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COkhF-0003Tr-DU; Mon, 01 Nov 2004 17:30:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COkI4-0005SG-Av
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 17:04:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10058
	for <sipping@ietf.org>; Mon, 1 Nov 2004 17:04:38 -0500 (EST)
Received: from web53405.mail.yahoo.com ([206.190.37.52])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COkWs-0005a5-WD
	for sipping@ietf.org; Mon, 01 Nov 2004 17:20:09 -0500
Message-ID: <20041101220358.40981.qmail@web53405.mail.yahoo.com>
Received: from [65.220.123.2] by web53405.mail.yahoo.com via HTTP;
	Mon, 01 Nov 2004 14:03:58 PST
X-RocketYMMF: dgpetrie
Date: Mon, 1 Nov 2004 14:03:58 -0800 (PST)
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Subject: RE: [Sipping] Config framework - issue with parameters send in Event
	header
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>,
        Paul Kyzivat <pkyzivat@cisco.com>,
        "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D025EBC4@EXC01C.cselt.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id RAA10058
Cc: "Daniel G. Petrie" <dpetrie@pingtel.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpetrie@pingtel.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Content-Transfer-Encoding: quoted-printable

An earlier version of the config framework actually
proposed using the User-Agent header.  However the
User-Agent header is currently too syntactically
unconstrained to make the needed parameters parsable.
There were lots of groans from the audiance when this
was discussed and suggested that we should better
parameterize the Use-Agent header.

--- Simonetti Gabrielle
<Gabrielle.Simonetti@TILAB.COM> wrote:

> Providing the parameters in the body of the
> SUBSCRIBE is a good idea but would increase the load
> on the network, as well as require the definition of
> a new data schema for the SUBSCRIBE body. Why not
> use the User-Agent Header defined in RFC3261 to
> transport the information about the UA originating
> the request? It can contain several components
> together with their version number (e.g. the Nokia
> traditional User-Agent string used for HTTP:
> Nokia6600/ 1.0 (4.03.24) SymbianOS/ 6.1 Series60/
> 2.0 Profile/ MIDP- 2.0 Configuration/ CLDC- 1.0). In
> this case, the order in which the information is set
> in the header is not specified, however the
> constructor would know how the UA forms the header
> and thus understand the subscribe request for the
> device profile. This header would have to be
> mandatory in the profile delivery requests.
> Gabrielle
>=20
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org
> [mailto:sipping-bounces@ietf.org]On
> > Behalf Of Paul Kyzivat
> > Sent: marted=EC 26 ottobre 2004 0.41
> > To: Elwell, John
> > Cc: 'Daniel G. Petrie'; 'sipping@ietf.org'
> > Subject: Re: [Sipping] RE: Config framework -
> issue with=20
> > parameters send
> > inEvent header
> >=20
> >=20
> > Did anyone consider providing these parameters as
> a body in the=20
> > SUBSCRIBE? (Something like a "filter" in a warped
> sort of way.)
> >=20
> > 	Paul
> >=20
> > Elwell, John wrote:
> > > Dan,
> > >=20
> > > In-line [JRE]
> > >=20
> > > John (john.elwell@siemens.com)=20
> > >=20
> > > -----Original Message-----
> > > From: Daniel G. Petrie
> [mailto:dpetrie@pingtel.com]=20
> > > Sent: 22 October 2004 22:52
> > > To: Elwell, John
> > > Cc: 'sipping@ietf.org'
> > > Subject: Re: Config framework - issue with
> parameters send=20
> > in Event header
> > >=20
> > > Thanks for the comments.  I would like to hear
> opinions from
> > > folks on the list on whether they think this is
> a current
> > > requirement or not.
> > >=20
> > > Thanks,
> > > Dan
> > >=20
> > > "Elwell, John" wrote:
> > >=20
> > >>Dan,
> > >>
> > >>In reviewing the
> draft-ietf-sipping-config-framework-04, I=20
> > noticed that
> > >>several parameters had been defined for the
> Event header giving
> > >=20
> > > information
> > >=20
> > >>about the device, i.e., "vendor", "model" and
> "version". I=20
> > am concerned
> > >=20
> > > that
> > >=20
> > >>these may not be sufficient in all cases for the
> profile=20
> > delivery server
> > >=20
> > > to
> > >=20
> > >>determine the precise profile to be delivered.
> Moreover, the profile
> > >>delivery server may use these parameters to
> compile an inventory of
> > >=20
> > > devices
> > >=20
> > >>for admin purposes, and more detailed
> information might be=20
> > needed for this
> > >>purpose, even if it does not influence the
> choice of profile to be
> > >>delivered. Examples of extended information that
> might be considered
> > >=20
> > > useful
> > >=20
> > >>for the profile delivery server are:
> > >>
> > >>- where a particular UA model has different
> components,=20
> > each with its own
> > >>version number (e.g., hardware version and
> software version);
> > >>- where a particular UA model has some optional
> extras,=20
> > these may need to
> > >=20
> > > be
> > >=20
> > >>listed together with their respective version
> numbers.
> > >>
> > >=20
> > >=20
> > > I did not see any comments on this on the list.=20
> Are there=20
> > any opinions
> > > out there?  I see no technical reasons against
> adding a components
> > > parameter.  Components values can be a vendor
> scoped token. If there
> > > is more than one component that the user agent
> wants to specify it
> > > could add more than one "component" parameter
> each have a value of
> > > a token.
> > >=20
> > > My main reservation is the case for simplicity.=20
> It is very easy to
> > > add parameters in the future if we really need
> them.  Please speak
> > > up if you think there is a case for defining
> this now.
> > >=20
> > >=20
> > >>Has any consideration been given to providing an
> extensible=20
> > mechanism for
> > >>delivering UA information in a SUBSCRIBE request
> to a=20
> > profile delivery
> > >>server?
> > >>
> > >=20
> > >=20
> > > Doesn't the Event header parameters construct
> provide this?=20
> >  Do we need
> > > something more specific to profile delivery?
> > > [JRE] I guess I am confused about the mechanism
> for adding=20
> > new Event header
> > > parameters. Looking at RFC3265, there does not
> appear to be any IANA
> > > registry for Event header parameters. Perhaps
> this is=20
> > intentional - perhaps
> > > parameters are intended to be interpreted within
> the context of the
> > > particular event package concerned.
> > > Looking at the config framework, I don't see
> anything there=20
> > to register the
> > > new parameters (vendor, model, etc.) - sorry I
> failed to=20
> > pick that up during
> > > my review. However, even if the config framework
> were to=20
> > register these
> > > parameters with IANA, it might require an update
> to the=20
> > config framework in
> > > future to add new parameters unless, in creating
> the=20
> > registry, it allowed
> > > other means to add new parameters. What I had in
> mind was=20
> > the ability for a
> > > particular vendor to add further parameters
> according to=20
> > his needs. These
> > > might be meaningful to a server from the same
> vendor or=20
> > would be silently
> > > discarded if not recognised. So if there is not
> sufficient=20
> > interest in the
> > > community for the "component" parameter, at
> least a=20
> > particular vendor could
>=20
=3D=3D=3D message truncated =3D=3D=3D


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  1 18:02:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16820
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 18:02:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COlRG-0007ay-6g
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 18:18:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COkj8-0005Nj-TN; Mon, 01 Nov 2004 17:32:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COkU0-0004fO-3y
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 17:17:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11872
	for <sipping@ietf.org>; Mon, 1 Nov 2004 17:16:58 -0500 (EST)
Received: from web53404.mail.yahoo.com ([206.190.37.51])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COkiz-00066Y-4X
	for sipping@ietf.org; Mon, 01 Nov 2004 17:32:29 -0500
Message-ID: <20041101221624.86656.qmail@web53404.mail.yahoo.com>
Received: from [65.220.123.2] by web53404.mail.yahoo.com via HTTP;
	Mon, 01 Nov 2004 14:16:24 PST
X-RocketYMMF: dgpetrie
Date: Mon, 1 Nov 2004 14:16:24 -0800 (PST)
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Subject: RE: [Sipping] Comments on config framework draft- URIs and event
	package parameters
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>,
        "Daniel G. Petrie" <dpetrie@pingtel.com>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D025EBC3@EXC01C.cselt.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id RAA11872
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpetrie@pingtel.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: quoted-printable

Comments below:

Cheers,
Dan

--- Simonetti Gabrielle
<Gabrielle.Simonetti@TILAB.COM> wrote:

> Dan,
> inline.
>=20
> > -----Original Message-----
> > From: Daniel G. Petrie
> [mailto:dpetrie@pingtel.com]
> > Sent: venerd=EC 22 ottobre 2004 21.28
> > To: Simonetti Gabrielle
> > Cc: hisham.khartabil@nokia.com; sipping@ietf.org
> > Subject: Re: [Sipping] Comments on config
> framework draft- URIs and
> > eventpackage parameters
> >=20
> > Simonetti Gabrielle wrote:
> > >=20
> > > > Section 3.13.1
> > > > --------------
> > > >
> > > > - What if instance does not matter? Example
> all Nokia phone
> > > > 6600 model require the same profile, instance
> does not
> > > > matter. Vendor and model is the only thing
> needed to download
> > > > a profile. There is no need for the service
> provider to have
> > > > separate profiles for every device, especially
> will they are
> > > > identical.
> > >=20
> > > I agree that the instance-id might not matter in
> the case=20
> > of the "device" profile. In fact using the
> instance-id=20
> > creates unnecessary subscription targets, as these
> can be=20
> > grouped by "model", for example, as you say.
> > > 1/What do you suggest for the format of the
> subscription=20
> > URI then, leaving out the instance-id?
> > > 2/The question has already been raised whether
> "vendor",=20
> > "model" and "version" are sufficient to identify
> the precise=20
> > profile to be delivered, e.g. in the case where a
> particular=20
> > UA model has different components, each with its
> own version=20
> > number. A possible solution would be to define a
> new=20
> > parameter "component" for the Event Header to
> identify the=20
> > component for which the subscription is made.
> >=20
> > The instance-id does matter in the device profile
> when you=20
> > consider the
> > boot strapping of a new user agent.  Out of the
> box a new UA=20
> > only knows=20
> > its instance-id (or how to generate one).   It
> also knows how=20
> > to use its
> > instance-id to form the URI to subscribe for the
> device profile.  The
> > device profile needs to contain the default user
> AOR so that the UA
> > can subsequently figure out what user profile to
> subscribe to.  Hense,
> > minimally all device profiles may differ by the
> value of the default
> > user AOR.
> >=20
>=20
> Let's consider the case where the device profiles
> are delivered by a server within the constructor
> (that manages the UA versions): the constructor
> might not be aware of the identity of the users
> using the devices. On the contrary, the service
> provider is the one holding the user profiles, and
> could thus keep an association between instance IDs
> and default AORs. In addition, in some cases, the
> access provider coincides with the service
> provider... Have you considered including the
> default AOR in the local profile together with the
> other SIP parameters rather than in the device
> profile?=20
>=20

The Network-User Event header parameter MAY be set to
the AOR of the user.  In section 3.2 which talks about
the specifics of the Network-User parameter is states
that this parameter MAY be set for "device" or "local"
profile types.  Does this cover the use case you had
in mind?



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  1 18:04:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17041
	for <sipping-web-archive@ietf.org>; Mon, 1 Nov 2004 18:04:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COlSa-0007eL-0p
	for sipping-web-archive@ietf.org; Mon, 01 Nov 2004 18:19:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COkmx-0000AH-VY; Mon, 01 Nov 2004 17:36:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COkgD-00020D-EM
	for sipping@megatron.ietf.org; Mon, 01 Nov 2004 17:29:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13738
	for <sipping@ietf.org>; Mon, 1 Nov 2004 17:29:35 -0500 (EST)
Received: from web53406.mail.yahoo.com ([206.190.37.53])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COkvC-0006iK-Kt
	for sipping@ietf.org; Mon, 01 Nov 2004 17:45:07 -0500
Message-ID: <20041101222906.27689.qmail@web53406.mail.yahoo.com>
Received: from [65.220.123.2] by web53406.mail.yahoo.com via HTTP;
	Mon, 01 Nov 2004 14:29:06 PST
X-RocketYMMF: dgpetrie
Date: Mon, 1 Nov 2004 14:29:06 -0800 (PST)
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Subject: RE: [Sipping] Comments on config framework draft- URIs and event
	package parameters
To: dpetrie@pingtel.com, Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
In-Reply-To: <20041101221624.86656.qmail@web53404.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id RAA13738
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpetrie@pingtel.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable

Sorry, I just realized that the latest draft has
not made it through the works to be announced yet.

In the mean time the updated draft can be downloaded
from:

html:
http://scm.sipfoundry.org/viewsvn/*checkout*/ietf-drafts/sipping/config-f=
ramework/config-framework.html?rev=3D235

txt:
http://scm.sipfoundry.org/viewsvn/*checkout*/ietf-drafts/sipping/config-f=
ramework/config-framework.txt?rev=3D235


--- "Daniel G. Petrie" <dpetrie@pingtel.com> wrote:

> Comments below:
>=20
> Cheers,
> Dan
>=20
> --- Simonetti Gabrielle
> <Gabrielle.Simonetti@TILAB.COM> wrote:
>=20
> > Dan,
> > inline.
> >=20
> > > -----Original Message-----
> > > From: Daniel G. Petrie
> > [mailto:dpetrie@pingtel.com]
> > > Sent: venerd=EC 22 ottobre 2004 21.28
> > > To: Simonetti Gabrielle
> > > Cc: hisham.khartabil@nokia.com; sipping@ietf.org
> > > Subject: Re: [Sipping] Comments on config
> > framework draft- URIs and
> > > eventpackage parameters
> > >=20
> > > Simonetti Gabrielle wrote:
> > > >=20
> > > > > Section 3.13.1
> > > > > --------------
> > > > >
> > > > > - What if instance does not matter? Example
> > all Nokia phone
> > > > > 6600 model require the same profile,
> instance
> > does not
> > > > > matter. Vendor and model is the only thing
> > needed to download
> > > > > a profile. There is no need for the service
> > provider to have
> > > > > separate profiles for every device,
> especially
> > will they are
> > > > > identical.
> > > >=20
> > > > I agree that the instance-id might not matter
> in
> > the case=20
> > > of the "device" profile. In fact using the
> > instance-id=20
> > > creates unnecessary subscription targets, as
> these
> > can be=20
> > > grouped by "model", for example, as you say.
> > > > 1/What do you suggest for the format of the
> > subscription=20
> > > URI then, leaving out the instance-id?
> > > > 2/The question has already been raised whether
> > "vendor",=20
> > > "model" and "version" are sufficient to identify
> > the precise=20
> > > profile to be delivered, e.g. in the case where
> a
> > particular=20
> > > UA model has different components, each with its
> > own version=20
> > > number. A possible solution would be to define a
> > new=20
> > > parameter "component" for the Event Header to
> > identify the=20
> > > component for which the subscription is made.
> > >=20
> > > The instance-id does matter in the device
> profile
> > when you=20
> > > consider the
> > > boot strapping of a new user agent.  Out of the
> > box a new UA=20
> > > only knows=20
> > > its instance-id (or how to generate one).   It
> > also knows how=20
> > > to use its
> > > instance-id to form the URI to subscribe for the
> > device profile.  The
> > > device profile needs to contain the default user
> > AOR so that the UA
> > > can subsequently figure out what user profile to
> > subscribe to.  Hense,
> > > minimally all device profiles may differ by the
> > value of the default
> > > user AOR.
> > >=20
> >=20
> > Let's consider the case where the device profiles
> > are delivered by a server within the constructor
> > (that manages the UA versions): the constructor
> > might not be aware of the identity of the users
> > using the devices. On the contrary, the service
> > provider is the one holding the user profiles, and
> > could thus keep an association between instance
> IDs
> > and default AORs. In addition, in some cases, the
> > access provider coincides with the service
> > provider... Have you considered including the
> > default AOR in the local profile together with the
> > other SIP parameters rather than in the device
> > profile?=20
> >=20
>=20
> The Network-User Event header parameter MAY be set
> to
> the AOR of the user.  In section 3.2 which talks
> about
> the specifics of the Network-User parameter is
> states
> that this parameter MAY be set for "device" or
> "local"
> profile types.  Does this cover the use case you had
> in mind?
>=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 sipping-bounces@ietf.org  Tue Nov  2 05:38:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04801
	for <sipping-web-archive@ietf.org>; Tue, 2 Nov 2004 05:38:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COwIR-00061k-1M
	for sipping-web-archive@ietf.org; Tue, 02 Nov 2004 05:53:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COvvg-0006AF-Ak; Tue, 02 Nov 2004 05:30:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COvk6-0000il-Ht
	for sipping@megatron.ietf.org; Tue, 02 Nov 2004 05:18:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03551
	for <sipping@ietf.org>; Tue, 2 Nov 2004 05:18:20 -0500 (EST)
From: hisham.khartabil@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COvzB-0005f3-Uv
	for sipping@ietf.org; Tue, 02 Nov 2004 05:33:58 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA2AIE307961; Tue, 2 Nov 2004 12:18:14 +0200 (EET)
X-Scanned: Tue, 2 Nov 2004 12:17:38 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iA2AHcq9029012;
	Tue, 2 Nov 2004 12:17:38 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00sqNwyS; Tue, 02 Nov 2004 12:13:49 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA29tXa02297; Tue, 2 Nov 2004 11:55:33 +0200 (EET)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 2 Nov 2004 11:55:30 +0200
Received: from esebe009.NOE.Nokia.com ([172.21.138.41]) by
	esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 2 Nov 2004 11:55:31 +0200
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by
	esebe009.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 2 Nov 2004 11:55:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] Comments on config framework draft - security issues
Date: Tue, 2 Nov 2004 11:55:29 +0200
Message-ID: <5816828233DEFA41807A6CFDFDF2343C3A8BFB@esebe056.ntc.nokia.com>
Thread-Topic: [Sipping] Comments on config framework draft - security issues
Thread-Index: AcS440dVahQXxrjKRkWTcZcCUr4FJwH3OAPg
To: <dpetrie@pingtel.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 02 Nov 2004 09:55:30.0841 (UTC)
	FILETIME=[16972890:01C4C0C2]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable



> -----Original Message-----
> From: ext Daniel G. Petrie [mailto:dpetrie@pingtel.com]
> Sent: 23.October.2004 12:32
> To: Khartabil Hisham (Nokia-TP-MSW/Helsinki); sipping@ietf.org
> Subject: RE: [Sipping] Comments on config framework draft - security
> issues
>=20
>=20
> Hisham Khartabil wrote:
>=20
> >=20
> > Section 3.6
> > -----------
> >=20
> > - "If content indirection is used for delivering the
> >    profiles, the notifier does not need to authenticate the=20
> subscription
> >    as the profile content is not transported in the=20
> SUBSCRIBE or NOTIFY
> >    transaction messages."
> >=20
> > So what? the body of the NOTIFY still contains valuable=20
> information. I think it is a bad idea to suggest that=20
> authentication is not needed. I would say authentication is=20
> always needed.
>=20
> What is there that authentication is going to protect? =20
> Dialog information
> and the profile URI are not protected by authentication. These require
> TLS and S/MIME

The link in the NOTIFY body that points to the indirected content needs =
protecting. I know that HTTPS can be used to protect the content itself, =
but at least you need to mention and recommend that.

>=20
> >=20
> > - "If the user or device is not known to the profile=20
> delivery server,
> >    the implementer MAY accept the subscription or reject it.  It is
> >    recommended that the implementer accept the subscription."
> >=20
> > I think this is a very bad recommendation. This a a=20
> potential DoS attack on the server. The server should reject=20
> any subscriptions from unknown users or devices (opposite to=20
> the current recommendation)
>=20
> There are a few important use cases that require the subscriptions=20
> from unknown user agents to be accepted.
>=20
> 1) A new user agent is plugged into an enterprise environment.  The
> subscription server accepts the subscription and provides a default
> device profile that gives the device the ability to call the help
> desk (UA administrator) and emergency services.

Ok, fair enough.

>=20
> 2) A new user agent is plugged into an enterprise environment.  The
> user then tells the admin that the UA is plugged in and requests that
> it be assigned to the user (i.e. provisions profile delivery server to
> make the UA a known UA).  The profile delivery server then sends a=20
> NOTIFY in the dialog of the subscription to provide the UA with its=20
> device profile.  The UA is then provisioned without requiring any
> user action on the user agent.

This is a continuation from 1. In 1, a user is enabled to talk to =
administrator (help desk). The user who is requesting to be provisioned =
needs to be authenticated (I can plug and claim to be whoever), so =
further steps are needed.

I would recommend including this use case in the draft and suggesting =
that after the administrator configures the user in, the administrator =
terminates the subscription with a reason "deactivated". This results in =
an immediate new subscription that can be challenged (this is a SHOULD =
strength in RFC 3265).

deactivated: The subscription has been terminated, but the subscriber
      SHOULD retry immediately with a new subscription.  One primary use
      of such a status code is to allow migration of subscriptions
      between nodes.  The "retry-after" parameter has no semantics for
      "deactivated".


>=20
> >=20
> > - "If the profile delivery server does not accept the=20
> subscription from
> >    an unknown user or device, the administer or user must manually
> >    provoke the user agent to reSUBSCRIBE."
> >=20
> > So what? a UA can automatically and regularly retry the=20
> subscription if it wants.
>=20
> You do not want a bunch of new UAs in an enterprise polling with a=20
> SUBSCRIBE every minute to check if the profile delivery server now
> has a profile.  That is a bigger DoS problem than accepting the
> subscription.

No you don't want that, but my point was that you cannot prevent it by =
stating that a user must manually provoke ...


Regards,
Hisham

>=20
> >=20
> >=20
> > Section 4.2
> > ------------
> >=20
> > - "However the profile server SHOULD
> >    accept (with 2xx response) SUBSCRIBE requests from any=20
> user agent as
> >    explained in Section 3.5."
> >=20
> > I repeat my concerns here. This is a potential DoS attack.
> >
>=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 sipping-bounces@ietf.org  Tue Nov  2 16:39:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17917
	for <sipping-web-archive@ietf.org>; Tue, 2 Nov 2004 16:39:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP6cn-00071N-KQ
	for sipping-web-archive@ietf.org; Tue, 02 Nov 2004 16:55:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP63b-0001HB-LG; Tue, 02 Nov 2004 16:19:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP5gX-0008EB-JB; Tue, 02 Nov 2004 15:55:21 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10843;
	Tue, 2 Nov 2004 15:55:20 -0500 (EST)
Message-Id: <200411022055.PAA10843@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 02 Nov 2004 15:55:19 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-config-framework-05.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

--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		: A Framework for Session Initiation Protocol User 
			  Agent Profile Delivery
	Author(s)	: D. Petrie
	Filename	: draft-ietf-sipping-config-framework-05.txt
	Pages		: 34
	Date		: 2004-11-2
	
This document defines the application of a set of protocols for
   providing profile data to SIP user agents.  The objective is to
   define a means for automatically providing profile data a user agent
   needs to be functional without user or administrative intervention.
   The framework for discovery, delivery, notification and updates of
   user agent profile data is defined here.  As part of this framework a
   new SIP event package is defined here for the notification of profile
   changes.  This framework is also intended to ease ongoing
   administration and upgrading of large scale deployments of SIP user
   agents.  The contents and format of the profile data to be defined is
   outside the scope of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-framework-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-config-framework-05.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-config-framework-05.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: <2004-11-2161933.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-config-framework-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-config-framework-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--NextPart--





From sipping-bounces@ietf.org  Tue Nov  2 20:04:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09793
	for <sipping-web-archive@ietf.org>; Tue, 2 Nov 2004 20:04:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP9p6-0004I0-1T
	for sipping-web-archive@ietf.org; Tue, 02 Nov 2004 20:20:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP9Ox-0005s7-1V; Tue, 02 Nov 2004 19:53:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP97o-0004Ic-3h
	for sipping@megatron.ietf.org; Tue, 02 Nov 2004 19:35:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06869
	for <sipping@ietf.org>; Tue, 2 Nov 2004 19:35:40 -0500 (EST)
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP9N0-0003ce-Mw
	for sipping@ietf.org; Tue, 02 Nov 2004 19:51:27 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); Tue, 2 Nov 2004 16:35:11 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 2 Nov 2004 16:35:11 -0800
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Nov 2004 16:35:10 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03902C15@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: WGLC: conference-package-06
Thread-Index: AcTALwzLLVAsG5NuT5qeOkX6UCLbwABB+nAQ
From: "Orit Levin" <oritl@microsoft.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>,
        "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>
X-OriginalArrivalTime: 03 Nov 2004 00:35:11.0545 (UTC)
	FILETIME=[FA577290:01C4C13C]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 90f8d7cac99eccf384c4cdc57475e98c
Content-Transfer-Encoding: quoted-printable
Cc: SIPPING mailing list <sipping@ietf.org>
Subject: [Sipping] RE: WGLC: conference-package-06
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e9eeacd7fe925d5f7faae01ed8f85b97
Content-Transfer-Encoding: quoted-printable

Miguel,
Thanks you very much for the thorough review and all your comments!
I am replying inline and basically agreeing with almost all of the
comments but the first one about the "types" description.
I will update the text right after the IETF reflecting your inputs and
hopefully others' as well.

Thanks again,
Orit.

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]=20
> Sent: Monday, November 01, 2004 8:22 AM
> To: Jonathan Rosenberg; Henning Schulzrinne; Orit Levin
> Cc: SIPPING mailing list
> Subject: WGLC: conference-package-06
>=20
> Hi:
>=20
> I have some questions and comments to
> draft-ietf-sipping-conference-package-06.txt
>=20
>=20
> - General: I noticed that the I-D describes the elements of the=20
> Conference Info XML document by describing the XML schema, not a real=20
> XML document. For instance, the I-D describes in section 6.1.1 the=20
> "Conference-Type", which is a type definition in XML schema,=20
> not a real=20
> element. This is a general comment that applies to the whole=20
> document.=20
> My comment is that the textual description should not=20
> describe the bits=20
> and bytes of the XML schema, but the actual contents of a real=20
> Conference Info XML document. In short, there shouldn't be=20
> any mention=20
> to "types" in Section 6.
I disagree with this one :-(and only this one). My approach was to
consistently describe the elements starting from the top level. Each
element description provides the reasoning for the "element" and its
meaning, and points to its "type". The "type" description later in the
document provides the layout of the type in terms of its own attributes
and sub-elements and so on. Note also that many types are being used by
multiple elements and types.
>=20
> - General: - The document speaks quite a bit about "element=20
> with keys".=20
> It is not clear to me, after trying to understand it a few=20
> times, what a=20
> key is, and how a key is identified. So I guess you should a bit more=20
> effort in defining keys, and describing their identification.
>=20
Agree. Will do.

> - General: There are quite a few inconsistencies between the text and=20
> the XML schema definition (I actually predicted this will=20
> happen sooner=20
> or later). For instance, the following attributes are defined as=20
> "mandatory" in the text, but they are "optional" in the XML schema:
>=20
>      version, state (in various sub elements), entity
>=20
> My suggestion is to remove the "mandatory" or "optional" from=20
> the text,=20
> and make sure that things are right in the schema.
>=20
100% agree. Will do.

> - General: There are several instances of a <display-text> element=20
> (e.g., Sections 6.1.2.1, 6.1.3.1, 6.1.5.1, 6.1.6.1, 6.1.7.1)
>=20
> While I understand that it makes sense to have some display-text=20
> information for the conference, the host, or the user, I=20
> wonder how this=20
> can be of benefit for the endpoint or the media type. Further=20
> more, how=20
> can someone set this display type for the endpoint or the=20
> media type, or=20
> how can the conference focus determine it.
>
I would rather leave them in the schema. They are optional and can be
set by any out-of-band/configuration/management means.
=20
> - Section 4: After the first paragraph, the URN is missing. Add:
>=20
>      urn:ietf:params:xml:ns:conference-info
>=20
> - XML schema: since the 'state' attribute has a default value=20
> of "full",=20
> this should be indicated in the schema. You can do so by=20
> replacing all=20
> the 'state' attribute declarations with the following one, which=20
> includes the default value:
>=20
>         <xs:attribute name=3D"state" type=3D"state-type"
>                       use=3D"optional" default=3D"full" />
>=20
100%. Will do.
> - Section 5, 4th paragraph says:
>=20
>     If it contains "deleted" state,
>     indicated by the value of the "state" attribute in the
>     "conference-info" element, it means that the conference ceased to
>     exist and the subscriber SHOULD terminate the SUBSCRIBE dialog.
>=20
> The sentence "the subscriber SHOULD terminate the SUBSCRIBE dialog",=20
> does it mean the user SHOULD send a SUBSCRIBE with Expires=3D0=20
> or does it=20
> mean the user SHOULD consider implicitly the subscription dead? I=20
> suggest the former, but I would like to explicitly say that the UA=20
> SHOULD send a SUBSCRIBE with Expires=3D0 to avoid misunderstandings.
> I also think that the misunderstanding is due to "terminate the=20
> SUBSCRIBE dialog", I guess it should refer to the subscription rather=20
> than the dialog.
I agree. Will do.
>=20
> - Section 6.1.1 reads:
>=20
>     version: This mandatory attribute allows the recipient of=20
> conference
>        information documents to properly order them. =20
> Versions start at 0
>        and increment by one for each new document sent to a=20
> subscriber.
>        Versions are scoped within a subscription.  Versions MUST be
>        represented using a 32 bit integer.
>=20
> But the XML schema just indicates it is a string:
>=20
>       <xs:attribute name=3D"version" type=3D"xs:string" =
use=3D"optional"/>
>=20
> My suggestion is indicate the valid range (0 to 2^32-1) through the=20
> schema, something like:
>=20
>       <xs:attribute name=3D"version" type=3D"version-type"=20
> use=3D"required"/>
>=20
>       <!--
>       VERSION TYPE
>       -->
>       <xs:simpleType name=3D"version-type">
>               <xs:restriction base=3D"xs:nonNegativeInteger">
>               		<xs:maxInclusive value=3D"4294967295" />
>             	</xs:restriction>
>       </xs:simpleType>
>
I don't mind. BTW how is the same attribute being defined in other
SIP/SIMPLE/... schemas? =20
>=20
> - Section 6.1.2.4 <keywords> says:
>=20
>     This element contains a list of keywords which describe the
>     conference *topic*.
>=20
> I disagree. The topic is indicated in the <subject> element.=20
> I think you=20
> want to say that the <keywords> element contains a set of=20
> words that can=20
> be used by automatic search engines to better index the conference.
>=20
Will do.
> - Section 6.1.2.6 <conf-uris> says
>=20
>     This element contains information about additional conference URIs
>     that this conference can be accessed by.
>=20
> This is not correct, the <conf-uris> elements contains one or more=20
> <entry> elements, each one describing additional info about the=20
> conference. And that makes me think that the name <conf-uris> is not=20
> right either, since the URI is hidden in the <entry><uri> element.
>=20
Regarding this and the same comments below. I will rephrase the wording
but I really don't want to change the names in the schema. The structure
is not simple but the outer name conveys the semantics of these
elements.

> This comment is also applicable to <service-uris> (6.1.2.7)
>=20
> - Section 6.1.2.8 <maximum-user-count> says:
>=20
>     This element contains a count of the maximum number of users
>     permitted in the conference.
>=20
> Well, the element actually contains one or more <entry>=20
> elements, rather=20
> than a maximum number of users permitted in the conference. The=20
> definition in the schema is:
>=20
>      <xs:element name=3D"maximum-user-count"
>               type=3D"user-count-type" minOccurs=3D"0"/>
>=20
> I guess this element should have a nonNegativeInteger type=20
> rather than=20
> user-count-type.
>
The current definition allows to count the participants per their roles.

> - Section 6.1.3.3 <uris> says
>=20
>     The "entity" sub-element contains additional URIs relating to the
>     user hosting the conference.
>=20
> Obviously this is not the <entity> subelements, but the <uris>=20
> sub-element. Also, it can contain one or more <entry>=20
> elements, each of=20
> them contains additional URIs ...
>=20
> - Section 6.1.4.2  <security-level> says:
>=20
>     This element contains information about the conference security
>     level.  The values can be "none", "low", "medium", or "high".
>=20
> I don't understand how to map each of these values to=20
> something else. So=20
> what is the "conference security level", where is it=20
> described, and how=20
> can my application determine if the security level is any of the=20
> mentioned above. In short, I am missing some semantics for=20
> this element,=20
> and some guidance as for how can the focus determine the conference=20
> security level.
>=20
I copied the definition from the CPCP latest schema. I agree that we
need to add more semantics to it. I hope that we will do it as a part of
our more general effort to align between the two schemas during the
IETF.
> - Section 6.1.5.4 <language> says:
>=20
>    This element contains the language used by the user.
>=20
> Does this mean the conference is able to recognize the language I am=20
> using? I guess not, so perhaps the text should read "This element=20
> contains the preferred language used by the SIP application.=20
> The focus=20
> can determine its contents from the Accept-Contact header=20
> field in SIP".
>=20
Will do.

> - Section 6.1.6.7. The title of this section reads:
>=20
>     disconnection-info of disconnection-type
>=20
> Although there is not a disconnection-type, but an execution type.
Will change.
=20
> Nevertheless, I hope this comment becomes not applicable,=20
> after my other=20
> comment indicating that there shouldn't be any "type" mentioned in=20
> Section 6.
>=20
> - Section 6.1.6.8 <whispering-to> says:
>=20
>     If an endpoint is participating in a whisper session with other
>     entities, the URIs of these other entities MAY be=20
> contained in this
>     element.
>=20
> Absolutely a leak of privacy. If I am whispering to someone might be=20
> because I don't want the rest of the conference be aware that I am=20
> having a side-by conversation with someone else. This is the main=20
> difference between whispering and sidebars.
>=20
> If there were some mechanism where I could differentiate a "public=20
> whisper" from an "invisible whisper", I wouldn't mind to have this=20
> element indicating to who I am whispering. Unfortunately I am=20
> not aware=20
> of such mechanism, so I suggest to delete this element to=20
> avoid leaking=20
> privacy information.
>=20
I would rather prefer leaving this one because it is a kind of "sidebar"
that is widely implemented and implemented differently from the usual
sidebar techniques. The main difference between this and the plain
sidebar is that it is one-to-many and unidirectional. In terms of
privacy - the package contains a lot of private information that needs
to be filtered by a smart Notification Server in addition to this
particular point anyway.

I will be happy to clarify what "whisper" means and add the privacy
considerations to it.=20
> - Section 6.1.7 <media>, speaking about the 'entity' attribute says:
>=20
>        The value of this element
>        SHOULD correspond to the "mid" value in the SDP document as
>        defined in Grouping of Media Lines in the SDP [9].
>=20
> I don't agree with this. So does it mean I cannot join a=20
> conference if=20
> my SIP UA does not support the "mid" attribute? I guess there=20
> should be=20
> some guidelines as for what to do with this attribute if the=20
> UA supports=20
> basic SDP as per RFC 2327.
>=20
Agree 100%. Will add this clarification and the guidelines.

> - Sections 6.1.7.5, 6.1.7.6, 6.1.7.7 and 6.1.7.8
>=20
> I don't see the need for so many elements. I guess these=20
> properties can=20
> be expressed with just a single element, namely <direction>. This new=20
> <direction> element can take the values "sendrecv", "sendonly",=20
> "recvonly", "inactive", and can be mapped from the corresponding SDP=20
> attributes. Note that I didn't forget the "muted" element,=20
> since there=20
> are no semantics for it, and I don't understand what it means, and I=20
> believe it is not required.
>=20
> So please take my consideration into account and arrange=20
> these sections=20
> into one element.
Makes sense. Will do.
>=20
> - Section 6.1.7.8 <call>
>=20
> I don't understand why <call> is of type call-type, and=20
> call-type is of=20
> type dialog-id. I guess <call> should be of type dialog-id. I=20
> don't see=20
> the benefit in so many type indirection.
>
The reason is because the schema is designed not for SIP calls only.
This allows plugging in additional "call identifiers".
> Also this describes the <call-id>, <to-tag> and <from-tag>=20
> subelements.=20
> You should be associating semantics to the Call-ID header in SIP, the=20
> tag in the To and From header fields. Such semantics are not=20
> assigned in=20
> the current draft.
This was the intention. Will clarify.
>=20
> - Section 7. XML extensibility. I noticed that you have=20
> invented a new=20
> mechanism to extend an XML schema. It seems that the extensibility is=20
> provided by an undefined <extended> element. I said undefined=20
> because I=20
> didn't find its description in Section 6. This element may=20
> include any=20
> collection of elements from other namespaces. where the required=20
> attribute 'namespace' seems to indicate the namespace.
>=20
> However XML schema already contains a widely used mechanism to allow=20
> extensibility. To define an extension for an element from other=20
> namespace, you can add:
>=20
> <xs:any namespace=3D"##other" processContents=3D"lax" minOccurs=3D"0"=20
> maxOccurs=3D"unbounded"/>
>=20
> To define an attribute from another namespace, you can add:
>=20
> <xs:anyAttribute namespace=3D"##other"/>
>=20
> The result is the same you are trying to achieve, but the one I am=20
> proposing is commonly used in XML schemas, and I think we should be=20
> using the same instead of your invented mechanism.
>=20
> So can you use the standard extensibility mechanism?
Yes, I can and will do unless there are no objections from others.
>=20
> - Section 7, XML schema, <conference-info>
>=20
> The XML schema indicates that all the child elements of=20
> <conference-info> are optional. This means that the following=20
> document=20
> is valid:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <conference-info xmlns=3D"urn:ietf:params:xml:ns:conference-info"=20
> xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"=20
> xsi:schemaLocation=3D"urn:ietf:params:xml:ns:conference-info"=20
> entity=3D"http://www.altova.com" state=3D"full" version=3D"0"/>
>=20
> And this is a bit weird. I guess there should be something more in=20
> conference info. As a minimum, the conference has been=20
> instantiated, so=20
> I guess the conference-description and conference state=20
> should always be=20
> present.
>
I am not sure about this one... I would prefer to leave the schema as
is.
I am OK with adding text saying SHOULD be present.

> - Section 7, XML schema, 'entity' attribute
>=20
> I noticed that the 'entity' attribute is used by quite a few=20
> elements.=20
> In some cases, the 'entity' attribute can accommodate a URI whereas=20
> others can accommodate a string. While this is legal, it is=20
> really ugly.=20
> If you browse through the schema, you can see the following=20
> two definitions:
>=20
>      <xs:attribute name=3D"entity" type=3D"xs:anyURI" =
use=3D"required"/>
>=20
>      <xs:attribute name=3D"entity" type=3D"xs:string" =
use=3D"required"/>
>=20
> I would recommend that you rename the 'entity' that can take a string=20
> with something else.
>=20
Agree. Will do.

> - Section 7, XML schema, <label> attribute
>=20
> The definition of <label> in the schema is:
>=20
>   <xs:element name=3D"label" type=3D"xs:string" minOccurs=3D"0"/>
>=20
> However, it is the intention to use this label as a key to=20
> discover the=20
> URI of further services, such as the CPCP URI, and perhaps something=20
> else. However, the <label> element does not contain a list of=20
> possible=20
> services one can think of, so it is not possible that a SIP=20
> UA uses that=20
> information to, e.g., upload a CPCP document. The problem is that the=20
> string is not standardized.
>=20
> I don't know what people think about this, but I believe we either=20
> standardize a few enumerated values, and provide=20
> extensibility, or then=20
> this <label> attribute looks quite useless.
>
I would really like to keep this "label". OK with standardizing it,
though.
=20
> - Section 13. I think references 12 (RFC 2327) and 19=20
> (draft-ietf-mmusic-sdp-media-label) can't be informative, since there=20
> are strong dependencies on those. Further more, RFC 2327 is under=20
> (eternal) revision, draft-ietf-mmusic-sdp-new-12312.txt or something=20
> similar. Since there is a dependency on the inactive attribute=20
> introduced by this new SDP version, we should refer to it,=20
> but it would=20
> be good to find out the status of SDP new and learn if it is going to=20
> proceed to RFC before the end of the century.
>=20
I actually think that the dependency can be stated as "informative". We
are just borrowing few strings for clarity.
>=20
>=20
>=20
> Nits:
I agree with all the nits below and will incorporate them. Thanks a lot!
>=20
> - General: I would appreciate if we can refer to elements by=20
> enclosing=20
> the element in brackets rather than quotes. So far, all the document=20
> refers to elements such as "conference-info" rather than=20
> <conference-info>. We should refer to attributes by inserting them in=20
> single quotes, e.g., the 'entity' attribute. Enumerated=20
> values should be=20
> quoted, e.g., the value can be "active" and "inactive".
>=20
>=20
> - Section 4, first paragraph. Include references to "XML=20
> document" and=20
> UTF-8.
>=20
>     Conference information is an XML document [x]that MUST be=20
> well-formed
>     and SHOULD be valid.  Dialog information documents MUST=20
> be based on
>     XML 1.0 and MUST be encoded using UTF-8 [y]. This=20
> specification makes
>=20
>     [x]   Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
>           "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C
>           REC-xml-20001006, October 2000.
>=20
>     [y]   Yergeau, F., "UTF-8, a transformation format of ISO=20
> 10646", STD
>           63, RFC 3629, November 2003.
>=20
> - Section 4, 5th paragraph. For better readability, I would=20
> suggest to=20
> replace the current paragraph:
>=20
>     For elements with the optional "state" attribute, if the=20
> attribute is
>     omitted from the notification for the element, it means that the
>     reported element's state is "full".
>=20
> with this other one:
>=20
>     Elements can be characterized with an optional 'state' attribute=20
> that indicates whether a "full", "partial" or "deleted" state is=20
> indicated. The absence of a 'state' attribute has the same=20
> semantics as=20
> "full".
>=20
> - Section 5 reads in bullet point 3.1.1: "If a key does not=20
> exist in the=20
> local table, a row is added, and its content is set to the element=20
> information from the update."
> I think it is weird that an element can safely be deleted=20
> just because=20
> it does not provide any content. Imagine an element that can=20
> either be=20
> present or not, hypothetical example, <is-focus/>. I don't=20
> think it is=20
> safe to locally remove those elements.
>=20
> - Section 6: remove the urn:ietf:params:xml:ns:conference-info
> URN from this section.
>=20
> - Section 6.1.7.3. The last sentence is, for some reason, quoted.=20
> Action: remove the quotes.
>=20
> - Section 6.1.7.4., <label>. Replace the sentence:
>=20
>     The
>     value of this element corresponds to the "label" media=20
> attribute in
>     SDP [12] and defined in [19].
>=20
> with
>=20
>     The
>     value of this element corresponds to the "label" media=20
> attribute in
>     [19].
>=20
> - Section 7. Title. s/Schema/XML Schema
>=20
> - Section 13, reference 1 is now RFC 3688
>=20
>=20
>=20
> Best regards,
>=20
>      Miguel
>=20
> --=20
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Research Center      Helsinki, Finland
>=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 sipping-bounces@ietf.org  Wed Nov  3 03:08:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09111
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 03:08:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPGQr-00059g-Va
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 03:24:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPG0q-0003Ev-UH; Wed, 03 Nov 2004 02:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPFuO-0008Jh-Qq
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 02:50:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08064
	for <sipping@ietf.org>; Wed, 3 Nov 2004 02:50:19 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPG9c-0004p9-O2
	for sipping@ietf.org; Wed, 03 Nov 2004 03:06:08 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA37oFfM006993
	for <sipping@ietf.org>; Wed, 3 Nov 2004 08:50:15 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 3 Nov 2004 08:50:15 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id VJQG79FL; Wed, 3 Nov 2004 08:50:15 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id CBBF818AAC; Wed,  3 Nov 2004 09:50:14 +0200 (EET)
Message-ID: <41888DB6.5050204@ericsson.com>
Date: Wed, 03 Nov 2004 09:50:14 +0200
X-Sybari-Trust: 38e4e251 ad48f3dd b4145185 00000179
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
X-OriginalArrivalTime: 03 Nov 2004 07:50:15.0452 (UTC)
	FILETIME=[C17B8DC0:01C4C179]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] WGLC: Application Interaction
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Folks,

we would like to working group last call the following draft:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-interaction-framework-03.txt

This WGLC will finish on December 3rd. Please, send you comments to the 
authors and to the list.

As a suggestion, you may want to review this document and KPML, which is 
also under WGLC, together.

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 sipping-bounces@ietf.org  Wed Nov  3 06:03:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22002
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 06:03:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPJAk-0000lE-6n
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 06:19:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPIGw-0003UU-3f; Wed, 03 Nov 2004 05:21:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPHuR-0005zH-VA
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 04:58:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16803
	for <sipping@ietf.org>; Wed, 3 Nov 2004 04:58:29 -0500 (EST)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPI9h-0007jA-Hx
	for sipping@ietf.org; Wed, 03 Nov 2004 05:14:20 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA39wCe11659; Wed, 3 Nov 2004 11:58:12 +0200 (EET)
X-Scanned: Wed, 3 Nov 2004 11:57:35 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iA39vZQ0022381;
	Wed, 3 Nov 2004 11:57:35 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00x7EtRO; Wed, 03 Nov 2004 11:57:34 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA39vWa15257; Wed, 3 Nov 2004 11:57:32 +0200 (EET)
Received: from [172.21.37.239] ([172.21.37.239]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 3 Nov 2004 11:57:23 +0200
Message-ID: <4188AB82.9060909@nokia.com>
Date: Wed, 03 Nov 2004 11:57:22 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Orit Levin <oritl@microsoft.com>
References: <DD07841287D0AD428833021705E0D14E03902C15@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <DD07841287D0AD428833021705E0D14E03902C15@RED-MSG-52.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Nov 2004 09:57:23.0100 (UTC)
	FILETIME=[83EA45C0:01C4C18B]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 16a2b98d831858659c646b3dec9ed22b
Content-Transfer-Encoding: 7bit
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        SIPPING mailing list <sipping@ietf.org>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: [Sipping] Re: WGLC: conference-package-06
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 65215b440f7ab00ca9514de4a7a89926
Content-Transfer-Encoding: 7bit

Orit:

Thanks for your reply. I am now cutting the e-mail to only those points 
that require further discussion. See inline.

Orit Levin wrote:
> Miguel,
> Thanks you very much for the thorough review and all your comments!
> I am replying inline and basically agreeing with almost all of the
> comments but the first one about the "types" description.
> I will update the text right after the IETF reflecting your inputs and
> hopefully others' as well.
> 
> Thanks again,
> Orit.
> 
> 
>>-----Original Message-----
>>From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com] 
>>Sent: Monday, November 01, 2004 8:22 AM
>>To: Jonathan Rosenberg; Henning Schulzrinne; Orit Levin
>>Cc: SIPPING mailing list
>>Subject: WGLC: conference-package-06
>>
>>Hi:
>>
>>I have some questions and comments to
>>draft-ietf-sipping-conference-package-06.txt
>>
>>
>>- General: I noticed that the I-D describes the elements of the 
>>Conference Info XML document by describing the XML schema, not a real 
>>XML document. For instance, the I-D describes in section 6.1.1 the 
>>"Conference-Type", which is a type definition in XML schema, 
>>not a real 
>>element. This is a general comment that applies to the whole 
>>document. 
>>My comment is that the textual description should not 
>>describe the bits 
>>and bytes of the XML schema, but the actual contents of a real 
>>Conference Info XML document. In short, there shouldn't be 
>>any mention 
>>to "types" in Section 6.
> 
> I disagree with this one :-(and only this one). My approach was to
> consistently describe the elements starting from the top level. Each
> element description provides the reasoning for the "element" and its
> meaning, and points to its "type". The "type" description later in the
> document provides the layout of the type in terms of its own attributes
> and sub-elements and so on. Note also that many types are being used by
> multiple elements and types.
> 

This is not the approach that other document in SIMPLE has taken. For 
instance, take the prescaps or any other SIMPLE document, and you will 
find out that the descriptive text follows the structure of a the XML 
document, not the XML schema document.

I would like that the conference event package follows the same pattern, 
and you describe the elements that you find in an conference info 
document, not in the XML schema that represents the structure of the 
conference info document.

To be precise. Section 6 reads:

    A conference information document begins with the root element tag
    "conference-info".

And that is correct. But then you describe, in Section 6.1.1, a supposed 
  conference type, which is not a visible element in a conference-info 
document.

> 
> 
>>- General: There are several instances of a <display-text> element 
>>(e.g., Sections 6.1.2.1, 6.1.3.1, 6.1.5.1, 6.1.6.1, 6.1.7.1)
>>
>>While I understand that it makes sense to have some display-text 
>>information for the conference, the host, or the user, I 
>>wonder how this 
>>can be of benefit for the endpoint or the media type. Further 
>>more, how 
>>can someone set this display type for the endpoint or the 
>>media type, or 
>>how can the conference focus determine it.
>>
> 
> I would rather leave them in the schema. They are optional and can be
> set by any out-of-band/configuration/management means.
>  

The argument that they are optional is not that strong. We can put a lot 
of optional things, but at the end of the day, we need to figure out how 
is this going to be used. I don't find any usage for a display-text in 
an endpoint or a media type. I don't know how this can be set, and how 
my user agent can take the advantage of those fields.

Therefore, I still suggest to delete them, and if there is a future need 
for them, we can always extend the schema.

> 
>>- Section 6.1.1 reads:
>>
>>    version: This mandatory attribute allows the recipient of 
>>conference
>>       information documents to properly order them.  
>>Versions start at 0
>>       and increment by one for each new document sent to a 
>>subscriber.
>>       Versions are scoped within a subscription.  Versions MUST be
>>       represented using a 32 bit integer.
>>
>>But the XML schema just indicates it is a string:
>>
>>      <xs:attribute name="version" type="xs:string" use="optional"/>
>>
>>My suggestion is indicate the valid range (0 to 2^32-1) through the 
>>schema, something like:
>>
>>      <xs:attribute name="version" type="version-type" 
>>use="required"/>
>>
>>      <!--
>>      VERSION TYPE
>>      -->
>>      <xs:simpleType name="version-type">
>>              <xs:restriction base="xs:nonNegativeInteger">
>>              		<xs:maxInclusive value="4294967295" />
>>            	</xs:restriction>
>>      </xs:simpleType>
>>
> I don't mind. BTW how is the same attribute being defined in other
> SIP/SIMPLE/... schemas?  

Good point. At least the partial PIDF has defined the same attribute. So 
I will post an e-mail to SIMPLE and the PIDF authors suggesting them to 
follow the same approach as in here.



> 
>>- Section 6.1.6.8 <whispering-to> says:
>>
>>    If an endpoint is participating in a whisper session with other
>>    entities, the URIs of these other entities MAY be 
>>contained in this
>>    element.
>>
>>Absolutely a leak of privacy. If I am whispering to someone might be 
>>because I don't want the rest of the conference be aware that I am 
>>having a side-by conversation with someone else. This is the main 
>>difference between whispering and sidebars.
>>
>>If there were some mechanism where I could differentiate a "public 
>>whisper" from an "invisible whisper", I wouldn't mind to have this 
>>element indicating to who I am whispering. Unfortunately I am 
>>not aware 
>>of such mechanism, so I suggest to delete this element to 
>>avoid leaking 
>>privacy information.
>>
> 
> I would rather prefer leaving this one because it is a kind of "sidebar"
> that is widely implemented and implemented differently from the usual
> sidebar techniques. The main difference between this and the plain
> sidebar is that it is one-to-many and unidirectional. In terms of
> privacy - the package contains a lot of private information that needs
> to be filtered by a smart Notification Server in addition to this
> particular point anyway.
> 
> I will be happy to clarify what "whisper" means and add the privacy
> considerations to it. 

I still disagree. If you can proof me that there is such thing as a 
"public whisper" and "private whisper", then I would agree that the 
conference info includes the public whisper. However, I am not aware of 
any mechanism that allows me, as a participant of a conference, 
differentiate the private from the public whispering. If we have this 
element here the focus will be leaking privacy information of the 
participants, and I am not ready to accept this leakage.

My proposal is still to delete the element. If in the future we have a 
clear mechanism that allows the user to differentiate public from 
private whispering, then we can extend the conference info XML schema. 
But since there is not such mechanism today, I will propose to delete 
the <whispering-to> element.

> 
>>- Section 7, XML schema, <conference-info>
>>
>>The XML schema indicates that all the child elements of 
>><conference-info> are optional. This means that the following 
>>document 
>>is valid:
>>
>><?xml version="1.0" encoding="UTF-8"?>
>><conference-info xmlns="urn:ietf:params:xml:ns:conference-info" 
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>>xsi:schemaLocation="urn:ietf:params:xml:ns:conference-info" 
>>entity="http://www.altova.com" state="full" version="0"/>
>>
>>And this is a bit weird. I guess there should be something more in 
>>conference info. As a minimum, the conference has been 
>>instantiated, so 
>>I guess the conference-description and conference state 
>>should always be 
>>present.
>>
> 
> I am not sure about this one... I would prefer to leave the schema as
> is.
> I am OK with adding text saying SHOULD be present.

What I am suggesting is that there should be a minimum of conference 
information present in the document. I guess this should be 
<conference-description> and the <conference-state>. The former exists 
from the creation of a conference. The second as well, although it could 
potentially be empty.

What I am trying to avoid is that a conference server sends me a 
conference event package that just contains <conference-info />. This is 
legal according to the schema, but shouldn't be. Think that it is hard 
to create good interoperability if everything in the document except the 
top level element is optional.

  >>- Section 7, XML schema, <label> attribute
>>
>>The definition of <label> in the schema is:
>>
>>  <xs:element name="label" type="xs:string" minOccurs="0"/>
>>
>>However, it is the intention to use this label as a key to 
>>discover the 
>>URI of further services, such as the CPCP URI, and perhaps something 
>>else. However, the <label> element does not contain a list of 
>>possible 
>>services one can think of, so it is not possible that a SIP 
>>UA uses that 
>>information to, e.g., upload a CPCP document. The problem is that the 
>>string is not standardized.
>>
>>I don't know what people think about this, but I believe we either 
>>standardize a few enumerated values, and provide 
>>extensibility, or then 
>>this <label> attribute looks quite useless.
>>
> 
> I would really like to keep this "label". OK with standardizing it,
> though.

But you didn't answer my question. What is the semantics of the <label> 
element. Because in the mmusic label draft clearly indicates the 
semantics of the label attribute, as a mechanism to correlate static SDP 
documents with an actual SDP document. So in this sense, it is just a 
pointer with not further semantics.

By reading the conference event package, I got the impression that the 
idea is to overload the label attribute to indicate something else, for 
instance, that a URI is a CPCP or floor control URI.

If we check Section 6.1.7.4, it reads:

    The element "label" carries a unique identifier for this stream among
    all streams in the conference and is assigned by the focus.  The
    value of this element corresponds to the "label" media attribute in
    SDP [12] and defined in [19].

But the definition is not correct, because <label> is not only used in 
media streams, but also in URIs and user roles. I don't quite understand 
the relation between the "label" attribute in SDP and a URI or a user role.



>  
> 
>>- Section 13. I think references 12 (RFC 2327) and 19 
>>(draft-ietf-mmusic-sdp-media-label) can't be informative, since there 
>>are strong dependencies on those. Further more, RFC 2327 is under 
>>(eternal) revision, draft-ietf-mmusic-sdp-new-12312.txt or something 
>>similar. Since there is a dependency on the inactive attribute 
>>introduced by this new SDP version, we should refer to it, 
>>but it would 
>>be good to find out the status of SDP new and learn if it is going to 
>>proceed to RFC before the end of the century.
>>
> 
> I actually think that the dependency can be stated as "informative". We
> are just borrowing few strings for clarity.
> 

I disagree. The criteria I am using is the following: if there are 
normative statemens depending on another document, the reference to that 
is normative, otherwise the reference is informative.

Checking the conference info package, I found the following:

Section 6.1.2.9

    The "entry" sub-element MUST be a value registered for
    "proto" of SDP [12].

Similar text appears in 6.1.7.1

Further more, extensive sections of the conference info draft require 
the focus to understand SDP, so obviously SDP is a normative reference.



Regards,

           Miguel


-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov  3 06:28:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25785
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 06:28:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPJZ4-0001RN-Tg
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 06:44:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPJ76-0008PV-Rz; Wed, 03 Nov 2004 06:15:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPIgE-00072Q-G3
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 05:47:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20926
	for <sipping@ietf.org>; Wed, 3 Nov 2004 05:47:52 -0500 (EST)
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPIvW-0000Rf-Di
	for sipping@ietf.org; Wed, 03 Nov 2004 06:03:43 -0500
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <49HBJ069>; Wed, 3 Nov 2004 10:47:13 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F803E531A5@baker.datcon.co.uk>
From: "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
To: "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Wed, 3 Nov 2004 10:47:05 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

Jonathan,

Has a time and place for the get together that you alluded to below been
determined yet?

  ...Furthermore, we are 
  planning an informal get together at IETF 61 to continue the dialog, 
  focusing squarely on understanding requirements and specification gaps. 
  Details TBA shortly. Whether one likes the solutions that are out there 
  or not, the first step in doing anything is to understand the 
  requirements. I really want to do that....

Thanks,
Paul D Smith
Network Protocols Group 
Data Connection Ltd (DCL)
Tel: +44 20 8366 1177  Email: paul.d.smith@dataconnection.com 
Fax: +44 20 8363 1039  Web:   http://www.dataconnection.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 sipping-bounces@ietf.org  Wed Nov  3 06:33:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26229
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 06:33:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPJdB-0001ZZ-T1
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 06:49:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPJCL-0002ab-9p; Wed, 03 Nov 2004 06:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPIxV-0004g3-9w
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 06:05:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22396
	for <sipping@ietf.org>; Wed, 3 Nov 2004 06:05:42 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPJCc-0000pP-H8
	for sipping@ietf.org; Wed, 03 Nov 2004 06:21:34 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA3B5WR2019792 for <sipping@ietf.org>; Wed, 3 Nov 2004 12:05:32 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 3 Nov 2004 12:05:32 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WFKZNKBN; Wed, 3 Nov 2004 12:05:32 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 5C47418AA9; Wed,  3 Nov 2004 13:05:31 +0200 (EET)
Message-ID: <4188BB7B.4020803@ericsson.com>
Date: Wed, 03 Nov 2004 13:05:31 +0200
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
X-OriginalArrivalTime: 03 Nov 2004 11:05:32.0079 (UTC)
	FILETIME=[0922F3F0:01C4C195]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, Jon Peterson <Jon.Peterson@neustar.com>,
        Allison Mankin <mankin@psg.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] Ad-hoc on SBCs schedulling
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Folks,

we have two options to organize the ad-hoc meeting on Session Border 
Controllers:

1) Tuesday from 19:30 to 21:30 (we already have a room reserved)
2) Thursday in the evening/night (if many people prefer Thursday, we 
would try to book a room then)

If you intend to attend this ad-hoc, please send me a private email (no 
need to spam the mailing list) with your preference. Note that "both 
options suit me fine" is a valid answer.

Thanks,

Gonzalo
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 sipping-bounces@ietf.org  Wed Nov  3 10:03:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15765
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 10:03:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPMut-00075c-5b
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 10:19:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPMTt-0005WK-FS; Wed, 03 Nov 2004 09:51:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPMLa-0003ha-Bl
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 09:42:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13949
	for <sipping@ietf.org>; Wed, 3 Nov 2004 09:42:48 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPMau-0006Ya-Ak
	for sipping@ietf.org; Wed, 03 Nov 2004 09:58:41 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com
	[135.86.145.57])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iA3Egjf3020008
	for <sipping@ietf.org>; Wed, 3 Nov 2004 08:42:46 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service
	(5.5.2657.72) id <4MZV7ALV>; Wed, 3 Nov 2004 14:42:44 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00C290229@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>,
        sipping
	<sipping@ietf.org>
Subject: RE: [Sipping] WGLC: Application Interaction
Date: Wed, 3 Nov 2004 14:42:14 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Rohan Mahy <rohan@ekabal.com>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

I believe on the 23rd July 2004 there was a mail that clarified that this deliverable was actually a SIP charter item.

Has it now gone back to SIPPING.

regards

Keith

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
> Sent: 03 November 2004 07:50
> To: sipping
> Cc: Rohan Mahy; Dean Willis
> Subject: [Sipping] WGLC: Application Interaction
> 
> 
> Folks,
> 
> we would like to working group last call the following draft:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-int
eraction-framework-03.txt

This WGLC will finish on December 3rd. Please, send you comments to the 
authors and to the list.

As a suggestion, you may want to review this document and KPML, which is 
also under WGLC, together.

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 sipping-bounces@ietf.org  Wed Nov  3 15:16:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15956
	for <sipping-web-archive@ietf.org>; Wed, 3 Nov 2004 15:16:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPRoD-0006Kz-4W
	for sipping-web-archive@ietf.org; Wed, 03 Nov 2004 15:32:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPRTM-00029F-7u; Wed, 03 Nov 2004 15:11:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPRQ6-0008RA-Pr
	for sipping@megatron.ietf.org; Wed, 03 Nov 2004 15:07:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14662
	for <sipping@ietf.org>; Wed, 3 Nov 2004 15:07:48 -0500 (EST)
Received: from web90004.mail.scd.yahoo.com ([66.218.94.62])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPRfT-00067v-Eg
	for sipping@ietf.org; Wed, 03 Nov 2004 15:23:44 -0500
Message-ID: <20041103200717.10426.qmail@web90004.mail.scd.yahoo.com>
Received: from [192.91.75.29] by web90004.mail.scd.yahoo.com via HTTP;
	Wed, 03 Nov 2004 12:07:17 PST
Date: Wed, 3 Nov 2004 12:07:17 -0800 (PST)
From: Rajesh kapoor <sipuser123@yahoo.com>
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [Sipping] Automatic callback event package
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

Hi list,

Is there any latest version of
draft-ietf-sipping-dialog-package-02 available for
implementing automatic callback?

Or any other event package for this?


Thanks

Sachin



		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.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 sipping-bounces@ietf.org  Thu Nov  4 02:35:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22055
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 02:35:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPcPA-0004Ik-8O
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 02:51:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPc3Z-0000Aa-GF; Thu, 04 Nov 2004 02:29:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPc0N-0007AO-RS
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 02:26:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21292
	for <sipping@ietf.org>; Thu, 4 Nov 2004 02:25:58 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPcFd-000459-NB
	for sipping@ietf.org; Thu, 04 Nov 2004 02:42:00 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA47Phh5007835
	for <sipping@ietf.org>; Thu, 4 Nov 2004 08:25:43 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 4 Nov 2004 08:25:42 +0100
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WB1Z9DW4; Thu, 4 Nov 2004 08:25:40 +0100
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.196])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id E36BF18AAC; Thu,  4 Nov 2004 09:25:39 +0200 (EET)
Message-ID: <4189D973.2020205@ericsson.com>
Date: Thu, 04 Nov 2004 09:25:39 +0200
X-Sybari-Trust: 48cd1fca 8cefd49f 0abc6abd 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: "Drage, Keith (Keith)" <drage@lucent.com>
Subject: Re: [Sipping] WGLC: Application Interaction
References: <475FF955A05DD411980D00508B6D5FB00C290229@en0033exch001u.uk.lucent.com>
In-Reply-To: <475FF955A05DD411980D00508B6D5FB00C290229@en0033exch001u.uk.lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Nov 2004 07:25:42.0520 (UTC)
	FILETIME=[7DF5B780:01C4C23F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, sipping <sipping@ietf.org>,
        Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit

Hi Keith,

as you point out, this draft was done in SIPPING, but since it contains 
normative behavior, it should be run thru SIP as well. In any case, to 
avoid confusions, we will WGLC in both working groups. This way, 
everybody will have a chance to comment.

Thanks,

Gonzalo

Drage, Keith (Keith) wrote:

> I believe on the 23rd July 2004 there was a mail that clarified that this deliverable was actually a SIP charter item.
> 
> Has it now gone back to SIPPING.
> 
> regards
> 
> Keith
> 
> 
>>-----Original Message-----
>>From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
>>Sent: 03 November 2004 07:50
>>To: sipping
>>Cc: Rohan Mahy; Dean Willis
>>Subject: [Sipping] WGLC: Application Interaction
>>
>>
>>Folks,
>>
>>we would like to working group last call the following draft:
>>
>>http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-int
> 
> eraction-framework-03.txt
> 
> This WGLC will finish on December 3rd. Please, send you comments to the 
> authors and to the list.
> 
> As a suggestion, you may want to review this document and KPML, which is 
> also under WGLC, together.
> 
> 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

-- 
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 sipping-bounces@ietf.org  Thu Nov  4 06:12:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09577
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 06:12:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPfn1-0000y7-EH
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 06:28:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPfWW-0008Me-LU; Thu, 04 Nov 2004 06:11:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPfSG-00077G-4A
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 06:07:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09083
	for <sipping@ietf.org>; Thu, 4 Nov 2004 06:06:57 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPfhZ-0000pe-Qs
	for sipping@ietf.org; Thu, 04 Nov 2004 06:23:02 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA4B6kvD003705
	for <sipping@ietf.org>; Thu, 4 Nov 2004 12:06:46 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 4 Nov 2004 12:06:44 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WFZGZNGY>; Thu, 4 Nov 2004 12:06:44 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF07B08733@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Paul D.Smith'" <Paul.D.Smith@dataconnection.com>,
        "'Jonathan Rosenberg'" <jdrosen@cisco.com>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Thu, 4 Nov 2004 12:06:43 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 04 Nov 2004 11:06:44.0694 (UTC)
	FILETIME=[5ED4DF60:01C4C25E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: SIPPING WG <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a


Hi,

3GPP IMS currently uses a "SBC" (the IMS-ALG/TrGW) to do IPv4/IPv6 interworking, both on the signalling and media level (which means the SDP is re-written).

TISPAN-NGN will define a number of new "SBC" functions, and they will be used both between core networks (NNI), and between access- and core networks (UNI). NAT support is probably the most important function, but other functions (many of which can be found from Brian's list) have also been proposed.

Regards,

Christer Holmberg
Ericsson Finland






> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> Behalf Of Paul D.Smith
> Sent: 3. marraskuuta 2004 12:47
> To: 'Jonathan Rosenberg'
> Cc: SIPPING WG
> Subject: RE: [Sipping] What problems are SBCs addressing?
> 
> 
> Jonathan,
> 
> Has a time and place for the get together that you alluded to 
> below been
> determined yet?
> 
>   ...Furthermore, we are 
>   planning an informal get together at IETF 61 to continue 
> the dialog, 
>   focusing squarely on understanding requirements and 
> specification gaps. 
>   Details TBA shortly. Whether one likes the solutions that 
> are out there 
>   or not, the first step in doing anything is to understand the 
>   requirements. I really want to do that....
> 
> Thanks,
> Paul D Smith
> Network Protocols Group 
> Data Connection Ltd (DCL)
> Tel: +44 20 8366 1177  Email: paul.d.smith@dataconnection.com 
> Fax: +44 20 8363 1039  Web:   http://www.dataconnection.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 sipping-bounces@ietf.org  Thu Nov  4 07:42:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14972
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 07:42:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPhCS-0002fU-Qz
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 07:58:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPgkf-0007YB-Fm; Thu, 04 Nov 2004 07:30:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPgcl-0006KA-MY
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 07:21:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13830
	for <sipping@ietf.org>; Thu, 4 Nov 2004 07:21:55 -0500 (EST)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPgsG-0002HP-UW
	for sipping@ietf.org; Thu, 04 Nov 2004 07:37:58 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA4CLie04590; Thu, 4 Nov 2004 14:21:44 +0200 (EET)
X-Scanned: Thu, 4 Nov 2004 14:21:11 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iA4CLBw0028493;
	Thu, 4 Nov 2004 14:21:11 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00ABPJYu; Thu, 04 Nov 2004 14:20:51 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA4CKja18698; Thu, 4 Nov 2004 14:20:45 +0200 (EET)
Received: from [172.21.37.239] ([172.21.37.239]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 4 Nov 2004 14:20:36 +0200
Message-ID: <418A1E94.1040409@nokia.com>
Date: Thu, 04 Nov 2004 14:20:36 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Alan Johnston" <alan.johnston@mci.com>, Orit Levin <oritl@microsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Nov 2004 12:20:36.0102 (UTC)
	FILETIME=[B0281260:01C4C268]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Comments to cc-conferencing-05 (WGLC)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ed68cc91cc637fea89623888898579ba
Content-Transfer-Encoding: 7bit

Alan, Orit (and SIPING):

I have some comments to draft-ietf-sipping-cc-conferencing-05.txt. They 
are mostly nits. I hope you can take them into account.

- Section 3.1 reads in the second paragraph:

    "A focus SHOULD support the conference package [5] and indicate so in
    Allow-Events header fields in requests and responses. "

    I guess that we also need to say that the focus should behave as a 
notifier. Support of the conference package is not enough. I suggest 
something like:

    "A focus SHOULD support the conference event package [5], behave as 
a notifier for that package, and indicate its support in the 
Allow-Events header fields in requests and responses."

- Section 3.1 also reads in the second paragraph:

    "A focus MAY
    include information about the conference in SDP message bodies sent."

It would be good, since this is a normative statement (MAY), to indicate 
what kind of "information about the conference" we are speaking. Just to 
avoid that people have creativity in the SDP with something that wasn't 
the original intention. Presumably we are referring to i=, e=, u= and p= 
lines in SDP.

- Also Section 3.1 reads in the third paragraph:

   "A focus SHOULD support the Replaces [8] header field."

At this stage, since the usage of the Replaces headers have not been 
introduced, it would be good to have some motivation introductory text, 
something like:

    "In order to support advanced features, where a session established 
between two endpoints can migrate to a centralized conference, a focus 
SHOULD support the Replaces [8] header field."

- And more on section 3.1:

I also think we need some text in this section regarding the support of 
the Join header and the GRUU in the focus.

- Question on section 3.4:

Should the conference-aware UA support the replaces, join and GRUU? I 
guess it should be strongly recommended to implement it (perhaps a MUST).

- Section 4, Call flows, General.

I think all the Supported headers should always contain: join, replaces, 
gruu. There are some of them that do not contain 'join',  others not 
even gruu.

- Section 4, Call flows, General.

Most of the escaped URIs that in Refer-To headers are wrong. These URIs 
contain the "method" parameter, which is a URI parameter, not a header. 
Parameters are separated by semicolons ";", whereas headers are 
separated by question marks "?". Therefore, the following URI:

  Refer-To: <sip:bob@biloxi.example.com?method=REFER
               &Refer-To=sip:3402934234%40example.com>

is wrong, and should have been written as:

  Refer-To: <sip:bob@biloxi.example.com;method=REFER
               ?Refer-To=sip:3402934234%40example.com>

In case of doubt, RFC 3261 section 25.1 contains all the answers.

Suggestion: do a search for "method", and fix those which are not correct.

- Section 4, Call flows, General.

According to RFC 3264 Section 5, it is RECOMMENDED that the "s=" line in 
SDP contains a single space character (0x20) or a dash (-). The 
motivation is that SIP offers the Subject header field to describe the 
subject of a session. Therefore I recommend to follow RFC 3264 and make 
the "s=" line as recommended. It is up to you whether you want to 
include a Subject header field in the examples.

- Section 4, Call flows, General:

The Contact header field returned by the focus has the following structure:

       Contact: <sip:3402934234@example.com>;isfocus

while it is feasible to make "example.com" a hostname, and resolve to 
the focus, I found that in typical configurations "example.com" will be 
a domain name that does not resolve to any particular host. The contact 
header MUST resolve to the focus hostname.

I would find more typical that the Contact header has a clear indication 
that is host, for instance:

        Contact: <sip:3402934234@focus.example.com>;isfocus

You can argue that focus.example.com could also be a domain name, not a 
host name, which is correct. But in typical network deployments my 
proposal adheres to the typical example case.

So my suggestion is to replace the Contact header field of the focus to 
something more representative of a hostname.

As a counterpart, the RTP mixer is identified by ms5.conf.example.com 
and Alice's Contact as client.chicago.example.com, which are both 
according to what I am proposing.

- Section 4.2

I think the payloads in NOTIFYes F7 and F9 are exchanged somehow.
Alice is already a participant of the conference, so her NOTIFY F9 can 
be contain a partial information. Carol's NOTIFY F7 is the first NOTIFY 
she receives, so it should contain a full event package.

However, F7 contains a <conference-state> with version="0" and 
state="full", when it should be version="1" (or other number) and 
state="partial".

F9 contains the correct version="0", but the state="partial", when it 
should be "full".

- Section 4.2, Changing User Agents within a Conference

This is an interested case, but certainly there is nothing peculiar to 
the conferencing. In other words, this will be applicable to the 
one-to-one session. So if there is something remarkable when we apply 
this case to the conferencing framework, please explain. Otherwise, I 
don't know what is the value of this use case.

- Section 4.7, flow F1.

What is the 'conf' tag doing in a Supported header?

- Section 4.10, Bringing a Point-to-Point Session into a Conference
The second paragraph reads:

    "Alice then sends a REFER to the focus and
    includes an escaped Replaces header field in the Refer-To header
    field. "

This could be clarified by adding:

    "Alice then sends a REFER request to the focus to send an INVITE
    request ot the other participant. Alice includes an escaped
    Replaces header field in the URI included in the Refer-To header
    field. "

I am not sure if this is clearer, but I guess you get the point.

- Section 4.10

In Figure 10 the 200 OK F2 misses the isfocus parameter, so it does the 
INVITE F8. I think these are important to highlight, otherwise there 
won't be subscriptions.

Also this figure misses a SUBSCRIBE/NOTIFY between Alice and the Focus, 
right after the ACK F3. Without this SUBSCRIBE, the NOTIFY F15 does not 
exist.

- Section 4.11

s/&ltsip:/<sip:

- Section 4.12:

In Figure 12 the arrow of message F4 is reversed.

- Section 4.13, Flow F2:

This is a 200 OK response for an OPTIONS request. So the SDP should be 
in conformance with RFC 3264 section 9. Specifically the port numbers in 
the "m=" lines should be set to 0.

Also in this SDP, I noticed that the "m=audio" line contains a codec of 
type 1, but this type is "reserved" in RFC 3551, so I would suggest to 
delete it.

- Section 4.13.

Add references to the relevant RFCs in:

    "Supported.  The support of extensions such as replaces, join, and
    gruu."

    "Contact.  The presence of the "isfocus" feature parameter in the
    Contact header indicates that the URI is a conference URI and that
    the UA is a focus."

- Section 5.

If this is an appendix, it should be placed towards the end of the 
document, after the Acknowledgments and before the References section.

- Section 14 needs a few updates

Reference [1] is never used, but it should. I guess you need to add 
somewhere the typical terminology explanation "MUST", "SHOULD", etc. and 
refer to RFC 2119.

Reference [5] is now -06

Reference [6] is now RFC 3911

Reference [7] is now RFC 3840

Reference [12] seems to be expired, so you should delete this reference 
and delete the link to it.

Reference [16] is never used, so you can delete it.

Reference [17] is now -03

Reference [18] seems to be expired, but I assume this has been an error.





Best regards,

        Miguel


-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov  4 11:07:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04912
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 11:07:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPkP5-0007wl-Cf
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 11:24:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPk4I-0006Jk-1e; Thu, 04 Nov 2004 11:02:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPjuD-0003t4-VB
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 10:52:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02901
	for <sipping@ietf.org>; Thu, 4 Nov 2004 10:52:08 -0500 (EST)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPk9m-0007X4-8K
	for sipping@ietf.org; Thu, 04 Nov 2004 11:08:14 -0500
Received: from [131.161.248.87] (open-131-161-248-87.cliq.com [131.161.248.87])
	(authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iA4FpwC16771;
	Thu, 4 Nov 2004 07:51:58 -0800
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <664FE420-2E79-11D9-9263-000D93C60450@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Date: Thu, 4 Nov 2004 07:51:32 -0800
To: sipping@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>,
        "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] Clarification about WGLC of App Interaction
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Hi,

To clarify, we started a WGLC on App Interaction in both SIP and 
SIPPING.  Despite the filename of the current version of the draft 
(draft-ietf-sipping...), please send your comments to the SIP mailing 
list.

Many 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


From sipping-bounces@ietf.org  Thu Nov  4 14:51:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26824
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 14:51:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPnts-0005Bt-Lg
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 15:08:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPnUf-0005vW-D5; Thu, 04 Nov 2004 14:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPnPm-0004zP-Pl
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 14:36:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25582
	for <sipping@ietf.org>; Thu, 4 Nov 2004 14:36:57 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPnfF-0004s7-1g
	for sipping@ietf.org; Thu, 04 Nov 2004 14:53:05 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 04 Nov 2004 11:49:10 -0800
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iA4JaFcp022369;
	Thu, 4 Nov 2004 11:36:16 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMU60831; Thu, 4 Nov 2004 14:36:14 -0500 (EST)
Message-ID: <418A84AE.9050106@cisco.com>
Date: Thu, 04 Nov 2004 14:36:14 -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: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>,
        "Peterson,
	Jon" <jon.peterson@neustar.biz>
Subject: [Sipping] Re: draft-ietf-sipping-certs-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit

1) cert caching

                             "The UA needs to cache this certificate for
    future use.  The certificate MUST be removed from the cache if it has
    expired, if it is updated by a subsequent NOTIFY, or if the
    subscription has been terminated."

This implies that I must have an active subscription to anyone I may 
want to call. Since there tends to be very little call locality, that 
means a lot of subscriptions active all the time, or else establishing 
and ending a subscription for each call. Why not just admit that caching 
may be done after the subscription terminates, until the cert expires, 
at the risk of missing a revocation?

2) NOTIFY addressing

   "When the Credential Server receives a SUBSCRIBE for a certificate, it
    first checks to see if it has credentials for the requested URI.  If
    it does not it returns a response indicating the user was not found.
    Otherwise it sets up a subscription and forms a NOTIFY with the
    certificate in the body and the From header field value set to the
    request URI of the SUBSCRIBE."

The credential server has no choice about what to put in the From header 
of the Notify - it is determined by the dialog of the subscription, and 
will equal the To header of the Subscribe. It is likely that the To 
header and request header will be the same in this case, but that is not 
certain.

3) Server storing private keys

Having the credential server store the private keys means they are 
potentially in the hands of an organization subject to legal 
requirements for key disclosure. As a result, sessions secured with 
these credentials may be subject to wire tap. As a work-around to this, 
how about making the secret key optional when publishing and subscribing 
to the credentials. If a credential is published without a secret key, 
it will be distributed without. Then only those endpoints that have the 
private key can successfully use the credential - typically the device 
that published it.

4) multipart/alternative and offer

   "If a UA receives both an unencrypted and an encrypted SDP offer in an
    multipart/alternative body, it interprets these as it would a normal
    multipart alternative as defined in RFC 2046 [16], which means it
    picks the last alternative that it can support.  Any bodies that
    cannot be decrypted are treated as unsupportable.  The sending UA
    should generally put encrypted offers after unencrypted ones, since
    encrypted ones are preferred."

There is an issue of knowing whether an encrypted offer is in fact an 
offer or not. Offers (and answers) are recognized by Content-Disposition 
  of session. But in case of encrypted sdp, we have no rules that say 
what the content-disposition of the encrypted body must be - it will 
only be after decryption that the content disposition of the encrypted 
body was.

It may be that when using multipart/alternative, we specify that *it* 
must contain a content-disposition, which matches that of everything in 
it, and that a application/pkcs7-mime must also be tagged with the c-d 
of its content.

5) multipart/alternative and answer

                                  "The UA constructs the answer to the
    offer as it normally would and may include both encrypted and
    unencrypted versions of the answer using multipart/alternative."

Is this necessary? Is there a case where the answerer doesn't know 
whether the offerer will be able to decrypt the answer? For that matter, 
if the offer was encrypted, does it ever make sense for the answer to 
not be encrypted?

6) event type for certs

     SUBSCRIBE sip:bob@biloxi.example.com SIP/2.0
     ...
     Event: certificate

Isn't the event type supposed to be pkix-cert? (According to section 4.)


	Paul

P.S. "I'm over at Osama's house at 21.25'24"N 39.49'24"E" -
      I see you did your homework. Or were you carrying a GPS
      when you visited? :-)






_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov  4 20:07:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29856
	for <sipping-web-archive@ietf.org>; Thu, 4 Nov 2004 20:07:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPspb-0004bA-Ga
	for sipping-web-archive@ietf.org; Thu, 04 Nov 2004 20:23:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPsYD-0008QM-Ag; Thu, 04 Nov 2004 20:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPsV0-0007tg-VM
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 20:02:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29214
	for <sipping@ietf.org>; Thu, 4 Nov 2004 20:02:39 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPskd-0004Rz-E0
	for sipping@ietf.org; Thu, 04 Nov 2004 20:18:52 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 04 Nov 2004 17:15:05 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA5126om010677;
	Thu, 4 Nov 2004 17:02:07 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATT13766;
	Thu, 4 Nov 2004 17:02:08 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Thu, 04 Nov 2004 17:02:07 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, sipping <sipping@ietf.org>
Message-ID: <BDB0110F.186FB%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: 7bit
Subject: [Sipping] presence-rules-01 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit


In the transformations, is there a way to say "everything"




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 00:05:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17606
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 00:05:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPwXa-0000zT-7i
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 00:21:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPwFX-0005mB-Bj; Fri, 05 Nov 2004 00:02:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPwAq-0004sD-EA
	for sipping@megatron.ietf.org; Thu, 04 Nov 2004 23:58:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17271
	for <sipping@ietf.org>; Thu, 4 Nov 2004 23:58:05 -0500 (EST)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPwQV-0000s8-DS
	for sipping@ietf.org; Fri, 05 Nov 2004 00:14:19 -0500
Received: from [172.16.16.127] (da001d4094.stl-mo.osd.concentric.net
	[66.236.111.254]) (authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iA54vtC25397;
	Thu, 4 Nov 2004 20:57:55 -0800
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <336270A0-2EE7-11D9-B7B4-000D93C60450@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Date: Thu, 4 Nov 2004 20:57:31 -0800
To: sipping@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, hgs@cs.columbia.edu
Subject: [Sipping] dialog package -05 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Hi,

Due to a careless mistake on my part, I submitted the -05 version of  
the dialog package with the old boilerplate, and did not notice in time  
to resubmit.

I have revised -05 with the new boilerplate, but will not be able to  
resubmit until after IETF 61.  In the interim, the version I will  
submit is located in the sipfoundry repository (with companion HTML  
version):

https://scm.sipfoundry.org/rep/ietf-drafts/rohan/dialog-pkg/draft-ietf- 
sipping-dialog-package-05.txt
https://scm.sipfoundry.org/rep/ietf-drafts/rohan/dialog-pkg/draft-ietf- 
sipping-dialog-package-05.html

I believe this version incorporates all the comments received to date.   
Feel free to speak up if you notice any other issues.

many 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


From sipping-bounces@ietf.org  Fri Nov  5 05:12:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25036
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 05:12:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ1Kr-00070F-F6
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 05:28:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ0Sv-00062H-Kj; Fri, 05 Nov 2004 04:33:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ0Rh-0005gR-HJ
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 04:31:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19906
	for <sipping@ietf.org>; Fri, 5 Nov 2004 04:31:47 -0500 (EST)
Received: from smtp8.clb.oleane.net ([213.56.31.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ0hP-0005tI-96
	for sipping@ietf.org; Fri, 05 Nov 2004 04:48:03 -0500
Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be
	forged)) by smtp8.clb.oleane.net with ESMTP id iA59VB6c023150
	for <sipping@ietf.org>; Fri, 5 Nov 2004 10:31:17 +0100
Message-Id: <200411050931.iA59VB6c023150@smtp8.clb.oleane.net>
From: "Gunther Palmer" <g.palmer@dial.oleane.com>
To: <sipping@ietf.org>
Date: Fri, 5 Nov 2004 10:31:14 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTDGjGpQbuT49pxR6OvSgrjRxMi8w==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Subject: [Sipping] WiMAX Summit: Call for proposals
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0778244440=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48

This is a multi-part message in MIME format.

--===============0778244440==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0112_01C4C322.93CF7E90"

This is a multi-part message in MIME format.

------=_NextPart_000_0112_01C4C322.93CF7E90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

. What is the business model for WiMAX? 
. What do we learn from earlier deployments? 
. What about the future extensions of the standard? 
. How is addressed the interoperability challenge? 

These questions, among others, will be addressed during the second edition
of the WiMAX Summit, next April 5-8 2005, by distinguished experts and key
players in the field.

 

The call for proposal dead line has been extended to November 30.

 

Details at:

 <http://www.upperside.fr/wimax05/wimax2005intro.htm>
http://www.upperside.fr/wimax05/wimax2005intro.htm

 


------=_NextPart_000_0112_01C4C322.93CF7E90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Arial'>&#8226; =
</span></font></b></strong><font
size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'>What
is the <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>business
model</span></font></b></strong> for WiMAX? <br>
<strong><b><font face=3DArial><span style=3D'font-family:Arial'>&#8226; =
</span></font></b></strong>What
do we learn from <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>earlier
deployments</span></font></b></strong>? <br>
<strong><b><font face=3DArial><span style=3D'font-family:Arial'>&#8226; =
</span></font></b></strong>What
about the <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>future
extensions</span></font></b></strong> of the standard? <br>
<strong><b><font face=3DArial><span style=3D'font-family:Arial'>&#8226; =
</span></font></b></strong>How
is addressed the <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>interoperability</span></font></b></strong>
challenge? <br>
<br>
These questions, among others, will be addressed during the second =
edition of
the <strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>WiMAX Summit,
next April 5-8 2005</span></font></b></strong>,&nbsp;by distinguished =
experts
and key players in the field.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The call for proposal dead line has been =
extended to
November 30.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Details at:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a =
href=3D"http://www.upperside.fr/wimax05/wimax2005intro.htm"
title=3D"http://www.upperside.fr/wimax05/wimax2005intro.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/wimax05/wimax2005intro.htm</span></a=
></span></font><font
size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0112_01C4C322.93CF7E90--



--===============0778244440==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0778244440==--




From sipping-bounces@ietf.org  Fri Nov  5 12:42:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01946
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 12:42:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ8MS-0008Ou-01
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 12:58:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ7s9-0000pS-Hh; Fri, 05 Nov 2004 12:27:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7gf-0005Px-Uk
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 12:15:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29783
	for <sipping@ietf.org>; Fri, 5 Nov 2004 12:15:43 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ7wO-0007pd-Gc
	for sipping@ietf.org; Fri, 05 Nov 2004 12:32:04 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 09:26:02 -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.10/8.12.6) with ESMTP id iA5HF8cp025340;
	Fri, 5 Nov 2004 09:15:08 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATT55549;
	Fri, 5 Nov 2004 09:15:08 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 09:15:08 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB0F51C.18813%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit
Cc: volkerh@bell-labs.com,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Subject: [Sipping] session-spec-policy-01 and session-indep-policy-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: 7bit


My meta comments is that this seems to be getting close on many of the "how
the policy is moved around" issues but still seem like fairly early work on
the "what the policy document is" stuff.

Right now it is trying to be an incredibly flexible do anything type
framework and I think that is a mistake. I think we should limit it down to
being able to meet the requirements described mostly in
draft-ietf-sipping-session-policy-req-02 - particularly the stuff in section
3.3. 

In the session spec policy ...

This is session spec policy, so, when the UA goes to the policy server, I'm
sure it has to provide some information about the session so the server can
provide the policy. I can't figure out how this happens reading the draft.

You need to decide  if the policy server is just providing hints that all
the UA not to violate the policy or if it  is doing something more. It it is
just a hint, then I don't think you need the token - you just need a flag
that say's yes, I have talked to the appropriate policy server. This will be
much easier to secure than something where the token has security
properties.

I can't imagine how this will work without needing it for answers as well as
offers. The example in section 4.2 PS-A will need to know the port that UA-A
put  in the answer so that it can open an pin hole in a firewall to allow
media to UA-A. 

I think this could be improved by specifically saying that what is revealed
to the PS in both an offer and answer case and was clear how the PS would
tell the UA to change the offer or answer in the case where the RTP
port/address needed to be changed.

We need to say how the PS informs the UA of DSCP and other QOS parameters.

The PS should be able to add per codec bandwidth and pps limits.

I think that SUB/NOT is a reasonable approach to talk to the PS. The reason
why is that any other choice is going to get you into a very complicated
story on how to authenticate things back and forth.


Moving on to indep-policy ....

Again, I think we can meet the requirements with something much simpler that
avoids most of the problems I bring up below.

I would add a  packets per seconds max per stream and per session. This is
important on 802.11 networks.

We need more on what to do with conflicts. The idea that an UA should alert
on a conflict is not really enough. Should say the UA should attempt the
call if there is a conflict? What about if the conflict is during a 911
call?

In the example in 4.4.3, is has RTP/AVP in the set_all. Since I must set
this, I assume I can not set SRTP. I don't get how I can optional use that.

What is an implementation supposed to do if it says forbid X and set_all X.
Which wins? 

How do I say you can use 300kbps for video but only 30kbps for audio.

Basically I think the current scheme is going to be incredibly difficult to
implement with different corner cases on all the implementation that make it
easy to come up with "invalid" policies that get circumvented in weird ways.

This is the same problem we have with all merged policy - if we just had
positive permissions, or just had negative permissions, it would be easier.
I sort off doubt we can do that in this case but perhaps someone can figure
out how. If we can't do this, I think we can still easily solve the
requirements at hand with specific instead of general solutions with
specific advice on how to merge and deal with conflicts.

Consider something like the following.

  We have a list of allowed codec in preferred order and they merger based
on nearest proxy on the signaling path having priority.

  We have a list of forbidden codecs.

  We have max session/stream bandwidth and pps that merge in obvious way.

  We have that these are clearly hints and conflicts should be ignored for
emergency calls but call should not be made for non emergency calls.

  A min and max RTP port that is allowed - these merge in obvious way.

  A DSCP that should be used.

  For each codec, a DSCP that should be used.


The include/exclude target stuff is very confusing on how it relates to the
selection of rules - needs clarification.

I did not see requirement for transport or direction stuff. Or the protocol
stuff which seems really confusing right now.

The media policy address stuff does not make sense. This is an IP that the
UA uses in the SDP then just sends from it's normal IP? You won't have to do
things with the port on a per session basis? I am suspicions that this only
makes sense in the session dependent work.













_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 12:44:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02070
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 12:44:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ8ON-0008S6-FA
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 13:00:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ7sA-0000qA-Vr; Fri, 05 Nov 2004 12:27:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7gh-0005Q0-2C
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 12:15:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29786
	for <sipping@ietf.org>; Fri, 5 Nov 2004 12:15:44 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ7wI-0007pP-2A
	for sipping@ietf.org; Fri, 05 Nov 2004 12:32:05 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 05 Nov 2004 09:28:06 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA5HF1cp025217;
	Fri, 5 Nov 2004 09:15:01 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATT55543;
	Fri, 5 Nov 2004 09:15:00 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 09:14:59 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB0F513.18813%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Subject: [Sipping] session-policy-req-02
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit


The draft says ...

   REQ-POL-11: The solution should allow proxies to request that Quality
      of Service (QoS) should be requested for a stream.
   REQ-POL-12: The solution should allow proxies to ask endpoints to use
      specific parameters in their QoS reservations.
   REQ-POL-13: The solution should allow proxies to ask endpoints to
      provide a specific credential in their QoS requests.  This
      requirement covers the functionality currently described in [9].

I agree with these but think we should get more specific about what we mean
here. I assume we mean DSCP values for one. Do we mean something specific
for RSVP? 




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 16:02:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17096
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 16:02:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQBU1-0004A6-Ru
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 16:18:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQB5w-0003o8-CS; Fri, 05 Nov 2004 15:54:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQB1p-0000zJ-4C
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 15:49:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16198
	for <sipping@ietf.org>; Fri, 5 Nov 2004 15:49:47 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQBHd-0003sH-5L
	for sipping@ietf.org; Fri, 05 Nov 2004 16:06:09 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 05 Nov 2004 13:02:21 -0800
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA5Kn9om010747;
	Fri, 5 Nov 2004 12:49:10 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMV51136; Fri, 5 Nov 2004 15:49:13 -0500 (EST)
Message-ID: <418BE749.10702@cisco.com>
Date: Fri, 05 Nov 2004 15:49:13 -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: fluffy@cisco.com, alan@jasomi.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Re: draft-jennings-sipping-outbound-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Cullen,

Great job of pulling together the semi-coherent mumblings from the last 
meeting to produce a draft that actually makes sense. A couple of small 
points:

4.4  Edge Proxies and Redirection

    Still work TODO here ...  If Alice calls Bob, the Registrar for Bob
    can send a 302 redirecting Alice to Bob's edge proxy.  TODO show how
    the path header that the edge proxy put in the Register gets copied
    to Alice and returned to the edge proxy and thus the whole thing
    works out fine.

Why invent some new mechanism for this. Alice should have requested a 
GRUU. Redirections should return the GRUU. (It may require a change to 
the gruu draft to clarify that should happen.) Use of the gruu ends up 
at proxy that is aware of registration and can use the path.

There may be optimizations to this, where the gruu itself homes on the 
edge proxy. That would make life simpler still, at least for this problem.

-----

There are corner cases that will need to be considered eventually. (But 
maybe not yet. Lets get the major issues ironed out first.)

One is if the registrar receives a registration where the instance id 
and contact address match an existing one, the connection id differs, 
and other contact parameters differ?

	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 sipping-bounces@ietf.org  Fri Nov  5 16:21:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19379
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 16:21:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQBWg-0004fx-Tj
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 16:21:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQBQ2-0007Go-Q5; Fri, 05 Nov 2004 16:14:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQBOJ-00065l-Fh
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 16:13:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18670
	for <sipping@ietf.org>; Fri, 5 Nov 2004 16:13:01 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQBOI-0004SK-06
	for sipping@ietf.org; Fri, 05 Nov 2004 16:13:03 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 13:23:24 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iA5LCOcr027402;
	Fri, 5 Nov 2004 13:12:29 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMV53304; Fri, 5 Nov 2004 16:12:24 -0500 (EST)
Message-ID: <418BECB8.4010008@cisco.com>
Date: Fri, 05 Nov 2004 16:12:24 -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>,
        sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: draft-ietf-sipping-uri-list-message-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Gonzalo,

One small point:

When the list server generates the recipient-list in the outbound 
messages, I think it should be specifying:

	Content-Disposition: recipient-list;handling=optional

This way a recipient that doesn't understand this part will be free to 
ignore it. As currently specified, since it isn't specified, the 
handling defaults to required, and a well behaved mime processor should 
consider it an error if it doesn't understand what to do with it.

	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 sipping-bounces@ietf.org  Fri Nov  5 16:27:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19760
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 16:27:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQBcK-0004nm-Q0
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 16:27:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQBWY-0001Rk-Cj; Fri, 05 Nov 2004 16:21:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQBQ1-0007Fx-IU
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 16:14:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18797
	for <sipping@ietf.org>; Fri, 5 Nov 2004 16:14:47 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQBPy-0004V1-OZ
	for sipping@ietf.org; Fri, 05 Nov 2004 16:14:49 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iA5L2p8q012498; Fri, 5 Nov 2004 16:02:54 -0500 (EST)
Received: by nhmail2.eng.brooktrout.com with Internet Mail Service
	(5.5.2653.19) id <PQMPPJKW>; Fri, 5 Nov 2004 15:59:58 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331C10F24@nhmail2.eng.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: Rajiv Dharmadhikari <rajivdh@genesyslab.com>
Date: Fri, 5 Nov 2004 15:59:03 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: sipping@ietf.org
Subject: [Sipping] RE: Question related to netann draft
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Netann just says how to launch something, so mid-call events via INFO would
not violate netann.

That said, returning results from VoiceXML in SIP is a MAJOR VIOLATION OF
THE VOICEXML MODEL.  Big, Bad No-No.  We've discussed this here and in the
W3C.
See:
http://www1.ietf.org/mail-archive/web/sipping/current/msg03015.html
http://lists.w3.org/Archives/Public/www-voice/2004AprJun/0028.html (the
whole thread isn't there; that's the summary; go to the beginning of the
thread for the full juice of why this is a VERY BAD idea).

The big breakdown is a voice browser expects the next page after a submit.
One could recreate HTTP with SIP INFO's, but I don't think that would get
much traction here :)


> -----Original Message-----
> From: Rajiv Dharmadhikari [mailto:rajivdh@genesyslab.com]
> Sent: Monday, November 01, 2004 1:18 AM
> To: eburger@brooktrout.com
> Cc: sipping@ietf.org
> Subject: Question related to netann draft
> 
> 
> Eric,
> 
> This is a resend as I am not sure original email got posted 
> on the mailing list. 
> 
> Section 4 of 'netann' draft describes how VoiceXML 
> applications can be invoked by an external Application 
> Server. It is also expected that results would be posted back 
> to application server via HTTP POST mechanism. In true SIP 
> and VoiceXML world this works fine. When it comes to legacy 
> IN networks, you may not have a true application server. Even 
> if there is some way to launch VoiceXML scripts through 
> 'netann' model, posting results is tricky. Would some 
> mid-call signaling method like SIP INFO to send results be 
> violating spirit of 'netann'? 
> 
> I am copying this to the mailing list to see if others have 
> opinion on this topic.
> 
> Thanks,
> 
> -Rajiv
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 16:55:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22658
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 16:55:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQC3U-0005W0-2o
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 16:55:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQC2N-0008D5-Qb; Fri, 05 Nov 2004 16:54:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQBwm-00073N-1R
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 16:48:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21931
	for <sipping@ietf.org>; Fri, 5 Nov 2004 16:48:37 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQBwl-0005Mv-Rv
	for sipping@ietf.org; Fri, 05 Nov 2004 16:48:40 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 05 Nov 2004 16:48:10 -0500
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA5Lm49D019025; 
	Fri, 5 Nov 2004 16:48:05 -0500 (EST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMV56988; Fri, 5 Nov 2004 16:48:05 -0500 (EST)
Message-ID: <418BF515.9040409@cisco.com>
Date: Fri, 05 Nov 2004 16:48:05 -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: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] Re: draft-ietf-sipping-uri-list-message-01
References: <418BECB8.4010008@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>,
        Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit

Oops! One more thing - maybe more significant:

You are overloading the recipient-list semantics - to the list server is 
specifies who to send the message to, while to the ultimate recipient it 
identifies who the message *was* sent to. But what happens if one of the 
recipients happens to be a message list server? Nothing good.

To solve this you could use a different content-disposition type, or you 
might consider introducing parameters to the recipient-list 
content-disposition to distinguish these uses. The simplest might be to 
simply use content-disposition of "render", while continuing to use the 
application/resource-lists+xml content-type.

(The need for handling=optional remains.)

	Paul

Paul Kyzivat wrote:
> Gonzalo,
> 
> One small point:
> 
> When the list server generates the recipient-list in the outbound 
> messages, I think it should be specifying:
> 
>     Content-Disposition: recipient-list;handling=optional
> 
> This way a recipient that doesn't understand this part will be free to 
> ignore it. As currently specified, since it isn't specified, the 
> handling defaults to required, and a well behaved mime processor should 
> consider it an error if it doesn't understand what to do with it.
> 
>     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 sipping-bounces@ietf.org  Fri Nov  5 18:39:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01343
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 18:39:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQDfg-0007jw-K3
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 18:39:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQDWl-0003o2-4q; Fri, 05 Nov 2004 18:29:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQDQe-0002Yi-0O
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 18:23:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00625
	for <sipping@ietf.org>; Fri, 5 Nov 2004 18:23:33 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQDQd-0007Sm-Hg
	for sipping@ietf.org; Fri, 05 Nov 2004 18:23:37 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 05 Nov 2004 15:23:10 -0800
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iA5NMxJZ002022;
	Fri, 5 Nov 2004 15:23:00 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMV63688; Fri, 5 Nov 2004 18:22:58 -0500 (EST)
Message-ID: <418C0B51.9010801@cisco.com>
Date: Fri, 05 Nov 2004 18:22:57 -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: mahfuz@research.panasonic.com, kumarb@research.panasonic.com,
        bhu@Motorola.com, a.ahmed@ntt.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Re: draft-rahman-sipping-device-info-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

I'm not getting a clear understanding from this draft of what the 
granularity of a device is, or how you intend to address a device.

For example, lets assume I have a PC. On it I have two sip software 
agents: a softphone and an IM client. The softphone supports two "lines" 
(addresses), and the IM client supports a third address. For each of 
these addresses, there is an AOR, and a local contact that is registered 
with the corresponding AOR. The PC is behind a NAT, so it doesn't have 
stable contact addresses. So each time it registers, it requests a GRUU.

Summarizing:

PC IP address: 10.0.1.1

Softphone
- local sip address: 10.0.1.1:5060
- NATed address: 192.0.2.88:8866
- line 1
   - AOR: sip:alice@atlanta.com
   - contact: sip:line1@10.0.1.1:5060;instance=id="uuid:stuff"
   - GRUU: sip:lkjhg-alice@atlanta.com;grid=1
- line 2
   - AOR: sip:alice@biloxi.com
   - contact: sip:line2@10.0.1.1:5060;instance-id="uuid:stuff"
   - GRUU: sip:xcvbnm-alice@biloxi.com;grid=2
IM client
- local sip address: 10.0.1.1:7654
- NATed address: 192.0.2.88:8872
- AOR: sip:alice@IMs-R-us.com
- contact: sip:10.0.1.1:7654;instance-id="uuid:something"
- GRUU: sip:rtyuiop-alice@IMs-R-us.com

How does the device-info event package get used in this context?

- from your point of view, how many devices are there here?
- which of the above addresses can I use to invoke it?
   (Or do you imagine a separate "device address"?)
- does the answer I get depend on which address I use?
- should there be any tie between the data in the device info
   package and the instance-id used for GRUU?


	Thanks,
	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 sipping-bounces@ietf.org  Fri Nov  5 20:24:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09620
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 20:24:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQFJZ-0001uP-O6
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 20:24:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQF8e-00048s-1u; Fri, 05 Nov 2004 20:13:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQF16-0001sK-NH
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 20:05:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08547
	for <sipping@ietf.org>; Fri, 5 Nov 2004 20:05:17 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQF17-0001Vf-AY
	for sipping@ietf.org; Fri, 05 Nov 2004 20:05:22 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 05 Nov 2004 17:17:54 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA614OnC028180;
	Fri, 5 Nov 2004 17:04:24 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU04415;
	Fri, 5 Nov 2004 17:04:45 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 17:04:45 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB1632D.189B9%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] consent-framework-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit


I like this but I have one big comments. I'm not convinced yet that we need
to make it dependent on XCAP. I'm fine if XCAP is one of the ways to move
the permissions around, but for most simple cases, it seems like the same
Common Policy style permissions and requests could be carried in CONSENT
req/resp and in the SUB/NOT req/resp.

We want to make this CONSENT must implement and making XCAP must implement
for a wide range of devices scares me.

Security section still TBD :-) Given the amount of email to emails lists
that claims it is from me when I did not send it, I think that strong sender
based identity should be a MUST implement for this work.







_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 20:27:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09810
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 20:27:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQFMC-0001yW-Vv
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 20:27:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQF8f-00049K-0y; Fri, 05 Nov 2004 20:13:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQF1B-0001si-Nj
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 20:05:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08559
	for <sipping@ietf.org>; Fri, 5 Nov 2004 20:05:22 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQF1D-0001Vq-9U
	for sipping@ietf.org; Fri, 05 Nov 2004 20:05:27 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 17:15:50 -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.10/8.12.6) with ESMTP id iA614qcp012972;
	Fri, 5 Nov 2004 17:04:52 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU04422;
	Fri, 5 Nov 2004 17:04:52 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 17:04:51 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB16333.189B9%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] consent-req-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit


I like it

Req 18. "note" should be "not"

I would like to add a requirement that...

When a relay sends a message to a users, it should be possible for the user
to figure out which permissions server granted permission for that action
and also any credentials that the user would need to revoke that permission.

 




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 20:29:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09961
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 20:29:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQFOS-000228-OH
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 20:29:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQF8f-00049Z-Ts; Fri, 05 Nov 2004 20:13:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQF1C-0001sk-6w
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 20:05:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08563
	for <sipping@ietf.org>; Fri, 5 Nov 2004 20:05:22 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQF1D-0001Vq-Pn
	for sipping@ietf.org; Fri, 05 Nov 2004 20:05:28 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 17:15:56 -0800
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.10/8.12.6) with ESMTP id iA614som023120;
	Fri, 5 Nov 2004 17:04:54 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU04423;
	Fri, 5 Nov 2004 17:04:57 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 17:04:57 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB16339.189B9%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: Daniel Petrie <dpetrie@pingtel.com>,
        Scott Lawrence <slawrence@pingtel.com>
Subject: [Sipping] profile-datasets-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit


This seems to have gotten tangled up into the policy work in sort of scary
way. The phone know if it supports g711 or not - what I want to configure
into my phone is what the username and AOR are, an outbound proxy, a speed
dial list, things like that.

Not clear what a UA subscribes to to get a particular dataset.

I think you intend to do this but  - we have to deal with the access control
in section 4.2 from the beginning because we won't be able to add it in a
backwards compatible way.

4.3.1 might want to expand iff

I hate the forbid, set_all, set_one etc stuff in this. This is not a
document to describe to a phone how to render a user interfaces for the user
to select how to configure the phones. It's the data that is the
configuration for the phone.

I think the scheme is more complicated that is needed or will get
implemented on low end devices.

I like the much simpler earlier versions of this work much better.

We have to address the merging issues not just leave it TBD and I suspect
that it is data specific.

I like the lists of things in section 6 - let's expand those out .

Section 7.2 - are we trying to describe phone capabilities to the server or
have the server reflect preferences to the phone or what.





_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 20:31:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10121
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 20:31:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQFQJ-00025G-Ur
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 20:31:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQF8g-00049f-Jc; Fri, 05 Nov 2004 20:13:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQF1D-0001sm-N3
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 20:05:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08567
	for <sipping@ietf.org>; Fri, 5 Nov 2004 20:05:24 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQF1E-0001Vq-Ar
	for sipping@ietf.org; Fri, 05 Nov 2004 20:05:29 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 17:16:03 -0800
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.10/8.12.6) with ESMTP id iA6152om023233;
	Fri, 5 Nov 2004 17:05:02 -0800 (PST)
Received: from [10.32.131.248] ([10.32.131.248])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU04430;
	Fri, 5 Nov 2004 17:05:05 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 17:05:05 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB16341.189B9%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: Daniel Petrie <dpetrie@pingtel.com>
Subject: [Sipping] config-framework
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit


I like how this is going and it is looking like it is getting close.

How the security works with content indirection confuses me. Say that the
scheme is HTTPS - how do I get a username password to the phone that is uses
for the HTTPS. How do I protect that. The odds that device has a cert that
the HTTPS server can use seems very low to me - at best it would indicate
hostname and that is not going to be useful in requesting a user profile
information such as buddy list.

I think we need to say that HTTP and HTTPS are must implement schemes for
content indirection if it is implemented.

Seems to have some bad characters in it.

Should vendor names be arbitrary self assigned strings or should they be a
domain that the vendors controls java style: ie "cisco" or "com.cisco"

Not sure I see why we need both document and app-id - I may be very confused
here

might need to describe hotelling where it is first used

On the topic of device URI, I tend to be on the path these days that UUID
should be strongly recommended.

Section 4.4 - tilt nit but the say this is written the SHOULD makes it
unclear if any MUST in section 6 is actual a SHOULD. I think should should
move the should to be just non normative here so that the normative language
in other sections is clear what it means.

split references to normative non normative

idnits says...
  Warnings:
    Line 507 has weird spacing: '...ication  of pr...'
    Line 871 has weird spacing: '...hat the  admin...'
    Line 1337 has weird spacing: '...Changes  in XM...'




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov  5 22:15:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17513
	for <sipping-web-archive@ietf.org>; Fri, 5 Nov 2004 22:15:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQH2m-0004IV-SJ
	for sipping-web-archive@ietf.org; Fri, 05 Nov 2004 22:15:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQGuR-0007zP-1n; Fri, 05 Nov 2004 22:06:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQGmv-0005SX-6l
	for sipping@megatron.ietf.org; Fri, 05 Nov 2004 21:58:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16023
	for <sipping@ietf.org>; Fri, 5 Nov 2004 21:58:46 -0500 (EST)
Received: from web53401.mail.yahoo.com ([206.190.37.48])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQGmx-0003nq-Er
	for sipping@ietf.org; Fri, 05 Nov 2004 21:58:51 -0500
Message-ID: <20041106025817.52976.qmail@web53401.mail.yahoo.com>
Received: from [24.147.233.128] by web53401.mail.yahoo.com via HTTP;
	Fri, 05 Nov 2004 18:58:17 PST
X-RocketYMMF: dgpetrie
Date: Fri, 5 Nov 2004 18:58:17 -0800 (PST)
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
In-Reply-To: <BDB16341.189B9%fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: Daniel Petrie <dpetrie@pingtel.com>
Subject: [Sipping] Re: config-framework
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpetrie@pingtel.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003

Cullen:
Thanks for the comments.  Response inline:

Cheers,
Dan

--- Cullen Jennings <fluffy@cisco.com> wrote:

> 
> I like how this is going and it is looking like it
> is getting close.
> 
> How the security works with content indirection
> confuses me. Say that the
> scheme is HTTPS - how do I get a username password
> to the phone that is uses

I only see two choices here:  Either the UA has
a cert. and the server validates it against the
identity somehow;  Or a RFC 2617 basic/digest based
password gets put on the UA through some out of band
means (e.g. typed in by user, SIM, bluetooth, etc.)

> for the HTTPS. How do I protect that. The odds that

"That" meaning protect the password stored on the user
agent? That sounds like an implementation problem of
how to safely store the password on the UA not an IETF
problem.

> device has a cert that
> the HTTPS server can use seems very low to me - at
> best it would indicate
> hostname and that is not going to be useful in
> requesting a user profile
> information such as buddy list.

I agree RFC 2617 based authentication seems like a 
more likely and simpler solution.

> 
> I think we need to say that HTTP and HTTPS are must
> implement schemes for
> content indirection if it is implemented.

Ok.  I have added this to the sections 3.5 and 3.8 for
the next draft version

> 
> Seems to have some bad characters in it.
> 
> Should vendor names be arbitrary self assigned
> strings or should they be a
> domain that the vendors controls java style: ie
> "cisco" or "com.cisco"
> 
> Not sure I see why we need both document and app-id
> - I may be very confused
> here

I may be as well, but I will attempt to explain.
The document parameter may contain a relative path.
It the first path segment can be either global or
a user specific id.  If that is as far as the path
is specified, app-id may be used to further constrain
what profile data is desired.


> 
> might need to describe hotelling where it is first
> used

Added definitions for roaming and hotelling to section
2.2

> 
> On the topic of device URI, I tend to be on the path
> these days that UUID
> should be strongly recommended.
> 

I still do not understand why we care how the instance
id is generated any more than we care for call-id.
I think it is fine to make a recommendation, but
this is an implementation issue.

> Section 4.4 - tilt nit but the say this is written
> the SHOULD makes it
> unclear if any MUST in section 6 is actual a SHOULD.
> I think should should
> move the should to be just non normative here so
> that the normative language
> in other sections is clear what it means.

Will do.

> 
> split references to normative non normative

Will do.

> 
> idnits says...
>   Warnings:
>     Line 507 has weird spacing: '...ication  of
> pr...'
>     Line 871 has weird spacing: '...hat the 
> admin...'
>     Line 1337 has weird spacing: '...Changes  in
> XM...'
> 

Thanks. Fixed the first two the second one is in
the xcap-package reference.

> 
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 01:05:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28627
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 01:05:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQJhZ-0007Sm-Tj
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 01:05:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQJWL-0007I2-Dp; Sat, 06 Nov 2004 00:53:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQJPe-0006KR-0r
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 00:46:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27591
	for <sipping@ietf.org>; Sat, 6 Nov 2004 00:46:54 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQJPh-00074D-Ss
	for sipping@ietf.org; Sat, 06 Nov 2004 00:47:02 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 21:57:24 -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.10/8.12.6) with ESMTP id iA65jXnC014379;
	Fri, 5 Nov 2004 21:45:33 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn1-488.cisco.com [10.21.97.232])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU14331;
	Fri, 5 Nov 2004 21:46:22 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 21:08:29 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB19C4D.189C6%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: James Polk <jmpolk@cisco.com>
Subject: [Sipping] location-requirements-02
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit


Some of the things I mention below are, in my mind, very hard to solve
without multipart support. I think the WG should consider making multipart
support mandatory. 

If you can put an LO in a 200, what happens if the 200 is too big? Does it
just get silently dropped. Related to this, if the UAC does not support
multipart, and the UAS forms a 200 with a multipart, what happens?

If we go with a proxy forms an error to tell the UAC to insert an LO, then
how does a proxy tell the UAS what LO to put in the answer. If the proxy
rejects calls without an LO (and provides information on how to insert one)
and the UAS does not support multipart, what happens.

The idea that a proxy that fails and attempt the first time must remember
this and allow it the next time does not seem workable to me. I think you
need to get it so that the proxy will not fail things it can not fail. (page
36)

Consider the problem described in the draft where  UA-A sends an INVITE to a
proxy that decides to route it to B, then before their is a dialog formed,
UA-A location changes such that the call would not be routed to C. I think
that in this case, we should just fail this call and try again or just let
the call go to B.

Imagine that A is calling B via proxy-a and proxy-b. I think it is a
requirement that A should be able to reveal it's location to proxy-a but not
to B. I'm not sure I can think of a good reason why. Anyways, sorting out
the the answer to this seems somewhat important. A related case is A routes
to proxy-hotel that goes to proxy-a to B and A wants to reveal location to
proxy-a but not proxy-hotel. U-U2 might need to get a bit more specific on
"confidential" with respect to who.

Paragraph at end of section 2 sounds like a poster child use case for e2m
security. 

The example with putting the two locations in a refer looks really
complicated to get right. Do we need this? Agree it looks possible.

Example 8.2.1 might be better if the text/plain was not encrypted but the LO
was. Glad to help provide text.

Around page 34 - "the second probability in message flows" I think you mean
problem 











_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 01:10:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29133
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 01:10:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQJmC-0007cC-Or
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 01:10:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQJWN-0007IF-Pm; Sat, 06 Nov 2004 00:53:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQJPf-0006KY-4B
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 00:46:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27597
	for <sipping@ietf.org>; Sat, 6 Nov 2004 00:46:55 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQJPi-00074C-2z
	for sipping@ietf.org; Sat, 06 Nov 2004 00:47:03 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 05 Nov 2004 21:57:25 -0800
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.10/8.12.6) with ESMTP id iA65kCoo012872;
	Fri, 5 Nov 2004 21:46:14 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn1-488.cisco.com [10.21.97.232])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU14330;
	Fri, 5 Nov 2004 21:46:22 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 05 Nov 2004 20:45:09 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: Paul H Kyzivat <pkyzivat@cisco.com>
Message-ID: <BDB196D5.189C2%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] gruu-reg-event-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit


Nice. 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 12:34:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22828
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 12:34:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQUSd-0002jb-JF
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 12:34:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQURG-0007Ss-8h; Sat, 06 Nov 2004 12:33:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUM3-0006Zd-0S
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 12:27:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22453
	for <sipping@ietf.org>; Sat, 6 Nov 2004 12:27:55 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQUMD-0002aw-6C
	for sipping@ietf.org; Sat, 06 Nov 2004 12:28:09 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iA6HRElc010444;
	Sat, 6 Nov 2004 12:27:14 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 126483C80B4;
	Sat,  6 Nov 2004 12:25:19 -0500 (EST)
Received: from pintlmail.MITL.Research.Panasonic.COM 
	(pintlmail.mitl.research.panasonic.com [150.169.1.62])by 
	redwood.research.panasonic.com (Postfix) with ESMTP id E07413C80B4;
	Sat,  6 Nov 2004 12:25:11 -0500 (EST)
Received: from [68.36.209.209] by 
	pintlmail.MITL.Research.Panasonic.COM(mshttpd);
	Sat, 06 Nov 2004 12:27:07 -0500
From: Brijesh Kumar <kumarb@research.panasonic.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Message-ID: <51c424d446.4d44651c42@pintlmail.MITL.Research.Panasonic.COM>
Date: Sat, 06 Nov 2004 12:27:07 -0500
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
Content-Type: text/plain;
	charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:47.24096 C:17 M:6 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
Cc: a.ahmed@ntt.com, sipping <sipping@ietf.org>, bhu@Motorola.com,
        mahfuz@research.panasonic.com
Subject: [Sipping] Re: draft-rahman-sipping-device-info-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit

Hi Paul:

Thanks for reading the draft and raising some very relevant questions.
Please see the response inline.

----- Original Message -----
From: Paul Kyzivat <pkyzivat@cisco.com>
Date: Friday, November 5, 2004 6:22 pm

> I'm not getting a clear understanding from this draft of what the 
> granularity of a device is, or how you intend to address a device.

A device in the draft correspond to an AOR. A device can be a pure 
software instantiation, or a hardware plus software instantiation.


> For example, lets assume I have a PC. On it I have two sip 
> software 
> agents: a softphone and an IM client. The softphone supports two 
> "lines" 
> (addresses), and the IM client supports a third address. For each 
> of 
> these addresses, there is an AOR, and a local contact that is 
> registered 
> with the corresponding AOR. The PC is behind a NAT, so it doesn't 
> have 
> stable contact addresses. So each time it registers, it requests a 
> GRUU.
> Summarizing:
> 
> PC IP address: 10.0.1.1
> 
> Softphone
> - local sip address: 10.0.1.1:5060
> - NATed address: 192.0.2.88:8866
> - line 1
>   - AOR: sip:alice@atlanta.com
>   - contact: sip:line1@10.0.1.1:5060;instance=id="uuid:stuff"
>   - GRUU: sip:lkjhg-alice@atlanta.com;grid=1
> - line 2
>   - AOR: sip:alice@biloxi.com
>   - contact: sip:line2@10.0.1.1:5060;instance-id="uuid:stuff"
>   - GRUU: sip:xcvbnm-alice@biloxi.com;grid=2
> IM client
> - local sip address: 10.0.1.1:7654
> - NATed address: 192.0.2.88:8872
> - AOR: sip:alice@IMs-R-us.com
> - contact: sip:10.0.1.1:7654;instance-id="uuid:something"
> - GRUU: sip:rtyuiop-alice@IMs-R-us.com
> 
> How does the device-info event package get used in this context?

We treat each AOR  (sip:alice@atlanta.com,alice@biloxi.com,
and sip:alice@IMs-R-us.com) as  a separate sip device.
 
> - from your point of view, how many devices are there here?

We will treat them as three devices since there are three AORs.

> - which of the above addresses can I use to invoke it?
>   (Or do you imagine a separate "device address"?)

Any of the above - but status returned would be different in each
case. Basically, we need to treat each device separately depending 
upon whose status we are interested in monitoring.

> - does the answer I get depend on which address I use?

Yes - beacuse each device represents separate operating
status which is independent from other devices (though
there may be some correlation in depending upon 
implementations, and how status information is maintained.)

> - should there be any tie between the data in the device info
>   package and the instance-id used for GRUU?

NO - this is not needed.

Thanks for your input. We will add some more 
clarification to the draft in the future revision.

regards,

--brijesh and mahfuz




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 19:37:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20730
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 19:37:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQb3c-0002I8-Hj
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 19:37:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQaz8-00033j-WE; Sat, 06 Nov 2004 19:32:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQar9-0001QL-6i
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 19:24:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19506
	for <sipping@ietf.org>; Sat, 6 Nov 2004 19:24:26 -0500 (EST)
Received: from dirty.research.bell-labs.com ([204.178.16.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQarM-00021L-CL
	for sipping@ietf.org; Sat, 06 Nov 2004 19:24:44 -0500
Received: from scummy.research.bell-labs.com
	(H-135-104-2-10.research.bell-labs.com [135.104.2.10])
	by dirty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	iA70OHXJ003352; Sat, 6 Nov 2004 19:24:17 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by scummy.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA70OBU1092442; Sat, 6 Nov 2004 19:24:11 -0500 (EST)
Received: from [127.0.0.1] ([135.104.20.78])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA70O69o020041; Sat, 6 Nov 2004 19:24:10 -0500 (EST)
Message-ID: <418D6B35.3080702@bell-labs.com>
Date: Sat, 06 Nov 2004 19:24:21 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] session-spec-policy-01 
References: <BDB0F51C.18813%fluffy@cisco.com>
In-Reply-To: <BDB0F51C.18813%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit

Cullen,

thanks much for the comments! I'll respond in different emails for the 
session-specific and the session-independent draft.

Cullen Jennings wrote:
> In the session spec policy ...
> 
> This is session spec policy, so, when the UA goes to the policy server, I'm
> sure it has to provide some information about the session so the server can
> provide the policy. I can't figure out how this happens reading the draft.
> 
Yes, the UA needs to provide session information to the policy server. 
This is something that happens on the policy channel, which is the major 
open issue for this draft now and needs to be specified. The examples in 
section 4 provide an abstract view on how the UA provides session 
information to the PS over the policy channel in "InfoOffer" and 
"InfoAnswer".

> You need to decide  if the policy server is just providing hints that all
> the UA not to violate the policy or if it  is doing something more. It it is
> just a hint, then I don't think you need the token - you just need a flag
> that say's yes, I have talked to the appropriate policy server. This will be
> much easier to secure than something where the token has security
> properties.
> 
I agree that there are two choices here: the UA can include a flag, 
which says, yes I know this policy server. Or the UA can include a token 
it has received from the policy server which also indicates that the UA 
has actually talked to the server.

The draft currently makes use of a token but also allows the use of the 
PS URI, which is essentially a flag for one server (which is exactly 
what is needed by a proxy). I agree that a token might actually not 
provide too much extra value. It does indicate that the UA has talked to 
the server but it does not say that the UA has really used the received 
policies. For this reason, I'll remove the use of the token from the 
draft and simply keep the use of the PS URI.

> I can't imagine how this will work without needing it for answers as well as
> offers. The example in section 4.2 PS-A will need to know the port that UA-A
> put  in the answer so that it can open an pin hole in a firewall to allow
> media to UA-A. 
> 
The examples in section 4 illustrate the basic call flow - there is no 
deeper semantic behind them. I guess what you had in mind is the 
firewall traversal example, which would not work without providing the 
answer to the PS.

This was added as an open issue because the question came up whether it 
is possible/desirable to reduce the scope of session-specific policies 
to only policing the offer. A possible option could be that the policy 
server tells the UA in the offer cycle, whether it wants to be contacted 
for the answer and for the BYE.

> I think this could be improved by specifically saying that what is revealed
> to the PS in both an offer and answer case and was clear how the PS would
> tell the UA to change the offer or answer in the case where the RTP
> port/address needed to be changed.
> 
Yes, the media routing policy still needs some more clarifications!

> I think that SUB/NOT is a reasonable approach to talk to the PS. The reason
> why is that any other choice is going to get you into a very complicated
> story on how to authenticate things back and forth.
> 
I agree.

Thanks,

Volker







_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 19:39:42 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21064
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 19:39:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQb68-0002M4-5B
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 19:40:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQb3E-0004G4-Vz; Sat, 06 Nov 2004 19:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQayi-0002pK-2t
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 19:32:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20279
	for <sipping@ietf.org>; Sat, 6 Nov 2004 19:32:16 -0500 (EST)
Received: from dirty.research.bell-labs.com ([204.178.16.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQayt-0002AF-8o
	for sipping@ietf.org; Sat, 06 Nov 2004 19:32:34 -0500
Received: from grubby.research.bell-labs.com
	(H-135-104-2-9.research.bell-labs.com [135.104.2.9])
	by dirty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	iA70WEXJ003367; Sat, 6 Nov 2004 19:32:14 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by grubby.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA70W9dj078786; Sat, 6 Nov 2004 19:32:09 -0500 (EST)
Received: from [127.0.0.1] ([135.104.20.78])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA70W69o020081; Sat, 6 Nov 2004 19:32:08 -0500 (EST)
Message-ID: <418D6D17.9070202@bell-labs.com>
Date: Sat, 06 Nov 2004 19:32:23 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] session-indep-policy-01
References: <BDB0F51C.18813%fluffy@cisco.com>
In-Reply-To: <BDB0F51C.18813%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: 7bit

Cullen,

thanks much for the comments! I'll respond in different emails for the
session-specific and the session-independent draft.

Cullen Jennings wrote:
> My meta comments is that this seems to be getting close on many of the "how
> the policy is moved around" issues but still seem like fairly early work on
> the "what the policy document is" stuff.
> 
> Right now it is trying to be an incredibly flexible do anything type
> framework and I think that is a mistake. I think we should limit it down to
> being able to meet the requirements described mostly in
> draft-ietf-sipping-session-policy-req-02 - particularly the stuff in section
> 3.3. 
> 
This issue is certainly the most important one to get resolved for the 
session-independent framework. Once the general structure of policies 
and the way constraints are specified is nailed down, it should be 
fairly easy to define XML schemas for policy documents.

The current framework is indeed quite flexible. I believe it is 
deterministic and UAs can calculate their working profile by processing 
a policy document step by step as described in the draft.

Having said this, I agree that it might make sense to reduce this 
flexibility and define something less general that only applies to the 
specific policies.  I'll try to put together an alternative proposal for 
the D.C. meeting.

> We need to say how the PS informs the UA of DSCP and other QOS parameters.
> 
Do you have examples about what you would like to see in a QoS parameter 
policy?

> The PS should be able to add per codec bandwidth and pps limits.
> 
I'll add a "type" and a "codec" attribute to the maxBandwidthStream and
the new maxPacketsStream (see below) elements.


> Moving on to indep-policy ....
> 
> Again, I think we can meet the requirements with something much simpler that
> avoids most of the problems I bring up below.
> 
As mentioned, I agree that there are simpler approaches that should be 
explored.

> I would add a  packets per seconds max per stream and per session. This is
> important on 802.11 networks.
> 
I'll add a maxPacketsStream and a maxPacketsSession element to the media
policy schema.

> We need more on what to do with conflicts. The idea that an UA should alert
> on a conflict is not really enough. Should say the UA should attempt the
> call if there is a conflict? What about if the conflict is during a 911
> call?
> 
I think the general question is if something useful can be done when 
policies conflict. When the conflicting policies are both enforced, 
there might be no resolution at all. The approach of the current draft 
is to have a section that defines conflict handling rules for each schema.

> In the example in 4.4.3, is has RTP/AVP in the set_all. Since I must set
> this, I assume I can not set SRTP. I don't get how I can optional use that.
> 
In the example, RTP/AVP MUST to be in the working profile. If it's the 
only transport in the working profile, the UA must use it.

If the policy has optional elements in the <set_any> container, the UA 
may add these element to the working profile. It can then choose between 
RTP and SRTP. If you want to force the UA to use RTP/SAVP, simply don't 
put a transport alternative in the <set_any> container.

> What is an implementation supposed to do if it says forbid X and set_all X.
> Which wins? 
> 
Since forbid MUST be processed first, X is removed from the working
profile and then added again. The behavior is deterministic (although
it's not the most useful policy).

> How do I say you can use 300kbps for video but only 30kbps for audio.
> 
Good point. I'll added a type attribute to maxBandwidthStream element.

> Basically I think the current scheme is going to be incredibly difficult to
> implement with different corner cases on all the implementation that make it
> easy to come up with "invalid" policies that get circumvented in weird ways.
> 
> This is the same problem we have with all merged policy - if we just had
> positive permissions, or just had negative permissions, it would be easier.
> I sort off doubt we can do that in this case but perhaps someone can figure
> out how. If we can't do this, I think we can still easily solve the
> requirements at hand with specific instead of general solutions with
> specific advice on how to merge and deal with conflicts.
> 
> Consider something like the following.
> 
>   We have a list of allowed codec in preferred order and they merger based
> on nearest proxy on the signaling path having priority.
> 
>   We have a list of forbidden codecs.
> 
>   We have max session/stream bandwidth and pps that merge in obvious way.
> 
>   We have that these are clearly hints and conflicts should be ignored for
> emergency calls but call should not be made for non emergency calls.
> 
>   A min and max RTP port that is allowed - these merge in obvious way.
> 
>   A DSCP that should be used.
> 
>   For each codec, a DSCP that should be used.
> 
These are very good points. Again, I'll try to put something together 
for the D.C. meeting.

> The include/exclude target stuff is very confusing on how it relates to the
> selection of rules - needs clarification.
> 
The selection of the policies for a target needs more clarification in 
the draft. The idea is that it is possible to define a policy that, for 
example, only applies to non-local targets (e.g. a firewall traversal 
policy). I'll add some wording that clarifies the use of these elements.

> I did not see requirement for transport or direction stuff. Or the protocol
> stuff which seems really confusing right now.
> 
I'm ok with removing the transport and direction stuff if this is not 
needed. Regarding the protocol stuff, this could be move to a separate 
policy draft if people feel that it should not be part of the framework 
draft.

> The media policy address stuff does not make sense. This is an IP that the
> UA uses in the SDP then just sends from it's normal IP? You won't have to do
> things with the port on a per session basis? I am suspicions that this only
> makes sense in the session dependent work.
> 
All XML schemas in this draft can also be used for session-specific 
policies. I agree that the media routing policies are more useful in 
conjunction with session-specific policies and should probably be 
separated out into a separate draft (this is listed as a work item). The 
media routing policies also need a lot more explanation about a UA 
should process them. This is on the to-do list for the next revision of 
the draft(s).

Thanks,

Volker


-- 
Volker Hilt                      Bell Labs / Lucent Technologies
phone: +1 732 332 6432           101 Crawfords Corner Rd
email: volkerh@bell-labs.com     Holmdel, NJ 07733







_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 20:17:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23048
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 20:17:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbgO-00030Y-SC
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 20:17:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQbcH-0000qH-QU; Sat, 06 Nov 2004 20:13:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQbXS-00070C-8U
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 20:08:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22639
	for <sipping@ietf.org>; Sat, 6 Nov 2004 20:08:12 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbXf-0002r8-Jw
	for sipping@ietf.org; Sat, 06 Nov 2004 20:08:28 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 06 Nov 2004 17:20:58 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA717anC018892
	for <sipping@ietf.org>; Sat, 6 Nov 2004 17:07:37 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn4-496.cisco.com [10.21.81.240])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU31348;
	Sat, 6 Nov 2004 17:07:38 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 06 Nov 2004 15:19:02 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB29BE6.18AB9%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Subject: [Sipping] device-info-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit


Nice draft - few comments ...

As a completely alternative suggestions.... How much of this information can
you get by just sending an OPTION request to the device.

I would remove all the discussion of the device status - you don't define
anything about how to do it so the discussion does not help.

This reports things that should not change so rate of notifications is very
very seldom.

I would add an optional UUID to the profile

You might want to add software version.

I would make the schema URL and name attributes of a schema object so that
the device can lists multiple schema that it can support.








_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sat Nov  6 20:25:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23646
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 20:25:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbo9-0003CW-7C
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 20:25:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQbcK-0000ry-TU; Sat, 06 Nov 2004 20:13:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQbXU-00070d-GX
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 20:08:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22651
	for <sipping@ietf.org>; Sat, 6 Nov 2004 20:08:14 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbXi-0002r8-17
	for sipping@ietf.org; Sat, 06 Nov 2004 20:08:31 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 06 Nov 2004 17:21:00 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA717fcp023697;
	Sat, 6 Nov 2004 17:07:41 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn4-496.cisco.com [10.21.81.240])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU31353;
	Sat, 6 Nov 2004 17:07:40 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 06 Nov 2004 17:06:08 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB2B500.18AC0%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: Miguel Garcia <Miguel.An.Garcia@nokia.com>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        markus.isomaki@nokia.com, Aki Niemi <aki.niemi@nokia.com>
Subject: [Sipping] multiple-refer-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit


I think I might be confused about how normal refer works. If B has an invite
dialog with C. And A knows about this dialog (perhaps A is subscribed to
dialog or conference package on B). I don't think that A can send a refer to
B that gets it to send a BYE to C. You would need to put the rest of the
dialog information (to/from tag, call id) in refer somehow. I think Sean and
Rohan had some work on this.

Anyways, I don't get how the example in the draft will work.

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 sipping-bounces@ietf.org  Sat Nov  6 20:27:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23954
	for <sipping-web-archive@ietf.org>; Sat, 6 Nov 2004 20:27:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbqA-0003Hf-Vd
	for sipping-web-archive@ietf.org; Sat, 06 Nov 2004 20:27:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQbcL-0000s6-KX; Sat, 06 Nov 2004 20:13:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQbXU-00070f-PZ
	for sipping@megatron.ietf.org; Sat, 06 Nov 2004 20:08:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22654
	for <sipping@ietf.org>; Sat, 6 Nov 2004 20:08:15 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQbXi-0002rD-9j
	for sipping@ietf.org; Sat, 06 Nov 2004 20:08:31 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 06 Nov 2004 17:21:01 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA717ecr023695;
	Sat, 6 Nov 2004 17:07:41 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn4-496.cisco.com [10.21.81.240])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU31352;
	Sat, 6 Nov 2004 17:07:40 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 06 Nov 2004 16:38:51 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB2AE9B.18ABF%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>, Adam Roach <adam@nostrum.com>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Subject: [Sipping] uri-list-subscribe-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit


As far as I can tell, this document does not say what happens to the NOTIFYs
- seems like an important detail.




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sun Nov  7 11:14:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00222
	for <sipping-web-archive@ietf.org>; Sun, 7 Nov 2004 11:14:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQpgZ-000688-LX
	for sipping-web-archive@ietf.org; Sun, 07 Nov 2004 11:14:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQpdu-0003ak-Rl; Sun, 07 Nov 2004 11:11:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQpcl-0003NA-Sp
	for sipping@megatron.ietf.org; Sun, 07 Nov 2004 11:10:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00044
	for <sipping@ietf.org>; Sun, 7 Nov 2004 11:10:37 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQpd7-00064H-FM
	for sipping@ietf.org; Sun, 07 Nov 2004 11:11:02 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 07 Nov 2004 08:23:30 -0800
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA7G9tnC026254;
	Sun, 7 Nov 2004 08:09:59 -0800 (PST)
Received: from [10.32.245.155] (stealth-10-32-245-155.cisco.com
	[10.32.245.155])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iA7GAtmg014189;
	Sun, 7 Nov 2004 08:10:55 -0800
In-Reply-To: <BDB0F513.18813%fluffy@cisco.com>
References: <BDB0F513.18813%fluffy@cisco.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <77A7F8DB-30D7-11D9-A153-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] session-policy-req-02
Date: Sun, 7 Nov 2004 11:09:56 -0500
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1099843856.707343"; x:"432200"; a:"rsa-sha1"; b:"nofws:1573";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"qGQLZXhHvkCidg8Ozr4/VzTqH8UdjvBSiLF0lr1QV29qIY+cLoILwauhrSAxJ"
	"ZUUnOBXICO/3M59UdJNsF90SDik0XxTDzwi/hFAYX7TZ2Nx1GHPnnLTk+0OZx"
	"N4qgoeRlQIAJLZx48Q2J6oUqPg+VDa0X5xoUAdV3TxZUU+MVY=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] session-policy-req-02";
	c:"Date: Sun, 7 Nov 2004 11:09:56 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit


On Nov 5, 2004, at 12:14 PM, Cullen Jennings wrote:

>
> The draft says ...
>
>    REQ-POL-11: The solution should allow proxies to request that 
> Quality
>       of Service (QoS) should be requested for a stream.
>    REQ-POL-12: The solution should allow proxies to ask endpoints to 
> use
>       specific parameters in their QoS reservations.
>    REQ-POL-13: The solution should allow proxies to ask endpoints to
>       provide a specific credential in their QoS requests.  This
>       requirement covers the functionality currently described in [9].
>
> I agree with these but think we should get more specific about what we 
> mean
> here. I assume we mean DSCP values for one.
No, I think it means the same thing as it would in the RFC3312. How the 
endpoint maps the policy to specific QoS parameters is sort of related 
to POL-12, which probably ought to get slightly restated to 
"...endpoints to use specific QoS mechanisms (e.g. Diffserv, Intserv) 
with mechanism-specific parameters (e.g. PHB for diffserv, TSPEC for 
intserv).

> Do we mean something specific
> for RSVP?
>
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Sun Nov  7 13:48:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12165
	for <sipping-web-archive@ietf.org>; Sun, 7 Nov 2004 13:48:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQs5k-0000lg-28
	for sipping-web-archive@ietf.org; Sun, 07 Nov 2004 13:48:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQrwE-0004UR-2R; Sun, 07 Nov 2004 13:38:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQrvp-0004ME-F7
	for sipping@megatron.ietf.org; Sun, 07 Nov 2004 13:38:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11610
	for <sipping@ietf.org>; Sun, 7 Nov 2004 13:38:25 -0500 (EST)
Received: from fep10.012.net.il ([212.117.129.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQrwC-0000bD-Ni
	for sipping@ietf.org; Sun, 07 Nov 2004 13:38:53 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep10.012.net.il with ESMTP
	id <20041107183741.DNIJ1249.fep10@isrexch01.israel.polycom.com>
	for <sipping@ietf.org>; Sun, 7 Nov 2004 20:37:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 7 Nov 2004 20:37:46 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C3B5322@IsrExch01.israel.polycom.com>
Thread-Topic: questions on draft-ietf-sipping-conferencing-framework-03.txt
Thread-Index: AcTEy3ny2F1KQmpRTXqOdCYBYPNE2w==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "sipping" <sipping@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Subject: [Sipping] questions on
	draft-ietf-sipping-conferencing-framework-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1865879042=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56

This is a multi-part message in MIME format.

--===============1865879042==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C4F8.E07457BD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C4F8.E07457BD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
Reading section 6.3 left me with some comments:
1.	How state changes are notified to the user if the mixing server
does not have notification services. Does the application server
constantly poll the mixing server to get state changes like change of
speakers. In the more general case the mixing server may need some
action in the signaling path and there is no way for it to notify the
AS.
2.	In general this approach is similar to MSCML with the difference
that the conference level channel is using CPCP except that there is no
way for the mixing server to report back events that happened in the
mixing server.=20

Roni

*************************************************************
Roni Even
Polycom Israel
=20
Tel: +972-3-9251200
Cell: +972-54-5481099
Fax: +972-3-9211571
*****************************************************************


------_=_NextPart_001_01C4C4F8.E07457BD
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>questions on =
draft-ietf-sipping-conferencing-framework-03.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Hi,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Reading section 6.3 left me with some =
comments:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">How state changes are notified to the user if the mixing =
server does not have notification services. Does the application server =
constantly poll the mixing server to get state changes like change of =
speakers.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> In the more general case =
the mixing server may need some action in the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">signaling</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">path and there is no way for it to notify the =
AS.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">In general this approach is similar to MSCML with the =
difference that the conference level channel is using CPCP except that =
there is no way for the mixing server to report back events that =
happened in the m</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">ixing =
server</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Roni</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">**********************************************************=
***</FONT></SPAN></A><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Roni Even</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Polycom Israel</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Tel: +972-3-9251200</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Cell: +972-54-5481099</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Fax: +972-3-9211571</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">**********************************************************=
*******</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C4F8.E07457BD--


--===============1865879042==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============1865879042==--



From sipping-bounces@ietf.org  Sun Nov  7 14:38:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16107
	for <sipping-web-archive@ietf.org>; Sun, 7 Nov 2004 14:38:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQsrz-0001rb-Oi
	for sipping-web-archive@ietf.org; Sun, 07 Nov 2004 14:38:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQsqQ-0007uH-R4; Sun, 07 Nov 2004 14:36:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQskp-0006oY-GB
	for sipping@megatron.ietf.org; Sun, 07 Nov 2004 14:31:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15492
	for <sipping@ietf.org>; Sun, 7 Nov 2004 14:31:09 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQslD-0001ic-OD
	for sipping@ietf.org; Sun, 07 Nov 2004 14:31:36 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 07 Nov 2004 11:44:04 -0800
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA7JUTnC000444;
	Sun, 7 Nov 2004 11:30:30 -0800 (PST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMW03403; Sun, 7 Nov 2004 14:30:26 -0500 (EST)
Message-ID: <418E77D2.6030706@cisco.com>
Date: Sun, 07 Nov 2004 14:30:26 -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: Brijesh Kumar <kumarb@research.panasonic.com>
Subject: Re: [Sipping] Re: draft-rahman-sipping-device-info-01.txt
References: <51c424d446.4d44651c42@pintlmail.MITL.Research.Panasonic.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, bhu@Motorola.com, a.ahmed@ntt.com,
        mahfuz@research.panasonic.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit

Brijesh,

I think this notion of device needs further exploration.

You are suggesting to equate it to AOR. But there can be multiple 
registrations against the same AOR, in which case requests for 
device-info would fork.

Also, a distinction between device and service is being worked out in 
SIMPLE. The Service corresponds to a contact address, and there can be a 
many-many relationship between service and device.

At the very least we will have major confusion if we utilize different 
notions of the granualarity of device and relationship to other things. 
So at least the names need to be changed to protect the innocent.

	Paul

Brijesh Kumar wrote:
> Hi Paul:
> 
> Thanks for reading the draft and raising some very relevant questions.
> Please see the response inline.
> 
> ----- Original Message -----
> From: Paul Kyzivat <pkyzivat@cisco.com>
> Date: Friday, November 5, 2004 6:22 pm
> 
> 
>>I'm not getting a clear understanding from this draft of what the 
>>granularity of a device is, or how you intend to address a device.
> 
> 
> A device in the draft correspond to an AOR. A device can be a pure 
> software instantiation, or a hardware plus software instantiation.
> 
> 
> 
>>For example, lets assume I have a PC. On it I have two sip 
>>software 
>>agents: a softphone and an IM client. The softphone supports two 
>>"lines" 
>>(addresses), and the IM client supports a third address. For each 
>>of 
>>these addresses, there is an AOR, and a local contact that is 
>>registered 
>>with the corresponding AOR. The PC is behind a NAT, so it doesn't 
>>have 
>>stable contact addresses. So each time it registers, it requests a 
>>GRUU.
>>Summarizing:
>>
>>PC IP address: 10.0.1.1
>>
>>Softphone
>>- local sip address: 10.0.1.1:5060
>>- NATed address: 192.0.2.88:8866
>>- line 1
>>  - AOR: sip:alice@atlanta.com
>>  - contact: sip:line1@10.0.1.1:5060;instance=id="uuid:stuff"
>>  - GRUU: sip:lkjhg-alice@atlanta.com;grid=1
>>- line 2
>>  - AOR: sip:alice@biloxi.com
>>  - contact: sip:line2@10.0.1.1:5060;instance-id="uuid:stuff"
>>  - GRUU: sip:xcvbnm-alice@biloxi.com;grid=2
>>IM client
>>- local sip address: 10.0.1.1:7654
>>- NATed address: 192.0.2.88:8872
>>- AOR: sip:alice@IMs-R-us.com
>>- contact: sip:10.0.1.1:7654;instance-id="uuid:something"
>>- GRUU: sip:rtyuiop-alice@IMs-R-us.com
>>
>>How does the device-info event package get used in this context?
> 
> 
> We treat each AOR  (sip:alice@atlanta.com,alice@biloxi.com,
> and sip:alice@IMs-R-us.com) as  a separate sip device.
>  
> 
>>- from your point of view, how many devices are there here?
> 
> 
> We will treat them as three devices since there are three AORs.
> 
> 
>>- which of the above addresses can I use to invoke it?
>>  (Or do you imagine a separate "device address"?)
> 
> 
> Any of the above - but status returned would be different in each
> case. Basically, we need to treat each device separately depending 
> upon whose status we are interested in monitoring.
> 
> 
>>- does the answer I get depend on which address I use?
> 
> 
> Yes - beacuse each device represents separate operating
> status which is independent from other devices (though
> there may be some correlation in depending upon 
> implementations, and how status information is maintained.)
> 
> 
>>- should there be any tie between the data in the device info
>>  package and the instance-id used for GRUU?
> 
> 
> NO - this is not needed.
> 
> Thanks for your input. We will add some more 
> clarification to the draft in the future revision.
> 
> regards,
> 
> --brijesh and mahfuz
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org  Sun Nov  7 16:38:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29238
	for <sipping-web-archive@ietf.org>; Sun, 7 Nov 2004 16:38:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQuka-00055k-2o
	for sipping-web-archive@ietf.org; Sun, 07 Nov 2004 16:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQuhK-0002PJ-CP; Sun, 07 Nov 2004 16:35:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQuaB-0005eS-V3
	for sipping@megatron.ietf.org; Sun, 07 Nov 2004 16:28:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27972
	for <sipping@ietf.org>; Sun, 7 Nov 2004 16:28:17 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQuaP-0004nS-9l
	for sipping@ietf.org; Sun, 07 Nov 2004 16:28:45 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA7LS2R2021327 for <sipping@ietf.org>; Sun, 7 Nov 2004 22:28:02 +0100
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 7 Nov 2004 22:28:01 +0100
Received: from ericsson.com (EFO9N000L5C7100 [153.88.41.238]) by
	esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WHL3S74D; Sun, 7 Nov 2004 22:28:01 +0100
Message-ID: <418E935A.4030800@ericsson.com>
Date: Sun, 07 Nov 2004 23:27:54 +0200
X-Sybari-Trust: 1a88d6f4 bfd556f1 2aded789 00000139
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
X-OriginalArrivalTime: 07 Nov 2004 21:28:01.0792 (UTC)
	FILETIME=[A8F3E000:01C4C510]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: rohan Mahy <rohan@ekabal.com>, Allison Mankin <mankin@psg.com>,
        Jon Peterson <Jon.Peterson@neustar.biz>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] Announcement: Ad-hoc meeting on SBCs
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Folks,

after taking into account all the responses received, we have decided to 
  schedulle the ad-hoc meeting on Session Border Controllers (SBCs) on 
Tuesday, from 19:00 to 21:00. The room is called Hemisphere and it 
should be big enough for all of those who want to attend.

A number of people mentioned that they have already pre-paid the social 
event. Unfortunatelly, we were unable to find any other slot which was 
suitable for everyone (a large number of people cannot make it on 
Thursday and Tuesday after the social was too late for many).

Regards,

Gonzalo
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 sipping-bounces@ietf.org  Sun Nov  7 21:38:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24684
	for <sipping-web-archive@ietf.org>; Sun, 7 Nov 2004 21:38:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQzQf-0003AA-Ct
	for sipping-web-archive@ietf.org; Sun, 07 Nov 2004 21:38:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQzOu-0002qO-UP; Sun, 07 Nov 2004 21:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQzNM-0002Xp-Jk
	for sipping@megatron.ietf.org; Sun, 07 Nov 2004 21:35:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24506
	for <sipping@ietf.org>; Sun, 7 Nov 2004 21:35:22 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQzNe-00036E-Jx
	for sipping@ietf.org; Sun, 07 Nov 2004 21:35:53 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iA82Yh44007761;
	Sun, 7 Nov 2004 21:34:43 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 64EFA3C80E1;
	Sun,  7 Nov 2004 21:32:47 -0500 (EST)
Received: from pintlmail.MITL.Research.Panasonic.COM 
	(pintlmail.mitl.research.panasonic.com [150.169.1.62])by 
	redwood.research.panasonic.com (Postfix) with ESMTP id 07D103C80B4;
	Sun,  7 Nov 2004 21:32:44 -0500 (EST)
Received: from [4.250.141.32] by 
	pintlmail.MITL.Research.Panasonic.COM(mshttpd);
	Sun, 07 Nov 2004 21:34:39 -0500
From: Mahfuz Rahman <mahfuz@research.panasonic.com>
To: sipping@ietf.org
Message-ID: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM>
Date: Sun, 07 Nov 2004 21:34:39 -0500
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
MIME-Version: 1.0
Content-Language: en
Subject: Re:[Sipping] device-info-01
X-Accept-Language: en
Priority: normal
Content-Type: text/plain;
	charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:21 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: a.ahmed@ntt.com, bhu@motorola.com, mahfuz@research.panasonic.com,
        kumarb@research.panasonic.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit

Thanks Cullen for making some good comments. My response is as follows:  

OPTIONS method is used to query device capabilities such as supported methods,
contnet types, codesc etc.. This draft defines data elements for device profile
which is  different from the tags defined for OPTIONS. So if we like to define
tags for each of the data elements we have defined in the profile it will be a long
list. I am not sure if it is acceptable. Also, as you suggested to include multiple
schemas and URLs for a device it would be difficult to represent using OPTIONS unless
we allow attachment of a body in the OPTIONS response with the following content type: 
application/device-profile+xml. 

I agree with you to add software version and also an optional UUID.

The status part will be extended in the future revision which might include a 
common XML format. Currently it describes only how vendor specific status information
can be retrieved. 

- mahfuz

-----Original Message-----
From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
Behalf Of Cullen Jennings
Sent: Saturday, November 06, 2004 6:19 PM
To: sipping
Subject: [Sipping] device-info-01


Nice draft - few comments ...

As a completely alternative suggestions.... How much of this information can
you get by just sending an OPTION request to the device.

I would remove all the discussion of the device status - you don't define
anything about how to do it so the discussion does not help.

This reports things that should not change so rate of notifications is very
very seldom.

I would add an optional UUID to the profile

You might want to add software version.

I would make the schema URL and name attributes of a schema object so that
the device can lists multiple schema that it can support.








_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 00:29:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07549
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 00:29:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR269-0006Yo-M0
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 00:29:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR1wi-0003mL-PP; Mon, 08 Nov 2004 00:20:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR1wM-0003bp-2o
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 00:19:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06827
	for <sipping@ietf.org>; Mon, 8 Nov 2004 00:19:38 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR1wo-0006Li-Lz
	for sipping@ietf.org; Mon, 08 Nov 2004 00:20:11 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 07 Nov 2004 21:32:38 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iA85J6cp011174;
	Sun, 7 Nov 2004 21:19:06 -0800 (PST)
Received: from [10.67.87.61] (sjc-vpn4-1194.cisco.com [10.21.84.169])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATU57710;
	Sun, 7 Nov 2004 21:18:57 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sun, 07 Nov 2004 13:59:16 -0500
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>, Rohan Mahy <rohan@ekabal.com>,
        Dean Willis <dean.willis@softarmor.com>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        Alan Johnston <alan.johnston@mci.com>, Adam Roach <adam@nostrum.com>
Message-ID: <BDB3DAB4.18BAC%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: [Sipping] Changes in sipping-conference-package-06 and whisper
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit


Section 6.1.6.8 Whisper URI stuff.

I sort of looks like this has been added since the 05 version but it's not
mentioned in the changes since 05 section. I don't remember any mailing list
discussion on whisper getting added in other that someone  pointing out the
privacy aspects are broken but perhaps I missed it. What's going on here -
this does not seem right for a WG document to slip in on the final copy that
get WGLC. 

On a note on the actual merit of the whisper stuff, I don't know how it
would work, it is totally underspecified, there are no security
considerations to it, and it is definitely not ready for WGLC.

I notice that "locked" seems to have just slipped in too. How many other
things changed? I don't think that the locked concept is synced up with CPCP
and it seems like it needs to be. I like the locked concept -  it is simple
and useful but we need to figure out how it interacts with the policy stuff.

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 sipping-bounces@ietf.org  Mon Nov  8 10:05:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16307
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 10:05:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRB6K-0003QL-NV
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 10:06:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRAqY-0001uj-8L; Mon, 08 Nov 2004 09:50:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAky-0008Nt-O3
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 09:44:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14037
	for <sipping@ietf.org>; Mon, 8 Nov 2004 09:44:30 -0500 (EST)
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAlW-0002lg-AY
	for sipping@ietf.org; Mon, 08 Nov 2004 09:45:07 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA8EiRW24035; Mon, 8 Nov 2004 16:44:27 +0200 (EET)
X-Scanned: Mon, 8 Nov 2004 16:44:18 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iA8EiICw010588;
	Mon, 8 Nov 2004 16:44:18 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00ZZecW6; Mon, 08 Nov 2004 16:44:15 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iA8EiFS18391; Mon, 8 Nov 2004 16:44:15 +0200 (EET)
Received: from [10.162.15.125] ([10.162.15.125]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 8 Nov 2004 16:44:14 +0200
Message-ID: <418F863D.8080809@nokia.com>
Date: Mon, 08 Nov 2004 16:44:13 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <BDB2B500.18AC0%fluffy@cisco.com>
In-Reply-To: <BDB2B500.18AC0%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2004 14:44:14.0802 (UTC)
	FILETIME=[6AF45320:01C4C5A1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>,
        "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>,
        markus.isomaki@nokia.com, Aki Niemi <aki.niemi@nokia.com>
Subject: [Sipping] Re: multiple-refer-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit

Cullen Jennings wrote:

> I think I might be confused about how normal refer works. If B has an invite
> dialog with C. And A knows about this dialog (perhaps A is subscribed to
> dialog or conference package on B). I don't think that A can send a refer to
> B that gets it to send a BYE to C. You would need to put the rest of the
> dialog information (to/from tag, call id) in refer somehow. I think Sean and
> Rohan had some work on this.
> 
> Anyways, I don't get how the example in the draft will work.

Presumably the focus has a table that maps AORs with existing dialogs. 
If a SIP UA, using a particular AOR has only a single dialog with the 
focus, then the focus is able to send any SIP request to that 
participant. If the participant uses a single AOR from different SIP 
UAs, then the focus will send send a BYE to each of them.

Further more, if this is a problem, it is affecting also CPCP, where you 
can do the same sort of things based on an AOR.

I think we can add some more text indicating this case where a 
participant might have joined the conference from different SIP UAs.

> 
> Cullen
> 
> 

   Miguel


-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 10:15:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17665
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 10:15:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRBFI-0003ix-0i
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 10:16:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRB7U-0001PG-DV; Mon, 08 Nov 2004 10:07:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAsx-0002bH-Tu
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 09:52:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15022
	for <sipping@ietf.org>; Mon, 8 Nov 2004 09:52:45 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAtM-00033P-6n
	for sipping@ietf.org; Mon, 08 Nov 2004 09:53:22 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA8EqZR2012109 for <sipping@ietf.org>; Mon, 8 Nov 2004 15:52:35 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 8 Nov 2004 15:52:34 +0100
Received: from ericsson.com (EFO9N000L5C7100 [153.88.41.163]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WFZH5R3G; Mon, 8 Nov 2004 15:52:34 +0100
Message-ID: <418F8830.5010103@ericsson.com>
Date: Mon, 08 Nov 2004 16:52:32 +0200
X-Sybari-Trust: b0a8b60e ad48f3dd 600c526e 00000179
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: Miguel Garcia <Miguel.An.Garcia@nokia.com>
References: <BDB2B500.18AC0%fluffy@cisco.com> <418F863D.8080809@nokia.com>
In-Reply-To: <418F863D.8080809@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Nov 2004 14:52:34.0736 (UTC)
	FILETIME=[94F03300:01C4C5A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>,
        Aki Niemi <aki.niemi@nokia.com>, markus.isomaki@nokia.com
Subject: [Sipping] Re: multiple-refer-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit

Cullen,

how to remove a participant from a conference using REFER is normatively 
defined in Section 4.11 of the following document:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-conferencing-05.txt

"The requestor does not need to know the dialog information about the
    dialog between the focus and the participant who will be removed -
    the focus knows this information and fills it when it generates the
    BYE request."

The multiple-refer document only references such a case as an example.

Thanks,

Gonzalo

Miguel Garcia wrote:
> Cullen Jennings wrote:
> 
>> I think I might be confused about how normal refer works. If B has an 
>> invite
>> dialog with C. And A knows about this dialog (perhaps A is subscribed to
>> dialog or conference package on B). I don't think that A can send a 
>> refer to
>> B that gets it to send a BYE to C. You would need to put the rest of the
>> dialog information (to/from tag, call id) in refer somehow. I think 
>> Sean and
>> Rohan had some work on this.
>>
>> Anyways, I don't get how the example in the draft will work.
> 
> 
> Presumably the focus has a table that maps AORs with existing dialogs. 
> If a SIP UA, using a particular AOR has only a single dialog with the 
> focus, then the focus is able to send any SIP request to that 
> participant. If the participant uses a single AOR from different SIP 
> UAs, then the focus will send send a BYE to each of them.
> 
> Further more, if this is a problem, it is affecting also CPCP, where you 
> can do the same sort of things based on an AOR.
> 
> I think we can add some more text indicating this case where a 
> participant might have joined the conference from different SIP UAs.
> 
>>
>> Cullen
>>
>>
> 
>   Miguel
> 
> 

-- 
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 sipping-bounces@ietf.org  Mon Nov  8 13:42:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11225
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 13:42:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREU5-0001I7-E6
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 13:43:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRECX-0001b5-B8; Mon, 08 Nov 2004 13:25:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRE7j-0008Ag-Ed
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 13:20:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09035
	for <sipping@ietf.org>; Mon, 8 Nov 2004 13:20:11 -0500 (EST)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRE89-0000k1-9I
	for sipping@ietf.org; Mon, 08 Nov 2004 13:20:52 -0500
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6V00D5XH5F1K@dns2.cselt.it> for sipping@ietf.org; Mon,
	08 Nov 2004 19:10:27 +0100 (MET)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 08 Nov 2004 19:16:27 +0100
Date: Mon, 08 Nov 2004 19:19:30 +0100
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] Comments on config framework draft- default AOR
To: dpetrie@pingtel.com
Message-id: <E5880434292FCB448F00BDAEE44A60D025EC0C@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] Comments on config framework draft- default AOR
thread-index: AcTFv1REv+7f9ht7QfOHiqFxoEItzA==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 08 Nov 2004 18:16:27.0875 (UTC)
	FILETIME=[10751330:01C4C5BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

> >=20
> > Let's consider the case where the device profiles
> > are delivered by a server within the constructor
> > (that manages the UA versions): the constructor
> > might not be aware of the identity of the users
> > using the devices. On the contrary, the service
> > provider is the one holding the user profiles, and
> > could thus keep an association between instance IDs
> > and default AORs. In addition, in some cases, the
> > access provider coincides with the service
> > provider... Have you considered including the
> > default AOR in the local profile together with the
> > other SIP parameters rather than in the device
> > profile?=20
> >=20
>=20
> The Network-User Event header parameter MAY be set to
> the AOR of the user.  In section 3.2 which talks about
> the specifics of the Network-User parameter is states
> that this parameter MAY be set for "device" or "local"
> profile types.  Does this cover the use case you had
> in mind?

Actually, what I meant is that the default AOR used to retrieve the user =
profile could also be provided from the server to the UA together with =
the "local" profile data (rather than in the "device" profile data as =
specified in the framework). Do you see anything wrong with this?
Gabrielle
=20



Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 13:44:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11411
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 13:44:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREW4-0001LJ-5s
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 13:45:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRECZ-0001bm-LW; Mon, 08 Nov 2004 13:25:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRE7x-0008BW-3w
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 13:20:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09042
	for <sipping@ietf.org>; Mon, 8 Nov 2004 13:20:25 -0500 (EST)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRE8X-0000l3-59
	for sipping@ietf.org; Mon, 08 Nov 2004 13:21:06 -0500
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6V00C8LH64XX@dns2.cselt.it> for sipping@ietf.org; Mon,
	08 Nov 2004 19:10:52 +0100 (MET)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 08 Nov 2004 19:16:52 +0100
Date: Mon, 08 Nov 2004 19:19:56 +0100
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] profile-datasets-00
To: Cullen Jennings <fluffy@cisco.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EC0D@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] profile-datasets-00
thread-index: AcTFv2OmVVj8CiFbRXG7+ukxsq9jKQ==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 08 Nov 2004 18:16:52.0375 (UTC)
	FILETIME=[1F0F7A70:01C4C5BF]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> Behalf Of Cullen Jennings
> Sent: sabato 6 novembre 2004 2.05
> To: sipping
> Cc: Daniel Petrie; Scott Lawrence
> Subject: [Sipping] profile-datasets-00
>=20
>
> I hate the forbid, set_all, set_one etc stuff in this. This is not a
> document to describe to a phone how to render a user=20
> interfaces for the user
> to select how to configure the phones. It's the data that is the
> configuration for the phone.

I also think that the forbid, set_all, set_one and set_any elements =
serve the policy purpose and should not be defined in this document. =
Rather, the precise definition of the data sets (XML schemas) seems to =
me a more important issue. It should align in some way with =
session-indep-policy-01 to simplify the delivery of UA profile data =
based on the profile delivery framework.

It could also be useful to split the profile data in two sections, one =
with plain settings and the other with possible combinations of such =
settings, for example to force some codec to be used in concordance to =
an outbound proxy (acting as RTP proxy/transcoder), or when trying to =
set a codec from a list, some codecs may require the device to point =
toward such a proxy while others may use a different one.
Gabrielle



Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 13:46:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11566
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 13:46:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREXH-0001O8-9S
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 13:46:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRECa-0001c1-Ts; Mon, 08 Nov 2004 13:25:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRE8k-0008SB-OZ
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 13:21:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09129
	for <sipping@ietf.org>; Mon, 8 Nov 2004 13:21:15 -0500 (EST)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRE9L-0000lw-6V
	for sipping@ietf.org; Mon, 08 Nov 2004 13:21:55 -0500
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6V00D6TH7I1K@dns2.cselt.it> for sipping@ietf.org; Mon,
	08 Nov 2004 19:11:42 +0100 (MET)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 08 Nov 2004 19:17:42 +0100
Date: Mon, 08 Nov 2004 19:20:46 +0100
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] config framework - "document" and "app-id" parameters
To: Cullen Jennings <fluffy@cisco.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EC0E@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] config framework - "document" and "app-id"
	parameters
thread-index: AcTFv4FcpmFrmFSaTfWadrONgdit6g==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 08 Nov 2004 18:17:42.0250 (UTC)
	FILETIME=[3CC9CCA0:01C4C5BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

> >=20
> > Not sure I see why we need both document and app-id
> > - I may be very confused
> > here
>=20
> I may be as well, but I will attempt to explain.
> The document parameter may contain a relative path.
> It the first path segment can be either global or
> a user specific id.  If that is as far as the path
> is specified, app-id may be used to further constrain
> what profile data is desired.

Reading the configuration framework draft, I understand that the =
"document" parameter is meant to contain the URI for a specific profile =
document, while the "app-id" parameter is meant to contain an =
application *token* (when the profile-type is set to "application"). The =
use of tokens allows the URI semantics to be opaque to the UA. However, =
the framework could be more specific on how these tokens are to be =
defined. I believe that they have to be understood by the application =
profile delivery server, so it could be the ASP's role to define them, =
in the case of proprietary services. For more general services, the =
tokens should be defined maybe by the IANA.

Another question: what's the use of the "profile-type" parameter when =
the "document" parameter already contains the URI of the document in =
which the UA is interested?

Gabrielle




Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 13:47:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11792
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 13:47:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CREYt-0001SM-4p
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 13:48:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRECc-0001cD-0S; Mon, 08 Nov 2004 13:25:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRE8z-0008UJ-I6
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 13:21:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09132
	for <sipping@ietf.org>; Mon, 8 Nov 2004 13:21:30 -0500 (EST)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRE9Y-0000m9-V7
	for sipping@ietf.org; Mon, 08 Nov 2004 13:22:10 -0500
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6V00D72H7W1K@dns2.cselt.it> for sipping@ietf.org; Mon,
	08 Nov 2004 19:11:56 +0100 (MET)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 08 Nov 2004 19:17:56 +0100
Date: Mon, 08 Nov 2004 19:20:59 +0100
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] session-indep-policy-01
To: Cullen Jennings <fluffy@cisco.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EC0F@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] session-indep-policy-01
thread-index: AcTFv4mVyJzbqmedRvao8qOH5OiVyg==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 08 Nov 2004 18:17:56.0359 (UTC)
	FILETIME=[4532A970:01C4C5BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable

inline...

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> Behalf Of Volker Hilt
> Sent: domenica 7 novembre 2004 1.32
> To: Cullen Jennings
> Cc: sipping; gonzalo.camarillo@ericsson.com
> Subject: Re: [Sipping] session-indep-policy-01
>=20
> Cullen,
>=20
> thanks much for the comments! I'll respond in different emails for the
> session-specific and the session-independent draft.
>=20
> Cullen Jennings wrote:
> >
> > Moving on to indep-policy ....
> >=20
> > What is an implementation supposed to do if it says forbid=20
> X and set_all X.
> > Which wins?=20
> >=20
> Since forbid MUST be processed first, X is removed from the working
> profile and then added again. The behavior is deterministic (although
> it's not the most useful policy).

What about two different property-sets containing opposite policies =
(e.g. in two NOTIFY for separate subscriptions)? How should the UA solve =
the conflict in this case?
Gabrielle




Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 14:51:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20896
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 14:51:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRFYX-0003XV-0c
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 14:52:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRFJZ-0002LX-Dg; Mon, 08 Nov 2004 14:36:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRF23-00074h-HX
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 14:18:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16678
	for <sipping@ietf.org>; Mon, 8 Nov 2004 14:18:25 -0500 (EST)
Received: from dirty.research.bell-labs.com ([204.178.16.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRF2e-0002Te-Ji
	for sipping@ietf.org; Mon, 08 Nov 2004 14:19:04 -0500
Received: from grubby.research.bell-labs.com
	(H-135-104-2-9.research.bell-labs.com [135.104.2.9])
	by dirty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	iA8JIPXJ012792; Mon, 8 Nov 2004 14:18:25 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by grubby.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA8JIKdj026408; Mon, 8 Nov 2004 14:18:20 -0500 (EST)
Received: from [135.104.20.78] ([135.104.20.78])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA8JIJ9n013368; Mon, 8 Nov 2004 14:18:19 -0500 (EST)
Message-ID: <418FC674.9040209@bell-labs.com>
Date: Mon, 08 Nov 2004 14:18:12 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Simonetti Gabrielle <Gabrielle.Simonetti@tilab.com>
Subject: Re: [Sipping] session-indep-policy-01
References: <E5880434292FCB448F00BDAEE44A60D025EC0F@EXC01C.cselt.it>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D025EC0F@EXC01C.cselt.it>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

Gabrielle,

>>Since forbid MUST be processed first, X is removed from the working
>>profile and then added again. The behavior is deterministic (although
>>it's not the most useful policy).
> 
> What about two different property-sets containing opposite policies
> (e.g. in two NOTIFY for separate subscriptions)? How should the UA solve
> the conflict in this case?

We need to address the issue of conflicts between policies in general. 
One approach is to define specific conflict resolution rules for each 
policy schema and maybe even for each element in a policy schema (e.g. 
along the lines of Cullens example in the last mail). This is something 
that needs some more discussion and clearly needs to be addressed in the 
next rev of the draft.

Thanks,

Volker

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov  8 15:33:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26884
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 15:33:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRGD1-0004ih-J5
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 15:33:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRFxH-0005JF-Py; Mon, 08 Nov 2004 15:17:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRFkS-0005Bk-Sk
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 15:04:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22566
	for <sipping@ietf.org>; Mon, 8 Nov 2004 15:04:18 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRFkz-0003rU-VH
	for sipping@ietf.org; Mon, 08 Nov 2004 15:04:55 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-5.cisco.com with ESMTP; 08 Nov 2004 12:04:04 -0800
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iA8K3HnC001874;
	Mon, 8 Nov 2004 12:03:17 -0800 (PST)
Received: from [130.129.133.70] (sjc-vpn1-334.cisco.com [10.21.97.78])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iA8K4U1f021502;
	Mon, 8 Nov 2004 12:04:30 -0800
In-Reply-To: <418FC674.9040209@bell-labs.com>
References: <E5880434292FCB448F00BDAEE44A60D025EC0F@EXC01C.cselt.it>
	<418FC674.9040209@bell-labs.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4641D84C-31C1-11D9-A227-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] session-indep-policy-01
Date: Mon, 8 Nov 2004 15:03:36 -0500
To: Volker Hilt <volkerh@bell-labs.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1099944271.299782"; x:"432200"; a:"rsa-sha1"; b:"nofws:1497";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"L4fZgkmojvGGyozViT7Q0RafVfehAjk3bKr6ISSZuMlHEb4X7oKUL+XMQs5ZV"
	"8jzjOtBbo2lN6Q1lu/vyZsf2xHsCITgw5wL3pVj6qKfcTfQd7b6XiZKhfmfMC"
	"m2URoDdEYtelDfyygDkPOwdvXRfBvXw4IgrhiCqSgTZlCvav0=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] session-indep-policy-01";
	c:"Date: Mon, 8 Nov 2004 15:03:36 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit


On Nov 8, 2004, at 2:18 PM, Volker Hilt wrote:

> Gabrielle,
>
>>> Since forbid MUST be processed first, X is removed from the working
>>> profile and then added again. The behavior is deterministic (although
>>> it's not the most useful policy).
>> What about two different property-sets containing opposite policies
>> (e.g. in two NOTIFY for separate subscriptions)? How should the UA 
>> solve
>> the conflict in this case?
>
> We need to address the issue of conflicts between policies in general. 
> One approach is to define specific conflict resolution rules for each 
> policy schema and maybe even for each element in a policy schema (e.g. 
> along the lines of Cullens example in the last mail). This is 
> something that needs some more discussion and clearly needs to be 
> addressed in the next rev of the draft.
>
Ouch! for non-trivial policy languages conflict detection is quadratic 
time for policies with >2 terms, and for more complex languages 
conflict resolution can be NP hard.

> Thanks,
>
> Volker
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Mon Nov  8 16:02:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01364
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 16:02:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRGfP-0005e8-6Z
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 16:03:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRGUi-0007x5-6G; Mon, 08 Nov 2004 15:52:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRGKx-00037R-DU
	for sipping@megatron.ietf.org; Mon, 08 Nov 2004 15:42:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27903
	for <sipping@ietf.org>; Mon, 8 Nov 2004 15:42:00 -0500 (EST)
Received: from crufty.research.bell-labs.com ([204.178.16.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRGLY-000504-TX
	for sipping@ietf.org; Mon, 08 Nov 2004 15:42:41 -0500
Received: from grubby.research.bell-labs.com
	(H-135-104-2-9.research.bell-labs.com [135.104.2.9])
	by crufty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	iA8Keu1O047672; Mon, 8 Nov 2004 15:40:56 -0500 (EST)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by grubby.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA8Keodj028406; Mon, 8 Nov 2004 15:40:50 -0500 (EST)
Received: from [135.104.20.78] ([135.104.20.78])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	iA8Keo9n015498; Mon, 8 Nov 2004 15:40:50 -0500 (EST)
Message-ID: <418FD9CC.70006@bell-labs.com>
Date: Mon, 08 Nov 2004 15:40:44 -0500
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] session-indep-policy-01
References: <E5880434292FCB448F00BDAEE44A60D025EC0F@EXC01C.cselt.it>
	<418FC674.9040209@bell-labs.com>
	<4641D84C-31C1-11D9-A227-000A95C73842@cisco.com>
In-Reply-To: <4641D84C-31C1-11D9-A227-000A95C73842@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit

David R Oran wrote:
> On Nov 8, 2004, at 2:18 PM, Volker Hilt wrote:
>> Gabrielle,
>>> What about two different property-sets containing opposite policies
>>> (e.g. in two NOTIFY for separate subscriptions)? How should the UA solve
>>> the conflict in this case?
>>
>> We need to address the issue of conflicts between policies in general. 
>> One approach is to define specific conflict resolution rules for each 
>> policy schema and maybe even for each element in a policy schema (e.g. 
>> along the lines of Cullens example in the last mail). This is 
>> something that needs some more discussion and clearly needs to be 
>> addressed in the next rev of the draft.
>>
> Ouch! for non-trivial policy languages conflict detection is quadratic 
> time for policies with >2 terms, and for more complex languages conflict 
> resolution can be NP hard.
> 
I guess my comment above was not quite clear. I'm *not* saying that we 
should build a general solution for conflict resolution. I agree that 
this would be extremely complex and go way beyond what is needed to make 
this work.

There might be some simple rules that can be defined for specific 
elements. For example, if there are multiple bandwidth restrictions - 
pick the lowest one. Such rules should probably be defined in a policy 
schema. In cases these rules can't resolve a conflict, there might also 
be a simple default behavior, such as "alert the user".

Again, I do not think we should attempt to solve the general problem of 
conflict resolution for this draft!

Volker



>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the 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 Fellow
> Cisco Systems
> 7 Ladyslipper Lane
> Acton, MA 01720 USA
> Tel: +1 978 264 2048
> 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 sipping-bounces@ietf.org  Mon Nov  8 23:01:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22151
	for <sipping-web-archive@ietf.org>; Mon, 8 Nov 2004 23:01:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRNCo-0007RA-FK
	for sipping-web-archive@ietf.org; Mon, 08 Nov 2004 23:02:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRN9u-0003gY-Sg; Mon, 08 Nov 2004 22:59:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRN5v-00032T-I3; Mon, 08 Nov 2004 22:54:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21682;
	Mon, 8 Nov 2004 22:54:56 -0500 (EST)
Received: from omzesmtp01.mci.com ([199.249.17.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRN6X-0007Jl-Lb; Mon, 08 Nov 2004 22:55:41 -0500
Received: from pmismtp04.wcomnet.com ([166.38.62.39])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I6W0095H86MVH@firewall.mci.com>; Tue,
	09 Nov 2004 03:54:22 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I6W00I0186LW5@pmismtp04.mcilink.com>; Tue,
	09 Nov 2004 03:54:22 +0000 (GMT)
Received: from ThinkpadT40 ([131.146.54.147])
	by pmismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I6W00H6Z86G7T@pmismtp04.mcilink.com>; Tue,
	09 Nov 2004 03:54:21 +0000 (GMT)
Date: Mon, 08 Nov 2004 21:54:16 -0600
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
To: rmonmib@ietf.org, sipping@ietf.org
Message-id: <0I6W00H7486K7T@pmismtp04.mcilink.com>
Organization: MCI
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcTGDgjgtoMfXMtvRNuLCfFqS38YBg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: "'Johnston, Alan'" <Alan.Johnston@mci.com>,
        "'Alan Clark'" <alan.d.clark@telchemy.com>,
        "'Amy Pendleton'" <aspen@nortelnetworks.com>
Subject: [Sipping] RAQMON I-Ds Last Call
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

Three excellent I-Ds for RAQMON are on last call in the RMONMIB WG: 

http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon-
framework-07.txt

http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon-
pdu-07.txt

http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-rmonmib-raqmon-
mib-05.txt

This is very thorough work and should be made available to the Internet
community as INFORMATIVE RFCs IMHO. The reason why informative ONLY is
recommended is that application specific reporting, such as for VoIP, IM or
SMS messaging, etc. may be application targeted and service providers or IT
managers should not be mandated to use this SNMP based approach, where other
techniques are preferable. The specific approach should be the choice of the
service provider, IT group and the application vendor, for example a desktop
office suite enabled with real time communications or IM and presence SLA
may not need SNMP. 

An example of a VoIP targeted approach is

http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-summary-04.t
xt

This proposal is based on the experience of deploying and monitoring large
numbers of personal IP telephony devices, such as SIP phones and PC soft
phones. Other approaches may emerge as well. How do we monitor all the
communication enabled applications on the PC for example, now that every
application, for example in Microsoft Office (Word, PowerPoint, Outlook,
Access are SIP/SIMPLE enabled, besides the Windows Messenger and
Conferencing/Collaboration, etc.)?

In summary, the RAQMON I-Ds are ready for last call, but should NOT be the
only mandated approach. I suggest some additional wording to be added to
make this point clear.

I have copied here the co-authors of the proposal for the RTCP Summary in
case the issue of normative vs. informative RAQMON RFCs needs to be
discussed on the list.

Thanks, Henry

Henry Sinnreich
MCI
1201 E. Arapaho Rd./Office 1020
Richardson, Texas 75081
USA
 




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov  9 08:54:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27450
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 08:54:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRWSo-00041i-HL
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 08:55:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRWOl-0007XA-Rx; Tue, 09 Nov 2004 08:51:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRWDJ-0005OK-E5; Tue, 09 Nov 2004 08:39:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25490;
	Tue, 9 Nov 2004 08:39:11 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRWE2-0003cd-3x; Tue, 09 Nov 2004 08:40:00 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA9DUt2m000798; Tue, 9 Nov 2004 08:30:56 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iA9DUl2m000541; Tue, 9 Nov 2004 08:30:48 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] RAQMON I-Ds Last Call
Date: Tue, 9 Nov 2004 15:38:55 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9F1B@is0004avexu1.global.avaya.com>
Thread-Topic: [Sipping] RAQMON I-Ds Last Call
Thread-Index: AcTGDgjgtoMfXMtvRNuLCfFqS38YBgAUPwXQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Henry Sinnreich" <Henry.Sinnreich@mci.com>, <rmonmib@ietf.org>,
        <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: quoted-printable
Cc: "Johnston, Alan" <Alan.Johnston@mci.com>,
        "Bert Wijnen \(E-mail\)" <bwijnen@lucent.com>,
        Alan Clark <alan.d.clark@telchemy.com>,
        Amy Pendleton <aspen@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable

Henry,

Thank you for your message, and for reading and commenting on the RAQMON =
drafts.=20

I am not sure what you mean when you say that RAQMON is 'SNMP-based'. Do =
you refer to the transport of the RAQMON PDUs? I agree with you that one =
single transport method for the performance monitoring information =
should not be mandate in complex multi-application environments. Exactly =
for this reason RAQMON does not mandate SNMP as a transport, but offers =
another choice that is mapping RAQMON PDUs over TCP.=20

If you refer to the RAQMON MIB, RAQMON indeed provides an SNMP MIB =
interface for the collectors, which are entities that aggregate =
information from many data sources (endpoints for example). SNMP MIBs =
are developed for all the RMON family of protocols, and RAQMON is part =
of the RMON performance monitoring. Same RTP, SIP, etc. have standard =
track MIB modules.=20

The RMON MIB WG has RAQMON in its charter as a standard track item. At =
the end of the day, it is the IESG who decides what status the documents =
will receive. SNMP MIBs are the approach recommended by the Operation =
and Management Area to retrieve management information, especially when =
it comes to performance monitoring. As I said I agree with you that =
multiple methods are required, but my opinion is that RAQMON should be =
standards track.=20

I would invite you and the other interested parties to attend the RMON =
WG meeting on Thursday. RAQMON is the main item on the agenda, and the =
WG would like to wrap up this work=20

Regards,

Dan



> -----Original Message-----
> From: sipping-bounces@ietf.org=20
> [mailto:sipping-bounces@ietf.org]On Behalf Of Henry Sinnreich
> Sent: 09 November, 2004 5:54 AM
> To: rmonmib@ietf.org; sipping@ietf.org
> Cc: 'Johnston, Alan'; 'Alan Clark'; 'Amy Pendleton'
> Subject: [Sipping] RAQMON I-Ds Last Call
>=20
>=20
> Three excellent I-Ds for RAQMON are on last call in the RMONMIB WG:=20
>=20
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> framework-07.txt
>=20
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> pdu-07.txt
>=20
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> mib-05.txt
>=20
> This is very thorough work and should be made available to=20
> the Internet
> community as INFORMATIVE RFCs IMHO. The reason why informative ONLY is
> recommended is that application specific reporting, such as=20
> for VoIP, IM or
> SMS messaging, etc. may be application targeted and service=20
> providers or IT
> managers should not be mandated to use this SNMP based=20
> approach, where other
> techniques are preferable. The specific approach should be=20
> the choice of the
> service provider, IT group and the application vendor, for=20
> example a desktop
> office suite enabled with real time communications or IM and=20
> presence SLA
> may not need SNMP.=20
>=20
> An example of a VoIP targeted approach is
>=20
> http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtc
> p-summary-04.t
> xt
>=20
> This proposal is based on the experience of deploying and=20
> monitoring large
> numbers of personal IP telephony devices, such as SIP phones=20
> and PC soft
> phones. Other approaches may emerge as well. How do we monitor all the
> communication enabled applications on the PC for example, now=20
> that every
> application, for example in Microsoft Office (Word,=20
> PowerPoint, Outlook,
> Access are SIP/SIMPLE enabled, besides the Windows Messenger and
> Conferencing/Collaboration, etc.)?
>=20
> In summary, the RAQMON I-Ds are ready for last call, but=20
> should NOT be the
> only mandated approach. I suggest some additional wording to=20
> be added to
> make this point clear.
>=20
> I have copied here the co-authors of the proposal for the=20
> RTCP Summary in
> case the issue of normative vs. informative RAQMON RFCs needs to be
> discussed on the list.
>=20
> Thanks, Henry
>=20
> Henry Sinnreich
> MCI
> 1201 E. Arapaho Rd./Office 1020
> Richardson, Texas 75081
> USA
> =20
>=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
>=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 sipping-bounces@ietf.org  Tue Nov  9 10:15:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07220
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 10:15:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRXj4-00067g-KS
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 10:16:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRXeR-000303-Gr; Tue, 09 Nov 2004 10:11:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRXTU-0005RI-0e; Tue, 09 Nov 2004 10:00:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04763;
	Tue, 9 Nov 2004 09:59:57 -0500 (EST)
Received: from pmesmtp01.wcom.com ([199.249.20.1] helo=pmesmtp01.mci.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRXUC-0005hJ-5Y; Tue, 09 Nov 2004 10:00:47 -0500
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I6X00D162Z1KS@firewall.mci.com>; Tue,
	09 Nov 2004 14:59:25 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I6X00C012XZIK@dgismtp04.mcilink.com>; Tue,
	09 Nov 2004 14:59:25 +0000 (GMT)
Received: from ThinkpadT40 ([131.146.27.1])
	by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I6X00BJ22YGCE@dgismtp04.mcilink.com>; Tue,
	09 Nov 2004 14:59:05 +0000 (GMT)
Date: Tue, 09 Nov 2004 08:59:04 -0600
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: [Sipping] RAQMON I-Ds Last Call
To: "'Romascanu, Dan (Dan)'" <dromasca@avaya.com>, rmonmib@ietf.org,
        sipping@ietf.org
Message-id: <0I6X00BJ32YGCE@dgismtp04.mcilink.com>
Organization: MCI
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcTGDgjgtoMfXMtvRNuLCfFqS38YBgAUPwXQAANGdIAAABvb8A==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: 7bit
Cc: "'Johnston, Alan'" <Alan.Johnston@mci.com>,
        "'Bert Wijnen \(E-mail\)'" <bwijnen@lucent.com>,
        "'Alan Clark'" <alan.d.clark@telchemy.com>,
        "'Amy Pendleton'" <aspen@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit

Thanks to all for your patience with this last minute discussion! The main
points I wanted to make:

- This is good work,

- There is more than one single approach for monitoring QoS for services and
applications, and we should offer the market some choices.

Thanks again, Henry


-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Tuesday, November 09, 2004 7:39 AM
To: Henry Sinnreich; rmonmib@ietf.org; sipping@ietf.org
Cc: Johnston, Alan; Alan Clark; Amy Pendleton; Bert Wijnen (E-mail)
Subject: RE: [Sipping] RAQMON I-Ds Last Call

Henry,

Thank you for your message, and for reading and commenting on the RAQMON
drafts. 

I am not sure what you mean when you say that RAQMON is 'SNMP-based'. Do you
refer to the transport of the RAQMON PDUs? I agree with you that one single
transport method for the performance monitoring information should not be
mandate in complex multi-application environments. Exactly for this reason
RAQMON does not mandate SNMP as a transport, but offers another choice that
is mapping RAQMON PDUs over TCP. 

If you refer to the RAQMON MIB, RAQMON indeed provides an SNMP MIB interface
for the collectors, which are entities that aggregate information from many
data sources (endpoints for example). SNMP MIBs are developed for all the
RMON family of protocols, and RAQMON is part of the RMON performance
monitoring. Same RTP, SIP, etc. have standard track MIB modules. 

The RMON MIB WG has RAQMON in its charter as a standard track item. At the
end of the day, it is the IESG who decides what status the documents will
receive. SNMP MIBs are the approach recommended by the Operation and
Management Area to retrieve management information, especially when it comes
to performance monitoring. As I said I agree with you that multiple methods
are required, but my opinion is that RAQMON should be standards track. 

I would invite you and the other interested parties to attend the RMON WG
meeting on Thursday. RAQMON is the main item on the agenda, and the WG would
like to wrap up this work 

Regards,

Dan



> -----Original Message-----
> From: sipping-bounces@ietf.org
> [mailto:sipping-bounces@ietf.org]On Behalf Of Henry Sinnreich
> Sent: 09 November, 2004 5:54 AM
> To: rmonmib@ietf.org; sipping@ietf.org
> Cc: 'Johnston, Alan'; 'Alan Clark'; 'Amy Pendleton'
> Subject: [Sipping] RAQMON I-Ds Last Call
> 
> 
> Three excellent I-Ds for RAQMON are on last call in the RMONMIB WG: 
> 
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> framework-07.txt
> 
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> pdu-07.txt
> 
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-r
> monmib-raqmon-
> mib-05.txt
> 
> This is very thorough work and should be made available to the 
> Internet community as INFORMATIVE RFCs IMHO. The reason why 
> informative ONLY is recommended is that application specific 
> reporting, such as for VoIP, IM or SMS messaging, etc. may be 
> application targeted and service providers or IT managers should not 
> be mandated to use this SNMP based approach, where other techniques 
> are preferable. The specific approach should be the choice of the 
> service provider, IT group and the application vendor, for example a 
> desktop office suite enabled with real time communications or IM and 
> presence SLA may not need SNMP.
> 
> An example of a VoIP targeted approach is
> 
> http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtc
> p-summary-04.t
> xt
> 
> This proposal is based on the experience of deploying and monitoring 
> large numbers of personal IP telephony devices, such as SIP phones and 
> PC soft phones. Other approaches may emerge as well. How do we monitor 
> all the communication enabled applications on the PC for example, now 
> that every application, for example in Microsoft Office (Word, 
> PowerPoint, Outlook, Access are SIP/SIMPLE enabled, besides the 
> Windows Messenger and Conferencing/Collaboration, etc.)?
> 
> In summary, the RAQMON I-Ds are ready for last call, but should NOT be 
> the only mandated approach. I suggest some additional wording to be 
> added to make this point clear.
> 
> I have copied here the co-authors of the proposal for the RTCP Summary 
> in case the issue of normative vs. informative RAQMON RFCs needs to be 
> discussed on the list.
> 
> Thanks, Henry
> 
> Henry Sinnreich
> MCI
> 1201 E. Arapaho Rd./Office 1020
> Richardson, Texas 75081
> USA
>  
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov  9 12:25:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22319
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 12:25:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRZkt-0001Lr-TA
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 12:26:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRZQw-0008KB-3v; Tue, 09 Nov 2004 12:05:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRZK6-0006tA-Rl
	for sipping@megatron.ietf.org; Tue, 09 Nov 2004 11:58:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19794
	for <sipping@ietf.org>; Tue, 9 Nov 2004 11:58:24 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRZKt-0000d3-Gj
	for sipping@ietf.org; Tue, 09 Nov 2004 11:59:15 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 09 Nov 2004 09:09:33 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iA9Gvqcp020729;
	Tue, 9 Nov 2004 08:57:52 -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 IAA21194;
	Tue, 9 Nov 2004 08:57:52 -0800 (PST)
Message-Id: <4.3.2.7.2.20041109101606.03685608@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 09 Nov 2004 10:57:56 -0600
To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <BDB19C4D.189C6%fluffy@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Subject: [Sipping] Re: location-requirements-02
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d

At 09:08 PM 11/5/2004 -0800, Cullen Jennings wrote:

>Some of the things I mention below are, in my mind, very hard to solve
>without multipart support. I think the WG should consider making multipart
>support mandatory.

I will bring this up during the ID presentation (as your idea  ;-)


>If you can put an LO in a 200, what happens if the 200 is too big? Does it
>just get silently dropped.

We know we cannot error a UAS Response - so this creates a problem. I will 
bring this up in the preso also and see what people say

>Related to this, if the UAC does not support
>multipart, and the UAS forms a 200 with a multipart, what happens?

this is a problem that's not exclusive to location - but this brings it to 
the surface


>If we go with a proxy forms an error to tell the UAC to insert an LO, then
>how does a proxy tell the UAS what LO to put in the answer.

this isn't specified, it's currently up to Bob

This is an open issue I've had in the doc since non-wg item -00, with no 
resolution

There was talk in San Diego of work coming to address how to request a body 
(hopefully specifying the body type...)

>If the proxy
>rejects calls without an LO (and provides information on how to insert one)
>and the UAS does not support multipart, what happens.

If the UAS does not support multipart, this issue has been raised and will 
be asked of the group

If the question is about the proxy erroring the UAC if no LO was present 
and the UAS doesn't include an LO, the proxy cannot currently (as stated) 
error a UAS


>The idea that a proxy that fails and attempt the first time must remember
>this and allow it the next time does not seem workable to me.

Why not? If the Proxy is aware enough to fail for this new reason, why 
can't it be expected to have code addressing the situation that it needs to 
look for a follow-up message that no longer error meets that same error 
condition?

>I think you
>need to get it so that the proxy will not fail things it can not fail. (page
>36)

don't I state that on page 36 already?


>Consider the problem described in the draft where  UA-A sends an INVITE to a
>proxy that decides to route it to B, then before their is a dialog formed,
>UA-A location changes such that the call would not be routed to C. I think
>that in this case, we should just fail this call and try again or just let
>the call go to B.

I was looking for guidance on this - failing the pending request is 
acceptable. Do you agree that the Proxy sends a CANCEL towards the 
UAS/Proxy, but what 4XX would you send to the UAC that tells it to retry 
immediately? Is this another new 4XX code (I hope not).


>Imagine that A is calling B via proxy-a and proxy-b. I think it is a
>requirement that A should be able to reveal it's location to proxy-a but not
>to B. I'm not sure I can think of a good reason why.

Wouldn't this require Proxy-A conceal the body from Proxy-B (middle-2-end 
security)? This will add time to the call set-up in an emergency situation, 
many will not like that, and we should have a discussion about it.

>Anyways, sorting out
>the the answer to this seems somewhat important. A related case is A routes
>to proxy-hotel that goes to proxy-a to B and A wants to reveal location to
>proxy-a but not proxy-hotel.

This is fairly clearly e2m, isn't it? But how does A know about each 
component in the signaling path? And, how does A get Proxy-a's key?

>U-U2 might need to get a bit more specific on
>"confidential" with respect to who.

please offer text


>Paragraph at end of section 2 sounds like a poster child use case for e2m
>security.

ok


>The example with putting the two locations in a refer looks really
>complicated to get right. Do we need this?

the longer it's in the doc, the more complicated it looks - so I'm leaning 
towards removing it

>Agree it looks possible.
>
>Example 8.2.1 might be better if the text/plain was not encrypted but the LO
>was.

good idea

>Glad to help provide text.

please


>Around page 34 - "the second probability in message flows" I think you mean
>problem

yep



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 sipping-bounces@ietf.org  Tue Nov  9 15:34:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10362
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 15:34:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRciS-0005oX-5W
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 15:35:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRcZn-0001ML-RK; Tue, 09 Nov 2004 15:26:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRcUc-0005ZT-Cp
	for sipping@megatron.ietf.org; Tue, 09 Nov 2004 15:21:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09060
	for <sipping@ietf.org>; Tue, 9 Nov 2004 15:21:28 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRcVQ-0005Ud-Sg
	for sipping@ietf.org; Tue, 09 Nov 2004 15:22:21 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 09 Nov 2004 12:34:45 -0800
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA9KKrom015730;
	Tue, 9 Nov 2004 12:20:54 -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 MAA25316;
	Tue, 9 Nov 2004 12:20:56 -0800 (PST)
Message-Id: <4.3.2.7.2.20041109140506.028628f8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 09 Nov 2004 14:21:00 -0600
To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [Sipping] Fwd: Re: location-requirements-02
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5

I oopsed on two counts below... (hopefully) corrected in-line

>Date: Tue, 09 Nov 2004 10:57:56 -0600
>To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
>From: "James M. Polk" <jmpolk@cisco.com>
>Subject: Re: location-requirements-02
>Cc: Brian Rosen <br@brianrosen.net>
>
>At 09:08 PM 11/5/2004 -0800, Cullen Jennings wrote:
>
>>I think you
>>need to get it so that the proxy will not fail things it can not fail. (page
>>36)
>
>don't I state that on page 36 already?

I misread your comment the first time.

Imagine a good citizen UAC that uses good security properties in an INVITE 
to a 911-type service and the request fails. I believe we want the 
situation to be that the subsequent INVITE is sent by that same UAC is in 
clear-text (concluding some security property failed the original attempt) 
to ensure the Request gets to the destination as fast as possible. We don't 
want the UAC searching for why the first attempt failed (by reducing 
security properties a step at a time) and thus taking a long time getting 
the INVITE to the ERC

>>Imagine that A is calling B via proxy-a and proxy-b. I think it is a
>>requirement that A should be able to reveal it's location to proxy-a but not
>>to B. I'm not sure I can think of a good reason why.
>
>Wouldn't this require Proxy-A conceal the body from Proxy-B (middle-2-end 
>security)? This will add time to the call set-up in an emergency 
>situation, many will not like that, and we should have a discussion about it.

I misread this comment of yours the first time too

Is proxy-a removing the LO message body ok with you here? Now, keep in mind 
proxy-a needs to know that B isn't to get the LO from A. I do not know of 
any indication that A can put in the SIP message or body to address the LO 
to proxy-a and not for B's viewing pleasure if the packet is destined for B.


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 sipping-bounces@ietf.org  Tue Nov  9 17:31:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21780
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 17:31:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CReXf-0000KZ-E4
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 17:32:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CReGu-0007Ci-5t; Tue, 09 Nov 2004 17:15:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRWSS-0008Jw-Tp
	for sipping@megatron.ietf.org; Tue, 09 Nov 2004 08:54:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27522
	for <sipping@ietf.org>; Tue, 9 Nov 2004 08:54:51 -0500 (EST)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRWTD-00042K-Li
	for sipping@ietf.org; Tue, 09 Nov 2004 08:55:40 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id iA9DsXP6016259;
	Tue, 9 Nov 2004 14:54:33 +0100
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.12.6/8.12.6) with ESMTP id iA9DsWma022724;
	Tue, 9 Nov 2004 14:54:32 +0100
Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de
	[139.21.200.58])
	by moody.mchh.siemens.de (8.12.6/8.12.6) with ESMTP id iA9DsV17024070; 
	Tue, 9 Nov 2004 14:54:31 +0100
Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <V1R8HW9L>; Tue, 9 Nov 2004 14:54:30 +0100
Message-ID: <76592C4D3DA1AC4FB8424084D10D31A804D10A1C@mchh2c4e.mchh.siemens.de>
From: Tan Ya-Ching <ya-ching.tan@siemens.com>
To: sipping@ietf.org
Subject: [Sipping] Comments on the FSM in dialog package -05 
Date: Tue, 9 Nov 2004 14:54:28 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-Mailman-Approved-At: Tue, 09 Nov 2004 17:15:24 -0500
Cc: "'Rohan Mahy'" <rohan@ekabal.com>, hgs@cs.columbia.edu
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

Section 3.7.1 of draft-ietf-sipping_dialog-package-05:

1) 'If the UAC should send a CANCEL, and then subsequently receive a 487
   to its INVITE transaction, all FSMs spawned from that INVITE
   transition to the "terminated" state with the event "cancelled".'

   Surely you mean only the Proceeding or Early dialogs.


2) 'Once in the confirmed state, the call is active.  It can transition
   to the terminated state if the UAC sends a BYE or receives a BYE
   (corresponding to the "local-bye" and "remote-bye" events as
   appropriate), if a mid-dialog request generates a 481 or 408 response
   (corresponding to the "error" event), or a mid-dialog request
   generates no response (corresponding to the "timeout" event).'

   But RFC 3261 (12.2.1.2 Processing the Responses) states that :

   "If the response for a request within a dialog is a 481
   (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the UAC
   SHOULD terminate the dialog.  A UAC SHOULD also terminate a dialog if
   no response at all is received for the request (the client
   transaction would inform the TU about the timeout.)

      For INVITE initiated dialogs, terminating the dialog consists of
      sending a BYE."

   It is stated specifically that terminating the dialog consists of
   sending a BYE. Therefore, the "error" event and "timeout"
   event in the FSM should not directly lead to the terminated
   state. Only the "local-bye" and "remote-bye" events could lead to
   the terminated state.

   To be precise, perhaps it should even be stated that :

   "If a UAC sends a BYE, and receives a 2xx response for the BYE, or
    if the BYE generates a 481 or 408 response, or if it generates no
    response, the dialog transitions to the terminated state. This
    correspond to the "local-bye" event.  If a UAS receives a BYE,
    and responds with a 2xx or 481 response, or does not respond to 
    the BYE and the BYE times out, the dialog transitions to the
    terminated state. This correspond to the "remote-bye" event."

   I think it is necessary to be precise because RFC 3261 (8.2 UAS
   Behavior) states that :

   "Note that request processing is atomic.  If a request is accepted,
    all state changes associated with it MUST be performed.  If it is
    rejected, all state changes MUST NOT be performed."


Regards,
Ya-Ching


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov  9 20:26:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07227
	for <sipping-web-archive@ietf.org>; Tue, 9 Nov 2004 20:26:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRhGS-00042V-Dm
	for sipping-web-archive@ietf.org; Tue, 09 Nov 2004 20:27:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRhAX-0001Ru-UL; Tue, 09 Nov 2004 20:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRh9i-0001LQ-NM
	for sipping@megatron.ietf.org; Tue, 09 Nov 2004 20:20:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06893
	for <sipping@ietf.org>; Tue, 9 Nov 2004 20:20:12 -0500 (EST)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRhAZ-0003ub-HI
	for sipping@ietf.org; Tue, 09 Nov 2004 20:21:08 -0500
Received: from [130.129.134.164] ([130.129.134.164]) (authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iAA1K1C15387;
	Tue, 9 Nov 2004 17:20:01 -0800
In-Reply-To: <76592C4D3DA1AC4FB8424084D10D31A804D10A1C@mchh2c4e.mchh.siemens.de>
References: <76592C4D3DA1AC4FB8424084D10D31A804D10A1C@mchh2c4e.mchh.siemens.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A3CB49B4-32B6-11D9-AFD7-000D93C60450@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Subject: Re: [Sipping] Comments on the FSM in dialog package -05 
Date: Tue, 9 Nov 2004 20:19:59 -0500
To: Tan Ya-Ching <ya-ching.tan@siemens.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, hgs@cs.columbia.edu
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit

Hi,

Thanks for reviewing the dialog package.  I believe that the two 
specific sections you mention are actually correct.  Please see my 
comments inline.

On Nov 9, 2004, at 8:54, Tan Ya-Ching wrote:
> Section 3.7.1 of draft-ietf-sipping_dialog-package-05:
>
> 1) 'If the UAC should send a CANCEL, and then subsequently receive a 
> 487
>    to its INVITE transaction, all FSMs spawned from that INVITE
>    transition to the "terminated" state with the event "cancelled".'
>
>    Surely you mean only the Proceeding or Early dialogs.

Yes, you are correct, but stating this is redundant, since you can only 
receive a 487 to an INVITE if all the dialogs are in Proceeding or 
Early (by definition).

> 2) 'Once in the confirmed state, the call is active.  It can transition
>    to the terminated state if the UAC sends a BYE or receives a BYE
>    (corresponding to the "local-bye" and "remote-bye" events as
>    appropriate), if a mid-dialog request generates a 481 or 408 
> response
>    (corresponding to the "error" event), or a mid-dialog request
>    generates no response (corresponding to the "timeout" event).'
>
>    But RFC 3261 (12.2.1.2 Processing the Responses) states that :
>
>    "If the response for a request within a dialog is a 481
>    (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the 
> UAC
>    SHOULD terminate the dialog.  A UAC SHOULD also terminate a dialog 
> if
>    no response at all is received for the request (the client
>    transaction would inform the TU about the timeout.)
>
>       For INVITE initiated dialogs, terminating the dialog consists of
>       sending a BYE."
>
>    It is stated specifically that terminating the dialog consists of
>    sending a BYE. Therefore, the "error" event and "timeout"
>    event in the FSM should not directly lead to the terminated
>    state. Only the "local-bye" and "remote-bye" events could lead to
>    the terminated state.

No, according to RFC 3261 section 12.2.1.2 which you quote above, if I 
send a reINVITE, OPTIONS, PRACK, INFO, UPDATE, or other in-dialog 
request and get a 408, timeout, or 481, then the state of the dialog 
moves to terminated.

thanks,
-rohan

>    To be precise, perhaps it should even be stated that :
>
>    "If a UAC sends a BYE, and receives a 2xx response for the BYE, or
>     if the BYE generates a 481 or 408 response, or if it generates no
>     response, the dialog transitions to the terminated state. This
>     correspond to the "local-bye" event.  If a UAS receives a BYE,
>     and responds with a 2xx or 481 response, or does not respond to
>     the BYE and the BYE times out, the dialog transitions to the
>     terminated state. This correspond to the "remote-bye" event."
>
>    I think it is necessary to be precise because RFC 3261 (8.2 UAS
>    Behavior) states that :
>
>    "Note that request processing is atomic.  If a request is accepted,
>     all state changes associated with it MUST be performed.  If it is
>     rejected, all state changes MUST NOT be performed."
>
>
> Regards,
> Ya-Ching


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 07:36:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00405
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 07:36:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRriq-0000TN-L1
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 07:37:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRrga-00013X-Eo; Wed, 10 Nov 2004 07:34:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRrc5-0000bW-Tg
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 07:30:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29611
	for <sipping@ietf.org>; Wed, 10 Nov 2004 07:30:12 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRrd3-0000Ls-3F
	for sipping@ietf.org; Wed, 10 Nov 2004 07:31:13 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iAACP8XD022746; Wed, 10 Nov 2004 07:25:10 -0500 (EST)
Received: by nhmail2.eng.brooktrout.com with Internet Mail Service
	(5.5.2653.19) id <W31JZ1NK>; Wed, 10 Nov 2004 07:22:14 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331C1112B@nhmail2.eng.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: ??? <tgkang@etri.re.kr>
Subject: RE: [sipping] Intelligent Transcoding Gateway Model for Transcodi ng
Date: Wed, 10 Nov 2004 07:22:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="KS_C_5601-1987"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

This actually is an old idea, of which I can think of three different
implementations.

There is clear market need for such a service.

There also clearly is the technology to do the service.  Let's pick one of
the many ways of doing this, or develop another one.  Either way, let's
bang this one out.

-----Original Message-----
From: tgkang@etri.re.kr [mailto:tgkang@etri.re.kr]
Sent: Monday, November 01, 2004 7:00 AM
To: 'sipping@ietf.org'
Subject: [sipping] Intelligent Transcoding Gateway Model for Transcoding


I would like to send you my first internet draft. 
I submitted it to 'internet-drafts@ietf.org' on 14 of October, but it is
not yet posted. 
So, I am sending you the file. 
If you have any comment or question for it, please send email to me. 
with regards Tae-Gyu Kang 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 09:30:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12031
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 09:30:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRtV6-0003K3-PO
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 09:31:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRtSM-0001gl-CB; Wed, 10 Nov 2004 09:28:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRtLN-0008NM-Tg
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 09:21:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11035
	for <sipping@ietf.org>; Wed, 10 Nov 2004 09:21:04 -0500 (EST)
Received: from [65.220.123.3] (helo=mail.pingtel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtMJ-00034G-0b
	for sipping@ietf.org; Wed, 10 Nov 2004 09:22:06 -0500
Received: from [10.1.1.152] (hide.pingtel.com [65.220.123.2])
	by mail.pingtel.com (8.11.6/8.11.6) with ESMTP id iAAEL0229310;
	Wed, 10 Nov 2004 09:21:00 -0500
Subject: Re: [Sipping] profile-datasets-00
From: Scott Lawrence <slawrence@pingtel.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BDB16339.189B9%fluffy@cisco.com>
References: <BDB16339.189B9%fluffy@cisco.com>
Content-Type: text/plain
Organization: Pingtel Corp.  http://www.pingtel.com/
Message-Id: <1100096460.4570.1.camel@cdhcp152.pingtel.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Wed, 10 Nov 2004 09:21:00 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: Daniel Petrie <dpetrie@pingtel.com>, sipping <sipping@ietf.org>,
        Scott Lawrence <slawrence@pingtel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit

On Fri, 2004-11-05 at 20:04, Cullen Jennings wrote:
> This seems to have gotten tangled up into the policy work in sort of scary
> way. 

We are very much aware of the overlap, and have been discussing how to
unify them appropriately.

> The phone know if it supports g711 or not - what I want to configure
> into my phone is what the username and AOR are, an outbound proxy, a speed
> dial list, things like that.

But there are a great many other things that administrators of networks
want to configure into user agents.

> Not clear what a UA subscribes to to get a particular dataset.

That is dealt with in draft-ietf-sipping-config-framework-*

> I think you intend to do this but  - we have to deal with the access control
> in section 4.2 from the beginning because we won't be able to add it in a
> backwards compatible way

Absolutely - we just didn't get it into the -00 draft.

> 4.3.1 might want to expand iff

yes, probably.

> I hate the forbid, set_all, set_one etc stuff in this. This is not a
> document to describe to a phone how to render a user interfaces for the user
> to select how to configure the phones. It's the data that is the
> configuration for the phone.

The intent was certainly not to specify a user interface.  Configuring
real devices in real networks is complex - it can't be done by
specifying a bunch of separate data values.  Configuration parameters
have relationships between them, and the profile mechanism needs to be
able to express those relationships; that's what all that is about.  
The other aspect of the containers that I think is convenient is that
they express what is required or forbidden - separating that from the
expression of the data values themselves.

> We have to address the merging issues not just leave it TBD and I suspect
> that it is data specific.

In a discussion we had with several interested people in San Diego we
reached the same conclusion - and agreed with everyone that more
guidance on merging is certainly needed.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 09:59:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15184
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 09:59:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRtxv-0004CT-Gk
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 10:00:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRttV-0006XT-BF; Wed, 10 Nov 2004 09:56:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRthN-00043R-Do
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 09:43:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13289
	for <sipping@ietf.org>; Wed, 10 Nov 2004 09:43:47 -0500 (EST)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtiL-0003e3-FK
	for sipping@ietf.org; Wed, 10 Nov 2004 09:44:50 -0500
Received: from [130.129.134.164] ([130.129.134.164]) (authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iAAEheC26216;
	Wed, 10 Nov 2004 06:43:40 -0800
In-Reply-To: <76592C4D3DA1AC4FB8424084D10D31A804D10A21@mchh2c4e.mchh.siemens.de>
References: <76592C4D3DA1AC4FB8424084D10D31A804D10A21@mchh2c4e.mchh.siemens.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E8A983B8-3326-11D9-AEBF-000D93C60450@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Subject: Re: AW: [Sipping] Comments on the FSM in dialog package -05 
Date: Wed, 10 Nov 2004 09:43:38 -0500
To: Tan Ya-Ching <ya-ching.tan@siemens.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, hgs@cs.columbia.edu
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit

Hi,

If you want to propose specific language for a change to RFC 3261 that 
would get incorporated if we do an errata, please send a short note to 
the SIP list with the current text and the proposed text.

many thanks,
-rohan

On Nov 10, 2004, at 3:33, Tan Ya-Ching wrote:
> Hi,
>
> Thanks for your answer. My further comments below :
>
>>>   But RFC 3261 (12.2.1.2 Processing the Responses) states that :
>>>
>>>   "If the response for a request within a dialog is a 481
>>>   (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the
>>>   UAC SHOULD terminate the dialog.  A UAC SHOULD also terminate a
>>>   dialog if no response at all is received for the request (the 
>>> client
>>>   transaction would inform the TU about the timeout.)
>>>
>>>      For INVITE initiated dialogs, terminating the dialog consists of
>>>      sending a BYE."
>>>
>>>   It is stated specifically that terminating the dialog consists of
>>>   sending a BYE. Therefore, the "error" event and "timeout"
>>>   event in the FSM should not directly lead to the terminated
>>>   state. Only the "local-bye" and "remote-bye" events could lead to
>>>   the terminated state.
>
>> No, according to RFC 3261 section 12.2.1.2 which you quote above, if I
>> send a reINVITE, OPTIONS, PRACK, INFO, UPDATE, or other in-dialog
>> request and get a 408, timeout, or 481, then the state of the dialog
>> moves to terminated.
>
> If that is so, why doesn't RFC 3261 quoted above simply state that
> "the dialog terminates" instead of "the UAC SHOULD terminate the 
> dialog",
> and as I pointed above, it further clarifies that "terminating the
> dialog consists of sending a BYE".
>
> For similar situation in RFC 3265 :
>
> "If a NOTIFY request receives a 481 response, the notifier MUST
> remove the corresponding subscription..."  and
> "If a subscription's destruction leaves no other application state
> associated with the dialog, the dialog terminates".
>
> There it is clear that the dialog simply terminates, with no
> further action required from the UAC.
>
> Ya-Ching


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 10:51:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22794
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 10:51:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRule-0005Ws-F9
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 10:52:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRudK-0006tF-UA; Wed, 10 Nov 2004 10:43:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRuTn-0004mM-6B
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 10:33:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20724
	for <sipping@ietf.org>; Wed, 10 Nov 2004 10:33:48 -0500 (EST)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRuUl-00055R-Co
	for sipping@ietf.org; Wed, 10 Nov 2004 10:34:51 -0500
Received: from [130.129.134.164] ([130.129.134.164]) (authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iAAFXgC27133;
	Wed, 10 Nov 2004 07:33:42 -0800
In-Reply-To: <76592C4D3DA1AC4FB8424084D10D31A804D10A33@mchh2c4e.mchh.siemens.de>
References: <76592C4D3DA1AC4FB8424084D10D31A804D10A33@mchh2c4e.mchh.siemens.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <E5F162D0-332D-11D9-AEBF-000D93C60450@ekabal.com>
Content-Transfer-Encoding: quoted-printable
From: Rohan Mahy <rohan@ekabal.com>
Subject: Re: AW: AW: [Sipping] Comments on the FSM in dialog package -05 
Date: Wed, 10 Nov 2004 10:33:40 -0500
To: Tan Ya-Ching <ya-ching.tan@siemens.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org, hgs@cs.columbia.edu
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Content-Transfer-Encoding: quoted-printable

Hi,

After a 481 is received on a mid-dialog request, the *local* state of=20
the dialog package is that the dialog is terminated. I think the=20
current language in RFC3261 is sufficiently clear to convey this.  If=20
you disagree, then feel free to suggest some text.  If you don't wish=20
to, don't send text. Sending a BYE or not sending a BYE at this point=20
does not affect this *local* state.  The dialog package only deals with=20=

the local view of this state and does not comment on any other protocol=20=

requirements.  For example, the dialog package does not (and should=20
not) comment on what happens when (for example) a 401 response to a=20
mid-dialog request is received, because this does not affect the=20
*local* state.

thanks,
-rohan


On Nov 10, 2004, at 10:20, Tan Ya-Ching wrote:
> Hi,
>
> Why should I do an errata when I don't think there is any error or=20
> ambiquity in RFC 3261 regarding this. It says "the UAC SHOULD=20
> terminate the dialog" and "terminating the dialog consists of sending=20=

> a BYE".
>
> The problem is that the dialog package implies that a dialog simply=20
> terminates when a mid-dialog request generates a 481 or 408 response.=20=

> If that is the way you think it should be, perhaps you should do an=20
> errata for RFC 3261.
>
> The same is with the "replace". The draft states that :
>
> "If the UAC (why not UAS?) receives a new invitation (with a Replace=20=

> header) which replaces the current Early or Confirmed dialog, all=20
> INVITE transactions(you probably mean INVITE dialogs here) spawned=20
> from the replaced invitation transition to the "terminated" state"
>
> RFC 3891 does not state that Early or Confirmed dialogs simply=20
> terminate on reception of the new invitation, but the UAS has to=20
> terminate the dialogs with CANCEL or BYE, as appropriate. So as far as=20=

> these dialogs are concerned, they are terminated by the event=20
> "cancelled" or "BYE", even though the trigger for the CANCEL or BYE=20
> may be "replaced".
>
> Ya-Ching
>
>
> -----Urspr=FCngliche Nachricht-----
> Von: Rohan Mahy [mailto:rohan@ekabal.com]
> Gesendet: Mittwoch, 10. November 2004 15:44
> An: Tan Ya-Ching
> Cc: sipping@ietf.org; 'Jonathan Rosenberg'; hgs@cs.columbia.edu
> Betreff: Re: AW: [Sipping] Comments on the FSM in dialog package -05
>
>
> Hi,
>
> If you want to propose specific language for a change to RFC 3261 that
> would get incorporated if we do an errata, please send a short note to
> the SIP list with the current text and the proposed text.
>
> many thanks,
> -rohan
>
> On Nov 10, 2004, at 3:33, Tan Ya-Ching wrote:
>> Hi,
>>
>> Thanks for your answer. My further comments below :
>>
>>>>   But RFC 3261 (12.2.1.2 Processing the Responses) states that :
>>>>
>>>>   "If the response for a request within a dialog is a 481
>>>>   (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the
>>>>   UAC SHOULD terminate the dialog.  A UAC SHOULD also terminate a
>>>>   dialog if no response at all is received for the request (the
>>>> client
>>>>   transaction would inform the TU about the timeout.)
>>>>
>>>>      For INVITE initiated dialogs, terminating the dialog consists=20=

>>>> of
>>>>      sending a BYE."
>>>>
>>>>   It is stated specifically that terminating the dialog consists of
>>>>   sending a BYE. Therefore, the "error" event and "timeout"
>>>>   event in the FSM should not directly lead to the terminated
>>>>   state. Only the "local-bye" and "remote-bye" events could lead to
>>>>   the terminated state.
>>
>>> No, according to RFC 3261 section 12.2.1.2 which you quote above, if=20=

>>> I
>>> send a reINVITE, OPTIONS, PRACK, INFO, UPDATE, or other in-dialog
>>> request and get a 408, timeout, or 481, then the state of the dialog
>>> moves to terminated.
>>
>> If that is so, why doesn't RFC 3261 quoted above simply state that
>> "the dialog terminates" instead of "the UAC SHOULD terminate the
>> dialog",
>> and as I pointed above, it further clarifies that "terminating the
>> dialog consists of sending a BYE".
>>
>> For similar situation in RFC 3265 :
>>
>> "If a NOTIFY request receives a 481 response, the notifier MUST
>> remove the corresponding subscription..."  and
>> "If a subscription's destruction leaves no other application state
>> associated with the dialog, the dialog terminates".
>>
>> There it is clear that the dialog simply terminates, with no
>> further action required from the UAC.
>>
>> Ya-Ching


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 11:18:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26323
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 11:18:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRvC5-0006Mm-Rp
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 11:19:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRv6V-00005j-Uu; Wed, 10 Nov 2004 11:13:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRuvr-0003L2-AG
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 11:02:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24419
	for <sipping@ietf.org>; Wed, 10 Nov 2004 11:02:48 -0500 (EST)
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRuwo-0005tH-Kg
	for sipping@ietf.org; Wed, 10 Nov 2004 11:03:51 -0500
Received: from eamrcnt751.exu.ericsson.se (eamrcnt751.exu.ericsson.se
	[138.85.133.52])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id iAAG35CR027917;
	Wed, 10 Nov 2004 10:03:05 -0600 (CST)
Received: from ericsson.com (EFO9N000L5C7100 [153.88.41.89]) by
	eamrcnt751.exu.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTA1T2QD; Wed, 10 Nov 2004 10:02:16 -0600
Message-ID: <41923B82.70900@ericsson.com>
Date: Wed, 10 Nov 2004 18:02:10 +0200
X-Sybari-Trust: e1acd7ad 8cefd49f bdcc08c1 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: Paul Kyzivat <pkyzivat@cisco.com>
References: <418BECB8.4010008@cisco.com>
In-Reply-To: <418BECB8.4010008@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Re: draft-ietf-sipping-uri-list-message-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Paul,

you are right. We will fix it.

Thanks,

Gonzalo

Paul Kyzivat wrote:

> Gonzalo,
> 
> One small point:
> 
> When the list server generates the recipient-list in the outbound 
> messages, I think it should be specifying:
> 
>     Content-Disposition: recipient-list;handling=optional
> 
> This way a recipient that doesn't understand this part will be free to 
> ignore it. As currently specified, since it isn't specified, the 
> handling defaults to required, and a well behaved mime processor should 
> consider it an error if it doesn't understand what to do with it.
> 
>     Paul

-- 
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 sipping-bounces@ietf.org  Wed Nov 10 11:23:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26658
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 11:23:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRvGQ-0006T7-Q8
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 11:24:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRvA4-0000pZ-OT; Wed, 10 Nov 2004 11:17:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRuxF-0003ou-BP
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 11:04:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24555
	for <sipping@ietf.org>; Wed, 10 Nov 2004 11:04:14 -0500 (EST)
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRuyE-0005w6-BM
	for sipping@ietf.org; Wed, 10 Nov 2004 11:05:18 -0500
Received: from eamrcnt751.exu.ericsson.se (eamrcnt751.exu.ericsson.se
	[138.85.133.52])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id iAAG4XCR028244;
	Wed, 10 Nov 2004 10:04:33 -0600 (CST)
Received: from ericsson.com (EFO9N000L5C7100 [153.88.41.89]) by
	eamrcnt751.exu.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTA1T28Y; Wed, 10 Nov 2004 10:03:43 -0600
Message-ID: <41923BDA.1030506@ericsson.com>
Date: Wed, 10 Nov 2004 18:03:38 +0200
X-Sybari-Trust: d1fadd71 8cefd49f bdcc08c1 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: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] Re: draft-ietf-sipping-uri-list-message-01
References: <418BECB8.4010008@cisco.com> <418BF515.9040409@cisco.com>
In-Reply-To: <418BF515.9040409@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit

Paul,

yes, we will use a different content disposition.

Thanks for all your comments,

Gonzalo

Paul Kyzivat wrote:

> Oops! One more thing - maybe more significant:
> 
> You are overloading the recipient-list semantics - to the list server is 
> specifies who to send the message to, while to the ultimate recipient it 
> identifies who the message *was* sent to. But what happens if one of the 
> recipients happens to be a message list server? Nothing good.
> 
> To solve this you could use a different content-disposition type, or you 
> might consider introducing parameters to the recipient-list 
> content-disposition to distinguish these uses. The simplest might be to 
> simply use content-disposition of "render", while continuing to use the 
> application/resource-lists+xml content-type.
> 
> (The need for handling=optional remains.)
> 
>     Paul
> 
> Paul Kyzivat wrote:
> 
>> Gonzalo,
>>
>> One small point:
>>
>> When the list server generates the recipient-list in the outbound 
>> messages, I think it should be specifying:
>>
>>     Content-Disposition: recipient-list;handling=optional
>>
>> This way a recipient that doesn't understand this part will be free to 
>> ignore it. As currently specified, since it isn't specified, the 
>> handling defaults to required, and a well behaved mime processor 
>> should consider it an error if it doesn't understand what to do with it.
>>
>>     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
>>

-- 
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 sipping-bounces@ietf.org  Wed Nov 10 11:29:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27465
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 11:29:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRvMQ-0006dI-NG
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 11:30:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRvER-0001qH-0V; Wed, 10 Nov 2004 11:22:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRv8V-0000VY-Sw
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 11:15:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25805
	for <sipping@ietf.org>; Wed, 10 Nov 2004 11:15:53 -0500 (EST)
Received: from [65.220.123.3] (helo=mail.pingtel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRv9U-0006FK-On
	for sipping@ietf.org; Wed, 10 Nov 2004 11:16:57 -0500
Received: from [10.1.1.152] (hide.pingtel.com [65.220.123.2])
	by mail.pingtel.com (8.11.6/8.11.6) with ESMTP id iAAGE9231466;
	Wed, 10 Nov 2004 11:14:14 -0500
Subject: RE: [Sipping] profile-datasets-00
From: Scott Lawrence <slawrence@pingtel.com>
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D025EC0D@EXC01C.cselt.it>
References: <E5880434292FCB448F00BDAEE44A60D025EC0D@EXC01C.cselt.it>
Content-Type: text/plain
Organization: Pingtel Corp.  http://www.pingtel.com/
Message-Id: <1100103248.4570.9.camel@cdhcp152.pingtel.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Wed, 10 Nov 2004 11:14:08 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit


> I also think that the forbid, set_all, set_one and set_any elements
> serve the policy purpose and should not be defined in this document.
> Rather, the precise definition of the data sets (XML schemas) seems to
> me a more important issue. It should align in some way with
> session-indep-policy-01 to simplify the delivery of UA profile data
> based on the profile delivery framework.

> It could also be useful to split the profile data in two sections, one
> with plain settings and the other with possible combinations of such
> settings, for example to force some codec to be used in concordance to
> an outbound proxy (acting as RTP proxy/transcoder), or when trying to
> set a codec from a list, some codecs may require the device to point
> toward such a proxy while others may use a different one.

That is exactly what the set_all, set_one and set_any constructs are
meant to accomplish.  By combining them, you can express how settings
interact.

Yes, there is overlap with policy - I'm not sure that in the real world
the two can be completely separated, and there is work to be done to
harmonize the two approaches - we've come at overlapping problems from
two different perspectives, and we all agree that there is work to do to
converge.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 10 19:49:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24391
	for <sipping-web-archive@ietf.org>; Wed, 10 Nov 2004 19:49:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CS3Ak-0003dR-IM
	for sipping-web-archive@ietf.org; Wed, 10 Nov 2004 19:50:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS34c-0007X3-Sx; Wed, 10 Nov 2004 19:44:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS2zj-0006ju-4C
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 19:39:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23434
	for <sipping@ietf.org>; Wed, 10 Nov 2004 19:39:19 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS30l-0003NF-UN
	for sipping@ietf.org; Wed, 10 Nov 2004 19:40:29 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-4.cisco.com with ESMTP; 10 Nov 2004 16:39:27 -0800
X-BrightmailFiltered: true
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.10/8.12.6) with ESMTP id iAB0cjnC025915
	for <sipping@ietf.org>; Wed, 10 Nov 2004 16:38:46 -0800 (PST)
Received: from [130.129.133.34] (sjc-vpn1-580.cisco.com [10.21.98.68])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATX24211;
	Wed, 10 Nov 2004 16:38:47 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Wed, 10 Nov 2004 19:38:47 -0500
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDB81EC7.1953D%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: [Sipping] comment on conference package
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit


The display-text field seems semantic free. I don't know what goes in here,
how I can use it, or how it gets set. I asked a few different people and got
a few different answers.

Alan gave one that I thought sounded like a good idea. I think he suggested
that it was text to display in the roster and it was set by a non SIP means
such as a profile that the user had on the conferencing system.

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 sipping-bounces@ietf.org  Thu Nov 11 05:03:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20146
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 05:03:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSBoj-0005kS-GF
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 05:04:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSBkU-0004Mo-JT; Thu, 11 Nov 2004 05:00:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSBi0-0003zH-Op
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 04:57:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19726
	for <sipping@ietf.org>; Thu, 11 Nov 2004 04:57:38 -0500 (EST)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSBj8-0005cI-Sk
	for sipping@ietf.org; Thu, 11 Nov 2004 04:58:51 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id iAB9vcfO003140
	for <sipping@ietf.org>; Thu, 11 Nov 2004 10:57:38 +0100
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id iAB9vcBO023672
	for <sipping@ietf.org>; Thu, 11 Nov 2004 10:57:38 +0100
Received: from mchh246e.mchh.siemens.de (mchh246e.mchh.siemens.de
	[139.21.200.56])
	by moody.mchh.siemens.de (8.12.6/8.12.6) with ESMTP id iAB9vc17012638
	for <sipping@ietf.org>; Thu, 11 Nov 2004 10:57:38 +0100
Received: by mchh246e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <47399B09>; Thu, 11 Nov 2004 10:57:38 +0100
Message-ID: <76592C4D3DA1AC4FB8424084D10D31A804D10A3D@mchh2c4e.mchh.siemens.de>
From: Tan Ya-Ching <ya-ching.tan@siemens.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: AW: AW: AW: [Sipping] Comments on the FSM in dialog package -05 
Date: Thu, 11 Nov 2004 10:57:34 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: quoted-printable

Hi,

If the dialog state is only maintained in the user agents, you may be =
right in saying that sending a BYE or not sending a BYE does not affect =
the state. But what if there is a state agent (eg. network agent) which =
is not the UA, but knows the state of the dialogs because it acts as a =
call-stateful proxy ? If it strictly follows RFC 3261, it cannot assume =
that a dialog terminates until the dialog is terminated with a BYE, and =
this is especially true in the case of "replace".=20

Thanks,
Ya-Ching


-----Urspr=FCngliche Nachricht-----
Von: Rohan Mahy [mailto:rohan@ekabal.com]=20
Gesendet: Mittwoch, 10. November 2004 16:34
An: Tan Ya-Ching
Cc: sipping@ietf.org; 'Jonathan Rosenberg'; hgs@cs.columbia.edu
Betreff: Re: AW: AW: [Sipping] Comments on the FSM in dialog package =
-05=20


Hi,

After a 481 is received on a mid-dialog request, the *local* state of=20
the dialog package is that the dialog is terminated. I think the=20
current language in RFC3261 is sufficiently clear to convey this.  If=20
you disagree, then feel free to suggest some text.  If you don't wish=20
to, don't send text. Sending a BYE or not sending a BYE at this point=20
does not affect this *local* state.  The dialog package only deals with =

the local view of this state and does not comment on any other protocol =

requirements.  For example, the dialog package does not (and should=20
not) comment on what happens when (for example) a 401 response to a=20
mid-dialog request is received, because this does not affect the=20
*local* state.

thanks,
-rohan


On Nov 10, 2004, at 10:20, Tan Ya-Ching wrote:
> Hi,
>
> Why should I do an errata when I don't think there is any error or=20
> ambiquity in RFC 3261 regarding this. It says "the UAC SHOULD=20
> terminate the dialog" and "terminating the dialog consists of sending =

> a BYE".
>
> The problem is that the dialog package implies that a dialog simply=20
> terminates when a mid-dialog request generates a 481 or 408 response. =

> If that is the way you think it should be, perhaps you should do an=20
> errata for RFC 3261.
>
> The same is with the "replace". The draft states that :
>
> "If the UAC (why not UAS?) receives a new invitation (with a Replace=20
> header) which replaces the current Early or Confirmed dialog, all=20
> INVITE transactions(you probably mean INVITE dialogs here) spawned=20
> from the replaced invitation transition to the "terminated" state"
>
> RFC 3891 does not state that Early or Confirmed dialogs simply=20
> terminate on reception of the new invitation, but the UAS has to=20
> terminate the dialogs with CANCEL or BYE, as appropriate. So as far =
as=20
> these dialogs are concerned, they are terminated by the event=20
> "cancelled" or "BYE", even though the trigger for the CANCEL or BYE=20
> may be "replaced".
>
> Ya-Ching
>
>
> -----Urspr=FCngliche Nachricht-----
> Von: Rohan Mahy [mailto:rohan@ekabal.com]
> Gesendet: Mittwoch, 10. November 2004 15:44
> An: Tan Ya-Ching
> Cc: sipping@ietf.org; 'Jonathan Rosenberg'; hgs@cs.columbia.edu
> Betreff: Re: AW: [Sipping] Comments on the FSM in dialog package -05
>
>
> Hi,
>
> If you want to propose specific language for a change to RFC 3261 =
that
> would get incorporated if we do an errata, please send a short note =
to
> the SIP list with the current text and the proposed text.
>
> many thanks,
> -rohan
>
> On Nov 10, 2004, at 3:33, Tan Ya-Ching wrote:
>> Hi,
>>
>> Thanks for your answer. My further comments below :
>>
>>>>   But RFC 3261 (12.2.1.2 Processing the Responses) states that :
>>>>
>>>>   "If the response for a request within a dialog is a 481
>>>>   (Call/Transaction Does Not Exist) or a 408 (Request Timeout), =
the
>>>>   UAC SHOULD terminate the dialog.  A UAC SHOULD also terminate a
>>>>   dialog if no response at all is received for the request (the
>>>> client
>>>>   transaction would inform the TU about the timeout.)
>>>>
>>>>      For INVITE initiated dialogs, terminating the dialog consists =

>>>> of
>>>>      sending a BYE."
>>>>
>>>>   It is stated specifically that terminating the dialog consists =
of
>>>>   sending a BYE. Therefore, the "error" event and "timeout"
>>>>   event in the FSM should not directly lead to the terminated
>>>>   state. Only the "local-bye" and "remote-bye" events could lead =
to
>>>>   the terminated state.
>>
>>> No, according to RFC 3261 section 12.2.1.2 which you quote above, =
if=20
>>> I
>>> send a reINVITE, OPTIONS, PRACK, INFO, UPDATE, or other in-dialog
>>> request and get a 408, timeout, or 481, then the state of the =
dialog
>>> moves to terminated.
>>
>> If that is so, why doesn't RFC 3261 quoted above simply state that
>> "the dialog terminates" instead of "the UAC SHOULD terminate the
>> dialog",
>> and as I pointed above, it further clarifies that "terminating the
>> dialog consists of sending a BYE".
>>
>> For similar situation in RFC 3265 :
>>
>> "If a NOTIFY request receives a 481 response, the notifier MUST
>> remove the corresponding subscription..."  and
>> "If a subscription's destruction leaves no other application state
>> associated with the dialog, the dialog terminates".
>>
>> There it is clear that the dialog simply terminates, with no
>> further action required from the UAC.
>>
>> Ya-Ching

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 05:06:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20469
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 05:06:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSBrO-0005ob-LW
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 05:07:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSBkV-0004Mz-Ov; Thu, 11 Nov 2004 05:00:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSBiJ-00043w-J2
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 04:58:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19748
	for <sipping@ietf.org>; Thu, 11 Nov 2004 04:57:57 -0500 (EST)
Received: from cms1.etri.re.kr ([129.254.16.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSBjR-0005c2-7N
	for sipping@ietf.org; Thu, 11 Nov 2004 04:59:10 -0500
Received: by cms1 with Internet Mail Service (5.5.2657.72)
	id <VRH203NN>; Thu, 11 Nov 2004 18:57:25 +0900
Message-ID: <0957B4ABF486CF4E8494A29B85DEE51016A5E3@cms1>
From: =?euc-kr?B?sK3FwrHU?= <tgkang@etri.re.kr>
To: "'Eric Burger'" <eburger@brooktrout.com>
Subject: RE: [sipping] Intelligent Transcoding Gateway Model for Transcodi ng
Date: Thu, 11 Nov 2004 18:57:17 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-RCPTTO: tgkang@etri.re.kr
X-Mailer: tgkang@etri.re.kr
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0585655418=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f

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.

--===============0585655418==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C7D4.D3AAF1AA"

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_01C4C7D4.D3AAF1AA
Content-Type: text/plain;
	charset="euc-kr"

Thank you for your reponse.

I don't know exactly three different implementations what you said. Could
you explain for them?

Nobody knows a real market need. but, I can guess that network conversion
market with transcoding technology will be growing near future.
Because there are existing several networks, PSTN, 3GPP, ITSP(internet
Telephony Service Provider using wired and wireless LAN VoIP), 
with different codecs.

Taegyu Kang  
---------------------------
Eric Burger[eburger@brooktrout.com]
'sipping@ietf.org'
RE: [sipping] Intelligent Transcoding Gateway Model for Transcodi ng
2004/11/10 21:22


This actually is an old idea, of which I can think of three different
implementations.

There is clear market need for such a service.

There also clearly is the technology to do the service. Let's pick one of
the many ways of doing this, or develop another one. Either way, let's
bang this one out.

-----Original Message-----
From: tgkang@etri.re.kr [mailto:tgkang@etri.re.kr]
Sent: Monday, November 01, 2004 7:00 AM
To: 'sipping@ietf.org'
Subject: [sipping] Intelligent Transcoding Gateway Model for Transcoding


I would like to send you my first internet draft. 
I submitted it to 'internet-drafts@ietf.org' on 14 of October, but it is
not yet posted. 
So, I am sending you the file. 
If you have any comment or question for it, please send email to me. 
with regards Tae-Gyu Kang 

------_=_NextPart_001_01C4C7D4.D3AAF1AA
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>RE: [sipping] Intelligent Transcoding Gateway Model for =
Transcodi ng</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Thank you for your reponse.</FONT>
</P>

<P><FONT SIZE=3D2>I don't know exactly three different implementations =
what you said. Could you explain for them?</FONT>
</P>

<P><FONT SIZE=3D2>Nobody knows a real market need. but, I can guess =
that network conversion market with transcoding technology will be =
growing near future.</FONT></P>

<P><FONT SIZE=3D2>Because there are existing several networks, PSTN, =
3GPP, ITSP(internet Telephony Service Provider using wired and wireless =
LAN VoIP), </FONT></P>

<P><FONT SIZE=3D2>with different codecs.</FONT>
</P>

<P><FONT SIZE=3D2>Taegyu Kang&nbsp; </FONT>
<BR><FONT SIZE=3D2>---------------------------</FONT>
<BR><FONT SIZE=3D2>Eric Burger[eburger@brooktrout.com]</FONT>
<BR><FONT SIZE=3D2>'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>RE: [sipping] Intelligent Transcoding Gateway Model =
for Transcodi ng</FONT>
<BR><FONT SIZE=3D2>2004/11/10 21:22</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>This actually is an old idea, of which I can think of =
three different</FONT>
<BR><FONT SIZE=3D2>implementations.</FONT>
</P>

<P><FONT SIZE=3D2>There is clear market need for such a service.</FONT>
</P>

<P><FONT SIZE=3D2>There also clearly is the technology to do the =
service. Let's pick one of</FONT>
<BR><FONT SIZE=3D2>the many ways of doing this, or develop another one. =
Either way, let's</FONT>
<BR><FONT SIZE=3D2>bang this one out.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: tgkang@etri.re.kr [<A =
HREF=3D"mailto:tgkang@etri.re.kr">mailto:tgkang@etri.re.kr</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, November 01, 2004 7:00 AM</FONT>
<BR><FONT SIZE=3D2>To: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: [sipping] Intelligent Transcoding Gateway =
Model for Transcoding</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I would like to send you my first internet draft. =
</FONT>
<BR><FONT SIZE=3D2>I submitted it to 'internet-drafts@ietf.org' on 14 =
of October, but it is</FONT>
<BR><FONT SIZE=3D2>not yet posted. </FONT>
<BR><FONT SIZE=3D2>So, I am sending you the file. </FONT>
<BR><FONT SIZE=3D2>If you have any comment or question for it, please =
send email to me. </FONT>
<BR><FONT SIZE=3D2>with regards Tae-Gyu Kang </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C7D4.D3AAF1AA--


--===============0585655418==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0585655418==--



From sipping-bounces@ietf.org  Thu Nov 11 05:57:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24896
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 05:57:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSCek-0006w5-Gn
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 05:58:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSCcd-0004ZX-Pp; Thu, 11 Nov 2004 05:56:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSCbO-0004QP-Md
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 05:54:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24762
	for <sipping@ietf.org>; Thu, 11 Nov 2004 05:54:52 -0500 (EST)
From: tgkang@etri.re.kr
Received: from mail.ietf61.org ([130.129.16.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSCcW-0006tJ-W9
	for sipping@ietf.org; Thu, 11 Nov 2004 05:56:06 -0500
Received: from [130.129.130.225] (helo=LocalHost)
	by MAIL.ietf61.org with smtp (Exim 4.24; FreeBSD)
	id 1CSCaG-00037e-PE; Thu, 11 Nov 2004 05:53:44 -0500
To: "Eric Burger" <eburger@brooktrout.com>
Subject: RE: [sipping] Intelligent Transcoding Gateway Model for Transcoding
Date: Thu, 11 Nov 2004 19:54:48 +0900
Message-ID: <LFEAIALAKPMKHCOCINJHCEAICAAA.tgkang@etri.re.kr>
MIME-Version: 1.0
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: <EDD694D47377D7119C8400D0B77FD331C1112B@nhmail2.eng.brooktrout.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0142803602=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

--===============0142803602==
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

VGhhbmsgeW91IGZvciB5b3VyIHJlcG9uc2UuDQoNCkkgZG9uJ3Qga25vdyBleGFjdGx5IHRocmVl
IGRpZmZlcmVudCBpbXBsZW1lbnRhdGlvbnMgd2hhdCB5b3Ugc2FpZC4gQ291bGQgeW91IGV4cGxh
aW4gZm9yIHRoZW0/DQoNCk5vYm9keSBrbm93cyBhIHJlYWwgbWFya2V0IG5lZWQuIGJ1dCwgSSBj
YW4gZ3Vlc3MgdGhhdCBuZXR3b3JrIGNvbnZlcnNpb24gbWFya2V0IHdpdGggdHJhbnNjb2Rpbmcg
dGVjaG5vbG9neSB3aWxsIGJlIGdyb3dpbmcgbmVhciBmdXR1cmUuDQpCZWNhdXNlIHRoZXJlIGFy
ZSBleGlzdGluZyBzZXZlcmFsIG5ldHdvcmtzLCBQU1ROLCAzR1BQLCBJVFNQKGludGVybmV0IFRl
bGVwaG9ueSBTZXJ2aWNlIFByb3ZpZGVyIHVzaW5nIHdpcmVkIGFuZCB3aXJlbGVzcyBMQU4gVm9J
UCksIA0Kd2l0aCBkaWZmZXJlbnQgY29kZWNzLg0KDQpUYWVneXUgS2FuZyAgDQoNCi0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBFcmljIEJ1cmdlciBbbWFpbHRvOmVidXJnZXJAYnJv
b2t0cm91dC5jb21dDQpTZW50OiBXZWRuZXNkYXksIE5vdmVtYmVyIDEwLCAyMDA0IDk6MjIgUE0N
ClRvOiA/Pz8NCkNjOiAnc2lwcGluZ0BpZXRmLm9yZycNClN1YmplY3Q6IFJFOiBbc2lwcGluZ10g
SW50ZWxsaWdlbnQgVHJhbnNjb2RpbmcgR2F0ZXdheSBNb2RlbCBmb3INClRyYW5zY29kaW5nDQoN
Cg0KDQpUaGlzIGFjdHVhbGx5IGlzIGFuIG9sZCBpZGVhLCBvZiB3aGljaCBJIGNhbiB0aGluayBv
ZiB0aHJlZSBkaWZmZXJlbnQNCmltcGxlbWVudGF0aW9ucy4NCg0KVGhlcmUgaXMgY2xlYXIgbWFy
a2V0IG5lZWQgZm9yIHN1Y2ggYSBzZXJ2aWNlLg0KDQpUaGVyZSBhbHNvIGNsZWFybHkgaXMgdGhl
IHRlY2hub2xvZ3kgdG8gZG8gdGhlIHNlcnZpY2UuICBMZXQncyBwaWNrIG9uZSBvZg0KdGhlIG1h
bnkgd2F5cyBvZiBkb2luZyB0aGlzLCBvciBkZXZlbG9wIGFub3RoZXIgb25lLiAgRWl0aGVyIHdh
eSwgbGV0J3MNCmJhbmcgdGhpcyBvbmUgb3V0Lg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KRnJvbTogdGdrYW5nQGV0cmkucmUua3IgW21haWx0bzp0Z2thbmdAZXRyaS5yZS5rcl0NClNl
bnQ6IE1vbmRheSwgTm92ZW1iZXIgMDEsIDIwMDQgNzowMCBBTQ0KVG86ICdzaXBwaW5nQGlldGYu
b3JnJw0KU3ViamVjdDogW3NpcHBpbmddIEludGVsbGlnZW50IFRyYW5zY29kaW5nIEdhdGV3YXkg
TW9kZWwgZm9yIFRyYW5zY29kaW5nDQoNCg0KSSB3b3VsZCBsaWtlIHRvIHNlbmQgeW91IG15IGZp
cnN0IGludGVybmV0IGRyYWZ0LiANCkkgc3VibWl0dGVkIGl0IHRvICdpbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmcnIG9uIDE0IG9mIE9jdG9iZXIsIGJ1dCBpdCBpcw0Kbm90IHlldCBwb3N0ZWQuIA0K
U28sIEkgYW0gc2VuZGluZyB5b3UgdGhlIGZpbGUuIA0KSWYgeW91IGhhdmUgYW55IGNvbW1lbnQg
b3IgcXVlc3Rpb24gZm9yIGl0LCBwbGVhc2Ugc2VuZCBlbWFpbCB0byBtZS4gDQp3aXRoIHJlZ2Fy
ZHMgVGFlLUd5dSBLYW5nIA==



--===============0142803602==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
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
--===============0142803602==--


From sipping-bounces@ietf.org  Thu Nov 11 07:59:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05678
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 07:59:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSEZE-00012D-39
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 08:00:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSEV7-0006Bv-K2; Thu, 11 Nov 2004 07:56:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSETy-00064S-1C
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 07:55:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05360
	for <sipping@ietf.org>; Thu, 11 Nov 2004 07:55:21 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSEV8-0000wg-9L
	for sipping@ietf.org; Thu, 11 Nov 2004 07:56:34 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iABCrHek009019; Thu, 11 Nov 2004 07:53:19 -0500 (EST)
Received: by nhmail2.eng.brooktrout.com with Internet Mail Service
	(5.5.2653.19) id <W31JZ194>; Thu, 11 Nov 2004 07:50:22 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331C111F1@nhmail2.eng.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: tgkang@etri.re.kr
Subject: RE: [sipping] Intelligent Transcoding Gateway Model for Transcodi ng
Date: Thu, 11 Nov 2004 07:50:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d

1. Exploders directed to a xcod service (see netann -02)

2. Next-hop parameter in SIP Request-URI directed to a xcod service

3. Full B2BUA (What most SBC's do)



> -----Original Message-----
> From: tgkang@etri.re.kr [mailto:tgkang@etri.re.kr]
> Sent: Thursday, November 11, 2004 5:55 AM
> To: Eric Burger
> Cc: sipping@ietf.org
> Subject: RE: [sipping] Intelligent Transcoding Gateway Model 
> for Transcoding
> 
> 
> Thank you for your reponse.
> 
> I don't know exactly three different implementations what you 
> said. Could you explain for them?
> 
> Nobody knows a real market need. but, I can guess that 
> network conversion market with transcoding technology will be 
> growing near future.
> Because there are existing several networks, PSTN, 3GPP, 
> ITSP(internet Telephony Service Provider using wired and 
> wireless LAN VoIP), 
> with different codecs.
> 
> Taegyu Kang  
> 
> -----Original Message-----
> From: Eric Burger [mailto:eburger@brooktrout.com]
> Sent: Wednesday, November 10, 2004 9:22 PM
> To: ???
> Cc: 'sipping@ietf.org'
> Subject: RE: [sipping] Intelligent Transcoding Gateway Model for
> Transcoding
> 
> 
> 
> This actually is an old idea, of which I can think of three different
> implementations.
> 
> There is clear market need for such a service.
> 
> There also clearly is the technology to do the service.  
> Let's pick one of
> the many ways of doing this, or develop another one.  Either 
> way, let's
> bang this one out.
> 
> -----Original Message-----
> From: tgkang@etri.re.kr [mailto:tgkang@etri.re.kr]
> Sent: Monday, November 01, 2004 7:00 AM
> To: 'sipping@ietf.org'
> Subject: [sipping] Intelligent Transcoding Gateway Model for 
> Transcoding
> 
> 
> I would like to send you my first internet draft. 
> I submitted it to 'internet-drafts@ietf.org' on 14 of 
> October, but it is
> not yet posted. 
> So, I am sending you the file. 
> If you have any comment or question for it, please send email to me. 
> with regards Tae-Gyu Kang 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 09:52:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17033
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 09:52:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSGKM-0003pr-81
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 09:53:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSGGS-0001iw-QJ; Thu, 11 Nov 2004 09:49:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSGDB-00012Z-AB
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 09:46:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16493
	for <sipping@ietf.org>; Thu, 11 Nov 2004 09:46:07 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSGEJ-0003h1-EC
	for sipping@ietf.org; Thu, 11 Nov 2004 09:47:22 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 11 Nov 2004 06:59:32 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iABEjNcp011539;
	Thu, 11 Nov 2004 06:45:23 -0800 (PST)
Received: from [130.129.135.140] (sjc-vpn4-736.cisco.com [10.21.82.224])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFR22124;
	Thu, 11 Nov 2004 06:45:22 -0800 (PST)
Message-ID: <41937B03.4000508@cisco.com>
Date: Thu, 11 Nov 2004 09:45:23 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mahfuz Rahman <mahfuz@research.panasonic.com>
Subject: Re: [Sipping] device-info-01
References: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM>
In-Reply-To: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: a.ahmed@ntt.com, bhu@motorola.com, sipping@ietf.org,
        kumarb@research.panasonic.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit

I think there is an interesting question at the root of this draft. The 
interesting question is how to manage a "network" where the network 
includes all of the SIP user agents (and in particular, single user 
devices like softphones and hardphones). Management, in this context, 
includes configuration (where things like the config profile are 
targeted), but also includes fault management, accounting, performance 
and security management. This draft is targeted roughly in the area of 
device performance management, and thats a laudable goal.

However, I think the problem is fairly broad, and would benefit from a 
top-down look at what really needs to be done here, rather than jumping 
to an event package or OPTIONS or whatever. The problem is complicated 
because in many cases, these devices are run and managed by end users.

-Jonathan R.

Mahfuz Rahman wrote:

> Thanks Cullen for making some good comments. My response is as follows:  
> 
> OPTIONS method is used to query device capabilities such as supported methods,
> contnet types, codesc etc.. This draft defines data elements for device profile
> which is  different from the tags defined for OPTIONS. So if we like to define
> tags for each of the data elements we have defined in the profile it will be a long
> list. I am not sure if it is acceptable. Also, as you suggested to include multiple
> schemas and URLs for a device it would be difficult to represent using OPTIONS unless
> we allow attachment of a body in the OPTIONS response with the following content type: 
> application/device-profile+xml. 
> 
> I agree with you to add software version and also an optional UUID.
> 
> The status part will be extended in the future revision which might include a 
> common XML format. Currently it describes only how vendor specific status information
> can be retrieved. 
> 
> - mahfuz
> 
> -----Original Message-----
> From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> Behalf Of Cullen Jennings
> Sent: Saturday, November 06, 2004 6:19 PM
> To: sipping
> Subject: [Sipping] device-info-01
> 
> 
> Nice draft - few comments ...
> 
> As a completely alternative suggestions.... How much of this information can
> you get by just sending an OPTION request to the device.
> 
> I would remove all the discussion of the device status - you don't define
> anything about how to do it so the discussion does not help.
> 
> This reports things that should not change so rate of notifications is very
> very seldom.
> 
> I would add an optional UUID to the profile
> 
> You might want to add software version.
> 
> I would make the schema URL and name attributes of a schema object so that
> the device can lists multiple schema that it can support.
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Thu Nov 11 11:59:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01570
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 11:59:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSIIz-00072V-9A
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 12:00:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSIG6-0001H4-J1; Thu, 11 Nov 2004 11:57:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSI8P-0007iA-2I
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 11:49:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00388
	for <sipping@ietf.org>; Thu, 11 Nov 2004 11:49:18 -0500 (EST)
Received: from mail.sonusnet.com ([208.45.178.33] helo=revere.sonusnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSI9b-0006ix-6A
	for sipping@ietf.org; Thu, 11 Nov 2004 11:50:35 -0500
Received: from sonusms1.sonusnet.com (sonusms1 [10.128.32.93])
	by revere.sonusnet.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	iABGmn1l006308
	for <sipping@ietf.org>; Thu, 11 Nov 2004 11:48:49 -0500 (EST)
Received: from sonustxmail01.sonusnet.com (unverified) by sonusms1.sonusnet.com
	(Content Technologies SMTPRS 4.3.12) with ESMTP id
	<T6d33dfa1880a80205d438@sonusms1.sonusnet.com>; 
	Thu, 11 Nov 2004 11:48:49 -0500
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] device-info-01
Date: Thu, 11 Nov 2004 10:48:47 -0600
Message-ID: <8C0CF305DEE53240BC3739EB4DC557D705E1B4@sonustxmail01.sonusnet.com>
Thread-Topic: [Sipping] device-info-01
Thread-Index: AcTH/i7UfV43JzRsRtSq7DoVaUu1XwAACJ6w
From: "Summers, Kevin" <kevin.summers@sonusnet.com>
To: "Mahfuz Rahman" <mahfuz@research.panasonic.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org, bhu@motorola.com, a.ahmed@ntt.com,
        kumarb@research.panasonic.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Content-Transfer-Encoding: quoted-printable

Clearly, as deployments of SIP endpoints spread, this cloying issue must =
be addressed for those who need to manage SIP endpoints at some level.

To Jonathan's last comment, assuming that certain descriptive config =
data that is end-user settable (e.g., SIP UA make/type, software rev. =
level, etc), a query result may not accurately reflect the true data. =
For example, I can set my browser to look like Microsoft IE even though =
I am using a different browser (of course I might do this to ease my =
user experience with those web sites that are Microsoft IE optimized).

While it certainly *could* be done using SIP, I am not sure that a =
SIP-based mechanism is the most appropriate.

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]
Sent: Thursday, November 11, 2004 8:45 AM
To: Mahfuz Rahman
Cc: a.ahmed@ntt.com; bhu@motorola.com; sipping@ietf.org;
kumarb@research.panasonic.com
Subject: Re: [Sipping] device-info-01


I think there is an interesting question at the root of this draft. The=20
interesting question is how to manage a "network" where the network=20
includes all of the SIP user agents (and in particular, single user=20
devices like softphones and hardphones). Management, in this context,=20
includes configuration (where things like the config profile are=20
targeted), but also includes fault management, accounting, performance=20
and security management. This draft is targeted roughly in the area of=20
device performance management, and thats a laudable goal.

However, I think the problem is fairly broad, and would benefit from a=20
top-down look at what really needs to be done here, rather than jumping=20
to an event package or OPTIONS or whatever. The problem is complicated=20
because in many cases, these devices are run and managed by end users.

-Jonathan R.

Mahfuz Rahman wrote:

> Thanks Cullen for making some good comments. My response is as =
follows: =20
>=20
> OPTIONS method is used to query device capabilities such as supported =
methods,
> contnet types, codesc etc.. This draft defines data elements for =
device profile
> which is  different from the tags defined for OPTIONS. So if we like =
to define
> tags for each of the data elements we have defined in the profile it =
will be a long
> list. I am not sure if it is acceptable. Also, as you suggested to =
include multiple
> schemas and URLs for a device it would be difficult to represent using =
OPTIONS unless
> we allow attachment of a body in the OPTIONS response with the =
following content type:=20
> application/device-profile+xml.=20
>=20
> I agree with you to add software version and also an optional UUID.
>=20
> The status part will be extended in the future revision which might =
include a=20
> common XML format. Currently it describes only how vendor specific =
status information
> can be retrieved.=20
>=20
> - mahfuz
>=20
> -----Original Message-----
> From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> Behalf Of Cullen Jennings
> Sent: Saturday, November 06, 2004 6:19 PM
> To: sipping
> Subject: [Sipping] device-info-01
>=20
>=20
> Nice draft - few comments ...
>=20
> As a completely alternative suggestions.... How much of this =
information can
> you get by just sending an OPTION request to the device.
>=20
> I would remove all the discussion of the device status - you don't =
define
> anything about how to do it so the discussion does not help.
>=20
> This reports things that should not change so rate of notifications is =
very
> very seldom.
>=20
> I would add an optional UUID to the profile
>=20
> You might want to add software version.
>=20
> I would make the schema URL and name attributes of a schema object so =
that
> the device can lists multiple schema that it can support.
>=20
>=20
>=20
>=20
>=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
>=20
>=20
>=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
>=20

--=20
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Thu Nov 11 13:00:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07909
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 13:00:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSJGO-0000E7-Bg
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 13:01:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSJAa-0007cz-6g; Thu, 11 Nov 2004 12:55:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJ7y-0007CM-A2
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 12:52:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07342
	for <sipping@ietf.org>; Thu, 11 Nov 2004 12:52:55 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJ9B-0008W1-3n
	for sipping@ietf.org; Thu, 11 Nov 2004 12:54:13 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iABHpP2h017722;
	Thu, 11 Nov 2004 12:51:25 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id ABC903C8155;
	Thu, 11 Nov 2004 12:49:28 -0500 (EST)
Received: from MAHFUZT12K (dhcp222.Research.Panasonic.COM [150.169.1.222])by
	redwood.research.panasonic.com (Postfix) with SMTP id 87A393C8158;
	Thu, 11 Nov 2004 12:49:27 -0500 (EST)
Message-ID: <001a01c4c816$c93c1450$de01a996@MAHFUZT12K>
From: "Mahfuzur Rahman" <mahfuz@research.panasonic.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
References: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM> 
	<41937B03.4000508@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Thu, 11 Nov 2004 12:49:26 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:14 M:0 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit
Cc: a.ahmed@ntt.com, bhu@motorola.com, sipping@ietf.org,
        kumarb@research.panasonic.com,
        Mahfuzur Rahman <mahfuz@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: 7bit

The goal of this draft is not to provide solution for "network"  management.
This draft is addressing a very important use case where a user would like
to retrieve some information about a device particularly its status before
communicating with it. Status here refers to availability, location,
operating mode etc which has some similarity with presence as defined in
SIMPLE. The problem of this draft can be easily solved using an event
package.

The issue of "network" management (performance, fault management,
accounting, performance) is a different problem and out of the scope of this
draft. Hope this clarifies the issue.

- mahfuz

----- Original Message ----- 
From: "Jonathan Rosenberg" <jdrosen@cisco.com>
To: "Mahfuz Rahman" <mahfuz@research.panasonic.com>
Cc: <sipping@ietf.org>; <a.ahmed@ntt.com>; <bhu@motorola.com>;
<kumarb@research.panasonic.com>
Sent: Thursday, November 11, 2004 9:45 AM
Subject: Re: [Sipping] device-info-01


> I think there is an interesting question at the root of this draft. The
> interesting question is how to manage a "network" where the network
> includes all of the SIP user agents (and in particular, single user
> devices like softphones and hardphones). Management, in this context,
> includes configuration (where things like the config profile are
> targeted), but also includes fault management, accounting, performance
> and security management. This draft is targeted roughly in the area of
> device performance management, and thats a laudable goal.
>
> However, I think the problem is fairly broad, and would benefit from a
> top-down look at what really needs to be done here, rather than jumping
> to an event package or OPTIONS or whatever. The problem is complicated
> because in many cases, these devices are run and managed by end users.
>
> -Jonathan R.
>
> Mahfuz Rahman wrote:
>
> > Thanks Cullen for making some good comments. My response is as follows:
> >
> > OPTIONS method is used to query device capabilities such as supported
methods,
> > contnet types, codesc etc.. This draft defines data elements for device
profile
> > which is  different from the tags defined for OPTIONS. So if we like to
define
> > tags for each of the data elements we have defined in the profile it
will be a long
> > list. I am not sure if it is acceptable. Also, as you suggested to
include multiple
> > schemas and URLs for a device it would be difficult to represent using
OPTIONS unless
> > we allow attachment of a body in the OPTIONS response with the following
content type:
> > application/device-profile+xml.
> >
> > I agree with you to add software version and also an optional UUID.
> >
> > The status part will be extended in the future revision which might
include a
> > common XML format. Currently it describes only how vendor specific
status information
> > can be retrieved.
> >
> > - mahfuz
> >
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> > Behalf Of Cullen Jennings
> > Sent: Saturday, November 06, 2004 6:19 PM
> > To: sipping
> > Subject: [Sipping] device-info-01
> >
> >
> > Nice draft - few comments ...
> >
> > As a completely alternative suggestions.... How much of this information
can
> > you get by just sending an OPTION request to the device.
> >
> > I would remove all the discussion of the device status - you don't
define
> > anything about how to do it so the discussion does not help.
> >
> > This reports things that should not change so rate of notifications is
very
> > very seldom.
> >
> > I would add an optional UUID to the profile
> >
> > You might want to add software version.
> >
> > I would make the schema URL and name attributes of a schema object so
that
> > the device can lists multiple schema that it can support.
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
> Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.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 sipping-bounces@ietf.org  Thu Nov 11 13:50:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11543
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 13:50:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSK2l-0001D8-1C
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 13:51:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSJwC-0008RA-Ga; Thu, 11 Nov 2004 13:44:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJs4-0007QL-Mn
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 13:40:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11052
	for <sipping@ietf.org>; Thu, 11 Nov 2004 13:40:35 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJtH-00013l-3P
	for sipping@ietf.org; Thu, 11 Nov 2004 13:41:52 -0500
Received: from [130.129.132.245] ([130.129.132.245]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iABIeWRs085530
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 11 Nov 2004 12:40:33 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <4193B221.7070402@nostrum.com>
Date: Thu, 11 Nov 2004 12:40:33 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alan Johnston <alan.johnston@mci.com>,
        Henry Sinnreich <Henry.Sinnreich@mci.com>, alan@telchemy.com,
        aspen@nortelnetworks.com
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
Subject: [Sipping] PUBLISH in SIP Performance Report Event
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

I just want to make a quick comment on the use of PUBLISH in this
document. I think there needs to be some clarification on when this is
sent -- that is, how the UA knows that the proxy *wants* these
publication messages. From the text currently in the draft, this looks
an awful lot like using PUBLISH as an end-around sending unsolicited
NOTIFY messages by simply changing the method name. I hope that I've
misunderstood -- in which case some clarifying text might be in order;
otherwise, I'm very concerned about the precedent this document sets.

/a


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 14:31:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15390
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 14:31:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSKgh-0002F1-Rd
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 14:32:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSKaX-0000HH-Qc; Thu, 11 Nov 2004 14:26:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSKUm-0007NE-E7
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 14:20:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14253
	for <sipping@ietf.org>; Thu, 11 Nov 2004 14:20:35 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSKW0-0001vM-4C
	for sipping@ietf.org; Thu, 11 Nov 2004 14:21:52 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 11 Nov 2004 11:32:09 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iABJK1om028349;
	Thu, 11 Nov 2004 11:20:01 -0800 (PST)
Received: from [130.129.133.70] (sjc-vpn5-732.cisco.com [10.21.90.220])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id iABJKhTj011356;
	Thu, 11 Nov 2004 11:20:43 -0800
In-Reply-To: <4193B221.7070402@nostrum.com>
References: <4193B221.7070402@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
Date: Thu, 11 Nov 2004 14:19:59 -0500
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1100200844.723297"; x:"432200"; a:"rsa-sha1"; b:"nofws:1531";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"P1X8uXfP9DViCOSb/uRpVX9uRJO4IyH5lTyrvGVD2T63xJKZDOMqF/WT+Fytd"
	"1BoUfZQIRqLoSChXSaLBcXcDDWUjWKVJHRXAy7FJlaGteikYfl9zuqGrQ6vyT"
	"HO2fmBerWK8gX3VAMZZ3NDFkO67IK4MipGQvb9JvmAufgalC8=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event";
	c:"Date: Thu, 11 Nov 2004 14:19:59 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Alan Johnston <alan.johnston@mci.com>, aspen@nortelnetworks.com,
        sipping@ietf.org, Henry Sinnreich <Henry.Sinnreich@mci.com>,
        alan@telchemy.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit


On Nov 11, 2004, at 1:40 PM, Adam Roach wrote:

> I just want to make a quick comment on the use of PUBLISH in this
> document. I think there needs to be some clarification on when this is
> sent -- that is, how the UA knows that the proxy *wants* these
> publication messages.
If the server (not proxy, necessarily...) doesn't want them, it can 
send an error.

> From the text currently in the draft, this looks
> an awful lot like using PUBLISH as an end-around sending unsolicited
> NOTIFY messages by simply changing the method name. I hope that I've
> misunderstood -- in which case some clarifying text might be in order;
No you haven't fundamentally misunderstood - that's more or less what's 
going on. Just being honest here...

> otherwise, I'm very concerned about the precedent this document sets.
>
Could you elaborate on why you think this is a bad precedent?

The underlying motivation is so that the authorization is moved to the 
data collector rather than having the endpoint have to authorize 
subscriptions for this information.

> /a
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Thu Nov 11 15:43:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24748
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 15:43:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSLog-0004Hd-Ct
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 15:45:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSLgq-0007aE-MT; Thu, 11 Nov 2004 15:37:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSLZJ-0002EL-TO
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 15:29:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22621
	for <sipping@ietf.org>; Thu, 11 Nov 2004 15:29:20 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSLaY-0003j4-3e
	for sipping@ietf.org; Thu, 11 Nov 2004 15:30:38 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 11 Nov 2004 15:53:58 -0500
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iABKSmb3017191; 
	Thu, 11 Nov 2004 15:28:48 -0500 (EST)
Received: from cisco.com (rtp-vpn3-424.cisco.com [10.82.217.170])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMZ09159;
	Thu, 11 Nov 2004 15:28:46 -0500 (EST)
Message-ID: <4193CB7E.9080802@cisco.com>
Date: Thu, 11 Nov 2004 15:28:46 -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: Mahfuzur Rahman <mahfuz@research.panasonic.com>
Subject: Re: [Sipping] device-info-01
References: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM>
	<41937B03.4000508@cisco.com>
	<001a01c4c816$c93c1450$de01a996@MAHFUZT12K>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, bhu@motorola.com, a.ahmed@ntt.com,
        kumarb@research.panasonic.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Content-Transfer-Encoding: 7bit

As came out in the meeting discussion today, there are many questions 
about this particular use. But if this is your intent, and if anything 
is to come of it, then I think you need to be careful of terminology. 
(My earlier comments highlighted possible ambiguity in the terminology.)

Based on discussion and the text below, you don't seem to be talking 
about "device" info so much as proprietary UA info.

	Paul

Mahfuzur Rahman wrote:
> The goal of this draft is not to provide solution for "network"  management.
> This draft is addressing a very important use case where a user would like
> to retrieve some information about a device particularly its status before
> communicating with it. Status here refers to availability, location,
> operating mode etc which has some similarity with presence as defined in
> SIMPLE. The problem of this draft can be easily solved using an event
> package.
> 
> The issue of "network" management (performance, fault management,
> accounting, performance) is a different problem and out of the scope of this
> draft. Hope this clarifies the issue.
> 
> - mahfuz
> 
> ----- Original Message ----- 
> From: "Jonathan Rosenberg" <jdrosen@cisco.com>
> To: "Mahfuz Rahman" <mahfuz@research.panasonic.com>
> Cc: <sipping@ietf.org>; <a.ahmed@ntt.com>; <bhu@motorola.com>;
> <kumarb@research.panasonic.com>
> Sent: Thursday, November 11, 2004 9:45 AM
> Subject: Re: [Sipping] device-info-01
> 
> 
> 
>>I think there is an interesting question at the root of this draft. The
>>interesting question is how to manage a "network" where the network
>>includes all of the SIP user agents (and in particular, single user
>>devices like softphones and hardphones). Management, in this context,
>>includes configuration (where things like the config profile are
>>targeted), but also includes fault management, accounting, performance
>>and security management. This draft is targeted roughly in the area of
>>device performance management, and thats a laudable goal.
>>
>>However, I think the problem is fairly broad, and would benefit from a
>>top-down look at what really needs to be done here, rather than jumping
>>to an event package or OPTIONS or whatever. The problem is complicated
>>because in many cases, these devices are run and managed by end users.
>>
>>-Jonathan R.
>>
>>Mahfuz Rahman wrote:
>>
>>
>>>Thanks Cullen for making some good comments. My response is as follows:
>>>
>>>OPTIONS method is used to query device capabilities such as supported
>>
> methods,
> 
>>>contnet types, codesc etc.. This draft defines data elements for device
>>
> profile
> 
>>>which is  different from the tags defined for OPTIONS. So if we like to
>>
> define
> 
>>>tags for each of the data elements we have defined in the profile it
>>
> will be a long
> 
>>>list. I am not sure if it is acceptable. Also, as you suggested to
>>
> include multiple
> 
>>>schemas and URLs for a device it would be difficult to represent using
>>
> OPTIONS unless
> 
>>>we allow attachment of a body in the OPTIONS response with the following
>>
> content type:
> 
>>>application/device-profile+xml.
>>>
>>>I agree with you to add software version and also an optional UUID.
>>>
>>>The status part will be extended in the future revision which might
>>
> include a
> 
>>>common XML format. Currently it describes only how vendor specific
>>
> status information
> 
>>>can be retrieved.
>>>
>>>- mahfuz
>>>
>>>-----Original Message-----
>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>Behalf Of Cullen Jennings
>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>To: sipping
>>>Subject: [Sipping] device-info-01
>>>
>>>
>>>Nice draft - few comments ...
>>>
>>>As a completely alternative suggestions.... How much of this information
>>
> can
> 
>>>you get by just sending an OPTION request to the device.
>>>
>>>I would remove all the discussion of the device status - you don't
>>
> define
> 
>>>anything about how to do it so the discussion does not help.
>>>
>>>This reports things that should not change so rate of notifications is
>>
> very
> 
>>>very seldom.
>>>
>>>I would add an optional UUID to the profile
>>>
>>>You might want to add software version.
>>>
>>>I would make the schema URL and name attributes of a schema object so
>>
> that
> 
>>>the device can lists multiple schema that it can support.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the 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
>>Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
>>Cisco Systems
>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>http://www.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 sipping-bounces@ietf.org  Thu Nov 11 15:57:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26725
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 15:57:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSM1o-0004ft-5s
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 15:58:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSLuc-0007Sb-Cd; Thu, 11 Nov 2004 15:51:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSLol-0003jK-Uo
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 15:45:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25066
	for <sipping@ietf.org>; Thu, 11 Nov 2004 15:45:18 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSLpz-0004Jo-UI
	for sipping@ietf.org; Thu, 11 Nov 2004 15:46:36 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iABKieDh022865;
	Thu, 11 Nov 2004 15:44:40 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 53D033C8159;
	Thu, 11 Nov 2004 15:42:43 -0500 (EST)
Received: from MAHFUZT12K (dhcp222.Research.Panasonic.COM [150.169.1.222])by
	redwood.research.panasonic.com (Postfix) with SMTP id 157583C8159;
	Thu, 11 Nov 2004 15:42:43 -0500 (EST)
Message-ID: <009501c4c82e$fd93cff0$de01a996@MAHFUZT12K>
From: "Mahfuzur Rahman" <mahfuz@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
References: <4b35b4e3f6.4e3f64b35b@pintlmail.MITL.Research.Panasonic.COM> 
	<41937B03.4000508@cisco.com>
	<001a01c4c816$c93c1450$de01a996@MAHFUZT12K> 
	<4193CB7E.9080802@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Thu, 11 Nov 2004 15:42:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:14 M:0 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Content-Transfer-Encoding: 7bit
Cc: bhu@motorola.com, a.ahmed@ntt.com, kumarb@research.panasonic.com,
        Mahfuzur Rahman <mahfuz@research.panasonic.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Content-Transfer-Encoding: 7bit

We do not be mind to change or take suggestion on terminology to avoid any
possible confusion as long as the concept is clear.

-mahfuz

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Mahfuzur Rahman" <mahfuz@research.panasonic.com>
Cc: "Jonathan Rosenberg" <jdrosen@cisco.com>; <a.ahmed@ntt.com>;
<bhu@motorola.com>; <sipping@ietf.org>; <kumarb@research.panasonic.com>
Sent: Thursday, November 11, 2004 3:28 PM
Subject: Re: [Sipping] device-info-01


> As came out in the meeting discussion today, there are many questions
> about this particular use. But if this is your intent, and if anything
> is to come of it, then I think you need to be careful of terminology.
> (My earlier comments highlighted possible ambiguity in the terminology.)
>
> Based on discussion and the text below, you don't seem to be talking
> about "device" info so much as proprietary UA info.
>
> Paul
>
> Mahfuzur Rahman wrote:
> > The goal of this draft is not to provide solution for "network"
management.
> > This draft is addressing a very important use case where a user would
like
> > to retrieve some information about a device particularly its status
before
> > communicating with it. Status here refers to availability, location,
> > operating mode etc which has some similarity with presence as defined in
> > SIMPLE. The problem of this draft can be easily solved using an event
> > package.
> >
> > The issue of "network" management (performance, fault management,
> > accounting, performance) is a different problem and out of the scope of
this
> > draft. Hope this clarifies the issue.
> >
> > - mahfuz
> >
> > ----- Original Message ----- 
> > From: "Jonathan Rosenberg" <jdrosen@cisco.com>
> > To: "Mahfuz Rahman" <mahfuz@research.panasonic.com>
> > Cc: <sipping@ietf.org>; <a.ahmed@ntt.com>; <bhu@motorola.com>;
> > <kumarb@research.panasonic.com>
> > Sent: Thursday, November 11, 2004 9:45 AM
> > Subject: Re: [Sipping] device-info-01
> >
> >
> >
> >>I think there is an interesting question at the root of this draft. The
> >>interesting question is how to manage a "network" where the network
> >>includes all of the SIP user agents (and in particular, single user
> >>devices like softphones and hardphones). Management, in this context,
> >>includes configuration (where things like the config profile are
> >>targeted), but also includes fault management, accounting, performance
> >>and security management. This draft is targeted roughly in the area of
> >>device performance management, and thats a laudable goal.
> >>
> >>However, I think the problem is fairly broad, and would benefit from a
> >>top-down look at what really needs to be done here, rather than jumping
> >>to an event package or OPTIONS or whatever. The problem is complicated
> >>because in many cases, these devices are run and managed by end users.
> >>
> >>-Jonathan R.
> >>
> >>Mahfuz Rahman wrote:
> >>
> >>
> >>>Thanks Cullen for making some good comments. My response is as follows:
> >>>
> >>>OPTIONS method is used to query device capabilities such as supported
> >>
> > methods,
> >
> >>>contnet types, codesc etc.. This draft defines data elements for device
> >>
> > profile
> >
> >>>which is  different from the tags defined for OPTIONS. So if we like to
> >>
> > define
> >
> >>>tags for each of the data elements we have defined in the profile it
> >>
> > will be a long
> >
> >>>list. I am not sure if it is acceptable. Also, as you suggested to
> >>
> > include multiple
> >
> >>>schemas and URLs for a device it would be difficult to represent using
> >>
> > OPTIONS unless
> >
> >>>we allow attachment of a body in the OPTIONS response with the
following
> >>
> > content type:
> >
> >>>application/device-profile+xml.
> >>>
> >>>I agree with you to add software version and also an optional UUID.
> >>>
> >>>The status part will be extended in the future revision which might
> >>
> > include a
> >
> >>>common XML format. Currently it describes only how vendor specific
> >>
> > status information
> >
> >>>can be retrieved.
> >>>
> >>>- mahfuz
> >>>
> >>>-----Original Message-----
> >>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> >>>Behalf Of Cullen Jennings
> >>>Sent: Saturday, November 06, 2004 6:19 PM
> >>>To: sipping
> >>>Subject: [Sipping] device-info-01
> >>>
> >>>
> >>>Nice draft - few comments ...
> >>>
> >>>As a completely alternative suggestions.... How much of this
information
> >>
> > can
> >
> >>>you get by just sending an OPTION request to the device.
> >>>
> >>>I would remove all the discussion of the device status - you don't
> >>
> > define
> >
> >>>anything about how to do it so the discussion does not help.
> >>>
> >>>This reports things that should not change so rate of notifications is
> >>
> > very
> >
> >>>very seldom.
> >>>
> >>>I would add an optional UUID to the profile
> >>>
> >>>You might want to add software version.
> >>>
> >>>I would make the schema URL and name attributes of a schema object so
> >>
> > that
> >
> >>>the device can lists multiple schema that it can support.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >>>This list is for NEW development of the 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
> >>Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
> >>Cisco Systems
> >>jdrosen@cisco.com                              FAX:   (973) 952-5050
> >>http://www.jdrosen.net                         PHONE: (973) 952-5000
> >>http://www.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 sipping-bounces@ietf.org  Thu Nov 11 16:23:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29789
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 16:23:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSMRK-0005b0-65
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 16:25:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSMGc-0004Kc-3l; Thu, 11 Nov 2004 16:14:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMAk-0008Hs-8C
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 16:08:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28199
	for <sipping@ietf.org>; Thu, 11 Nov 2004 16:08:00 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSMBy-000598-Vp
	for sipping@ietf.org; Thu, 11 Nov 2004 16:09:19 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 11 Nov 2004 13:21:37 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iABL7GnC024489;
	Thu, 11 Nov 2004 13:07:16 -0800 (PST)
Received: from [130.129.135.140] (sjc-vpn5-601.cisco.com [10.21.90.89])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFR48799;
	Thu, 11 Nov 2004 13:07:25 -0800 (PST)
Message-ID: <4193D48C.1030700@cisco.com>
Date: Thu, 11 Nov 2004 16:07:24 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>
	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
In-Reply-To: <AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, alan@telchemy.com,
        Alan Johnston <alan.johnston@mci.com>, aspen@nortelnetworks.com,
        sipping@ietf.org, Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit



David R Oran wrote:

>> I just want to make a quick comment on the use of PUBLISH in this
>> document. I think there needs to be some clarification on when this is
>> sent -- that is, how the UA knows that the proxy *wants* these
>> publication messages.
> 
> If the server (not proxy, necessarily...) doesn't want them, it can send an error. 

Which error? Section 5 of RFC 3903 does not point out a condition which 
means,
"don't publish to this aor any more".


> 
>> From the text currently in the draft, this looks
>> an awful lot like using PUBLISH as an end-around sending unsolicited
>> NOTIFY messages by simply changing the method name. I hope that I've
>> misunderstood -- in which case some clarifying text might be in order;
> 
> No you haven't fundamentally misunderstood - that's more or less what's 
> going on. Just being honest here...
> 
>> otherwise, I'm very concerned about the precedent this document sets.
>>
> Could you elaborate on why you think this is a bad precedent?

I don't follow why its a bad precedent here and not everywhere else; 
PUBLISH is fundamentally about an unsolicited push of data to a 
collector. If doing that is bad, then PUBLISH is bad.

When you use PUBLISH, you do want to be sure that it is wanted. I think 
that is generally done by end system configuration/provisioning. You 
would only PUBLISH for a particular resource for a particular event 
package if a particular flag was set to do so.


-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Thu Nov 11 16:40:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01530
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 16:40:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSMhP-00061n-Mi
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 16:41:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSMSd-0002pT-1E; Thu, 11 Nov 2004 16:26:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMHI-0004ci-6M
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 16:14:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28858
	for <sipping@ietf.org>; Thu, 11 Nov 2004 16:14:46 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMIV-0005KE-I6
	for sipping@ietf.org; Thu, 11 Nov 2004 16:16:05 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 11 Nov 2004 13:14:28 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id iABLECcj004279;
	Thu, 11 Nov 2004 13:14:13 -0800 (PST)
Received: from [130.129.135.140] (sjc-vpn5-601.cisco.com [10.21.90.89])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFR49385;
	Thu, 11 Nov 2004 13:14:11 -0800 (PST)
Message-ID: <4193D623.8090103@cisco.com>
Date: Thu, 11 Nov 2004 16:14:11 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David <david@kayote.com>
Subject: Re: [Sipping] automatic answer
References: <200410310720.CAA03497@ietf.org>
In-Reply-To: <200410310720.CAA03497@ietf.org>
Content-Type: text/plain; charset=EUC-KR
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA28858
Cc: sipping@ietf.org, "'Dean Willis'" <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: quoted-printable

I still don't understand why the answering machine wouldn't know that it
is an answering machine. As long as it knows, it can know to pick up
immediately.

I do see value in allowing an answering machine to tell a caller that it
has reached an answering machine. We have that capability in RFC 3840,
which allows the UAS to indicate, through capability parameters in its
Contact header field in the 200 OK, that it is an answering machine.

Thanks,
Jonathan R.

David wrote:

> Hi Dean.
>=20
> While I totally agree that the network should not control the edges,
> however, I would contend that there is a difference between controlling=
 and
> informing. I do not see the harm in a network providing extra services =
to
> the edges in the form of additional information regarding the request a=
bout
> to be made. Whether in the case of voice mail or spam, I think that if =
the
> network has some info that it wishes to share it should do so and allow=
 the
> edge to decide what to do with this information. Thus, in this particul=
ar
> case the network does not have to KNOW that the edge is an answering
> machine, rather it could say "By the way, if you are an answering machi=
ne
> ...".=20
>=20
> David Schwartz=20
>=20
>=20
>>-----Original Message-----
>>From: sipping-bounces@ietf.org=20
>>[mailto:sipping-bounces@ietf.org] On Behalf Of Dean Willis
>>Sent: Thursday, October 28, 2004 8:15 PM
>>To: ???
>>Cc: sipping@ietf.org
>>Subject: Re: [Sipping] automatic answer
>>
>>=C8=B2=C1=F8=B0=E6 (Jinkyung Hwang) wrote:
>>
>>
>>>Hi,
>>>=20
>>>Is there any I-D regarding params for SIP phone to answer=20
>>>automatically ? (for answering machine functionality)
>>>=20
>>>I would like to know when the call arrives a phone, by which=20
>>>param/header value the phone answers without ringing.
>>>=20
>>>=20
>>
>>This generally isn't something that is signaled to the=20
>>answering machine, it's just something the answering machine=20
>>does because it KNOWS it's an answering machine.
>>
>>Remember, SIP isn't about network control of edge devices.=20
>>Rather, it is about how a bunch of edge devices can find and=20
>>engage each other in an appropriate  and useful manner.
>>
>>The routing infrastructure and the calling party generally=20
>>don't know that a specific device is an answering machine.=20
>>They know that it's a possible endpoint, and they MAY know=20
>>something about previous routing attempts or decisions made=20
>>elsewhere in the network. Consequently, having them insert=20
>>some sort of special parameter to make the device "act like=20
>>an answering machine" is probably inappropriate.
>>
>>For example, I sometimes use an Asterisk box to provide=20
>>voice-mail services for my SIP phone. No special paramters or=20
>>singaling are sent from my proxy to the Asterisk box to=20
>>invoke it. Instead, it REGISTERs to my AOR just like all my=20
>>other SIP endpoints. But rather than answering immediately on=20
>>receiving a 200 OK, it is configured to wait ten seconds.=20
>>Consequently, if I answer at one of my SIP phones in a timely=20
>>fashion, the Asterisk VM is never connected, but if I don't=20
>>answer, it picks up the call.
>>
>>
>>That being said, they are two places that useful information=20
>>might be conveyed.
>>
>>If the asnwering machine is being reached as a result of a=20
>>call forwarding action performed by a proxy (perhaps as a=20
>>result of a CPL script), then the URI for the answering=20
>>machine can be constructed and configured into the forwarding=20
>>proxy to convey meaningful information, which MIGHT include=20
>>device-specific parameters. This approach is dicsussed in=20
>>Cullen Jenning's draft,  draft-jennings-sip-voicemail-uri-03.
>>
>>Another possibility would be for the call-forwarding action=20
>>to be presented in the request delivered to the answering=20
>>machine in the format specified by the history-info document=20
>>that I announced a working-group last call on earlier today.=20
>>While this may be useful for certain PSTN-interaction cases,=20
>>I personally find it an unattractive approach for=20
>>implementing general-purpose voice mail solutions of the kind=20
>>I described above.
>>
>>--
>>Dean
>>
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP=20
>>Use sip-implementors@cs.columbia.edu for questions on current=20
>>sip Use sip@ietf.org for new developments of core SIP
>>
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004
>>=20
>>
>=20
>=20
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004
> =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

--=20
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Thu Nov 11 17:08:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04446
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 17:08:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSN8t-0006lf-B1
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 17:10:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSN4j-0005NW-56; Thu, 11 Nov 2004 17:05:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMsC-0002hW-2M
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 16:52:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02696
	for <sipping@ietf.org>; Thu, 11 Nov 2004 16:52:54 -0500 (EST)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMtR-0006Lw-1n
	for sipping@ietf.org; Thu, 11 Nov 2004 16:54:13 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iABLqXF13520; Thu, 11 Nov 2004 23:52:34 +0200 (EET)
X-Scanned: Thu, 11 Nov 2004 23:53:52 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iABLrqwK018686;
	Thu, 11 Nov 2004 23:53:52 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00X6JHcR; Thu, 11 Nov 2004 23:53:50 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iABLqEa13571; Thu, 11 Nov 2004 23:52:14 +0200 (EET)
Received: from [130.129.134.192] ([10.241.59.134]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 11 Nov 2004 23:52:11 +0200
Message-ID: <4193DF03.8020903@nokia.com>
Date: Thu, 11 Nov 2004 16:52:03 -0500
From: Aki Niemi <aki.niemi@nokia.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ext Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
	<4193D48C.1030700@cisco.com>
In-Reply-To: <4193D48C.1030700@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Nov 2004 21:52:11.0979 (UTC)
	FILETIME=[B2FBD9B0:01C4C838]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, aspen@nortelnetworks.com,
        Alan Johnston <alan.johnston@mci.com>, David R Oran <oran@cisco.com>,
        alan@telchemy.com, sipping@ietf.org,
        Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Inline.

ext Jonathan Rosenberg wrote:
> 
> 
> David R Oran wrote:
> 
>>> I just want to make a quick comment on the use of PUBLISH in this
>>> document. I think there needs to be some clarification on when this is
>>> sent -- that is, how the UA knows that the proxy *wants* these
>>> publication messages.
>>
>>
>> If the server (not proxy, necessarily...) doesn't want them, it can 
>> send an error. 
> 
> 
> Which error? Section 5 of RFC 3903 does not point out a condition which 
> means,
> "don't publish to this aor any more".

Perhaps there is nothing specific to PUBLISH here. So either 488 or 606 
might work?

>>> From the text currently in the draft, this looks
>>> an awful lot like using PUBLISH as an end-around sending unsolicited
>>> NOTIFY messages by simply changing the method name. I hope that I've
>>> misunderstood -- in which case some clarifying text might be in order;
>>
>>
>> No you haven't fundamentally misunderstood - that's more or less 
>> what's going on. Just being honest here...
>>
>>> otherwise, I'm very concerned about the precedent this document sets.
>>>
>> Could you elaborate on why you think this is a bad precedent?
> 
> 
> I don't follow why its a bad precedent here and not everywhere else; 
> PUBLISH is fundamentally about an unsolicited push of data to a 
> collector. If doing that is bad, then PUBLISH is bad.

Yeah, but there is explicit text in the RFC that says it isn't a generic 
transport of arbitrary data, but of event state. However, that is 
clearly a statement that is open to interpretation.

I really can't tell whether this particular use of PUBLISH goes against 
RFC 3903. Probably not, but it is close -- the POST method really might 
be a better fit ;-)

At least the draft should really spend some more time talking about the 
specifics, like how expiration is set, or etags are used, etc. It should 
also talk about the things RFC 3903 lists in section 10. (I made this 
comment on the list a while back.).

> When you use PUBLISH, you do want to be sure that it is wanted. I think 
> that is generally done by end system configuration/provisioning. You 
> would only PUBLISH for a particular resource for a particular event 
> package if a particular flag was set to do so.

Exactly. This part is no different from, say, presence.

Cheers,
Aki

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 17:12:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04778
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 17:12:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSNCC-0006qt-G3
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 17:13:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSN4k-0005Rq-Oz; Thu, 11 Nov 2004 17:05:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMu4-0002zA-BD
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 16:54:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02970
	for <sipping@ietf.org>; Thu, 11 Nov 2004 16:54:50 -0500 (EST)
Received: from mailhost.iperia.com ([204.57.52.4] helo=iperia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMvJ-0006Nw-55
	for sipping@ietf.org; Thu, 11 Nov 2004 16:56:09 -0500
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="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] automatic answer
Date: Thu, 11 Nov 2004 16:54:16 -0500
Message-ID: <8019F8581B5FC14DBD94BAF86844868E352DD8@viridis.IPeria.local>
Thread-Topic: [Sipping] automatic answer
Thread-Index: AcTINy9SMA/MOIYrSFu0jwPmilM1LQAAP3UQ
From: "Gordon Ledgard" <gledgard@iperia.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>, "David" <david@kayote.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Content-Transfer-Encoding: quoted-printable


I assume that the functionality you are trying to achieve is to have the =
called parties UA decide,
based on something about the call, to either ring the phone or =
immediately direct the phone call
to an answering machine because you do not want to be bothered by some =
certain set of calls.

This is acheiveable in a variety of ways without having the network add =
any more garbage to the INVITE.

I'm entirely with Jonathan on this. What possible paradigm would the "by =
the way, if you are an
answering machine...." be of use, and how on earth would the network =
know or understand this context?

Gordon Ledgard



-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On =
Behalf Of Jonathan Rosenberg
Sent: Thursday, November 11, 2004 4:14 PM
To: David
Cc: sipping@ietf.org; 'Dean Willis'
Subject: Re: [Sipping] automatic answer


I still don't understand why the answering machine wouldn't know that it
is an answering machine. As long as it knows, it can know to pick up
immediately.

I do see value in allowing an answering machine to tell a caller that it
has reached an answering machine. We have that capability in RFC 3840,
which allows the UAS to indicate, through capability parameters in its
Contact header field in the 200 OK, that it is an answering machine.

Thanks,
Jonathan R.

David wrote:

> Hi Dean.
>=20
> While I totally agree that the network should not control the edges,
> however, I would contend that there is a difference between =
controlling and
> informing. I do not see the harm in a network providing extra services =
to
> the edges in the form of additional information regarding the request =
about
> to be made. Whether in the case of voice mail or spam, I think that if =
the
> network has some info that it wishes to share it should do so and =
allow the
> edge to decide what to do with this information. Thus, in this =
particular
> case the network does not have to KNOW that the edge is an answering
> machine, rather it could say "By the way, if you are an answering =
machine
> ...".=20
>=20
> David Schwartz=20
>=20
>=20
>>-----Original Message-----
>>From: sipping-bounces@ietf.org=20
>>[mailto:sipping-bounces@ietf.org] On Behalf Of Dean Willis
>>Sent: Thursday, October 28, 2004 8:15 PM
>>To: ???
>>Cc: sipping@ietf.org
>>Subject: Re: [Sipping] automatic answer
>>
>>=C8=B2=C1=F8=B0=E6 (Jinkyung Hwang) wrote:
>>
>>
>>>Hi,
>>>=20
>>>Is there any I-D regarding params for SIP phone to answer=20
>>>automatically ? (for answering machine functionality)
>>>=20
>>>I would like to know when the call arrives a phone, by which=20
>>>param/header value the phone answers without ringing.
>>>=20
>>>=20
>>
>>This generally isn't something that is signaled to the=20
>>answering machine, it's just something the answering machine=20
>>does because it KNOWS it's an answering machine.
>>
>>Remember, SIP isn't about network control of edge devices.=20
>>Rather, it is about how a bunch of edge devices can find and=20
>>engage each other in an appropriate  and useful manner.
>>
>>The routing infrastructure and the calling party generally=20
>>don't know that a specific device is an answering machine.=20
>>They know that it's a possible endpoint, and they MAY know=20
>>something about previous routing attempts or decisions made=20
>>elsewhere in the network. Consequently, having them insert=20
>>some sort of special parameter to make the device "act like=20
>>an answering machine" is probably inappropriate.
>>
>>For example, I sometimes use an Asterisk box to provide=20
>>voice-mail services for my SIP phone. No special paramters or=20
>>singaling are sent from my proxy to the Asterisk box to=20
>>invoke it. Instead, it REGISTERs to my AOR just like all my=20
>>other SIP endpoints. But rather than answering immediately on=20
>>receiving a 200 OK, it is configured to wait ten seconds.=20
>>Consequently, if I answer at one of my SIP phones in a timely=20
>>fashion, the Asterisk VM is never connected, but if I don't=20
>>answer, it picks up the call.
>>
>>
>>That being said, they are two places that useful information=20
>>might be conveyed.
>>
>>If the asnwering machine is being reached as a result of a=20
>>call forwarding action performed by a proxy (perhaps as a=20
>>result of a CPL script), then the URI for the answering=20
>>machine can be constructed and configured into the forwarding=20
>>proxy to convey meaningful information, which MIGHT include=20
>>device-specific parameters. This approach is dicsussed in=20
>>Cullen Jenning's draft,  draft-jennings-sip-voicemail-uri-03.
>>
>>Another possibility would be for the call-forwarding action=20
>>to be presented in the request delivered to the answering=20
>>machine in the format specified by the history-info document=20
>>that I announced a working-group last call on earlier today.=20
>>While this may be useful for certain PSTN-interaction cases,=20
>>I personally find it an unattractive approach for=20
>>implementing general-purpose voice mail solutions of the kind=20
>>I described above.
>>
>>--
>>Dean
>>
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP=20
>>Use sip-implementors@cs.columbia.edu for questions on current=20
>>sip Use sip@ietf.org for new developments of core SIP
>>
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004
>>=20
>>
>=20
>=20
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004
> =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

--=20
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Thu Nov 11 17:14:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04952
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 17:14:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSNE8-0006uf-LM
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 17:15:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSN59-0005b2-KW; Thu, 11 Nov 2004 17:06:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSMyF-0003WY-75
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 16:59:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03339
	for <sipping@ietf.org>; Thu, 11 Nov 2004 16:59:09 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSMzU-0006Tj-2q
	for sipping@ietf.org; Thu, 11 Nov 2004 17:00:28 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iABLwV2Z024717;
	Thu, 11 Nov 2004 16:58:31 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 0A9FF3C8155;
	Thu, 11 Nov 2004 16:56:34 -0500 (EST)
Received: from pintlmail.MITL.Research.Panasonic.COM 
	(pintlmail.mitl.research.panasonic.com [150.169.1.62])by 
	redwood.research.panasonic.com (Postfix) with ESMTP id 114FD3C8155;
	Thu, 11 Nov 2004 16:56:25 -0500 (EST)
Received: from [130.129.132.19] by 
	pintlmail.MITL.Research.Panasonic.COM(mshttpd);
	Thu, 11 Nov 2004 16:58:21 -0500
From: Brijesh Kumar <kumarb@research.panasonic.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>
Message-ID: <58c6b5b6fa.5b6fa58c6b@pintlmail.MITL.Research.Panasonic.COM>
Date: Thu, 11 Nov 2004 16:58:21 -0500
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
MIME-Version: 1.0
Content-Language: en
Subject: Re: [Sipping] device-info-01
X-Accept-Language: en
Priority: normal
Content-Type: text/plain;
	charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:14 M:0 S:100 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, Mahfuz Rahman <mahfuz@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: Jonathan Rosenberg <jdrosen@cisco.com>
Date: Thursday, November 11, 2004 9:45 am
Subject: Re: [Sipping] device-info-01

> I think there is an interesting question at the root of this 
> draft. The 
> interesting question is how to manage a "network" where the 
> network 
> includes all of the SIP user agents (and in particular, single 
> user 
> devices like softphones and hardphones). Management, in this 
> context, 
> includes configuration (where things like the config profile are 
> targeted), but also includes fault management, accounting, 
> performance 
> and security management. This draft is targeted roughly in the 
> area of 
> device performance management, and thats a laudable goal.

Hi Jonathan:

As I clarified during our presentation, the purpose of this draft
is to monitor the useful states of a device that are 
relevant for a variety of applications. 
  
For example, I may be interested in knowing the current status
of a camera attached to a user's phone before I start streaming
video to him. Or, I may be interested in monitoring if the user's
device has enough memory left for me to stream a live video, and
then continue monitoring. Also, to know if the speaker is muted 
or not, or the camera is on or of.  I may even want to know if the 
my friend is inside his home in a comfortable environment rather than 
in open in 100 degree heat before streaming a live video to him.  

And, another example is what Dean mentioned - knowing the status of
of a video recorder, and then using that status information go to 
a different recorder to record a video stream.

There are many use cases that will benefit with the abilities 
to learn the device and various type of status information on the 
device.  I have only given examples related to applications that
are in the common knowledge - I know there are a lot many use
cases of similar nature. 

Cheers,

--brijesh 
 



> 
> However, I think the problem is fairly broad, and would benefit 
> from a 
> top-down look at what really needs to be done here, rather than 
> jumping 
> to an event package or OPTIONS or whatever. The problem is 
> complicated 
> because in many cases, these devices are run and managed by end users.
> 
> -Jonathan R.
> 
> Mahfuz Rahman wrote:
> 
> > Thanks Cullen for making some good comments. My response is as 
> follows:  
> > 
> > OPTIONS method is used to query device capabilities such as 
> supported methods,
> > contnet types, codesc etc.. This draft defines data elements for 
> device profile
> > which is  different from the tags defined for OPTIONS. So if we 
> like to define
> > tags for each of the data elements we have defined in the 
> profile it will be a long
> > list. I am not sure if it is acceptable. Also, as you suggested 
> to include multiple
> > schemas and URLs for a device it would be difficult to represent 
> using OPTIONS unless
> > we allow attachment of a body in the OPTIONS response with the 
> following content type: 
> > application/device-profile+xml. 
> > 
> > I agree with you to add software version and also an optional UUID.
> > 
> > The status part will be extended in the future revision which 
> might include a 
> > common XML format. Currently it describes only how vendor 
> specific status information
> > can be retrieved. 
> > 
> > - mahfuz
> > 
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> > Behalf Of Cullen Jennings
> > Sent: Saturday, November 06, 2004 6:19 PM
> > To: sipping
> > Subject: [Sipping] device-info-01
> > 
> > 
> > Nice draft - few comments ...
> > 
> > As a completely alternative suggestions.... How much of this 
> information can
> > you get by just sending an OPTION request to the device.
> > 
> > I would remove all the discussion of the device status - you 
> don't define
> > anything about how to do it so the discussion does not help.
> > 
> > This reports things that should not change so rate of 
> notifications is very
> > very seldom.
> > 
> > I would add an optional UUID to the profile
> > 
> > You might want to add software version.
> > 
> > I would make the schema URL and name attributes of a schema 
> object so that
> > the device can lists multiple schema that it can support.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
> Director, Service Provider VoIP Architecture   Parsippany, NJ 
> 07054-2711
> Cisco Systems
> jdrosen@cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.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 sipping-bounces@ietf.org  Thu Nov 11 17:41:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07822
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 17:41:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSNe0-0007k7-Vs
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 17:42:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSNPq-0003BI-PC; Thu, 11 Nov 2004 17:27:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRt4P-0005QG-TR
	for sipping@megatron.ietf.org; Wed, 10 Nov 2004 09:03:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09489
	for <sipping@ietf.org>; Wed, 10 Nov 2004 09:03:32 -0500 (EST)
Received: from [65.220.123.3] (helo=mail.pingtel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRt5N-0002cQ-TE
	for sipping@ietf.org; Wed, 10 Nov 2004 09:04:34 -0500
Received: from [10.1.1.152] (hide.pingtel.com [65.220.123.2])
	by mail.pingtel.com (8.11.6/8.11.6) with ESMTP id iAAE3V229205;
	Wed, 10 Nov 2004 09:03:31 -0500
Subject: Re: [Sipping] profile-datasets-00
From: Scott Lawrence <lawrence@pingtel.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BDB16339.189B9%fluffy@cisco.com>
References: <BDB16339.189B9%fluffy@cisco.com>
Content-Type: text/plain
Message-Id: <1100095411.2567.39.camel@cdhcp152.pingtel.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Wed, 10 Nov 2004 09:03:31 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 11 Nov 2004 17:27:41 -0500
Cc: Daniel Petrie <dpetrie@pingtel.com>, sipping <sipping@ietf.org>,
        Scott Lawrence <slawrence@pingtel.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit

On Fri, 2004-11-05 at 20:04, Cullen Jennings wrote:
> This seems to have gotten tangled up into the policy work in sort of scary
> way. 

We are very much aware of the overlap, and have been discussing how to
unify them appropriately.

> The phone know if it supports g711 or not - what I want to configure
> into my phone is what the username and AOR are, an outbound proxy, a speed
> dial list, things like that.

But there are a great many other things that administrators of networks
want to configure into user agents.

> Not clear what a UA subscribes to to get a particular dataset.

That is dealt with in draft-ietf-sipping-config-framework-*

> I think you intend to do this but  - we have to deal with the access control
> in section 4.2 from the beginning because we won't be able to add it in a
> backwards compatible way

Absolutely - we just didn't get it into the -00 draft.

> 4.3.1 might want to expand iff

yes, probably.

> I hate the forbid, set_all, set_one etc stuff in this. This is not a
> document to describe to a phone how to render a user interfaces for the user
> to select how to configure the phones. It's the data that is the
> configuration for the phone.

The intent was certainly not to specify a user interface.  Configuring
real devices in real networks is complex - it can't be done by
specifying a bunch of separate data values.  Configuration parameters
have relationships between them, and the profile mechanism needs to be
able to express those relationships; that's what all that is about.  
The other aspect of the containers that I think is convenient is that
they express what is required or forbidden - separating that from the
expression of the data values themselves.

> We have to address the merging issues not just leave it TBD and I suspect
> that it is data specific.

In a discussion we had with several interested people in San Diego we
reached the same conclusion - and agreed with everyone that more
guidance on merging is certainly needed.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 18:49:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15327
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 18:49:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSOi8-0000vu-AA
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 18:50:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSOee-0005eg-GM; Thu, 11 Nov 2004 18:47:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSOcI-0004uG-57
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 18:44:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15057
	for <sipping@ietf.org>; Thu, 11 Nov 2004 18:44:35 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSOdY-0000qP-4G
	for sipping@ietf.org; Thu, 11 Nov 2004 18:45:56 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABNi2v21583; Thu, 11 Nov 2004 18:44:03 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTD13Y>; Thu, 11 Nov 2004 18:44:03 -0500
Message-ID: <7A3E36B3528ED04A880178D337F30C9A01B88939@zrc2hxm1.corp.nortel.com>
From: "Amy Pendleton" <aspen@nortelnetworks.com>
To: Adam Roach <adam@nostrum.com>
Date: Thu, 11 Nov 2004 18:43:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: Alan Johnston <alan.johnston@mci.com>, SIPPING WG list <sipping@ietf.org>,
        Henry Sinnreich <Henry.Sinnreich@mci.com>, alan@telchemy.com
Subject: [Sipping] RE: [Simple] PUBLISH in SIP Performance Report Event
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0400195381=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92

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.

--===============0400195381==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C848.50206F27"

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_01C4C848.50206F27
Content-Type: text/plain

I believe this might deserve some clarification because I am definitely not
attempting to use PUBLISH as a unsolicited NOTIFY.

Both in the case of SUBSCRIBE/NOTIFY and PUBLISH, all of the provisioning
for the service is stated in the document to be out of scope.  There are
many aspects that would likely need provisioning for this to work properly,
such as where to send the reports, how often the reports should be sent,
whether to send threshold reports and what the threshold values should be.  

My question is how does the UA know that the proxy wants to receive the
PUBLISH events in general?  If there is some mechanism of which I am not
making use, please let me know.

Thanks,
Amy

-----Original Message-----
From: Adam Roach [mailto:adam@nostrum.com] 
Sent: Thursday, November 11, 2004 1:39 PM
To: Adam Roach
Cc: Alan Johnston; Henry Sinnreich; alan@telchemy.com; Pendleton, Amy
[NGC:B601:EXCH]; simple@ietf.org
Subject: Re: [Simple] PUBLISH in SIP Performance Report Event


Sorry -- wrong list (typo)... taking to SIPPING.

/a

Adam Roach wrote:

> I just want to make a quick comment on the use of PUBLISH in this
> document. I think there needs to be some clarification on when this is 
> sent -- that is, how the UA knows that the proxy *wants* these 
> publication messages. From the text currently in the draft, this looks 
> an awful lot like using PUBLISH as an end-around sending unsolicited 
> NOTIFY messages by simply changing the method name. I hope that I've 
> misunderstood -- in which case some clarifying text might be in order; 
> otherwise, I'm very concerned about the precedent this document sets.
>
> /a
>
> _______________________________________________
> Simple mailing list
> Simple@ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
>



------_=_NextPart_001_01C4C848.50206F27
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Simple] PUBLISH in SIP Performance Report Event</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I believe this might deserve some clarification =
because I am definitely not attempting to use PUBLISH as a unsolicited =
NOTIFY.</FONT></P>

<P><FONT SIZE=3D2>Both in the case of SUBSCRIBE/NOTIFY and PUBLISH, all =
of the provisioning for the service is stated in the document to be out =
of scope.&nbsp; There are many aspects that would likely need =
provisioning for this to work properly, such as where to send the =
reports, how often the reports should be sent, whether to send =
threshold reports and what the threshold values should be.&nbsp; =
</FONT></P>

<P><FONT SIZE=3D2>My question is how does the UA know that the proxy =
wants to receive the PUBLISH events in general?&nbsp; If there is some =
mechanism of which I am not making use, please let me know.</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Amy</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Adam Roach [<A =
HREF=3D"mailto:adam@nostrum.com">mailto:adam@nostrum.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, November 11, 2004 1:39 PM</FONT>
<BR><FONT SIZE=3D2>To: Adam Roach</FONT>
<BR><FONT SIZE=3D2>Cc: Alan Johnston; Henry Sinnreich; =
alan@telchemy.com; Pendleton, Amy [NGC:B601:EXCH]; =
simple@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Simple] PUBLISH in SIP Performance =
Report Event</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Sorry -- wrong list (typo)... taking to =
SIPPING.</FONT>
</P>

<P><FONT SIZE=3D2>/a</FONT>
</P>

<P><FONT SIZE=3D2>Adam Roach wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; I just want to make a quick comment on the use =
of PUBLISH in this</FONT>
<BR><FONT SIZE=3D2>&gt; document. I think there needs to be some =
clarification on when this is </FONT>
<BR><FONT SIZE=3D2>&gt; sent -- that is, how the UA knows that the =
proxy *wants* these </FONT>
<BR><FONT SIZE=3D2>&gt; publication messages. From the text currently =
in the draft, this looks </FONT>
<BR><FONT SIZE=3D2>&gt; an awful lot like using PUBLISH as an =
end-around sending unsolicited </FONT>
<BR><FONT SIZE=3D2>&gt; NOTIFY messages by simply changing the method =
name. I hope that I've </FONT>
<BR><FONT SIZE=3D2>&gt; misunderstood -- in which case some clarifying =
text might be in order; </FONT>
<BR><FONT SIZE=3D2>&gt; otherwise, I'm very concerned about the =
precedent this document sets.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; /a</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Simple mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Simple@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/simple" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/simple</A></FON=
T>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C848.50206F27--


--===============0400195381==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0400195381==--



From sipping-bounces@ietf.org  Thu Nov 11 19:25:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17594
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 19:25:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSPHU-0001aP-RJ
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 19:27:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSPBK-0004Gh-39; Thu, 11 Nov 2004 19:20:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSP3r-00039v-4M
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 19:13:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16836
	for <sipping@ietf.org>; Thu, 11 Nov 2004 19:13:04 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSP55-0001LR-N2
	for sipping@ietf.org; Thu, 11 Nov 2004 19:14:25 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 11 Nov 2004 16:24:39 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAC0CQ04026279;
	Thu, 11 Nov 2004 16:12:26 -0800 (PST)
Received: from cisco.com (rtp-vpn1-555.cisco.com [10.82.226.43])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMZ28231;
	Thu, 11 Nov 2004 19:12:30 -0500 (EST)
Message-ID: <4193FFED.5000802@cisco.com>
Date: Thu, 11 Nov 2004 19:12:29 -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: Brijesh Kumar <kumarb@research.panasonic.com>
Subject: Re: [Sipping] device-info-01
References: <58c6b5b6fa.5b6fa58c6b@pintlmail.MITL.Research.Panasonic.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: 7bit
Cc: Mahfuz Rahman <mahfuz@research.panasonic.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Content-Transfer-Encoding: 7bit

Brijesh,

The more I hear the more I dislike. It sounds like you are trying to 
reinvent presence, but in a very device specific way. The functionality 
you describe can, I believe, be achieved in a much more interoperable 
way by defining new presence attributes which the device may publish, 
and which may be disclosed to you if policy of the owner of the device 
desires you to know it.

	Paul

Brijesh Kumar wrote:
> ----- Original Message -----
> From: Jonathan Rosenberg <jdrosen@cisco.com>
> Date: Thursday, November 11, 2004 9:45 am
> Subject: Re: [Sipping] device-info-01
> 
> 
>>I think there is an interesting question at the root of this 
>>draft. The 
>>interesting question is how to manage a "network" where the 
>>network 
>>includes all of the SIP user agents (and in particular, single 
>>user 
>>devices like softphones and hardphones). Management, in this 
>>context, 
>>includes configuration (where things like the config profile are 
>>targeted), but also includes fault management, accounting, 
>>performance 
>>and security management. This draft is targeted roughly in the 
>>area of 
>>device performance management, and thats a laudable goal.
> 
> 
> Hi Jonathan:
> 
> As I clarified during our presentation, the purpose of this draft
> is to monitor the useful states of a device that are 
> relevant for a variety of applications. 
>   
> For example, I may be interested in knowing the current status
> of a camera attached to a user's phone before I start streaming
> video to him. Or, I may be interested in monitoring if the user's
> device has enough memory left for me to stream a live video, and
> then continue monitoring. Also, to know if the speaker is muted 
> or not, or the camera is on or of.  I may even want to know if the 
> my friend is inside his home in a comfortable environment rather than 
> in open in 100 degree heat before streaming a live video to him.  
> 
> And, another example is what Dean mentioned - knowing the status of
> of a video recorder, and then using that status information go to 
> a different recorder to record a video stream.
> 
> There are many use cases that will benefit with the abilities 
> to learn the device and various type of status information on the 
> device.  I have only given examples related to applications that
> are in the common knowledge - I know there are a lot many use
> cases of similar nature. 
> 
> Cheers,
> 
> --brijesh 
>  
> 
> 
> 
> 
>>However, I think the problem is fairly broad, and would benefit 
>>from a 
>>top-down look at what really needs to be done here, rather than 
>>jumping 
>>to an event package or OPTIONS or whatever. The problem is 
>>complicated 
>>because in many cases, these devices are run and managed by end users.
>>
>>-Jonathan R.
>>
>>Mahfuz Rahman wrote:
>>
>>
>>>Thanks Cullen for making some good comments. My response is as 
>>
>>follows:  
>>
>>>OPTIONS method is used to query device capabilities such as 
>>
>>supported methods,
>>
>>>contnet types, codesc etc.. This draft defines data elements for 
>>
>>device profile
>>
>>>which is  different from the tags defined for OPTIONS. So if we 
>>
>>like to define
>>
>>>tags for each of the data elements we have defined in the 
>>
>>profile it will be a long
>>
>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>
>>to include multiple
>>
>>>schemas and URLs for a device it would be difficult to represent 
>>
>>using OPTIONS unless
>>
>>>we allow attachment of a body in the OPTIONS response with the 
>>
>>following content type: 
>>
>>>application/device-profile+xml. 
>>>
>>>I agree with you to add software version and also an optional UUID.
>>>
>>>The status part will be extended in the future revision which 
>>
>>might include a 
>>
>>>common XML format. Currently it describes only how vendor 
>>
>>specific status information
>>
>>>can be retrieved. 
>>>
>>>- mahfuz
>>>
>>>-----Original Message-----
>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>Behalf Of Cullen Jennings
>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>To: sipping
>>>Subject: [Sipping] device-info-01
>>>
>>>
>>>Nice draft - few comments ...
>>>
>>>As a completely alternative suggestions.... How much of this 
>>
>>information can
>>
>>>you get by just sending an OPTION request to the device.
>>>
>>>I would remove all the discussion of the device status - you 
>>
>>don't define
>>
>>>anything about how to do it so the discussion does not help.
>>>
>>>This reports things that should not change so rate of 
>>
>>notifications is very
>>
>>>very seldom.
>>>
>>>I would add an optional UUID to the profile
>>>
>>>You might want to add software version.
>>>
>>>I would make the schema URL and name attributes of a schema 
>>
>>object so that
>>
>>>the device can lists multiple schema that it can support.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the 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
>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>07054-2711
>>Cisco Systems
>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>http://www.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
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 20:03:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20401
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 20:03:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSPsJ-0002MN-2A
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 20:05:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSPoP-0002wv-GA; Thu, 11 Nov 2004 20:01:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSPnj-0002or-S2
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 20:00:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20122
	for <sipping@ietf.org>; Thu, 11 Nov 2004 20:00:30 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSPp0-0002Hk-CK
	for sipping@ietf.org; Thu, 11 Nov 2004 20:01:50 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iAC0xwsL028938;
	Thu, 11 Nov 2004 19:59:58 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 8CF853C8155;
	Thu, 11 Nov 2004 19:58:01 -0500 (EST)
Received: from pintlmail.MITL.Research.Panasonic.COM 
	(pintlmail.mitl.research.panasonic.com [150.169.1.62])by 
	redwood.research.panasonic.com (Postfix) with ESMTP id 077FD3C8158;
	Thu, 11 Nov 2004 19:57:55 -0500 (EST)
Received: from [4.250.141.9] by 
	pintlmail.MITL.Research.Panasonic.COM(mshttpd);
	Thu, 11 Nov 2004 19:59:52 -0500
From: Mahfuz Rahman <mahfuz@research.panasonic.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Message-ID: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
Date: Thu, 11 Nov 2004 19:59:52 -0500
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
MIME-Version: 1.0
Content-Language: en
Subject: Re: [Sipping] device-info-01
X-Accept-Language: en
Priority: normal
Content-Type: text/plain;
	charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:14 M:0 S:100 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, Brijesh Kumar <kumarb@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606
Content-Transfer-Encoding: 7bit

Paul:

We discussed the idea of assinging new presence attributes a 
year ago which we beleive would solve interoperability issue.
But we were advised not to do that on the basis that device 
status and presence are two different things and we should not
mix it up.

I am glad that you brought up this  issue of presence
attributes for device which I totally agree with and would be
happy to pursue our previous idea on presence and submit an 
alternate draft based on presence.

I hope the working group will support it then.

-mahfuz
 

----- Original Message -----
From: Paul Kyzivat <pkyzivat@cisco.com>
Date: Thursday, November 11, 2004 7:12 pm
Subject: Re: [Sipping] device-info-01

> Brijesh,
> 
> The more I hear the more I dislike. It sounds like you are trying 
> to 
> reinvent presence, but in a very device specific way. The 
> functionality 
> you describe can, I believe, be achieved in a much more 
> interoperable 
> way by defining new presence attributes which the device may 
> publish, 
> and which may be disclosed to you if policy of the owner of the 
> device 
> desires you to know it.
> 
> 	Paul
> 
> Brijesh Kumar wrote:
> > ----- Original Message -----
> > From: Jonathan Rosenberg <jdrosen@cisco.com>
> > Date: Thursday, November 11, 2004 9:45 am
> > Subject: Re: [Sipping] device-info-01
> > 
> > 
> >>I think there is an interesting question at the root of this 
> >>draft. The 
> >>interesting question is how to manage a "network" where the 
> >>network 
> >>includes all of the SIP user agents (and in particular, single 
> >>user 
> >>devices like softphones and hardphones). Management, in this 
> >>context, 
> >>includes configuration (where things like the config profile are 
> >>targeted), but also includes fault management, accounting, 
> >>performance 
> >>and security management. This draft is targeted roughly in the 
> >>area of 
> >>device performance management, and thats a laudable goal.
> > 
> > 
> > Hi Jonathan:
> > 
> > As I clarified during our presentation, the purpose of this draft
> > is to monitor the useful states of a device that are 
> > relevant for a variety of applications. 
> >   
> > For example, I may be interested in knowing the current status
> > of a camera attached to a user's phone before I start streaming
> > video to him. Or, I may be interested in monitoring if the user's
> > device has enough memory left for me to stream a live video, and
> > then continue monitoring. Also, to know if the speaker is muted 
> > or not, or the camera is on or of.  I may even want to know if 
> the 
> > my friend is inside his home in a comfortable environment rather 
> than 
> > in open in 100 degree heat before streaming a live video to him. 
> 
> > 
> > And, another example is what Dean mentioned - knowing the status of
> > of a video recorder, and then using that status information go 
> to 
> > a different recorder to record a video stream.
> > 
> > There are many use cases that will benefit with the abilities 
> > to learn the device and various type of status information on 
> the 
> > device.  I have only given examples related to applications that
> > are in the common knowledge - I know there are a lot many use
> > cases of similar nature. 
> > 
> > Cheers,
> > 
> > --brijesh 
> >  
> > 
> > 
> > 
> > 
> >>However, I think the problem is fairly broad, and would benefit 
> >>from a 
> >>top-down look at what really needs to be done here, rather than 
> >>jumping 
> >>to an event package or OPTIONS or whatever. The problem is 
> >>complicated 
> >>because in many cases, these devices are run and managed by end 
> users.>>
> >>-Jonathan R.
> >>
> >>Mahfuz Rahman wrote:
> >>
> >>
> >>>Thanks Cullen for making some good comments. My response is as 
> >>
> >>follows:  
> >>
> >>>OPTIONS method is used to query device capabilities such as 
> >>
> >>supported methods,
> >>
> >>>contnet types, codesc etc.. This draft defines data elements 
> for 
> >>
> >>device profile
> >>
> >>>which is  different from the tags defined for OPTIONS. So if we 
> >>
> >>like to define
> >>
> >>>tags for each of the data elements we have defined in the 
> >>
> >>profile it will be a long
> >>
> >>>list. I am not sure if it is acceptable. Also, as you suggested 
> >>
> >>to include multiple
> >>
> >>>schemas and URLs for a device it would be difficult to 
> represent 
> >>
> >>using OPTIONS unless
> >>
> >>>we allow attachment of a body in the OPTIONS response with the 
> >>
> >>following content type: 
> >>
> >>>application/device-profile+xml. 
> >>>
> >>>I agree with you to add software version and also an optional UUID.
> >>>
> >>>The status part will be extended in the future revision which 
> >>
> >>might include a 
> >>
> >>>common XML format. Currently it describes only how vendor 
> >>
> >>specific status information
> >>
> >>>can be retrieved. 
> >>>
> >>>- mahfuz
> >>>
> >>>-----Original Message-----
> >>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
> >>>Behalf Of Cullen Jennings
> >>>Sent: Saturday, November 06, 2004 6:19 PM
> >>>To: sipping
> >>>Subject: [Sipping] device-info-01
> >>>
> >>>
> >>>Nice draft - few comments ...
> >>>
> >>>As a completely alternative suggestions.... How much of this 
> >>
> >>information can
> >>
> >>>you get by just sending an OPTION request to the device.
> >>>
> >>>I would remove all the discussion of the device status - you 
> >>
> >>don't define
> >>
> >>>anything about how to do it so the discussion does not help.
> >>>
> >>>This reports things that should not change so rate of 
> >>
> >>notifications is very
> >>
> >>>very seldom.
> >>>
> >>>I would add an optional UUID to the profile
> >>>
> >>>You might want to add software version.
> >>>
> >>>I would make the schema URL and name attributes of a schema 
> >>
> >>object so that
> >>
> >>>the device can lists multiple schema that it can support.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
> NEW development of the 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
> >>Director, Service Provider VoIP Architecture   Parsippany, NJ 
> >>07054-2711
> >>Cisco Systems
> >>jdrosen@cisco.com                              FAX:   (973) 952-5050
> >>http://www.jdrosen.net                         PHONE: (973) 952-5000
> >>http://www.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
> > 
> 
> 
> 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 11 21:24:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27948
	for <sipping-web-archive@ietf.org>; Thu, 11 Nov 2004 21:24:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSR8j-000449-Rw
	for sipping-web-archive@ietf.org; Thu, 11 Nov 2004 21:26:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSR5O-0003Nd-51; Thu, 11 Nov 2004 21:22:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSQxp-0001qC-TH
	for sipping@megatron.ietf.org; Thu, 11 Nov 2004 21:15:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27250
	for <sipping@ietf.org>; Thu, 11 Nov 2004 21:15:00 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSQz7-0003t3-2j
	for sipping@ietf.org; Thu, 11 Nov 2004 21:16:21 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 11 Nov 2004 18:24:21 -0800
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAC29q04025806;
	Thu, 11 Nov 2004 18:09:53 -0800 (PST)
Received: from cisco.com (rtp-vpn1-555.cisco.com [10.82.226.43])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMZ33724;
	Thu, 11 Nov 2004 21:10:07 -0500 (EST)
Message-ID: <41941B7F.7070204@cisco.com>
Date: Thu, 11 Nov 2004 21:10:07 -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: Mahfuz Rahman <mahfuz@research.panasonic.com>
Subject: Re: [Sipping] device-info-01
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, Brijesh Kumar <kumarb@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Content-Transfer-Encoding: 7bit



Mahfuz Rahman wrote:
> Paul:
> 
> We discussed the idea of assinging new presence attributes a 
> year ago which we beleive would solve interoperability issue.
> But we were advised not to do that on the basis that device 
> status and presence are two different things and we should not
> mix it up.
> 
> I am glad that you brought up this  issue of presence
> attributes for device which I totally agree with and would be
> happy to pursue our previous idea on presence and submit an 
> alternate draft based on presence.
> 
> I hope the working group will support it then.

I think that will depend entirely on the details.

I suspect that availability for streaming video might be considered a 
reasonable presence status (if it can be demonstrated to be orthogonal 
to normal video), while "has N gb of free storage" might not be.

I have a sense that you have a concept that the sender will be making 
the decisions about what should be done to the receiver, while the 
popular presence viewpoint is that the presentity makes those decisions 
and announces availability at a higher level of abstraction.

It would perhaps be helpful if you would be more explicit about the use 
cases you are trying to enable.

	Paul

> -mahfuz
>  
> 
> ----- Original Message -----
> From: Paul Kyzivat <pkyzivat@cisco.com>
> Date: Thursday, November 11, 2004 7:12 pm
> Subject: Re: [Sipping] device-info-01
> 
> 
>>Brijesh,
>>
>>The more I hear the more I dislike. It sounds like you are trying 
>>to 
>>reinvent presence, but in a very device specific way. The 
>>functionality 
>>you describe can, I believe, be achieved in a much more 
>>interoperable 
>>way by defining new presence attributes which the device may 
>>publish, 
>>and which may be disclosed to you if policy of the owner of the 
>>device 
>>desires you to know it.
>>
>>	Paul
>>
>>Brijesh Kumar wrote:
>>
>>>----- Original Message -----
>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>Date: Thursday, November 11, 2004 9:45 am
>>>Subject: Re: [Sipping] device-info-01
>>>
>>>
>>>
>>>>I think there is an interesting question at the root of this 
>>>>draft. The 
>>>>interesting question is how to manage a "network" where the 
>>>>network 
>>>>includes all of the SIP user agents (and in particular, single 
>>>>user 
>>>>devices like softphones and hardphones). Management, in this 
>>>>context, 
>>>>includes configuration (where things like the config profile are 
>>>>targeted), but also includes fault management, accounting, 
>>>>performance 
>>>>and security management. This draft is targeted roughly in the 
>>>>area of 
>>>>device performance management, and thats a laudable goal.
>>>
>>>
>>>Hi Jonathan:
>>>
>>>As I clarified during our presentation, the purpose of this draft
>>>is to monitor the useful states of a device that are 
>>>relevant for a variety of applications. 
>>>  
>>>For example, I may be interested in knowing the current status
>>>of a camera attached to a user's phone before I start streaming
>>>video to him. Or, I may be interested in monitoring if the user's
>>>device has enough memory left for me to stream a live video, and
>>>then continue monitoring. Also, to know if the speaker is muted 
>>>or not, or the camera is on or of.  I may even want to know if 
>>
>>the 
>>
>>>my friend is inside his home in a comfortable environment rather 
>>
>>than 
>>
>>>in open in 100 degree heat before streaming a live video to him. 
>>
>>>And, another example is what Dean mentioned - knowing the status of
>>>of a video recorder, and then using that status information go 
>>
>>to 
>>
>>>a different recorder to record a video stream.
>>>
>>>There are many use cases that will benefit with the abilities 
>>>to learn the device and various type of status information on 
>>
>>the 
>>
>>>device.  I have only given examples related to applications that
>>>are in the common knowledge - I know there are a lot many use
>>>cases of similar nature. 
>>>
>>>Cheers,
>>>
>>>--brijesh 
>>> 
>>>
>>>
>>>
>>>
>>>
>>>>However, I think the problem is fairly broad, and would benefit 
>>>
>>>>from a 
>>>
>>>>top-down look at what really needs to be done here, rather than 
>>>>jumping 
>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>complicated 
>>>>because in many cases, these devices are run and managed by end 
>>>
>>users.>>
>>
>>>>-Jonathan R.
>>>>
>>>>Mahfuz Rahman wrote:
>>>>
>>>>
>>>>
>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>
>>>>follows:  
>>>>
>>>>
>>>>>OPTIONS method is used to query device capabilities such as 
>>>>
>>>>supported methods,
>>>>
>>>>
>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>
>>for 
>>
>>>>device profile
>>>>
>>>>
>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>
>>>>like to define
>>>>
>>>>
>>>>>tags for each of the data elements we have defined in the 
>>>>
>>>>profile it will be a long
>>>>
>>>>
>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>
>>>>to include multiple
>>>>
>>>>
>>>>>schemas and URLs for a device it would be difficult to 
>>>>
>>represent 
>>
>>>>using OPTIONS unless
>>>>
>>>>
>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>
>>>>following content type: 
>>>>
>>>>
>>>>>application/device-profile+xml. 
>>>>>
>>>>>I agree with you to add software version and also an optional UUID.
>>>>>
>>>>>The status part will be extended in the future revision which 
>>>>
>>>>might include a 
>>>>
>>>>
>>>>>common XML format. Currently it describes only how vendor 
>>>>
>>>>specific status information
>>>>
>>>>
>>>>>can be retrieved. 
>>>>>
>>>>>- mahfuz
>>>>>
>>>>>-----Original Message-----
>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>Behalf Of Cullen Jennings
>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>To: sipping
>>>>>Subject: [Sipping] device-info-01
>>>>>
>>>>>
>>>>>Nice draft - few comments ...
>>>>>
>>>>>As a completely alternative suggestions.... How much of this 
>>>>
>>>>information can
>>>>
>>>>
>>>>>you get by just sending an OPTION request to the device.
>>>>>
>>>>>I would remove all the discussion of the device status - you 
>>>>
>>>>don't define
>>>>
>>>>
>>>>>anything about how to do it so the discussion does not help.
>>>>>
>>>>>This reports things that should not change so rate of 
>>>>
>>>>notifications is very
>>>>
>>>>
>>>>>very seldom.
>>>>>
>>>>>I would add an optional UUID to the profile
>>>>>
>>>>>You might want to add software version.
>>>>>
>>>>>I would make the schema URL and name attributes of a schema 
>>>>
>>>>object so that
>>>>
>>>>
>>>>>the device can lists multiple schema that it can support.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>Sipping mailing list  
>>>>
>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>NEW development of the 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
>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>07054-2711
>>>>Cisco Systems
>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>http://www.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
>>>
>>
>>
>>
> 
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 07:22:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24574
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 07:22:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSaTU-0006Vr-NO
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 07:24:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSaKd-0000Pa-WC; Fri, 12 Nov 2004 07:15:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSaK4-0000Hd-M5
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 07:14:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24178
	for <sipping@ietf.org>; Fri, 12 Nov 2004 07:14:33 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSaLR-0006NO-Gw
	for sipping@ietf.org; Fri, 12 Nov 2004 07:16:01 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 12 Nov 2004 04:26:16 -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.10/8.12.6) with ESMTP id iACCDj04026890;
	Fri, 12 Nov 2004 04:13:46 -0800 (PST)
Received: from [10.67.86.107] (sjc-vpn5-84.cisco.com [10.21.88.84])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATY33297;
	Fri, 12 Nov 2004 04:14:00 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Thu, 11 Nov 2004 14:44:19 -0500
From: Cullen Jennings <fluffy@cisco.com>
To: Paul H Kyzivat <pkyzivat@cisco.com>, sipping <sipping@ietf.org>
Message-ID: <BDB92B43.19635%fluffy@cisco.com>
In-Reply-To: <418A84AE.9050106@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: Jon Peterson <jon.peterson@neustar.biz>
Subject: [Sipping] Re: draft-ietf-sipping-certs-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit


Great comments - thanks for catching this stuff will fix.
 

On 11/4/04 11:36 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:

> 1) cert caching
> 
>                              "The UA needs to cache this certificate for
>     future use.  The certificate MUST be removed from the cache if it has
>     expired, if it is updated by a subsequent NOTIFY, or if the
>     subscription has been terminated."
> 
> This implies that I must have an active subscription to anyone I may
> want to call. Since there tends to be very little call locality, that
> means a lot of subscriptions active all the time, or else establishing
> and ending a subscription for each call. Why not just admit that caching
> may be done after the subscription terminates, until the cert expires,
> at the risk of missing a revocation?

will add more text - your interpretation is correct. There is a strong
locality with people I call and people who's presence I monitor

> 
> 2) NOTIFY addressing
> 
>    "When the Credential Server receives a SUBSCRIBE for a certificate, it
>     first checks to see if it has credentials for the requested URI.  If
>     it does not it returns a response indicating the user was not found.
>     Otherwise it sets up a subscription and forms a NOTIFY with the
>     certificate in the body and the From header field value set to the
>     request URI of the SUBSCRIBE."
> 
> The credential server has no choice about what to put in the From header
> of the Notify - it is determined by the dialog of the subscription, and
> will equal the To header of the Subscribe. It is likely that the To
> header and request header will be the same in this case, but that is not
> certain.
>

Yes - will fix.
 
> 3) Server storing private keys
> 
> Having the credential server store the private keys means they are
> potentially in the hands of an organization subject to legal
> requirements for key disclosure. As a result, sessions secured with
> these credentials may be subject to wire tap. As a work-around to this,
> how about making the secret key optional when publishing and subscribing
> to the credentials. If a credential is published without a secret key,
> it will be distributed without. Then only those endpoints that have the
> private key can successfully use the credential - typically the device
> that published it.
> 

Good point. The pkcs8 data can be encrypted with a symmetric passphrase - I
will add text

> 4) multipart/alternative and offer
> 
>    "If a UA receives both an unencrypted and an encrypted SDP offer in an
>     multipart/alternative body, it interprets these as it would a normal
>     multipart alternative as defined in RFC 2046 [16], which means it
>     picks the last alternative that it can support.  Any bodies that
>     cannot be decrypted are treated as unsupportable.  The sending UA
>     should generally put encrypted offers after unencrypted ones, since
>     encrypted ones are preferred."
> 
> There is an issue of knowing whether an encrypted offer is in fact an
> offer or not. Offers (and answers) are recognized by Content-Disposition
>   of session. But in case of encrypted sdp, we have no rules that say
> what the content-disposition of the encrypted body must be - it will
> only be after decryption that the content disposition of the encrypted
> body was.
> 
> It may be that when using multipart/alternative, we specify that *it*
> must contain a content-disposition, which matches that of everything in
> it, and that a application/pkcs7-mime must also be tagged with the c-d
> of its content.

I will work with you on getting wording correct here

> 
> 5) multipart/alternative and answer
> 
>                                   "The UA constructs the answer to the
>     offer as it normally would and may include both encrypted and
>     unencrypted versions of the answer using multipart/alternative."
> 
> Is this necessary? Is there a case where the answerer doesn't know
> whether the offerer will be able to decrypt the answer? For that matter,
> if the offer was encrypted, does it ever make sense for the answer to
> not be encrypted?

will think about this but if offer indicates one can do S/MIME, seems like
safe assumption should be that it can do S/MIME on answer

> 
> 6) event type for certs
> 
>      SUBSCRIBE sip:bob@biloxi.example.com SIP/2.0
>      ...
>      Event: certificate
> 
> Isn't the event type supposed to be pkix-cert? (According to section 4.)
> 

oops - typo - thanks



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 12:29:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22740
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 12:29:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfG1-0005TO-JW
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 12:30:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSf7R-00048e-5h; Fri, 12 Nov 2004 12:21:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSew4-00089i-D9
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 12:10:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20858
	for <sipping@ietf.org>; Fri, 12 Nov 2004 12:10:05 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSexT-0004zR-6v
	for sipping@ietf.org; Fri, 12 Nov 2004 12:11:36 -0500
Received: from KUMARW2 (dhcp85.Research.Panasonic.COM [150.169.1.85])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iACH9W00012478;
	Fri, 12 Nov 2004 12:09:32 -0500
Message-ID: <005001c4c8da$62476b90$5501a996@KUMARW2>
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
        "Mahfuz Rahman" <mahfuz@research.panasonic.com>
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Fri, 12 Nov 2004 12:09:29 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 24d000849df6f171c5ec1cca2ea21b82
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f5932bfc8385127f631fc458a872feb1
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
> I have a sense that you have a concept that the sender will be making 
> the decisions about what should be done to the receiver, while the 
> popular presence viewpoint is that the presentity makes those decisions 
> and announces availability at a higher level of abstraction.
> 
> It would perhaps be helpful if you would be more explicit about the use 
> cases you are trying to enable.

We are adding a section that will describe use cases in more details in the
next revision. A number of use cases are lready being discussed in OMA,
and Dean who goes to OMA is aware those use cases.

regards,

--brijesh

>> 
>> ----- Original Message -----
>> From: Paul Kyzivat <pkyzivat@cisco.com>
>> Date: Thursday, November 11, 2004 7:12 pm
>> Subject: Re: [Sipping] device-info-01
>> 
>> 
>>>Brijesh,
>>>
>>>The more I hear the more I dislike. It sounds like you are trying 
>>>to 
>>>reinvent presence, but in a very device specific way. The 
>>>functionality 
>>>you describe can, I believe, be achieved in a much more 
>>>interoperable 
>>>way by defining new presence attributes which the device may 
>>>publish, 
>>>and which may be disclosed to you if policy of the owner of the 
>>>device 
>>>desires you to know it.
>>>
>>> Paul
>>>
>>>Brijesh Kumar wrote:
>>>
>>>>----- Original Message -----
>>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>>Date: Thursday, November 11, 2004 9:45 am
>>>>Subject: Re: [Sipping] device-info-01
>>>>
>>>>
>>>>
>>>>>I think there is an interesting question at the root of this 
>>>>>draft. The 
>>>>>interesting question is how to manage a "network" where the 
>>>>>network 
>>>>>includes all of the SIP user agents (and in particular, single 
>>>>>user 
>>>>>devices like softphones and hardphones). Management, in this 
>>>>>context, 
>>>>>includes configuration (where things like the config profile are 
>>>>>targeted), but also includes fault management, accounting, 
>>>>>performance 
>>>>>and security management. This draft is targeted roughly in the 
>>>>>area of 
>>>>>device performance management, and thats a laudable goal.
>>>>
>>>>
>>>>Hi Jonathan:
>>>>
>>>>As I clarified during our presentation, the purpose of this draft
>>>>is to monitor the useful states of a device that are 
>>>>relevant for a variety of applications. 
>>>>  
>>>>For example, I may be interested in knowing the current status
>>>>of a camera attached to a user's phone before I start streaming
>>>>video to him. Or, I may be interested in monitoring if the user's
>>>>device has enough memory left for me to stream a live video, and
>>>>then continue monitoring. Also, to know if the speaker is muted 
>>>>or not, or the camera is on or of.  I may even want to know if 
>>>
>>>the 
>>>
>>>>my friend is inside his home in a comfortable environment rather 
>>>
>>>than 
>>>
>>>>in open in 100 degree heat before streaming a live video to him. 
>>>
>>>>And, another example is what Dean mentioned - knowing the status of
>>>>of a video recorder, and then using that status information go 
>>>
>>>to 
>>>
>>>>a different recorder to record a video stream.
>>>>
>>>>There are many use cases that will benefit with the abilities 
>>>>to learn the device and various type of status information on 
>>>
>>>the 
>>>
>>>>device.  I have only given examples related to applications that
>>>>are in the common knowledge - I know there are a lot many use
>>>>cases of similar nature. 
>>>>
>>>>Cheers,
>>>>
>>>>--brijesh 
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>However, I think the problem is fairly broad, and would benefit 
>>>>
>>>>>from a 
>>>>
>>>>>top-down look at what really needs to be done here, rather than 
>>>>>jumping 
>>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>>complicated 
>>>>>because in many cases, these devices are run and managed by end 
>>>>
>>>users.>>
>>>
>>>>>-Jonathan R.
>>>>>
>>>>>Mahfuz Rahman wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>>
>>>>>follows:  
>>>>>
>>>>>
>>>>>>OPTIONS method is used to query device capabilities such as 
>>>>>
>>>>>supported methods,
>>>>>
>>>>>
>>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>>
>>>for 
>>>
>>>>>device profile
>>>>>
>>>>>
>>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>>
>>>>>like to define
>>>>>
>>>>>
>>>>>>tags for each of the data elements we have defined in the 
>>>>>
>>>>>profile it will be a long
>>>>>
>>>>>
>>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>>
>>>>>to include multiple
>>>>>
>>>>>
>>>>>>schemas and URLs for a device it would be difficult to 
>>>>>
>>>represent 
>>>
>>>>>using OPTIONS unless
>>>>>
>>>>>
>>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>>
>>>>>following content type: 
>>>>>
>>>>>
>>>>>>application/device-profile+xml. 
>>>>>>
>>>>>>I agree with you to add software version and also an optional UUID.
>>>>>>
>>>>>>The status part will be extended in the future revision which 
>>>>>
>>>>>might include a 
>>>>>
>>>>>
>>>>>>common XML format. Currently it describes only how vendor 
>>>>>
>>>>>specific status information
>>>>>
>>>>>
>>>>>>can be retrieved. 
>>>>>>
>>>>>>- mahfuz
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>>Behalf Of Cullen Jennings
>>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>>To: sipping
>>>>>>Subject: [Sipping] device-info-01
>>>>>>
>>>>>>
>>>>>>Nice draft - few comments ...
>>>>>>
>>>>>>As a completely alternative suggestions.... How much of this 
>>>>>
>>>>>information can
>>>>>
>>>>>
>>>>>>you get by just sending an OPTION request to the device.
>>>>>>
>>>>>>I would remove all the discussion of the device status - you 
>>>>>
>>>>>don't define
>>>>>
>>>>>
>>>>>>anything about how to do it so the discussion does not help.
>>>>>>
>>>>>>This reports things that should not change so rate of 
>>>>>
>>>>>notifications is very
>>>>>
>>>>>
>>>>>>very seldom.
>>>>>>
>>>>>>I would add an optional UUID to the profile
>>>>>>
>>>>>>You might want to add software version.
>>>>>>
>>>>>>I would make the schema URL and name attributes of a schema 
>>>>>
>>>>>object so that
>>>>>
>>>>>
>>>>>>the device can lists multiple schema that it can support.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Sipping mailing list  
>>>>>
>>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>>NEW development of the 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
>>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>>07054-2711
>>>>>Cisco Systems
>>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>>http://www.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
>>>>
>>>
>>>
>>>
>> 
>> 
>> 
> 
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 12:30:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22877
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 12:30:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfHf-0005WS-Cl
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 12:32:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSf7S-00049P-W5; Fri, 12 Nov 2004 12:21:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSews-0008Qq-6T
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 12:10:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20891
	for <sipping@ietf.org>; Fri, 12 Nov 2004 12:10:55 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSeyH-00050i-4Z
	for sipping@ietf.org; Fri, 12 Nov 2004 12:12:26 -0500
Received: from KUMARW2 (dhcp85.Research.Panasonic.COM [150.169.1.85])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iACHANKp012523;
	Fri, 12 Nov 2004 12:10:23 -0500
Message-ID: <005101c4c8da$80c95380$5501a996@KUMARW2>
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
        "Mahfuz Rahman" <mahfuz@research.panasonic.com>
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Fri, 12 Nov 2004 12:10:20 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
> I have a sense that you have a concept that the sender will be making 
> the decisions about what should be done to the receiver, while the 
> popular presence viewpoint is that the presentity makes those decisions 
> and announces availability at a higher level of abstraction.
> 
> It would perhaps be helpful if you would be more explicit about the use 
> cases you are trying to enable.

We are adding a section that will describe use cases in more details in the
next revision. A number of use cases are lready being discussed in Open
Mobile Alliance (OMA), and Dean who goes to OMA is aware those use 
cases. Some of these cases may be discussed in our revision.

regards,

--brijesh

>> 
>> ----- Original Message -----
>> From: Paul Kyzivat <pkyzivat@cisco.com>
>> Date: Thursday, November 11, 2004 7:12 pm
>> Subject: Re: [Sipping] device-info-01
>> 
>> 
>>>Brijesh,
>>>
>>>The more I hear the more I dislike. It sounds like you are trying 
>>>to 
>>>reinvent presence, but in a very device specific way. The 
>>>functionality 
>>>you describe can, I believe, be achieved in a much more 
>>>interoperable 
>>>way by defining new presence attributes which the device may 
>>>publish, 
>>>and which may be disclosed to you if policy of the owner of the 
>>>device 
>>>desires you to know it.
>>>
>>> Paul
>>>
>>>Brijesh Kumar wrote:
>>>
>>>>----- Original Message -----
>>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>>Date: Thursday, November 11, 2004 9:45 am
>>>>Subject: Re: [Sipping] device-info-01
>>>>
>>>>
>>>>
>>>>>I think there is an interesting question at the root of this 
>>>>>draft. The 
>>>>>interesting question is how to manage a "network" where the 
>>>>>network 
>>>>>includes all of the SIP user agents (and in particular, single 
>>>>>user 
>>>>>devices like softphones and hardphones). Management, in this 
>>>>>context, 
>>>>>includes configuration (where things like the config profile are 
>>>>>targeted), but also includes fault management, accounting, 
>>>>>performance 
>>>>>and security management. This draft is targeted roughly in the 
>>>>>area of 
>>>>>device performance management, and thats a laudable goal.
>>>>
>>>>
>>>>Hi Jonathan:
>>>>
>>>>As I clarified during our presentation, the purpose of this draft
>>>>is to monitor the useful states of a device that are 
>>>>relevant for a variety of applications. 
>>>>  
>>>>For example, I may be interested in knowing the current status
>>>>of a camera attached to a user's phone before I start streaming
>>>>video to him. Or, I may be interested in monitoring if the user's
>>>>device has enough memory left for me to stream a live video, and
>>>>then continue monitoring. Also, to know if the speaker is muted 
>>>>or not, or the camera is on or of.  I may even want to know if 
>>>
>>>the 
>>>
>>>>my friend is inside his home in a comfortable environment rather 
>>>
>>>than 
>>>
>>>>in open in 100 degree heat before streaming a live video to him. 
>>>
>>>>And, another example is what Dean mentioned - knowing the status of
>>>>of a video recorder, and then using that status information go 
>>>
>>>to 
>>>
>>>>a different recorder to record a video stream.
>>>>
>>>>There are many use cases that will benefit with the abilities 
>>>>to learn the device and various type of status information on 
>>>
>>>the 
>>>
>>>>device.  I have only given examples related to applications that
>>>>are in the common knowledge - I know there are a lot many use
>>>>cases of similar nature. 
>>>>
>>>>Cheers,
>>>>
>>>>--brijesh 
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>However, I think the problem is fairly broad, and would benefit 
>>>>
>>>>>from a 
>>>>
>>>>>top-down look at what really needs to be done here, rather than 
>>>>>jumping 
>>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>>complicated 
>>>>>because in many cases, these devices are run and managed by end 
>>>>
>>>users.>>
>>>
>>>>>-Jonathan R.
>>>>>
>>>>>Mahfuz Rahman wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>>
>>>>>follows:  
>>>>>
>>>>>
>>>>>>OPTIONS method is used to query device capabilities such as 
>>>>>
>>>>>supported methods,
>>>>>
>>>>>
>>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>>
>>>for 
>>>
>>>>>device profile
>>>>>
>>>>>
>>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>>
>>>>>like to define
>>>>>
>>>>>
>>>>>>tags for each of the data elements we have defined in the 
>>>>>
>>>>>profile it will be a long
>>>>>
>>>>>
>>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>>
>>>>>to include multiple
>>>>>
>>>>>
>>>>>>schemas and URLs for a device it would be difficult to 
>>>>>
>>>represent 
>>>
>>>>>using OPTIONS unless
>>>>>
>>>>>
>>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>>
>>>>>following content type: 
>>>>>
>>>>>
>>>>>>application/device-profile+xml. 
>>>>>>
>>>>>>I agree with you to add software version and also an optional UUID.
>>>>>>
>>>>>>The status part will be extended in the future revision which 
>>>>>
>>>>>might include a 
>>>>>
>>>>>
>>>>>>common XML format. Currently it describes only how vendor 
>>>>>
>>>>>specific status information
>>>>>
>>>>>
>>>>>>can be retrieved. 
>>>>>>
>>>>>>- mahfuz
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>>Behalf Of Cullen Jennings
>>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>>To: sipping
>>>>>>Subject: [Sipping] device-info-01
>>>>>>
>>>>>>
>>>>>>Nice draft - few comments ...
>>>>>>
>>>>>>As a completely alternative suggestions.... How much of this 
>>>>>
>>>>>information can
>>>>>
>>>>>
>>>>>>you get by just sending an OPTION request to the device.
>>>>>>
>>>>>>I would remove all the discussion of the device status - you 
>>>>>
>>>>>don't define
>>>>>
>>>>>
>>>>>>anything about how to do it so the discussion does not help.
>>>>>>
>>>>>>This reports things that should not change so rate of 
>>>>>
>>>>>notifications is very
>>>>>
>>>>>
>>>>>>very seldom.
>>>>>>
>>>>>>I would add an optional UUID to the profile
>>>>>>
>>>>>>You might want to add software version.
>>>>>>
>>>>>>I would make the schema URL and name attributes of a schema 
>>>>>
>>>>>object so that
>>>>>
>>>>>
>>>>>>the device can lists multiple schema that it can support.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Sipping mailing list  
>>>>>
>>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>>NEW development of the 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
>>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>>07054-2711
>>>>>Cisco Systems
>>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>>http://www.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
>>>>
>>>
>>>
>>>
>> 
>> 
>> 
> 
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 12:31:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22996
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 12:31:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfIc-0005YL-Ak
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 12:33:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSf7U-0004A8-Bf; Fri, 12 Nov 2004 12:21:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSeww-0008Sk-Ee
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 12:11:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20902
	for <sipping@ietf.org>; Fri, 12 Nov 2004 12:10:59 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSeyL-00050n-MM
	for sipping@ietf.org; Fri, 12 Nov 2004 12:12:30 -0500
Received: from KUMARW2 (dhcp85.Research.Panasonic.COM [150.169.1.85])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iACHATHu012530;
	Fri, 12 Nov 2004 12:10:29 -0500
Message-ID: <005201c4c8da$84338090$5501a996@KUMARW2>
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
        "Mahfuz Rahman" <mahfuz@research.panasonic.com>
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Fri, 12 Nov 2004 12:10:26 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
> I have a sense that you have a concept that the sender will be making 
> the decisions about what should be done to the receiver, while the 
> popular presence viewpoint is that the presentity makes those decisions 
> and announces availability at a higher level of abstraction.
> 
> It would perhaps be helpful if you would be more explicit about the use 
> cases you are trying to enable.

We are adding a section that will describe use cases in more details in the
next revision. A number of use cases are lready being discussed in Open
Mobile Alliance (OMA), and Dean who goes to OMA is aware those use 
cases. Some of these cases may be discussed in our revision.

regards,

--brijesh

>> 
>> ----- Original Message -----
>> From: Paul Kyzivat <pkyzivat@cisco.com>
>> Date: Thursday, November 11, 2004 7:12 pm
>> Subject: Re: [Sipping] device-info-01
>> 
>> 
>>>Brijesh,
>>>
>>>The more I hear the more I dislike. It sounds like you are trying 
>>>to 
>>>reinvent presence, but in a very device specific way. The 
>>>functionality 
>>>you describe can, I believe, be achieved in a much more 
>>>interoperable 
>>>way by defining new presence attributes which the device may 
>>>publish, 
>>>and which may be disclosed to you if policy of the owner of the 
>>>device 
>>>desires you to know it.
>>>
>>> Paul
>>>
>>>Brijesh Kumar wrote:
>>>
>>>>----- Original Message -----
>>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>>Date: Thursday, November 11, 2004 9:45 am
>>>>Subject: Re: [Sipping] device-info-01
>>>>
>>>>
>>>>
>>>>>I think there is an interesting question at the root of this 
>>>>>draft. The 
>>>>>interesting question is how to manage a "network" where the 
>>>>>network 
>>>>>includes all of the SIP user agents (and in particular, single 
>>>>>user 
>>>>>devices like softphones and hardphones). Management, in this 
>>>>>context, 
>>>>>includes configuration (where things like the config profile are 
>>>>>targeted), but also includes fault management, accounting, 
>>>>>performance 
>>>>>and security management. This draft is targeted roughly in the 
>>>>>area of 
>>>>>device performance management, and thats a laudable goal.
>>>>
>>>>
>>>>Hi Jonathan:
>>>>
>>>>As I clarified during our presentation, the purpose of this draft
>>>>is to monitor the useful states of a device that are 
>>>>relevant for a variety of applications. 
>>>>  
>>>>For example, I may be interested in knowing the current status
>>>>of a camera attached to a user's phone before I start streaming
>>>>video to him. Or, I may be interested in monitoring if the user's
>>>>device has enough memory left for me to stream a live video, and
>>>>then continue monitoring. Also, to know if the speaker is muted 
>>>>or not, or the camera is on or of.  I may even want to know if 
>>>
>>>the 
>>>
>>>>my friend is inside his home in a comfortable environment rather 
>>>
>>>than 
>>>
>>>>in open in 100 degree heat before streaming a live video to him. 
>>>
>>>>And, another example is what Dean mentioned - knowing the status of
>>>>of a video recorder, and then using that status information go 
>>>
>>>to 
>>>
>>>>a different recorder to record a video stream.
>>>>
>>>>There are many use cases that will benefit with the abilities 
>>>>to learn the device and various type of status information on 
>>>
>>>the 
>>>
>>>>device.  I have only given examples related to applications that
>>>>are in the common knowledge - I know there are a lot many use
>>>>cases of similar nature. 
>>>>
>>>>Cheers,
>>>>
>>>>--brijesh 
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>However, I think the problem is fairly broad, and would benefit 
>>>>
>>>>>from a 
>>>>
>>>>>top-down look at what really needs to be done here, rather than 
>>>>>jumping 
>>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>>complicated 
>>>>>because in many cases, these devices are run and managed by end 
>>>>
>>>users.>>
>>>
>>>>>-Jonathan R.
>>>>>
>>>>>Mahfuz Rahman wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>>
>>>>>follows:  
>>>>>
>>>>>
>>>>>>OPTIONS method is used to query device capabilities such as 
>>>>>
>>>>>supported methods,
>>>>>
>>>>>
>>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>>
>>>for 
>>>
>>>>>device profile
>>>>>
>>>>>
>>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>>
>>>>>like to define
>>>>>
>>>>>
>>>>>>tags for each of the data elements we have defined in the 
>>>>>
>>>>>profile it will be a long
>>>>>
>>>>>
>>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>>
>>>>>to include multiple
>>>>>
>>>>>
>>>>>>schemas and URLs for a device it would be difficult to 
>>>>>
>>>represent 
>>>
>>>>>using OPTIONS unless
>>>>>
>>>>>
>>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>>
>>>>>following content type: 
>>>>>
>>>>>
>>>>>>application/device-profile+xml. 
>>>>>>
>>>>>>I agree with you to add software version and also an optional UUID.
>>>>>>
>>>>>>The status part will be extended in the future revision which 
>>>>>
>>>>>might include a 
>>>>>
>>>>>
>>>>>>common XML format. Currently it describes only how vendor 
>>>>>
>>>>>specific status information
>>>>>
>>>>>
>>>>>>can be retrieved. 
>>>>>>
>>>>>>- mahfuz
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>>Behalf Of Cullen Jennings
>>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>>To: sipping
>>>>>>Subject: [Sipping] device-info-01
>>>>>>
>>>>>>
>>>>>>Nice draft - few comments ...
>>>>>>
>>>>>>As a completely alternative suggestions.... How much of this 
>>>>>
>>>>>information can
>>>>>
>>>>>
>>>>>>you get by just sending an OPTION request to the device.
>>>>>>
>>>>>>I would remove all the discussion of the device status - you 
>>>>>
>>>>>don't define
>>>>>
>>>>>
>>>>>>anything about how to do it so the discussion does not help.
>>>>>>
>>>>>>This reports things that should not change so rate of 
>>>>>
>>>>>notifications is very
>>>>>
>>>>>
>>>>>>very seldom.
>>>>>>
>>>>>>I would add an optional UUID to the profile
>>>>>>
>>>>>>You might want to add software version.
>>>>>>
>>>>>>I would make the schema URL and name attributes of a schema 
>>>>>
>>>>>object so that
>>>>>
>>>>>
>>>>>>the device can lists multiple schema that it can support.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Sipping mailing list  
>>>>>
>>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>>NEW development of the 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
>>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>>07054-2711
>>>>>Cisco Systems
>>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>>http://www.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
>>>>
>>>
>>>
>>>
>> 
>> 
>> 
> 
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 12:35:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23321
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 12:35:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfLq-0005f5-Cy
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 12:36:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSf7V-0004Ac-Vz; Fri, 12 Nov 2004 12:21:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSex4-0008UP-LB
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 12:11:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20917
	for <sipping@ietf.org>; Fri, 12 Nov 2004 12:11:07 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSeyT-00050r-UL
	for sipping@ietf.org; Fri, 12 Nov 2004 12:12:38 -0500
Received: from KUMARW2 (dhcp85.Research.Panasonic.COM [150.169.1.85])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iACHAb8d012537;
	Fri, 12 Nov 2004 12:10:37 -0500
Message-ID: <005301c4c8da$88d6c9e0$5501a996@KUMARW2>
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
        "Mahfuz Rahman" <mahfuz@research.panasonic.com>
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Fri, 12 Nov 2004 12:10:34 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
> I have a sense that you have a concept that the sender will be making 
> the decisions about what should be done to the receiver, while the 
> popular presence viewpoint is that the presentity makes those decisions 
> and announces availability at a higher level of abstraction.
> 
> It would perhaps be helpful if you would be more explicit about the use 
> cases you are trying to enable.

We are adding a section that will describe use cases in more details in the
next revision. A number of use cases are lready being discussed in Open
Mobile Alliance (OMA), and Dean who goes to OMA is aware those use 
cases. Some of these cases may be discussed in our revision.

regards,

--brijesh

>> 
>> ----- Original Message -----
>> From: Paul Kyzivat <pkyzivat@cisco.com>
>> Date: Thursday, November 11, 2004 7:12 pm
>> Subject: Re: [Sipping] device-info-01
>> 
>> 
>>>Brijesh,
>>>
>>>The more I hear the more I dislike. It sounds like you are trying 
>>>to 
>>>reinvent presence, but in a very device specific way. The 
>>>functionality 
>>>you describe can, I believe, be achieved in a much more 
>>>interoperable 
>>>way by defining new presence attributes which the device may 
>>>publish, 
>>>and which may be disclosed to you if policy of the owner of the 
>>>device 
>>>desires you to know it.
>>>
>>> Paul
>>>
>>>Brijesh Kumar wrote:
>>>
>>>>----- Original Message -----
>>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>>Date: Thursday, November 11, 2004 9:45 am
>>>>Subject: Re: [Sipping] device-info-01
>>>>
>>>>
>>>>
>>>>>I think there is an interesting question at the root of this 
>>>>>draft. The 
>>>>>interesting question is how to manage a "network" where the 
>>>>>network 
>>>>>includes all of the SIP user agents (and in particular, single 
>>>>>user 
>>>>>devices like softphones and hardphones). Management, in this 
>>>>>context, 
>>>>>includes configuration (where things like the config profile are 
>>>>>targeted), but also includes fault management, accounting, 
>>>>>performance 
>>>>>and security management. This draft is targeted roughly in the 
>>>>>area of 
>>>>>device performance management, and thats a laudable goal.
>>>>
>>>>
>>>>Hi Jonathan:
>>>>
>>>>As I clarified during our presentation, the purpose of this draft
>>>>is to monitor the useful states of a device that are 
>>>>relevant for a variety of applications. 
>>>>  
>>>>For example, I may be interested in knowing the current status
>>>>of a camera attached to a user's phone before I start streaming
>>>>video to him. Or, I may be interested in monitoring if the user's
>>>>device has enough memory left for me to stream a live video, and
>>>>then continue monitoring. Also, to know if the speaker is muted 
>>>>or not, or the camera is on or of.  I may even want to know if 
>>>
>>>the 
>>>
>>>>my friend is inside his home in a comfortable environment rather 
>>>
>>>than 
>>>
>>>>in open in 100 degree heat before streaming a live video to him. 
>>>
>>>>And, another example is what Dean mentioned - knowing the status of
>>>>of a video recorder, and then using that status information go 
>>>
>>>to 
>>>
>>>>a different recorder to record a video stream.
>>>>
>>>>There are many use cases that will benefit with the abilities 
>>>>to learn the device and various type of status information on 
>>>
>>>the 
>>>
>>>>device.  I have only given examples related to applications that
>>>>are in the common knowledge - I know there are a lot many use
>>>>cases of similar nature. 
>>>>
>>>>Cheers,
>>>>
>>>>--brijesh 
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>However, I think the problem is fairly broad, and would benefit 
>>>>
>>>>>from a 
>>>>
>>>>>top-down look at what really needs to be done here, rather than 
>>>>>jumping 
>>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>>complicated 
>>>>>because in many cases, these devices are run and managed by end 
>>>>
>>>users.>>
>>>
>>>>>-Jonathan R.
>>>>>
>>>>>Mahfuz Rahman wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>>
>>>>>follows:  
>>>>>
>>>>>
>>>>>>OPTIONS method is used to query device capabilities such as 
>>>>>
>>>>>supported methods,
>>>>>
>>>>>
>>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>>
>>>for 
>>>
>>>>>device profile
>>>>>
>>>>>
>>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>>
>>>>>like to define
>>>>>
>>>>>
>>>>>>tags for each of the data elements we have defined in the 
>>>>>
>>>>>profile it will be a long
>>>>>
>>>>>
>>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>>
>>>>>to include multiple
>>>>>
>>>>>
>>>>>>schemas and URLs for a device it would be difficult to 
>>>>>
>>>represent 
>>>
>>>>>using OPTIONS unless
>>>>>
>>>>>
>>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>>
>>>>>following content type: 
>>>>>
>>>>>
>>>>>>application/device-profile+xml. 
>>>>>>
>>>>>>I agree with you to add software version and also an optional UUID.
>>>>>>
>>>>>>The status part will be extended in the future revision which 
>>>>>
>>>>>might include a 
>>>>>
>>>>>
>>>>>>common XML format. Currently it describes only how vendor 
>>>>>
>>>>>specific status information
>>>>>
>>>>>
>>>>>>can be retrieved. 
>>>>>>
>>>>>>- mahfuz
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>>Behalf Of Cullen Jennings
>>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>>To: sipping
>>>>>>Subject: [Sipping] device-info-01
>>>>>>
>>>>>>
>>>>>>Nice draft - few comments ...
>>>>>>
>>>>>>As a completely alternative suggestions.... How much of this 
>>>>>
>>>>>information can
>>>>>
>>>>>
>>>>>>you get by just sending an OPTION request to the device.
>>>>>>
>>>>>>I would remove all the discussion of the device status - you 
>>>>>
>>>>>don't define
>>>>>
>>>>>
>>>>>>anything about how to do it so the discussion does not help.
>>>>>>
>>>>>>This reports things that should not change so rate of 
>>>>>
>>>>>notifications is very
>>>>>
>>>>>
>>>>>>very seldom.
>>>>>>
>>>>>>I would add an optional UUID to the profile
>>>>>>
>>>>>>You might want to add software version.
>>>>>>
>>>>>>I would make the schema URL and name attributes of a schema 
>>>>>
>>>>>object so that
>>>>>
>>>>>
>>>>>>the device can lists multiple schema that it can support.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Sipping mailing list  
>>>>>
>>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>>NEW development of the 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
>>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>>07054-2711
>>>>>Cisco Systems
>>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>>http://www.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
>>>>
>>>
>>>
>>>
>> 
>> 
>> 
> 
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 12:36:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23444
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 12:36:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfNP-0005i1-JS
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 12:38:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSf7Y-0004Bo-4q; Fri, 12 Nov 2004 12:22:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSexE-00004w-Uw
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 12:11:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20936
	for <sipping@ietf.org>; Fri, 12 Nov 2004 12:11:17 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSeyd-000514-Ja
	for sipping@ietf.org; Fri, 12 Nov 2004 12:12:48 -0500
Received: from KUMARW2 (dhcp85.Research.Panasonic.COM [150.169.1.85])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iACHAjJs012544;
	Fri, 12 Nov 2004 12:10:46 -0500
Message-ID: <005401c4c8da$8e3796d0$5501a996@KUMARW2>
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
        "Mahfuz Rahman" <mahfuz@research.panasonic.com>
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
Subject: Re: [Sipping] device-info-01
Date: Fri, 12 Nov 2004 12:10:43 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a4bcf8f67063cac573319207fe3db35
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
> I have a sense that you have a concept that the sender will be making 
> the decisions about what should be done to the receiver, while the 
> popular presence viewpoint is that the presentity makes those decisions 
> and announces availability at a higher level of abstraction.
> 
> It would perhaps be helpful if you would be more explicit about the use 
> cases you are trying to enable.

We are adding a section that will describe use cases in more details in the
next revision. A number of use cases are lready being discussed in Open
Mobile Alliance (OMA), and Dean who goes to OMA is aware those use 
cases. Some of these cases may be discussed in our revision.

regards,

--brijesh

>> 
>> ----- Original Message -----
>> From: Paul Kyzivat <pkyzivat@cisco.com>
>> Date: Thursday, November 11, 2004 7:12 pm
>> Subject: Re: [Sipping] device-info-01
>> 
>> 
>>>Brijesh,
>>>
>>>The more I hear the more I dislike. It sounds like you are trying 
>>>to 
>>>reinvent presence, but in a very device specific way. The 
>>>functionality 
>>>you describe can, I believe, be achieved in a much more 
>>>interoperable 
>>>way by defining new presence attributes which the device may 
>>>publish, 
>>>and which may be disclosed to you if policy of the owner of the 
>>>device 
>>>desires you to know it.
>>>
>>> Paul
>>>
>>>Brijesh Kumar wrote:
>>>
>>>>----- Original Message -----
>>>>From: Jonathan Rosenberg <jdrosen@cisco.com>
>>>>Date: Thursday, November 11, 2004 9:45 am
>>>>Subject: Re: [Sipping] device-info-01
>>>>
>>>>
>>>>
>>>>>I think there is an interesting question at the root of this 
>>>>>draft. The 
>>>>>interesting question is how to manage a "network" where the 
>>>>>network 
>>>>>includes all of the SIP user agents (and in particular, single 
>>>>>user 
>>>>>devices like softphones and hardphones). Management, in this 
>>>>>context, 
>>>>>includes configuration (where things like the config profile are 
>>>>>targeted), but also includes fault management, accounting, 
>>>>>performance 
>>>>>and security management. This draft is targeted roughly in the 
>>>>>area of 
>>>>>device performance management, and thats a laudable goal.
>>>>
>>>>
>>>>Hi Jonathan:
>>>>
>>>>As I clarified during our presentation, the purpose of this draft
>>>>is to monitor the useful states of a device that are 
>>>>relevant for a variety of applications. 
>>>>  
>>>>For example, I may be interested in knowing the current status
>>>>of a camera attached to a user's phone before I start streaming
>>>>video to him. Or, I may be interested in monitoring if the user's
>>>>device has enough memory left for me to stream a live video, and
>>>>then continue monitoring. Also, to know if the speaker is muted 
>>>>or not, or the camera is on or of.  I may even want to know if 
>>>
>>>the 
>>>
>>>>my friend is inside his home in a comfortable environment rather 
>>>
>>>than 
>>>
>>>>in open in 100 degree heat before streaming a live video to him. 
>>>
>>>>And, another example is what Dean mentioned - knowing the status of
>>>>of a video recorder, and then using that status information go 
>>>
>>>to 
>>>
>>>>a different recorder to record a video stream.
>>>>
>>>>There are many use cases that will benefit with the abilities 
>>>>to learn the device and various type of status information on 
>>>
>>>the 
>>>
>>>>device.  I have only given examples related to applications that
>>>>are in the common knowledge - I know there are a lot many use
>>>>cases of similar nature. 
>>>>
>>>>Cheers,
>>>>
>>>>--brijesh 
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>However, I think the problem is fairly broad, and would benefit 
>>>>
>>>>>from a 
>>>>
>>>>>top-down look at what really needs to be done here, rather than 
>>>>>jumping 
>>>>>to an event package or OPTIONS or whatever. The problem is 
>>>>>complicated 
>>>>>because in many cases, these devices are run and managed by end 
>>>>
>>>users.>>
>>>
>>>>>-Jonathan R.
>>>>>
>>>>>Mahfuz Rahman wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Thanks Cullen for making some good comments. My response is as 
>>>>>
>>>>>follows:  
>>>>>
>>>>>
>>>>>>OPTIONS method is used to query device capabilities such as 
>>>>>
>>>>>supported methods,
>>>>>
>>>>>
>>>>>>contnet types, codesc etc.. This draft defines data elements 
>>>>>
>>>for 
>>>
>>>>>device profile
>>>>>
>>>>>
>>>>>>which is  different from the tags defined for OPTIONS. So if we 
>>>>>
>>>>>like to define
>>>>>
>>>>>
>>>>>>tags for each of the data elements we have defined in the 
>>>>>
>>>>>profile it will be a long
>>>>>
>>>>>
>>>>>>list. I am not sure if it is acceptable. Also, as you suggested 
>>>>>
>>>>>to include multiple
>>>>>
>>>>>
>>>>>>schemas and URLs for a device it would be difficult to 
>>>>>
>>>represent 
>>>
>>>>>using OPTIONS unless
>>>>>
>>>>>
>>>>>>we allow attachment of a body in the OPTIONS response with the 
>>>>>
>>>>>following content type: 
>>>>>
>>>>>
>>>>>>application/device-profile+xml. 
>>>>>>
>>>>>>I agree with you to add software version and also an optional UUID.
>>>>>>
>>>>>>The status part will be extended in the future revision which 
>>>>>
>>>>>might include a 
>>>>>
>>>>>
>>>>>>common XML format. Currently it describes only how vendor 
>>>>>
>>>>>specific status information
>>>>>
>>>>>
>>>>>>can be retrieved. 
>>>>>>
>>>>>>- mahfuz
>>>>>>
>>>>>>-----Original Message-----
>>>>>>From: sipping-bounces@ietf.org [sipping-bounces@ietf.org]On
>>>>>>Behalf Of Cullen Jennings
>>>>>>Sent: Saturday, November 06, 2004 6:19 PM
>>>>>>To: sipping
>>>>>>Subject: [Sipping] device-info-01
>>>>>>
>>>>>>
>>>>>>Nice draft - few comments ...
>>>>>>
>>>>>>As a completely alternative suggestions.... How much of this 
>>>>>
>>>>>information can
>>>>>
>>>>>
>>>>>>you get by just sending an OPTION request to the device.
>>>>>>
>>>>>>I would remove all the discussion of the device status - you 
>>>>>
>>>>>don't define
>>>>>
>>>>>
>>>>>>anything about how to do it so the discussion does not help.
>>>>>>
>>>>>>This reports things that should not change so rate of 
>>>>>
>>>>>notifications is very
>>>>>
>>>>>
>>>>>>very seldom.
>>>>>>
>>>>>>I would add an optional UUID to the profile
>>>>>>
>>>>>>You might want to add software version.
>>>>>>
>>>>>>I would make the schema URL and name attributes of a schema 
>>>>>
>>>>>object so that
>>>>>
>>>>>
>>>>>>the device can lists multiple schema that it can support.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Sipping mailing list  
>>>>>
>>>https://www1.ietf.org/mailman/listinfo/sipping>>>This list is for 
>>>NEW development of the 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
>>>>>Director, Service Provider VoIP Architecture   Parsippany, NJ 
>>>>>07054-2711
>>>>>Cisco Systems
>>>>>jdrosen@cisco.com                              FAX:   (973) 952-5050
>>>>>http://www.jdrosen.net                         PHONE: (973) 952-5000
>>>>>http://www.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
>>>>
>>>
>>>
>>>
>> 
>> 
>> 
> 
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 13:22:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27909
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 13:22:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSg5k-0006sM-RT
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 13:24:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSg11-0008HL-0I; Fri, 12 Nov 2004 13:19:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSfwe-0007Gx-W7; Fri, 12 Nov 2004 13:14:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27167;
	Fri, 12 Nov 2004 13:14:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSfy5-0006gI-5M; Fri, 12 Nov 2004 13:16:17 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CSfss-0006DS-FH; Fri, 12 Nov 2004 13:10:54 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CSfss-0006DS-FH@megatron.ietf.org>
Date: Fri, 12 Nov 2004 13:10:54 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: sipping chair <rohan@ekabal.com>,
        Internet Architecture Board <iab@iab.org>,
        sipping chair <dean.willis@softarmor.com>,
        sipping mailing list <sipping@ietf.org>,
        sipping chair <gonzalo.camarillo@ericsson.com>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Sipping] Document Action: 'Input 3rd-Generation Partnership
 Project (3GPP) 
 Release 5 requirements on the Session Initiation Protocol (SIP)' to 
 Informational RFC 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

The IESG has approved the following document:

- 'Input 3rd-Generation Partnership Project (3GPP) Release 5 requirements 
   on the Session Initiation Protocol (SIP) '
   <draft-ietf-sipping-3gpp-r5-requirements-00.txt> as an Informational RFC

This document is the product of the Session Initiation Proposal Investigation 
Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

RFC Editor Notes


Change Title to "Input 3rd-Generation Partnership Project (3GPP) Release
5 requirements on the Session Initiation Protocol (SIP)"

Add to the Introduction
    The document "Input 3rd-Generation Partnership Project (3GPP) Release 5
    requirements on the Session Initiation Protocol (SIP)" is advisory in
    nature. Its primary purpose is to help the IETF understand the IMS
    environment and the manner in which 3GPP envisions using SIP within
    that environment. Given this better understanding, we expect that the
    IETF can more effectively evolve the SIP protocol. The IETF will not
    respond to the requirements given in this document on a
    point-for-point basis. Some requiremements have been and/or will be
    met by extensions to the SIP protocol. Others may be addressed by
    effectively using existing capabilities in SIP or other protocols,
    and we expect that individual members of the SIP community will work
    with 3GPP to achieve a better understanding of these mechanisms. Some
    of the requirements documented in this document may not be addressed.
    at all by the IETF, although we believe that the act of documenting
    and discussing them is in itself helpful in achieving a better
    all-around understanding of the task at hand.

Section 4. 24

Delete following paragraph:

For example, once an IPsec security association or a TLS connection
   is established, no additional round trips are required during session
   setup.  However, the requirement of minimizing the number of round
   trips is hard to satisfy with IKE or TLS.  It seems that IKE [6] adds
   a number of roundtrips, particularly if run together with legacy
   authentication extensions developed in the IPSRA WG.  TLS [3] uses
   fewer roundtrips, but on the other hand doesn't support UDP.

Replace:

and/or Diffie-Helman with e.g. Diffie-Hellman

4.24.3.1

Delete

and replay protection


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Fri Nov 12 16:11:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24331
	for <sipping-web-archive@ietf.org>; Fri, 12 Nov 2004 16:11:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSij7-0006Cr-9I
	for sipping-web-archive@ietf.org; Fri, 12 Nov 2004 16:13:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSiRy-0008Am-63; Fri, 12 Nov 2004 15:55:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CShrI-0005fa-L6
	for sipping@megatron.ietf.org; Fri, 12 Nov 2004 15:17:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09961
	for <sipping@ietf.org>; Fri, 12 Nov 2004 15:17:22 -0500 (EST)
Received: from airwolf.sentito.com ([65.202.222.11])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CShsb-0001Sm-Od
	for sipping@ietf.org; Fri, 12 Nov 2004 15:18:54 -0500
Received: (qmail 26279 invoked by uid 1014); 12 Nov 2004 20:16:35 -0000
Received: from cwang@sentito.com by airwolf.sentito.com by uid 1002 with
	qmail-scanner-1.22 
	(clamdscan: 0.80. spamassassin: 2.63.   Clear:RC:1(65.202.222.12):. 
	Processed in 0.043672 secs); 12 Nov 2004 20:16:35 -0000
Received: from unknown (HELO exchange.corp.sentito.com) (65.202.222.12)
	by airwolf.sentito.com with SMTP; 12 Nov 2004 20:16:35 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 12 Nov 2004 15:16:34 -0500
Message-ID: <E0BC4E905DBC6546B12F288DF702323340A86A@exchange.corp.sentito.com>
Thread-Topic: draft-ietf-sipping-realtimefax-02.txt
Thread-Index: AcTI9Z8btqvuAVIrQjGN5hu6foICBA==
From: "Chris Wang" <cwang@sentito.com>
To: <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] draft-ietf-sipping-realtimefax-02.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable

Can anyone send me or post to the list a copy of
draft-ietf-sipping-realtimefax-02.txt draft?

Thanks!

Chris Wang
sentitO 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 sipping-bounces@ietf.org  Mon Nov 15 16:48:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14273
	for <sipping-web-archive@ietf.org>; Mon, 15 Nov 2004 16:48:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTojt-0002yw-7C
	for sipping-web-archive@ietf.org; Mon, 15 Nov 2004 16:50:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTocE-0007cx-OP; Mon, 15 Nov 2004 16:42:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CToZ6-00060s-Sd
	for sipping@megatron.ietf.org; Mon, 15 Nov 2004 16:39:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13199
	for <sipping@ietf.org>; Mon, 15 Nov 2004 16:39:10 -0500 (EST)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTob8-0002jU-DA
	for sipping@ietf.org; Mon, 15 Nov 2004 16:41:21 -0500
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1247); 
	Mon, 15 Nov 2004 13:38:36 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1247); 
	Mon, 15 Nov 2004 12:27:49 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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] comment on conference package
Date: Mon, 15 Nov 2004 12:27:48 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03AE1200@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] comment on conference package
Thread-Index: AcTHiG1fkTA9wUPrQO+INRNotSTikADyHs0A
From: "Orit Levin" <oritl@microsoft.com>
To: "Cullen Jennings" <fluffy@cisco.com>, "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 15 Nov 2004 20:27:49.0802 (UTC)
	FILETIME=[9357F0A0:01C4CB51]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable

Cullen,
Thanks a lot for reviewing the draft!

Yes, I will add this description to the document. (It appeared in one of
the presented examples in XCON).
I will also remove the whispers from the SIPPING Conference package (per
your previous comment and as I already posted on the XCON list).

Orit.=20

> -----Original Message-----
> From: sipping-bounces@ietf.org=20
> [mailto:sipping-bounces@ietf.org] On Behalf Of Cullen Jennings
> Sent: Wednesday, November 10, 2004 4:39 PM
> To: sipping
> Subject: [Sipping] comment on conference package
>=20
>=20
> The display-text field seems semantic free. I don't know what=20
> goes in here, how I can use it, or how it gets set. I asked a=20
> few different people and got a few different answers.
>=20
> Alan gave one that I thought sounded like a good idea. I=20
> think he suggested that it was text to display in the roster=20
> and it was set by a non SIP means such as a profile that the=20
> user had on the conferencing system.
>=20
> Cullen
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP=20
> 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


From sipping-bounces@ietf.org  Mon Nov 15 20:58:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06914
	for <sipping-web-archive@ietf.org>; Mon, 15 Nov 2004 20:58:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTse2-0008RO-Va
	for sipping-web-archive@ietf.org; Mon, 15 Nov 2004 21:00:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTsas-0002O8-5t; Mon, 15 Nov 2004 20:57:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTsXP-0001zR-Ci
	for sipping@megatron.ietf.org; Mon, 15 Nov 2004 20:53:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06578
	for <sipping@ietf.org>; Mon, 15 Nov 2004 20:53:41 -0500 (EST)
Received: from pmesmtp01.wcom.com ([199.249.20.1] helo=pmesmtp01.mci.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTsZW-0008LO-14
	for sipping@ietf.org; Mon, 15 Nov 2004 20:55:54 -0500
Received: from pmismtp03.mcilink.com ([166.38.62.38])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I790043A18MJJ@firewall.mci.com> for sipping@ietf.org;
	Tue, 16 Nov 2004 01:53:10 +0000 (GMT)
Received: from pmismtp03.mcilink.com by pmismtp03.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I790050118LNH@pmismtp03.mcilink.com>; Tue,
	16 Nov 2004 01:53:09 +0000 (GMT)
Received: from dgmexch09.wcomnet.com ([166.38.58.240])
	by pmismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I790049818LGY@pmismtp03.mcilink.com>; Tue,
	16 Nov 2004 01:53:09 +0000 (GMT)
Received: by DGMEXCH09.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <WYRJ3614>; Tue, 16 Nov 2004 01:59:49 +0000
Content-return: allowed
Date: Tue, 16 Nov 2004 01:53:08 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
To: "'Miguel Garcia'" <Miguel.An.Garcia@nokia.com>,
        Orit Levin <oritl@microsoft.com>
Message-id: <EB7597BFB1C65844898A6D153DE09DB5089533@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] RE: Comments to cc-conferencing-05 (WGLC)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f

Miguel,

Thanks for your detailed comments.  We will make the corrections and changes
you suggested.  A few comments are below in your snipped comments.

Thanks,
Alan Johnston
MCI
sip:alan@sipstation.com

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com] 
> Sent: Thursday, November 04, 2004 6:21 AM
> To: Johnston, Alan; Orit Levin
> Cc: sipping
> Subject: Comments to cc-conferencing-05 (WGLC)
> 
> 
> Alan, Orit (and SIPPING):
> 
> I have some comments to 
> draft-ietf-sipping-cc-conferencing-05.txt. They 
> are mostly nits. I hope you can take them into account.
> 

<snip>

> - Also Section 3.1 reads in the third paragraph:
> 
>    "A focus SHOULD support the Replaces [8] header field."
> 
> At this stage, since the usage of the Replaces headers have not been 
> introduced, it would be good to have some motivation 
> introductory text, 
> something like:
> 
>     "In order to support advanced features, where a session 
> established 
> between two endpoints can migrate to a centralized 
> conference, a focus 
> SHOULD support the Replaces [8] header field."
> 
> - And more on section 3.1:
> 
> I also think we need some text in this section regarding the 
> support of 
> the Join header and the GRUU in the focus.
> 
> - Question on section 3.4:
> 
> Should the conference-aware UA support the replaces, join and GRUU? I 
> guess it should be strongly recommended to implement it 
> (perhaps a MUST).

While I think it is an excellent idea for any UA to support replaces, join,
and GRUU, a MUST level would imply interoperability failures if they didn't
support, which isn't true.

> 
> - Section 4, Call flows, General.
> 
> I think all the Supported headers should always contain: 
> join, replaces, 
> gruu. There are some of them that do not contain 'join',  others not 
> even gruu.

I will double check, but I think only non-focus UAs occasionally do not
support join and GRUU, which is acceptable.

<snip> 

> - Section 4.2
> 
> I think the payloads in NOTIFYes F7 and F9 are exchanged 
> somehow. Alice is already a participant of the conference, so 
> her NOTIFY F9 can 
> be contain a partial information. Carol's NOTIFY F7 is the 
> first NOTIFY 
> she receives, so it should contain a full event package.
> 

Agreed.

> However, F7 contains a <conference-state> with version="0" and 
> state="full",

This is exactly what you say in your previous statement, right?

 when it should be version="1" (or other number) and 
> state="partial".
> 
> F9 contains the correct version="0", but the state="partial", when it 
> should be "full".

No, F9 is sent to Alice, so it is partial, just as you say above.  Do I have
this wrong somehow?

> 
> - Section 4.2, Changing User Agents within a Conference
> 

You mean, section 4.2, right?

> This is an interested case, but certainly there is nothing 
> peculiar to 
> the conferencing. In other words, this will be applicable to the 
> one-to-one session. So if there is something remarkable when we apply 
> this case to the conferencing framework, please explain. Otherwise, I 
> don't know what is the value of this use case.

This is the use case for why the focus SHOULD support Replaces.  I will add
text earlier referring to this example to make this clear.

 
<snip>

> 
> 
> Best regards,
> 
>         Miguel
> 
> 
> -- 
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Research Center      Helsinki, Finland
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 16 02:15:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22703
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 02:15:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTxar-0005iR-PL
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 02:17:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTxXK-00069t-Cm; Tue, 16 Nov 2004 02:13:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTxWD-0005ib-Cp
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 02:12:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20497
	for <sipping@ietf.org>; Tue, 16 Nov 2004 02:12:48 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTxYN-0005fv-3s
	for sipping@ietf.org; Tue, 16 Nov 2004 02:15:03 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 15 Nov 2004 23:27:12 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAG7C73O015992;
	Mon, 15 Nov 2004 23:12:08 -0800 (PST)
Received: from [192.168.1.100] (sjc-vpn4-1387.cisco.com [10.21.85.106])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFT52561;
	Mon, 15 Nov 2004 23:12:13 -0800 (PST)
Message-ID: <4199A84D.4070904@cisco.com>
Date: Tue, 16 Nov 2004 02:12:13 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brijesh Kumar <kumarb@research.panasonic.com>
Subject: Re: [Sipping] device-info-01
References: <5b36958c45.58c455b369@pintlmail.MITL.Research.Panasonic.COM>
	<41941B7F.7070204@cisco.com>
	<005401c4c8da$8e3796d0$5501a996@KUMARW2>
In-Reply-To: <005401c4c8da$8e3796d0$5501a996@KUMARW2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
        Mahfuz Rahman <mahfuz@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

inline.

Brijesh Kumar wrote:

> ----- Original Message ----- From: "Paul Kyzivat" <pkyzivat@cisco.com>
> 
>> I have a sense that you have a concept that the sender will be making 
>> the decisions about what should be done to the receiver, while the 
>> popular presence viewpoint is that the presentity makes those 
>> decisions and announces availability at a higher level of abstraction.
>>
>> It would perhaps be helpful if you would be more explicit about the 
>> use cases you are trying to enable.
> 
> 
> We are adding a section that will describe use cases in more details in the
> next revision. A number of use cases are lready being discussed in Open
> Mobile Alliance (OMA), and Dean who goes to OMA is aware those use 
> cases. Some of these cases may be discussed in our revision.

"Some" and "may"??

The purpose of the sipping working group is to discuss problems and 
applications of sip. If you cannot discuss the problems and use cases 
that motivate a piece of work, I don't see how it can reasonably be 
discussed or developed.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Tue Nov 16 02:26:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26578
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 02:26:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTxlM-0005zH-Uh
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 02:28:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTxi2-0001rh-Ov; Tue, 16 Nov 2004 02:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTxgo-0001IB-M2
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 02:23:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26260
	for <sipping@ietf.org>; Tue, 16 Nov 2004 02:23:45 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTxiy-0005w4-Gp
	for sipping@ietf.org; Tue, 16 Nov 2004 02:26:00 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 15 Nov 2004 23:23:48 -0800
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id iAG7NCYr014767;
	Mon, 15 Nov 2004 23:23:12 -0800 (PST)
Received: from [192.168.1.100] (sjc-vpn4-1387.cisco.com [10.21.85.106])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFT52927;
	Mon, 15 Nov 2004 23:23:10 -0800 (PST)
Message-ID: <4199AADE.70101@cisco.com>
Date: Tue, 16 Nov 2004 02:23:10 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aki Niemi <aki.niemi@nokia.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
	<4193D48C.1030700@cisco.com> <4193DF03.8020903@nokia.com>
In-Reply-To: <4193DF03.8020903@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, aspen@nortelnetworks.com,
        Alan Johnston <alan.johnston@mci.com>, David R Oran <oran@cisco.com>,
        alan@telchemy.com, sipping@ietf.org,
        Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit

inline.

Aki Niemi wrote:

>>>
>>> If the server (not proxy, necessarily...) doesn't want them, it can 
>>> send an error. 
>>
>>
>>
>> Which error? Section 5 of RFC 3903 does not point out a condition 
>> which means,
>> "don't publish to this aor any more".
> 
> 
> Perhaps there is nothing specific to PUBLISH here. So either 488 or 606 
> might work?

I don't think so.

There is a PUBLISH-specific semantic you need here - namely, "please 
stop sending future PUBLISH requests for this resource and event package 
  until you are notified through other means that it is supported". 
PUBLISH would normally be resent periodically to refresh the soft-state, 
and you want to turn of those refreshes. No response code does that 
generally, afaik.


>>
>> I don't follow why its a bad precedent here and not everywhere else; 
>> PUBLISH is fundamentally about an unsolicited push of data to a 
>> collector. If doing that is bad, then PUBLISH is bad.
> 
> 
> Yeah, but there is explicit text in the RFC that says it isn't a generic 
> transport of arbitrary data, but of event state. However, that is 
> clearly a statement that is open to interpretation.

If you think that the performance data is a reasonable thing to turn 
into an event package, then PUBLISH usage with it is reasonable. The 
current draft posits and event package.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.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 sipping-bounces@ietf.org  Tue Nov 16 02:51:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00068
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 02:51:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTy9h-0006WG-Sw
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 02:53:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTy6U-0006Bt-UK; Tue, 16 Nov 2004 02:50:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTy2H-0005j2-4P
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 02:45:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29490
	for <sipping@ietf.org>; Tue, 16 Nov 2004 02:45:56 -0500 (EST)
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTy4Q-0006Px-MO
	for sipping@ietf.org; Tue, 16 Nov 2004 02:48:11 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAG7jR207965; Tue, 16 Nov 2004 09:45:28 +0200 (EET)
X-Scanned: Tue, 16 Nov 2004 09:46:53 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iAG7krpT006634;
	Tue, 16 Nov 2004 09:46:53 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 0088AVfI; Tue, 16 Nov 2004 09:46:53 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAG7ihS19245; Tue, 16 Nov 2004 09:44:43 +0200 (EET)
Received: from [172.21.34.165] ([172.21.34.165]) by esebh003.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 16 Nov 2004 09:44:33 +0200
Message-ID: <4199AFE1.1030203@nokia.com>
Date: Tue, 16 Nov 2004 02:44:33 -0500
From: Aki Niemi <aki.niemi@nokia.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ext Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>
	<4193D48C.1030700@cisco.com> <4193DF03.8020903@nokia.com>
	<4199AADE.70101@cisco.com>
In-Reply-To: <4199AADE.70101@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Nov 2004 07:44:33.0853 (UTC)
	FILETIME=[1D3E6ED0:01C4CBB0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, aspen@nortelnetworks.com,
        Alan Johnston <alan.johnston@mci.com>, David R Oran <oran@cisco.com>,
        alan@telchemy.com, sipping@ietf.org,
        Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

Inline.

ext Jonathan Rosenberg wrote:
>> Perhaps there is nothing specific to PUBLISH here. So either 488 or 
>> 606 might work?
> 
> 
> I don't think so.
> 
> There is a PUBLISH-specific semantic you need here - namely, "please 
> stop sending future PUBLISH requests for this resource and event package 
>  until you are notified through other means that it is supported". 
> PUBLISH would normally be resent periodically to refresh the soft-state, 
> and you want to turn of those refreshes. No response code does that 
> generally, afaik.

The composer could return a really long Expires value. That would quench 
the refreshes for the next 100 years or so. ;)

This is one of the things lacking specification in the draft. To me, 
expiry for the reports seems meaningless, and so does refreshing them. 
Also, will they ever need to be modified or removed? I don't think so, 
but again the draft doesn't (AFAIK) talk about this.

Cheers,
Aki

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 16 06:27:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16754
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 06:27:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU1Wv-0002cD-MU
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 06:29:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU1OO-0001S2-B4; Tue, 16 Nov 2004 06:21:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU1MG-0000S3-Ss
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 06:18:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15946
	for <sipping@ietf.org>; Tue, 16 Nov 2004 06:18:46 -0500 (EST)
Received: from [151.11.171.221] (helo=ict-srv-01.ictc.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU1OI-0002P7-Gm
	for sipping@ietf.org; Tue, 16 Nov 2004 06:21:05 -0500
Received: by mail.ictc.it with Internet Mail Service (5.5.2657.72)
	id <VMPD5JG6>; Tue, 16 Nov 2004 12:18:05 +0100
Message-ID: <2428672A00A1D411A4CC00D0B7C9F506A86B47@mail.ictc.it>
From: Antonio Corghi <corghi@ictc.it>
To: sipping@ietf.org
Date: Tue, 16 Nov 2004 12:18:04 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Sipping] SIP gateway between PSTN and IP network
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

Hello Everyone,

I'm trying to understand what should be the right call flow for a SIP
gateway between PSTN and IP networks. 
According to RFC3666, upon receiving the IAM message (let's suppose having
called party number +123456789), the SIP gateway should generate a SIP
Invite message whose "To" header field has the following syntax: 

sip:+123456789@abc.com;user=phone

where abc.com is known to be the domain of the outbound proxy used by the
SIP gateway to forward PSTN originated calls. 

But, if the gateway does know neither what's the domain of the outbound SIP
proxy (but only its IP address) nor what's the actual domain of the called
party, what's the right format of the To header field in the Invite message?
IHMO, two options are possible:

sip:+123456789@<IP_address_of_the SIP_outbound_proxy>;user=phone

or

tel:+123456789

Which one is better?

Thanks in advance
Bye,
	Antonio Corghi

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 16 07:28:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22778
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 07:28:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU2To-00043e-6P
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 07:30:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU2PS-0003St-Jr; Tue, 16 Nov 2004 07:26:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU2I9-000250-QP
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 07:18:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21861
	for <sipping@ietf.org>; Tue, 16 Nov 2004 07:18:37 -0500 (EST)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU2KL-0003o0-7O
	for sipping@ietf.org; Tue, 16 Nov 2004 07:20:54 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAGCITF17275; Tue, 16 Nov 2004 14:18:30 +0200 (EET)
X-Scanned: Tue, 16 Nov 2004 14:18:15 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iAGCIFFg026956;
	Tue, 16 Nov 2004 14:18:15 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00od7sYu; Tue, 16 Nov 2004 14:18:14 EET
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAGCIDa23853; Tue, 16 Nov 2004 14:18:13 +0200 (EET)
Received: from [172.21.39.152] ([172.21.39.152]) by esebh003.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 16 Nov 2004 14:17:43 +0200
Message-ID: <4199EFE6.10202@nokia.com>
Date: Tue, 16 Nov 2004 14:17:42 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Johnston, Alan" <Alan.Johnston@mci.com>
References: <EB7597BFB1C65844898A6D153DE09DB5089533@DGEXCH02.mcilink.com>
In-Reply-To: <EB7597BFB1C65844898A6D153DE09DB5089533@DGEXCH02.mcilink.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Nov 2004 12:17:43.0250 (UTC)
	FILETIME=[4615F320:01C4CBD6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>, sipping <sipping@ietf.org>
Subject: [Sipping] Re: Comments to cc-conferencing-05 (WGLC)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit

Hi Alan:

Thanks for your reply. I am just reducing the text to these points that 
need further discussion.



Johnston, Alan wrote:

> Miguel,
> 
> Thanks for your detailed comments.  We will make the corrections and changes
> you suggested.  A few comments are below in your snipped comments.
> 
> Thanks,
> Alan Johnston
> MCI
> sip:alan@sipstation.com
> 
> 
>>-----Original Message-----
>>From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com] 
>>Sent: Thursday, November 04, 2004 6:21 AM
>>To: Johnston, Alan; Orit Levin
>>Cc: sipping
>>Subject: Comments to cc-conferencing-05 (WGLC)
>>
>>
>>Alan, Orit (and SIPPING):
>>
>>I have some comments to 
>>draft-ietf-sipping-cc-conferencing-05.txt. They 
>>are mostly nits. I hope you can take them into account.
>>
> 
> 

> 
> 
>>- Section 4.2
>>
>>I think the payloads in NOTIFYes F7 and F9 are exchanged 
>>somehow. Alice is already a participant of the conference, so 
>>her NOTIFY F9 can 
>>be contain a partial information. Carol's NOTIFY F7 is the 
>>first NOTIFY 
>>she receives, so it should contain a full event package.
>>
> 
> 
> Agreed.
> 
> 
>>However, F7 contains a <conference-state> with version="0" and 
>>state="full",
> 
> 
> This is exactly what you say in your previous statement, right?
> 
>  when it should be version="1" (or other number) and 
> 
>>state="partial".
>>
>>F9 contains the correct version="0", but the state="partial", when it 
>>should be "full".
> 
> 
> No, F9 is sent to Alice, so it is partial, just as you say above.  Do I have
> this wrong somehow?
> 

Ok, I reviewed again the flow and it is correct. So, forget about my 
initial comments, and my apology for the possible waste of time created. 
The flow is correct as is.


> 
>>- Section 4.2, Changing User Agents within a Conference
>>
> 
> 
> You mean, section 4.2, right?

4.9, I meant 4.9, "Chaging User Agents within a Conference".


> 
>>This is an interested case, but certainly there is nothing 
>>peculiar to 
>>the conferencing. In other words, this will be applicable to the 
>>one-to-one session. So if there is something remarkable when we apply 
>>this case to the conferencing framework, please explain. Otherwise, I 
>>don't know what is the value of this use case.
> 
> 
> This is the use case for why the focus SHOULD support Replaces.  I will add
> text earlier referring to this example to make this clear.

OK to me.

Regards,

         Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 16 09:35:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02625
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 09:35:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU4SR-0006jQ-Ei
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 09:37:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU4JT-0003hK-LM; Tue, 16 Nov 2004 09:28:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4Eo-0002tz-CC
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 09:23:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02001
	for <sipping@ietf.org>; Tue, 16 Nov 2004 09:23:17 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4H2-0006Wp-2F
	for sipping@ietf.org; Tue, 16 Nov 2004 09:25:36 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 16 Nov 2004 09:22:48 -0500
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAGEMVWh024635; 
	Tue, 16 Nov 2004 09:22:44 -0500 (EST)
Received: from cisco.com ([161.44.79.125]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id ANB47324; Tue, 16 Nov 2004 09:22:30 -0500 (EST)
Message-ID: <419A0D26.1010900@cisco.com>
Date: Tue, 16 Nov 2004 09:22:30 -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@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>	<4193D48C.1030700@cisco.com>
	<4193DF03.8020903@nokia.com> <4199AADE.70101@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, Aki Niemi <aki.niemi@nokia.com>,
        alan@telchemy.com, Alan Johnston <alan.johnston@mci.com>,
        sipping@ietf.org, aspen@nortelnetworks.com,
        David R Oran <oran@cisco.com>,
        Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit



Jonathan Rosenberg wrote:
> inline.
> 
> Aki Niemi wrote:
> 
>>>>
>>>> If the server (not proxy, necessarily...) doesn't want them, it can 
>>>> send an error. 
>>>
>>> Which error? Section 5 of RFC 3903 does not point out a condition 
>>> which means,
>>> "don't publish to this aor any more".
>>
>> Perhaps there is nothing specific to PUBLISH here. So either 488 or 
>> 606 might work?
> 
> I don't think so.
> 
> There is a PUBLISH-specific semantic you need here - namely, "please 
> stop sending future PUBLISH requests for this resource and event package 
>  until you are notified through other means that it is supported". 
> PUBLISH would normally be resent periodically to refresh the soft-state, 
> and you want to turn of those refreshes. No response code does that 
> generally, afaik.

A 603 may be appropriate.

Or how about a 480 with an extremely large (e.g. many years) Retry-After 
time? The semantics aren't quite right, but the effect should be.

I am somewhat concerned that the level of detail in our error codes may 
be too high, so that we are constantly having to assign new ones from a 
limited namespace.

	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 sipping-bounces@ietf.org  Tue Nov 16 11:26:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15260
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 11:26:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU6Bs-00014I-QS
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 11:28:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU628-0003Bv-0N; Tue, 16 Nov 2004 11:18:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU5wK-0001wm-C5
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 11:12:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14017
	for <sipping@ietf.org>; Tue, 16 Nov 2004 11:12:18 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU5yY-0000kr-Bg
	for sipping@ietf.org; Tue, 16 Nov 2004 11:14:39 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with SMTP id iAGGBbnK005998;
	Tue, 16 Nov 2004 11:11:37 -0500
Received: from localhost (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with SMTP id 3B6CF3C8158;
	Tue, 16 Nov 2004 11:09:39 -0500 (EST)
Received: from Brijesh2K (dhcp251.Research.Panasonic.COM [150.169.1.251])by 
	redwood.research.panasonic.com (Postfix) with SMTP id 375463C8155;
	Tue, 16 Nov 2004 11:09:31 -0500 (EST)
From: "Brijesh Kumar" <kumarb@research.panasonic.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
Subject: RE: [Sipping] device-info-01
Date: Tue, 16 Nov 2004 11:15:19 -0500
Message-ID: <NBEBKGCOLIBFGNGLINKHMELDDFAA.kumarb@research.panasonic.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)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-reply-to: <4199A84D.4070904@cisco.com>
Importance: Normal
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:21 M:1 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
        Mahfuz Rahman <mahfuz@research.panasonic.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@cisco.com]
> ----- Original Message ----- From: "Paul Kyzivat" <pkyzivat@cisco.com>
 
> > We are adding a section that will describe use cases in more 
> details in the
> > next revision. Some of these cases may be discussed in our revision.
> 
> "Some" and "may"??
> 
> The purpose of the sipping working group is to discuss problems and 
> applications of sip. If you cannot discuss the problems and use cases 
> that motivate a piece of work, I don't see how it can reasonably be 
> discussed or developed.
 
Jonathan:

We have a large number of use cases - most of these involve a 
mobile device  getting the current operational state of a peer device 
and then using that information to make a decision as to when, where, 
which and how to transfer media streams to other sip enabled mobile 
multi-media devices. And, also there are other call center related
use cases. We can't include every thing in a draft.

Cheers,

--brijesh




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 16 20:02:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18275
	for <sipping-web-archive@ietf.org>; Tue, 16 Nov 2004 20:02:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUEGB-0000vh-Rb
	for sipping-web-archive@ietf.org; Tue, 16 Nov 2004 20:05:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUEC7-0004Sx-LA; Tue, 16 Nov 2004 20:01:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUE6z-0003Sf-6R
	for sipping@megatron.ietf.org; Tue, 16 Nov 2004 19:55:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17463
	for <sipping@ietf.org>; Tue, 16 Nov 2004 19:55:52 -0500 (EST)
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUE9J-0000is-4R
	for sipping@ietf.org; Tue, 16 Nov 2004 19:58:17 -0500
Received: from stntimc1.va.neustar.com (stntimc1.neustar.com [10.31.13.11])
	by oak.neustar.com (8.12.8/8.11.0) with ESMTP id iAH0tL10006236;
	Wed, 17 Nov 2004 00:55:21 GMT
Received: by stntimc1.cis.neustar.com with Internet Mail Service (5.5.2657.72)
	id <T32L8LDM>; Tue, 16 Nov 2004 19:55:21 -0500
Message-ID: <7927C67249E4AD43BC05B539AF0D129801AF4381@stntexch04.cis.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Antonio Corghi'" <corghi@ictc.it>, sipping@ietf.org
Subject: RE: [Sipping] SIP gateway between PSTN and IP network
Date: Tue, 16 Nov 2004 19:55:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4


See RFC3824 (which explains how to use telephone numbers in SIP, and what a
SIP UA should do when confronted with a telephone number). The guidance
given in RFC3666 is good advice, but in cases where the advice cannot be
followed for various reasons, there are alternatives described in RFC3824.

In your case, I think it would be appropriate to create a tel URI and
forward the request to the known IP address of the outbound SIP proxy
server.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Antonio Corghi [mailto:corghi@ictc.it]
> Sent: Tuesday, November 16, 2004 3:18 AM
> To: sipping@ietf.org
> Subject: [Sipping] SIP gateway between PSTN and IP network
> 
> 
> Hello Everyone,
> 
> I'm trying to understand what should be the right call flow for a SIP
> gateway between PSTN and IP networks. 
> According to RFC3666, upon receiving the IAM message (let's 
> suppose having
> called party number +123456789), the SIP gateway should generate a SIP
> Invite message whose "To" header field has the following syntax: 
> 
> sip:+123456789@abc.com;user=phone
> 
> where abc.com is known to be the domain of the outbound proxy 
> used by the
> SIP gateway to forward PSTN originated calls. 
> 
> But, if the gateway does know neither what's the domain of 
> the outbound SIP
> proxy (but only its IP address) nor what's the actual domain 
> of the called
> party, what's the right format of the To header field in the 
> Invite message?
> IHMO, two options are possible:
> 
> sip:+123456789@<IP_address_of_the SIP_outbound_proxy>;user=phone
> 
> or
> 
> tel:+123456789
> 
> Which one is better?
> 
> Thanks in advance
> Bye,
> 	Antonio Corghi
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 17 07:10:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19253
	for <sipping-web-archive@ietf.org>; Wed, 17 Nov 2004 07:10:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUOgK-0007JN-GE
	for sipping-web-archive@ietf.org; Wed, 17 Nov 2004 07:13:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUOai-0001DI-5U; Wed, 17 Nov 2004 07:07:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUOXL-0000gQ-4l
	for sipping@megatron.ietf.org; Wed, 17 Nov 2004 07:03:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18579
	for <sipping@ietf.org>; Wed, 17 Nov 2004 07:03:44 -0500 (EST)
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUOZj-0007AC-57
	for sipping@ietf.org; Wed, 17 Nov 2004 07:06:16 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAHC3QE09505; Wed, 17 Nov 2004 14:03:27 +0200 (EET)
X-Scanned: Wed, 17 Nov 2004 14:04:48 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iAHC4mPI008752;
	Wed, 17 Nov 2004 14:04:48 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00DlAhs7; Wed, 17 Nov 2004 14:04:47 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAHBo5a27596; Wed, 17 Nov 2004 13:50:05 +0200 (EET)
Received: from [172.21.38.168] ([172.21.38.168]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 17 Nov 2004 13:49:54 +0200
Message-ID: <419B3AE1.30103@nokia.com>
Date: Wed, 17 Nov 2004 13:49:53 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>,
        Orit Levin <oritl@microsoft.com>, sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Nov 2004 11:49:54.0582 (UTC)
	FILETIME=[8DE52B60:01C4CC9B]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
Subject: [Sipping] URIs in conference event package.
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Content-Transfer-Encoding: 7bit

On reviewing the conference event package, I found several places where 
URIs try to represent different aspects of the conference.

Specifically, the current event package defines these three types of 
URIs within the <conference-description> element:

<web-page>
<conf-uris>
<service-uris>

The <web-page> element is clear, it is just a displayable web page URI. 
The <conf-uris> is also clear, is just a URI where a participant can 
join the conference.
The <service-uris> is tricky. It pretends to be a URI that gives you 
access to other "things", such as CPCP, or MPCP, or access rules. 
However, there are no semantics associated with this element, so the 
software can only display this information to the user, and let him take 
an action about that URI.

I think this can be improved by having some automatic way of indicating 
to the software what is the purpose of a URI. Also, I think we can group 
all these URIs in a single element that contains a number of entries. 
The idea: a single <uris> element that includes one or more <entry> 
elements, which include a <uri> and a new <purpose> elements that 
indicate what is the purpose of that URI. The <purpose> element contains 
a token, such as "conference" (the actual conference uri), "information" 
(e.g., web page), "cpcp" (uri to do cpcp), "mpcp" (uri to do mpcp), 
"conference-event" (the actual uri to subscribe to this package) , 
"floor-control", "sidebars" or any other token that is required.

If we follow this scheme, there is no need for 3 different elements 
anymore, just one. And we get a standardized <purpose> element, so the 
software can get the information of where to do the appropriate action 
(e.g., start a floor control session).

An example of my proposal, including a couple of conference uris (sip 
and tel URLs), a CPCP URI and a web page:

<conference-info entity="sips:conf233@example.com" state="partial" 
version="5" >
  <conference-description>
    <subject>Agenda: This month's target</subject>
    <uris>
      <entry>
        <uri>sip:conf34@conf.example.com</uri>
        <purpose>conference</purpose>
      </entry>

      <entry>
        <uri>tel:+1-555-7777</uri>
        <purpose>conference</purpose>
      </entry>

      <entry>
        <uri>http://salesgroup.example.com/policies/meeting.xml</uri>
        <purpose>cpcp</purpose>
      </entry>

      <entry>
        <uri>http://info.example.com/conf/conf32.html</uri>
        <purpose>information</purpose>
      </entry>
   </uris>
</conference-description>

In my opinion, this is elegant and precise. The only drawback is that 
this requires to open an IANA registration for values of the <purpose> 
elements of URIs, but I don't see a big issue with this. It also 
requires to allocate semantics to each of these tokens.

The relevant part of the XML schema will look like this:

      <!--
        CONFERENCE URI TYPE
      -->
      <xs:complexType name="uri-type">
        <xs:sequence>
           <xs:element name="uri" type="xs:anyURI"/>
           <xs:element name="label" type="xs:string" minOccurs="0"/>
           <xs:element name="purpose" type="xs:string"
                       maxOccurs="unbounded"/>
           <xs:element name="modified" type="execution-type"
                       minOccurs="0"/>
           <xs:element name="extended" type="extended-type" minOccurs="0"
                       maxOccurs="unbounded"/>
        </xs:sequence>
        <xs:anyAttribute/>
      </xs:complexType>


The draft will also need to open an IANA registry for the values of the 
<purpose> element in this XML document. The initial values could be:
- information: web page containing additional conference information
- cpcp: URL to do CPCP actions
- mpcp: URL to do MPCP actions (if MPCP requires URLs)
- floor-control: URL to initiate a floor-control session
- conference-event: not required, just for completeness. URL to 
subscribe to the conference event package of this conference.
- access-rules? Is this one needed

One thing, though: I first thought about using substitution groups in 
the XML schema, but due to the discussion in SIMPLE about how to create 
extensible tokens, I believe the IANA registry and a text string is what 
we are looking for. But we should apply the same output as in SIMPLE 
documents.

But in essence, what is the feeling of the working group about this 
proposal?

Regards,

           Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 17 14:59:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05758
	for <sipping-web-archive@ietf.org>; Wed, 17 Nov 2004 14:59:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUW0L-0001tU-Ov
	for sipping-web-archive@ietf.org; Wed, 17 Nov 2004 15:02:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUVpQ-0003Fp-CH; Wed, 17 Nov 2004 14:50:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUVhV-0001UH-O3
	for sipping@megatron.ietf.org; Wed, 17 Nov 2004 14:42:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04529
	for <sipping@ietf.org>; Wed, 17 Nov 2004 14:42:44 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUVjy-0001Vb-Rb
	for sipping@ietf.org; Wed, 17 Nov 2004 14:45:19 -0500
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 17 Nov 2004 11:42:14 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1247); 
	Wed, 17 Nov 2004 11:42:11 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Nov 2004 11:42:14 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03B26925@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: URIs in conference event package.
Thread-Index: AcTMnXzkQic9SPiJTpWK+2y5IxzhJgAP0KKg
From: "Orit Levin" <oritl@microsoft.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>,
        "Jonathan Rosenberg" <jdrosen@cisco.com>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 17 Nov 2004 19:42:11.0864 (UTC)
	FILETIME=[883B4180:01C4CCDD]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] RE: URIs in conference event package.
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Content-Transfer-Encoding: quoted-printable

I think that it is a good proposal.

One comment: among other comments that I received, I am planning to
remove the <web-page> element and instead to add a text suggesting that
the "web-page" case falls under one of the <service-uris> with value to
be registered with IANA: "web-page".

Orit.=20

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]=20
> Sent: Wednesday, November 17, 2004 3:50 AM
> To: Jonathan Rosenberg; Henning Schulzrinne; Orit Levin; sipping
> Subject: URIs in conference event package.
>=20
> On reviewing the conference event package, I found several=20
> places where URIs try to represent different aspects of the=20
> conference.
>=20
> Specifically, the current event package defines these three=20
> types of URIs within the <conference-description> element:
>=20
> <web-page>
> <conf-uris>
> <service-uris>
>=20
> The <web-page> element is clear, it is just a displayable web=20
> page URI.=20
> The <conf-uris> is also clear, is just a URI where a=20
> participant can join the conference.
> The <service-uris> is tricky. It pretends to be a URI that=20
> gives you access to other "things", such as CPCP, or MPCP, or=20
> access rules.=20
> However, there are no semantics associated with this element,=20
> so the software can only display this information to the=20
> user, and let him take an action about that URI.
>=20
> I think this can be improved by having some automatic way of=20
> indicating to the software what is the purpose of a URI.=20
> Also, I think we can group all these URIs in a single element=20
> that contains a number of entries.=20
> The idea: a single <uris> element that includes one or more=20
> <entry> elements, which include a <uri> and a new <purpose>=20
> elements that indicate what is the purpose of that URI. The=20
> <purpose> element contains a token, such as "conference" (the=20
> actual conference uri), "information"=20
> (e.g., web page), "cpcp" (uri to do cpcp), "mpcp" (uri to do=20
> mpcp), "conference-event" (the actual uri to subscribe to=20
> this package) , "floor-control", "sidebars" or any other=20
> token that is required.
>=20
> If we follow this scheme, there is no need for 3 different=20
> elements anymore, just one. And we get a standardized=20
> <purpose> element, so the software can get the information of=20
> where to do the appropriate action (e.g., start a floor=20
> control session).
>=20
> An example of my proposal, including a couple of conference=20
> uris (sip and tel URLs), a CPCP URI and a web page:
>=20
> <conference-info entity=3D"sips:conf233@example.com" state=3D"partial" =

> version=3D"5" >
>   <conference-description>
>     <subject>Agenda: This month's target</subject>
>     <uris>
>       <entry>
>         <uri>sip:conf34@conf.example.com</uri>
>         <purpose>conference</purpose>
>       </entry>
>=20
>       <entry>
>         <uri>tel:+1-555-7777</uri>
>         <purpose>conference</purpose>
>       </entry>
>=20
>       <entry>
>         <uri>http://salesgroup.example.com/policies/meeting.xml</uri>
>         <purpose>cpcp</purpose>
>       </entry>
>=20
>       <entry>
>         <uri>http://info.example.com/conf/conf32.html</uri>
>         <purpose>information</purpose>
>       </entry>
>    </uris>
> </conference-description>
>=20
> In my opinion, this is elegant and precise. The only drawback=20
> is that this requires to open an IANA registration for values=20
> of the <purpose> elements of URIs, but I don't see a big=20
> issue with this. It also requires to allocate semantics to=20
> each of these tokens.
>=20
> The relevant part of the XML schema will look like this:
>=20
>       <!--
>         CONFERENCE URI TYPE
>       -->
>       <xs:complexType name=3D"uri-type">
>         <xs:sequence>
>            <xs:element name=3D"uri" type=3D"xs:anyURI"/>
>            <xs:element name=3D"label" type=3D"xs:string" =
minOccurs=3D"0"/>
>            <xs:element name=3D"purpose" type=3D"xs:string"
>                        maxOccurs=3D"unbounded"/>
>            <xs:element name=3D"modified" type=3D"execution-type"
>                        minOccurs=3D"0"/>
>            <xs:element name=3D"extended" type=3D"extended-type"=20
> minOccurs=3D"0"
>                        maxOccurs=3D"unbounded"/>
>         </xs:sequence>
>         <xs:anyAttribute/>
>       </xs:complexType>
>=20
>=20
> The draft will also need to open an IANA registry for the=20
> values of the <purpose> element in this XML document. The=20
> initial values could be:
> - information: web page containing additional conference information
> - cpcp: URL to do CPCP actions
> - mpcp: URL to do MPCP actions (if MPCP requires URLs)
> - floor-control: URL to initiate a floor-control session
> - conference-event: not required, just for completeness. URL=20
> to subscribe to the conference event package of this conference.
> - access-rules? Is this one needed
>=20
> One thing, though: I first thought about using substitution=20
> groups in the XML schema, but due to the discussion in SIMPLE=20
> about how to create extensible tokens, I believe the IANA=20
> registry and a text string is what we are looking for. But we=20
> should apply the same output as in SIMPLE documents.
>=20
> But in essence, what is the feeling of the working group=20
> about this proposal?
>=20
> Regards,
>=20
>            Miguel
> --=20
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Research Center      Helsinki, Finland
>=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 sipping-bounces@ietf.org  Wed Nov 17 17:00:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23682
	for <sipping-web-archive@ietf.org>; Wed, 17 Nov 2004 17:00:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUXtn-0006x1-87
	for sipping-web-archive@ietf.org; Wed, 17 Nov 2004 17:03:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUXdQ-00041s-1j; Wed, 17 Nov 2004 16:46:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUXIo-0000Jc-LR
	for sipping@megatron.ietf.org; Wed, 17 Nov 2004 16:25:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18351
	for <sipping@ietf.org>; Wed, 17 Nov 2004 16:25:20 -0500 (EST)
Received: from omzesmtp02.mci.com ([199.249.17.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUXLF-0005P3-Pw
	for sipping@ietf.org; Wed, 17 Nov 2004 16:27:57 -0500
Received: from pmismtp01.mcilink.com ([166.38.62.36])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I7C00F7VDYDZ4@firewall.mci.com> for sipping@ietf.org;
	Wed, 17 Nov 2004 21:20:37 +0000 (GMT)
Received: from pmismtp01.mcilink.com by pmismtp01.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I7C00A01DYCET@pmismtp01.mcilink.com> for
	sipping@ietf.org; Wed, 17 Nov 2004 21:20:37 +0000 (GMT)
Received: from dgmexch09.wcomnet.com ([166.38.58.240])
	by pmismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I7C0091ODYCX2@pmismtp01.mcilink.com> for
	sipping@ietf.org; Wed, 17 Nov 2004 21:20:36 +0000 (GMT)
Received: by DGMEXCH09.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <WYRJ4PA4>; Wed, 17 Nov 2004 21:27:18 +0000
Content-return: allowed
Date: Wed, 17 Nov 2004 21:20:30 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <EB7597BFB1C65844898A6D153DE09DB508954B@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Subject: [Sipping] WGLC conferencing framework
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0345568102=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

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.

--===============0345568102==
Content-return: allowed
Content-type: multipart/alternative;
	boundary="Boundary_(ID_lEWbHQgMAST0X4UH5KXR+g)"

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.

--Boundary_(ID_lEWbHQgMAST0X4UH5KXR+g)
Content-type: text/plain; CHARSET=us-ascii


With the exception of some scope relate changes (which are still being
discussed among the sipping and xcon chairs and Allison, so I won't bring up
here), I think the conferencing framework document is ready to send to the
IESG.

This document is a significant contribution to the SIP community and should
be published as an RFC.

Thanks,
Alan Johnston
sip:alan@sipstation.com

--Boundary_(ID_lEWbHQgMAST0X4UH5KXR+g)
Content-type: text/html; CHARSET=us-ascii
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>WGLC conferencing framework</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>With the exception of some scope relate changes =
(which are still being discussed among the sipping and xcon chairs and =
Allison, so I won't bring up here), I think the conferencing framework =
document is ready to send to the IESG.</FONT></P>

<P><FONT SIZE=3D2>This document is a significant contribution to the =
SIP community and should be published as an RFC.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>Alan Johnston</FONT>
<BR><FONT SIZE=3D2>sip:alan@sipstation.com</FONT>
</P>

</BODY>
</HTML>=

--Boundary_(ID_lEWbHQgMAST0X4UH5KXR+g)--


--===============0345568102==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0345568102==--



From sipping-bounces@ietf.org  Thu Nov 18 22:26:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23682
	for <sipping-web-archive@ietf.org>; Thu, 18 Nov 2004 22:26:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUzSR-0007qU-69
	for sipping-web-archive@ietf.org; Thu, 18 Nov 2004 22:29:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUzJ9-00064B-0g; Thu, 18 Nov 2004 22:19:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUwS5-0002Nk-2Y
	for sipping@megatron.ietf.org; Thu, 18 Nov 2004 19:16:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08000
	for <sipping@ietf.org>; Thu, 18 Nov 2004 19:16:33 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUwUn-0003gv-Eo
	for sipping@ietf.org; Thu, 18 Nov 2004 19:19:25 -0500
Received: from [63.110.3.165] ([64.100.183.165]) (authenticated bits=0)
	by nylon.softarmor.com (8.12.11/8.12.11) with ESMTP id iAJ0H03K010135
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 18 Nov 2004 18:17:02 -0600
Message-ID: <419D3B52.6060701@softarmor.com>
Date: Thu, 18 Nov 2004 18:16:18 -0600
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
References: <4193B221.7070402@nostrum.com>	<AE0C4150-3416-11D9-865E-000A95C73842@cisco.com>	<4193D48C.1030700@cisco.com>	<4193DF03.8020903@nokia.com>
	<4199AADE.70101@cisco.com> <419A0D26.1010900@cisco.com>
In-Reply-To: <419A0D26.1010900@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 18 Nov 2004 22:19:33 -0500
Cc: Adam Roach <adam@nostrum.com>, Aki Niemi <aki.niemi@nokia.com>,
        alan@telchemy.com, Alan Johnston <alan.johnston@mci.com>,
        David R Oran <oran@cisco.com>, aspen@nortelnetworks.com,
        sipping@ietf.org, Henry Sinnreich <Henry.Sinnreich@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Paul Kyzivat wrote:

>
> A 603 may be appropriate.
>
> Or how about a 480 with an extremely large (e.g. many years) 
> Retry-After time? The semantics aren't quite right, but the effect 
> should be.
>
> I am somewhat concerned that the level of detail in our error codes 
> may be too high, so that we are constantly having to assign new ones 
> from a limited namespace.
>
Aren't we saying "I am disallowing your PUBLISH request at this time. 
Don't bother me again unless you have reason to think the situation has 
changed."

How is that different from 405 "The method specified in the Request-Line 
is understood, but not allowed for the address identified by the 
Request-URI.".

--
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 sipping-bounces@ietf.org  Fri Nov 19 12:24:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23435
	for <sipping-web-archive@ietf.org>; Fri, 19 Nov 2004 12:24:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CVCXO-0001Yp-K5
	for sipping-web-archive@ietf.org; Fri, 19 Nov 2004 12:27:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CVCSb-0007xR-Vn; Fri, 19 Nov 2004 12:22:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CVCIr-0003Yb-0d
	for sipping@megatron.ietf.org; Fri, 19 Nov 2004 12:12:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22154
	for <sipping@ietf.org>; Fri, 19 Nov 2004 12:12:06 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVCLi-0001Cv-I8
	for sipping@ietf.org; Fri, 19 Nov 2004 12:15:07 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAJHBZV21045; Fri, 19 Nov 2004 12:11:35 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4TSSQ>; Fri, 19 Nov 2004 12:11:36 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB053124CF@zrc2hxm1.corp.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: Kumiko Ono <Ono.Kumiko@lab.ntt.co.jp>, tachimoto.shinya@lab.ntt.co.jp,
        sipping <sipping@ietf.org>
Subject: RE: [Sipping] WGLC: e2m security requirements
Date: Fri, 19 Nov 2004 12:11:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1170475184=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1f9797ba297220533cb8c3f4bc709a8

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.

--===============1170475184==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4CE5A.CF44347F"

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_01C4CE5A.CF44347F
Content-Type: text/plain

Summary:
--------
I think the draft is ready to forward to the IESG for review with the
correction and clarification of the following items.

Editorial nits:
---------------

- Section 1: Last paragraph, 1st sentence.  Change "...those that provides
services..." to "...those that provide services..."

- Section 4.2: REQ-CONF-1: Change "The solution MUST be enable an encrypted
data..." to
"The solution MUST enable encrypted data..." or perhaps even better would be
"The solution MUST allow encrypted data..."

- Section 4.2: REQ-CONF-4 is unclear to me:   
 "It MAY allow a UA to request that the recipient UA
  disclose information to the proxy server, which
  requesting UA is disclosing the information to."

I think you're saying that a UA MAY request that the UA that is receiving
the information should provide that information to the proxy server which
the requesting UA trusts to have that information in the first place,
provided of course that the proxy server's policies allow it to receive the
information from that UA (based on service provider policies).  

So, I would propose changing that to something like (provided I've properly
understood this requirement):
 "It MAY allow a UA to request that the recipient UA
  disclose information to the proxy server, to which the
  requesting UA is initially disclosing information."

- Section 4.2: paragraph just below REQ-CONF-4.  Change "...does not permit
to reveal the security policies..." to "...does not permit revealing the
security policies..."

- Section 5: 2nd paragraph. Fix typo in "...needs protection pagainst replay
attack." 

- Appendix A: Should likely have a note to RFC Editor to remove this section
when doc is published.  Also, would facilitate things for this to not be
listed in the Table of Contents. 

Regards,
Mary H. Barnes
mary.barnes@nortelnetworks.com


-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of Gonzalo Camarillo
Sent: Monday, October 18, 2004 11:40 PM
To: sipping
Cc: tachimoto.shinya@lab.ntt.co.jp; Rohan Mahy; Kumiko Ono; Dean Willis
Subject: [Sipping] WGLC: e2m security requirements


Folks,

we would like to working group last call the following draft:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-reqs-04.txt

This WGLC will finish on November 20th. Please, send you comments to the 
authors and to the list.

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


------_=_NextPart_001_01C4CE5A.CF44347F
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Sipping] WGLC: e2m security requirements</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Summary:</FONT>
<BR><FONT SIZE=3D2>--------</FONT>
<BR><FONT SIZE=3D2>I think the draft is ready to forward to the IESG =
for review with the correction and clarification of the following =
items.</FONT></P>

<P><FONT SIZE=3D2>Editorial nits:</FONT>
<BR><FONT SIZE=3D2>---------------</FONT>
</P>

<P><FONT SIZE=3D2>- Section 1: Last paragraph, 1st sentence.&nbsp; =
Change &quot;...those that provides services...&quot; to &quot;...those =
that provide services...&quot;</FONT></P>

<P><FONT SIZE=3D2>- Section 4.2: REQ-CONF-1: Change &quot;The solution =
MUST be enable an encrypted data...&quot; to</FONT>
<BR><FONT SIZE=3D2>&quot;The solution MUST enable encrypted =
data...&quot; or perhaps even better would be &quot;The solution MUST =
allow encrypted data...&quot;</FONT></P>

<P><FONT SIZE=3D2>- Section 4.2: REQ-CONF-4 is unclear to =
me:&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&quot;It MAY allow a UA to request that the =
recipient UA</FONT>
<BR><FONT SIZE=3D2>&nbsp; disclose information to the proxy server, =
which</FONT>
<BR><FONT SIZE=3D2>&nbsp; requesting UA is disclosing the information =
to.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>I think you're saying that a UA MAY request that the =
UA that is receiving the information should provide that information to =
the proxy server which the requesting UA trusts to have that =
information in the first place, provided of course that the proxy =
server's policies allow it to receive the information from that UA =
(based on service provider policies).&nbsp; </FONT></P>

<P><FONT SIZE=3D2>So, I would propose changing that to something like =
(provided I've properly understood this requirement):</FONT>
<BR><FONT SIZE=3D2>&nbsp;&quot;It MAY allow a UA to request that the =
recipient UA</FONT>
<BR><FONT SIZE=3D2>&nbsp; disclose information to the proxy server, to =
which the</FONT>
<BR><FONT SIZE=3D2>&nbsp; requesting UA is initially disclosing =
information.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>- Section 4.2: paragraph just below REQ-CONF-4.&nbsp; =
Change &quot;...does not permit to reveal the security =
policies...&quot; to &quot;...does not permit revealing the security =
policies...&quot;</FONT></P>

<P><FONT SIZE=3D2>- Section 5: 2nd paragraph. Fix typo in =
&quot;...needs protection pagainst replay attack.&quot; </FONT>
</P>

<P><FONT SIZE=3D2>- Appendix A: Should likely have a note to RFC Editor =
to remove this section when doc is published.&nbsp; Also, would =
facilitate things for this to not be listed in the Table of Contents. =
</FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Mary H. Barnes</FONT>
<BR><FONT SIZE=3D2>mary.barnes@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: sipping-bounces@ietf.org [<A =
HREF=3D"mailto:sipping-bounces@ietf.org">mailto:sipping-bounces@ietf.org=
</A>] On Behalf Of Gonzalo Camarillo</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, October 18, 2004 11:40 PM</FONT>
<BR><FONT SIZE=3D2>To: sipping</FONT>
<BR><FONT SIZE=3D2>Cc: tachimoto.shinya@lab.ntt.co.jp; Rohan Mahy; =
Kumiko Ono; Dean Willis</FONT>
<BR><FONT SIZE=3D2>Subject: [Sipping] WGLC: e2m security =
requirements</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Folks,</FONT>
</P>

<P><FONT SIZE=3D2>we would like to working group last call the =
following draft:</FONT>
</P>

<P><FONT SIZE=3D2><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-r=
eqs-04.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-sipping=
-e2m-sec-reqs-04.txt</A></FONT>
</P>

<P><FONT SIZE=3D2>This WGLC will finish on November 20th. Please, send =
you comments to the </FONT>
<BR><FONT SIZE=3D2>authors and to the list.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Gonzalo</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>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>This list is for NEW development of the application =
of SIP</FONT>
<BR><FONT SIZE=3D2>Use sip-implementors@cs.columbia.edu for questions =
on current sip</FONT>
<BR><FONT SIZE=3D2>Use sip@ietf.org for new developments of core =
SIP</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4CE5A.CF44347F--


--===============1170475184==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============1170475184==--



From sipping-bounces@ietf.org  Mon Nov 22 09:55:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04066
	for <sipping-web-archive@ietf.org>; Mon, 22 Nov 2004 09:55:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWFeq-000854-6n
	for sipping-web-archive@ietf.org; Mon, 22 Nov 2004 09:59:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWFUa-0004nS-UT; Mon, 22 Nov 2004 09:48:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWFQn-0003wQ-4T
	for sipping@megatron.ietf.org; Mon, 22 Nov 2004 09:44:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03342
	for <sipping@ietf.org>; Mon, 22 Nov 2004 09:44:39 -0500 (EST)
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWFUF-0007Yl-6u
	for sipping@ietf.org; Mon, 22 Nov 2004 09:48:16 -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.11/8.12.11) with ESMTP id
	iAMEiQ9j018812; Mon, 22 Nov 2004 23:44:26 +0900 (JST)
Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiPX9007583; Mon, 22 Nov 2004 23:44:25 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiPQq007579; Mon, 22 Nov 2004 23:44:25 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiPCY012844; Mon, 22 Nov 2004 23:44:25 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiOKQ012836; Mon, 22 Nov 2004 23:44:24 +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.11/8.12.11) with ESMTP id
	iAMEiOHJ017802; Mon, 22 Nov 2004 23:44:24 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiNMj022555; Mon, 22 Nov 2004 23:44:23 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (img0.m.ecl.ntt.co.jp [129.60.5.145])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	iAMEiNjk022550; Mon, 22 Nov 2004 23:44:23 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id XAA08617;
	Mon, 22 Nov 2004 23:44:23 +0900 (JST)
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
To: "Mary Barnes" <mary.barnes@nortelnetworks.com>,
        tachimoto.shinya@lab.ntt.co.jp, sipping <sipping@ietf.org>
Subject: RE: [Sipping] WGLC: e2m security requirements
Date: Mon, 22 Nov 2004 23:44:16 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.65 (WinNT,501)
In-Reply-To: <E3F9D87C63E2774390FE67C924EC99BB053124CF@zrc2hxm1.corp.nortel.com>
References: <E3F9D87C63E2774390FE67C924EC99BB053124CF@zrc2hxm1.corp.nortel.com>
Message-Id: <20C4D0A1BDDA25ono.kumiko@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit

Mary,

Thank you so much for the close reading. 
I will fix all you pointed out.

Kumiko

At 02:11 2004/11/20, "Mary Barnes" wrote:
>Summary:
>--------
>I think the draft is ready to forward to the IESG for review with the
>correction and clarification of the following items.
>
>Editorial nits:
>---------------
>
>- Section 1: Last paragraph, 1st sentence.  Change "...those that provides
>services..." to "...those that provide services..."
>
>- Section 4.2: REQ-CONF-1: Change "The solution MUST be enable an encrypted
>data..." to
>"The solution MUST enable encrypted data..." or perhaps even better would be
>"The solution MUST allow encrypted data..."
>
>- Section 4.2: REQ-CONF-4 is unclear to me:   
> "It MAY allow a UA to request that the recipient UA
>  disclose information to the proxy server, which
>  requesting UA is disclosing the information to."
>
>I think you're saying that a UA MAY request that the UA that is receiving
>the information should provide that information to the proxy server which
>the requesting UA trusts to have that information in the first place,
>provided of course that the proxy server's policies allow it to receive the
>information from that UA (based on service provider policies).  
>
>So, I would propose changing that to something like (provided I've properly
>understood this requirement):
> "It MAY allow a UA to request that the recipient UA
>  disclose information to the proxy server, to which the
>  requesting UA is initially disclosing information."
>
>- Section 4.2: paragraph just below REQ-CONF-4.  Change "...does not permit
>to reveal the security policies..." to "...does not permit revealing the
>security policies..."
>
>- Section 5: 2nd paragraph. Fix typo in "...needs protection pagainst replay
>attack." 
>
>- Appendix A: Should likely have a note to RFC Editor to remove this section
>when doc is published.  Also, would facilitate things for this to not be
>listed in the Table of Contents. 
>
>Regards,
>Mary H. Barnes
>mary.barnes@nortelnetworks.com
>
>
>-----Original Message-----
>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
>Of Gonzalo Camarillo
>Sent: Monday, October 18, 2004 11:40 PM
>To: sipping
>Cc: tachimoto.shinya@lab.ntt.co.jp; Rohan Mahy; Kumiko Ono; Dean Willis
>Subject: [Sipping] WGLC: e2m security requirements
>
>
>Folks,
>
>we would like to working group last call the following draft:
>
>http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-reqs-04.txt
>
>This WGLC will finish on November 20th. Please, send you comments to the 
>authors and to the list.
>
>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


--
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 sipping-bounces@ietf.org  Mon Nov 22 14:11:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03911
	for <sipping-web-archive@ietf.org>; Mon, 22 Nov 2004 14:11:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWJeA-0005Uq-7u
	for sipping-web-archive@ietf.org; Mon, 22 Nov 2004 14:14:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWJX1-00017N-7C; Mon, 22 Nov 2004 14:07:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWJMK-0006s1-TR
	for sipping@megatron.ietf.org; Mon, 22 Nov 2004 13:56:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02359
	for <sipping@ietf.org>; Mon, 22 Nov 2004 13:56:19 -0500 (EST)
Received: from mail.stw-bonn.de ([131.220.99.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWJPq-0003aD-2h
	for sipping@ietf.org; Mon, 22 Nov 2004 13:59:58 -0500
Received: from port-192-168-20-109.dhcp.stw-bonn.de
	(port-192-168-20-109.dhcp.stw-bonn.de [192.168.20.109])
	by mail.stw-bonn.de (Postfix) with ESMTP id E5BC23B52D6
	for <sipping@ietf.org>; Mon, 22 Nov 2004 18:55:47 +0000 (/etc/localtime)
From: Oliver Schwaneberg <oliver.schwaneberg@fokus.fraunhofer.de>
To: sipping <sipping@ietf.org>
Content-Type: text/plain
Date: Mon, 22 Nov 2004 16:27:21 +0100
Message-Id: <1101137241.31925.9.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 (2.0.2-3) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Conference speaker controll
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Hi everybody!
I'm new here and I like to know if there's any approach to determine
which participant of an conference is actually talking?

For example:
If you're using a central mixer it would be possible to scan for talking
participants (silence sound suppression, level detection, etc.). In that
case the Mixer could send NOTIFY-Messages in order to inform every
participant about the talking-state of every other participant.

So back to my question: Is there already something like this?

Thank you in advance!

Oliver Schwaneberg


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov 22 15:39:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13098
	for <sipping-web-archive@ietf.org>; Mon, 22 Nov 2004 15:39:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWL1N-0007vz-3F
	for sipping-web-archive@ietf.org; Mon, 22 Nov 2004 15:42:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWKnQ-0005Nh-Gv; Mon, 22 Nov 2004 15:28:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWKjD-00037V-1s
	for sipping@megatron.ietf.org; Mon, 22 Nov 2004 15:24:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11998
	for <sipping@ietf.org>; Mon, 22 Nov 2004 15:24:01 -0500 (EST)
Received: from omzesmtp03.mci.com ([199.249.17.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWKmj-0005qz-0V
	for sipping@ietf.org; Mon, 22 Nov 2004 15:27:41 -0500
Received: from dgismtp03.wcomnet.com ([166.38.58.143])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I7L00HOLKN39R@firewall.mci.com> for sipping@ietf.org;
	Mon, 22 Nov 2004 20:23:27 +0000 (GMT)
Received: from dgismtp03.wcomnet.com by dgismtp03.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I7L00K01KHQT7@dgismtp03.mcilink.com>; Mon,
	22 Nov 2004 20:23:26 +0000 (GMT)
Received: from dgmexch09.wcomnet.com ([166.38.58.240])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I7L00K3PKM3U1@dgismtp03.mcilink.com>; Mon,
	22 Nov 2004 20:22:51 +0000 (GMT)
Received: by DGMEXCH09.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <XHMSH0RM>; Mon, 22 Nov 2004 20:29:35 +0000
Content-return: allowed
Date: Mon, 22 Nov 2004 20:22:49 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
Subject: RE: [Sipping] Conference speaker controll
To: "'Oliver Schwaneberg'" <oliver.schwaneberg@fokus.fraunhofer.de>,
        sipping <sipping@ietf.org>
Message-id: <EB7597BFB1C65844898A6D153DE09DB5089583@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

Hi Oliver,

An RTP (SSRC) approach is possible using the SIP conference package.  See
Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.  This has
the advantage of being synchronized with the media (unlike a SIP NOTIFY
approach) but does require the RTP mixer to include SSRC identifiers.

Thanks,
Alan Johnston
sip:alan@sipstation.com

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> Sent: Monday, November 22, 2004 9:27 AM
> To: sipping
> Subject: [Sipping] Conference speaker controll
> 
> 
> Hi everybody!
> I'm new here and I like to know if there's any approach to 
> determine which participant of an conference is actually talking?
> 
> For example:
> If you're using a central mixer it would be possible to scan 
> for talking participants (silence sound suppression, level 
> detection, etc.). In that case the Mixer could send 
> NOTIFY-Messages in order to inform every participant about 
> the talking-state of every other participant.
> 
> So back to my question: Is there already something like this?
> 
> Thank you in advance!
> 
> Oliver Schwaneberg
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 23 11:19:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26681
	for <sipping-web-archive@ietf.org>; Tue, 23 Nov 2004 11:19:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWdSA-0006eU-Il
	for sipping-web-archive@ietf.org; Tue, 23 Nov 2004 11:23:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWdKo-000626-8l; Tue, 23 Nov 2004 11:16:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWd1r-0000hb-Sz
	for sipping@megatron.ietf.org; Tue, 23 Nov 2004 10:56:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24428
	for <sipping@ietf.org>; Tue, 23 Nov 2004 10:56:29 -0500 (EST)
Received: from omzesmtp03.mci.com ([199.249.17.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWd5Y-0003L6-Bz
	for sipping@ietf.org; Tue, 23 Nov 2004 11:00:21 -0500
Received: from dgismtp06.wcomnet.com ([166.38.58.89])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I7N0013L2ROLP@firewall.mci.com> for sipping@ietf.org;
	Tue, 23 Nov 2004 15:54:53 +0000 (GMT)
Received: from dgismtp06.wcomnet.com by dgismtp06.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I7N008012MPMF@dgismtp06.mcilink.com> for
	sipping@ietf.org; Tue, 23 Nov 2004 15:54:29 +0000 (GMT)
Received: from dgmexch09.wcomnet.com ([166.38.58.240])
	by dgismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I7N007Q82U5NS@dgismtp06.mcilink.com> for
	sipping@ietf.org; Tue, 23 Nov 2004 15:54:05 +0000 (GMT)
Received: by DGMEXCH09.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <XHMSKDZ4>; Tue, 23 Nov 2004 16:00:50 +0000
Content-return: allowed
Date: Tue, 23 Nov 2004 15:54:04 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <EB7597BFB1C65844898A6D153DE09DB5089590@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: "'Orit Levin'" <oritl@microsoft.com>
Subject: [Sipping] WGLC Summary for cc-conferencing
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

As WGLC has ended for draft-sipping-cc-conferencing-05, here's the summary
of issues raised and discussed during WGLC:

 A detailed review by Miguel Garcia (11/4) identified a number of
corrections, clarifications, and nits.

 No major issues were identified.

The authors plan to revise the document incorporating these changes,
updating conference package examples, removing change history, etc so it is
ready for the IETF Last Call with the other three SIP conferencing
documents. 

Thanks,
Alan Johnston
MCI
sip:alan@sipstation.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 sipping-bounces@ietf.org  Tue Nov 23 16:10:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01077
	for <sipping-web-archive@ietf.org>; Tue, 23 Nov 2004 16:10:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWhzD-0005gX-2U
	for sipping-web-archive@ietf.org; Tue, 23 Nov 2004 16:14:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWhBz-0000sR-Qj; Tue, 23 Nov 2004 15:23:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWgxX-0008Hr-O2; Tue, 23 Nov 2004 15:08:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17322;
	Tue, 23 Nov 2004 15:08:17 -0500 (EST)
Message-Id: <200411232008.PAA17322@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 23 Nov 2004 15:08:17 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--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		: An INVITE Inititiated Dialog Event Package for the
                          Session Initiation Protocol (SIP)
	Author(s)	: J. Rosenberg, et al.
	Filename	: draft-ietf-sipping-dialog-package-05.txt
	Pages		: 39
	Date		: 2004-11-23
	
This document defines a dialog event package for the SIP Events
architecture, along with a data format used in notifications for this
package. The dialog package allows users to subscribe to another
user, an receive notifications about the changes in state of INVITE
initiated dialogs that the user is involved in.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialog-package-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-dialog-package-05.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-dialog-package-05.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: <2004-11-23143811.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-dialog-package-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-dialog-package-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--NextPart--





From sipping-bounces@ietf.org  Tue Nov 23 16:37:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06684
	for <sipping-web-archive@ietf.org>; Tue, 23 Nov 2004 16:37:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWiPZ-0001pk-Pj
	for sipping-web-archive@ietf.org; Tue, 23 Nov 2004 16:41:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWi8o-0003S3-4g; Tue, 23 Nov 2004 16:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWhTu-0003EG-6i
	for sipping@megatron.ietf.org; Tue, 23 Nov 2004 15:41:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23369
	for <sipping@ietf.org>; Tue, 23 Nov 2004 15:41:43 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWhXd-0008Nk-9D
	for sipping@ietf.org; Tue, 23 Nov 2004 15:45:37 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 23 Nov 2004 12:41:23 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 23 Nov 2004 12:41:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 23 Nov 2004 12:41:12 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03C0B50E@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: WGLC summary for draft-ietf-sipping-conferencing-requirements-01
Thread-Index: AcTRnMUt2xj2ZQgmQYWpPutOg5seAA==
From: "Orit Levin" <oritl@microsoft.com>
To: "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 23 Nov 2004 20:41:13.0118 (UTC)
	FILETIME=[C5763BE0:01C4D19C]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Roni Even <roni.even@polycom.co.il>
Subject: [Sipping] WGLC summary for
	draft-ietf-sipping-conferencing-requirements-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1593316132=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

This is a multi-part message in MIME format.

--===============1593316132==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D19C.CDE90E38"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D19C.CDE90E38
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As WGLC has ended for draft-ietf-sipping-conferencing-requirements-01.

There were no comments post on the list, so it is ready for the IETF
Last Call.=20

Best Regards,

Orit Levin.


------_=_NextPart_001_01C4D19C.CDE90E38
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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P><FONT face=3DArial><FONT size=3D2>As WGLC has ended for=20
draft-ietf-sipping-conferencing-requirements-01<SPAN=20
class=3D891093620-23112004>.</SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D891093620-23112004>There were no=20
comments post on the list, </SPAN></FONT></FONT><FONT face=3DArial =
size=3D2>so it is=20
ready for the IETF Last Call. </FONT></P>
<P><SPAN class=3D891093620-23112004><FONT face=3DArial size=3D2>Best=20
Regards,</FONT></SPAN></P>
<P><SPAN class=3D891093620-23112004><FONT face=3DArial size=3D2>Orit=20
Levin.</FONT></SPAN></P></DIV></BODY></HTML>

------_=_NextPart_001_01C4D19C.CDE90E38--


--===============1593316132==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============1593316132==--



From sipping-bounces@ietf.org  Tue Nov 23 17:16:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12806
	for <sipping-web-archive@ietf.org>; Tue, 23 Nov 2004 17:16:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWj1b-00080t-2Z
	for sipping-web-archive@ietf.org; Tue, 23 Nov 2004 17:20:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWipi-0006kZ-Sp; Tue, 23 Nov 2004 17:08:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiXA-0004Jr-QM
	for sipping@megatron.ietf.org; Tue, 23 Nov 2004 16:49:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08317
	for <sipping@ietf.org>; Tue, 23 Nov 2004 16:49:09 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWiau-0003Vd-9R
	for sipping@ietf.org; Tue, 23 Nov 2004 16:53:04 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 23 Nov 2004 13:48:46 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 23 Nov 2004 13:48:39 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 23 Nov 2004 13:48:43 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03C0B5D6@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: WGLC Summary for draft-ietf-sipping-conference-package-06
Thread-Index: AcTRpjPJWLKHxbXgTS6WjrOeVoM6Sw==
From: "Orit Levin" <oritl@microsoft.com>
To: "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 23 Nov 2004 21:48:39.0394 (UTC)
	FILETIME=[313AF420:01C4D1A6]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: [Sipping] WGLC Summary for draft-ietf-sipping-conference-package-06
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1246499956=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0

This is a multi-part message in MIME format.

--===============1246499956==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D1A6.3F58D0B8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D1A6.3F58D0B8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

WGLC has ended for draft-ietf-sipping-conference-package-06.

I am planning to incorporate the comments by Miguel Garcia and Cullen
Jennings in the draft.

They will result in the following updates:

   o  Whispers are removed.
   o  The "version-type" is redefined as "unsignedInt".
   o  The "user" elements are grouped in a container named "users".
   o  The attribute "entity" of "media-type" is renamed to "id".
   o  The "media-state-type" is redefined to use SDP values "recvonly",
      "sendonly", "sendrecv", and "inactive".
   o  Sub-elements "snd-state", and "rcv-state" of "media-type" are
      removed.
   o  Sub-element "ssrc" of "media-type" is renamed to "src-id".
   o  The "extended-type" is removed and the standard XML extension
      conventions are used instead.
   o  Descriptive text and editorial nits are added throughout the
document.

   o  The XML elements and attributes are styled in the descriptive text
according to Miguel's suggestions.

=20
I tend to NOT incorporating (unless there is an objection expressed to
it) Miguel's suggestions to:
=20
   o  Merge the conf-uris and service-uris under the same element (they
clearly mean different things).
   o  Add the "purpose" element to the "uri-type" and register with IANA
the "purpose" values used with "service-uris" (leave this job to XCON)

No other major issues have been identified.

After resubmitting the draft as
draft-ietf-sipping-conference-package-07, I believe, it will be ready
for the next step in the process.

Best Regards,

Orit.


------_=_NextPart_001_01C4D1A6.3F58D0B8
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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<P><FONT face=3DArial size=3D2>WGLC has ended for=20
draft-ietf-sipping-conference-package-06<SPAN=20
class=3D774534120-23112004>.</SPAN></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN class=3D774534120-23112004>I =
am planning to=20
incorporate the comments </SPAN>by Miguel Garcia&nbsp;<SPAN=20
class=3D774534120-23112004>and&nbsp;Cullen Jennings</SPAN><SPAN=20
class=3D774534120-23112004> in the draft.</SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D774534120-23112004>They will result=20
in the following updates:</SPAN></FONT></FONT></P><FONT =
face=3DArial><FONT=20
size=3D+0><SPAN class=3D774534120-23112004>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"><FONT=20
size=3D2><SPAN style=3D"mso-spacerun: yes">&nbsp;<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;</SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Whispers are=20
removed.<BR>&nbsp;&nbsp;<SPAN=20
class=3D774534120-23112004>&nbsp;</SPAN></SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The "version-type" is =
redefined as=20
"unsignedInt".<BR><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>The "user" elements are =
grouped in a=20
container named "users".<BR><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
</SPAN>o<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The attribute =
"entity" of=20
"media-type" is renamed to "id".<BR><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
</SPAN>o<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The =
"media-state-type" is=20
redefined to use SDP values "recvonly",<BR><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>"sendonly",=20
"sendrecv", and "inactive".<BR><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
</SPAN>o<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>Sub-elements =
"snd-state",=20
and "rcv-state" of "media-type" are<BR><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>removed.<BR><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Sub-element "ssrc" of =
"media-type" is=20
renamed to "src-id".<BR><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>o<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>The =
"extended-type" is=20
removed and the standard XML extension<BR><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>conventions are=20
used instead.<BR><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Descriptive text&nbsp;<SPAN=20
class=3D774534120-23112004>and editorial nits are</SPAN>&nbsp;added =
throughout the=20
document.</FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
face=3D"Courier New"=20
size=3D2>&nbsp;<SPAN =
class=3D774534120-23112004>&nbsp;&nbsp;</SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;</SPAN><SPAN =
class=3D774534120-23112004>The=20
XML elements and attributes are styled in the descriptive text according =
to=20
Miguel's suggestions</SPAN>.</FONT></P><FONT=20
face=3D"Courier New"></FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D774534120-23112004></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D774534120-23112004><FONT=20
face=3D"Courier New">I tend to NOT incorporating (unless there is an =
objection=20
expressed to it) Miguel's suggestions =
to:</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D774534120-23112004></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D+0><SPAN =
class=3D774534120-23112004><FONT=20
face=3D"Courier New"><FONT size=3D2><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;=20
</SPAN>o<SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;Merge the =
conf-uris and=20
service-uris under the same element (they clearly mean different=20
things)</SPAN>.</FONT><BR></FONT><FONT size=3D2><FONT face=3D"Courier =
New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>o<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;<SPAN =
class=3D774534120-23112004>Add=20
t</SPAN></SPAN>he "purpose" element to the "uri-type" and register =
with<SPAN=20
class=3D774534120-23112004> </SPAN>IANA<SPAN class=3D774534120-23112004> =
t</SPAN>he=20
"purpose" values used with "service-uris" (leave this job to=20
XCON)</FONT></FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D+0><SPAN =
class=3D774534120-23112004><FONT=20
size=3D2><FONT face=3D"Courier =
New"></FONT><BR></FONT></SPAN></FONT></FONT><FONT=20
face=3DArial size=3D2>No&nbsp;<SPAN class=3D774534120-23112004>other =
</SPAN>major=20
issues&nbsp;<SPAN class=3D774534120-23112004>have been=20
</SPAN>identified.</FONT></DIV>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D774534120-23112004>After=20
resubmitting the draft as draft-ietf-sipping-conference-package-07, I =
believe,=20
</SPAN>it&nbsp;<SPAN class=3D774534120-23112004>will =
be</SPAN>&nbsp;ready for=20
the&nbsp;<SPAN class=3D774534120-23112004>next step in the=20
process.</SPAN></FONT></FONT></P>
<P><SPAN class=3D774534120-23112004><FONT face=3DArial size=3D2>Best=20
Regards,</FONT></SPAN></P>
<P><SPAN class=3D774534120-23112004><FONT face=3DArial=20
size=3D2>Orit.</FONT></SPAN></P></BODY></HTML>

------_=_NextPart_001_01C4D1A6.3F58D0B8--


--===============1246499956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============1246499956==--



From sipping-bounces@ietf.org  Wed Nov 24 10:18:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02712
	for <sipping-web-archive@ietf.org>; Wed, 24 Nov 2004 10:18:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWyyE-000590-NI
	for sipping-web-archive@ietf.org; Wed, 24 Nov 2004 10:22:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWylj-0001hU-Sk; Wed, 24 Nov 2004 10:09:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWyfn-0006eL-KR
	for sipping@megatron.ietf.org; Wed, 24 Nov 2004 10:03:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00514
	for <sipping@ietf.org>; Wed, 24 Nov 2004 10:03:09 -0500 (EST)
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWyjf-0003dn-Ks
	for sipping@ietf.org; Wed, 24 Nov 2004 10:07:13 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAOF2tS23841; Wed, 24 Nov 2004 17:03:00 +0200 (EET)
X-Scanned: Wed, 24 Nov 2004 17:02:45 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAOF2j3r025916;
	Wed, 24 Nov 2004 17:02:45 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 006WTZnU; Wed, 24 Nov 2004 17:02:44 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAOF2ha11595; Wed, 24 Nov 2004 17:02:43 +0200 (EET)
Received: from [172.21.38.233] ([172.21.38.233]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 24 Nov 2004 17:02:37 +0200
Message-ID: <41A4A28D.4010303@nokia.com>
Date: Wed, 24 Nov 2004 17:02:37 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Orit Levin <oritl@microsoft.com>
Subject: Re: [Sipping] WGLC Summary for
	draft-ietf-sipping-conference-package-06
References: <DD07841287D0AD428833021705E0D14E03C0B5D6@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <DD07841287D0AD428833021705E0D14E03C0B5D6@RED-MSG-52.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Nov 2004 15:02:37.0590 (UTC)
	FILETIME=[A2E06B60:01C4D236]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Hi:

Some comments on two of the not-agreed issues:

Orit Levin wrote:

>  
>    o  Merge the conf-uris and service-uris under the same element (they 
> clearly mean different things).

I agree that these URIs clearly mean different things, but we have the 
<purpose> element exactly to differentiate their means, so I don't think 
there is a need to do further differentiation into <service-uris> and 
<conf-uris>. This is more a aesthetic issue, since it doesn't have an 
inpact on the functionality.


>    o  Add the "purpose" element to the "uri-type" and register with IANA 
> the "purpose" values used with "service-uris" (leave this job to XCON)
> 

The <uri-type> will contain the <purpose> element, since this type will 
be used by any kind of URI. So, if I understand correctly, you don't 
want to register with IANA the possible values that will indicate 
additional services (e.g., CPCP, MPCP, ... you name it). If this is the 
case, I have no problem with this approach. We just need to make sure 
that the protocols in XCON (CPCP, MPCP), etc. will register with IANA 
the token in the <purpose> element of the conference event package.

- Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 24 11:51:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09687
	for <sipping-web-archive@ietf.org>; Wed, 24 Nov 2004 11:51:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX0Qz-00061h-KG
	for sipping-web-archive@ietf.org; Wed, 24 Nov 2004 11:56:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX0Ev-0006Zu-6r; Wed, 24 Nov 2004 11:43:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX09s-0005YU-S5; Wed, 24 Nov 2004 11:38:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08769;
	Wed, 24 Nov 2004 11:38:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX0Dm-0004or-Re; Wed, 24 Nov 2004 11:42:23 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CX054-0004PR-RS; Wed, 24 Nov 2004 11:33:22 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CX054-0004PR-RS@megatron.ietf.org>
Date: Wed, 24 Nov 2004 11:33:22 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: sipping chair <rohan@ekabal.com>,
        Internet Architecture Board <iab@iab.org>,
        sipping chair <dean.willis@softarmor.com>,
        sipping mailing list <sipping@ietf.org>,
        sipping chair <gonzalo.camarillo@ericsson.com>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Sipping] Document Action: 'Transcoding Services Invocation in the 
 Session Initiation Protocol (SIP) Using Third Party Call Control 
 (3pcc)' to Informational RFC 
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745

The IESG has approved the following document:

- 'Transcoding Services Invocation in the Session Initiation Protocol (SIP) 
   Using Third Party Call Control (3pcc) '
   <draft-ietf-sipping-transc-3pcc-02.txt> as an Informational RFC

This document is the product of the Session Initiation Proposal Investigation 
Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

RFC Editor Notes
Page 6, second to last paragraph:
OLD:
B may want to hide its capabilities,
NEW:
B may want to hide its lack of native capabilities,

------------
Page 9, last paragraph: Expand FID acronym.
OLD:
There are various possible solutions for this problem. One solution
consists of using the SDP group attribute with FID semantics [3]
NEW:
There are various possible solutions for this problem. One solution
consists of using the SDP group attribute with FID (Flow Identification)
semantics [3]


-----------
Section 3.5. Add the following paragraph after the second paragraph of
the section:
NEW:
Note this example uses unidirectional media streams (i.e., sendonly or
recvonly) to clearly identify which transcoder handles media in which
direction. Nevertheless, nothing precludes the use of bidirectional
streams in this scenario. They could be used, for example, by a human
relay to ask for clarifications (e.g., I did not get that, could you
repeat, please?) to the party he or she is receiving media from.

---------

OLD:
4 Security Considerations

    This document describes how to use third party call control to invoke
    transcoding services. It does not introduce new security
    considerations besides the ones discussed in [2].

NEW:
4 Security Considerations

RFC 3725 [2] discusses security considerations which relate to the use
of third party call control in SIP. These considerations apply to this
document, since it describes how to use third party call control to
invoke transcoding services.

In particular, RFC 3725 states that end-to-end media security is based
on the exchange of keying material within SDP and depends on the
controller behaving properly. That is, the controller should not try to
disable the security mechanisms offered by the other parties. As a
result, it is trivially possible for the controller to insert itself
as an intermediary on the media exchange, if it should so desire.

In this document, the controller is the UA invoking the transcoder, and
there is a media session established using third party call control
between the remote UA and the transcoder. Consequently, the attack
described in RFC 3725 does not constitute a threat because the
controller is the UA invoking the transcoding service and it has access
to the media anyway by definition. So, it seems unlikely that a UA
attempts to launch an attack against its own session by disabling
security between the transcoder and the remote UA.

Regarding end-to-end media security from the UAs' point of view, the
transcoder needs access to the media in order perform its function. So,
by definition, the transcoder behaves as a man in the middle. UAs that
do not want to a particular transcoder to have access to all the media
exchanged between them can use a different transcoder for each
direction. In addition, UAs can use different transcoders for different
media types.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Wed Nov 24 17:52:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11809
	for <sipping-web-archive@ietf.org>; Wed, 24 Nov 2004 17:52:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX63h-0000PU-PZ
	for sipping-web-archive@ietf.org; Wed, 24 Nov 2004 17:56:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX5xu-0000rX-5g; Wed, 24 Nov 2004 17:50:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX5ui-00005C-Bk
	for sipping@megatron.ietf.org; Wed, 24 Nov 2004 17:47:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11608
	for <sipping@ietf.org>; Wed, 24 Nov 2004 17:47:01 -0500 (EST)
Received: from omzesmtp02.mci.com ([199.249.17.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX5yf-0000KC-5m
	for sipping@ietf.org; Wed, 24 Nov 2004 17:51:09 -0500
Received: from pmismtp03.mcilink.com ([166.38.62.38])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I7P00HIVG549X@firewall.mci.com> for sipping@ietf.org;
	Wed, 24 Nov 2004 22:36:40 +0000 (GMT)
Received: from pmismtp03.mcilink.com by pmismtp03.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I7P00I01G537B@pmismtp03.mcilink.com>; Wed,
	24 Nov 2004 22:36:39 +0000 (GMT)
Received: from dgexch50.wcomnet.com ([166.38.58.238])
	by pmismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I7P00FE9G53XN@pmismtp03.mcilink.com>; Wed,
	24 Nov 2004 22:36:39 +0000 (GMT)
Received: by DGEXCH50.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <WYQ49GNZ>; Wed, 24 Nov 2004 22:36:39 +0000
Content-return: allowed
Date: Wed, 24 Nov 2004 22:36:37 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
Subject: RE: [Sipping] WGLC Summary for	draft-ietf-sipping-conference-pack
	age-06
To: "'Miguel Garcia'" <Miguel.An.Garcia@nokia.com>,
        Orit Levin <oritl@microsoft.com>
Message-id: <EB7597BFB1C65844898A6D153DE09DB50895AB@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: sipping <sipping@ietf.org>, Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be

Miguel,

See my comments below.

Thanks,
Alan Johnston
sip:alan@sipstation.com

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Miguel Garcia
> Sent: Wednesday, November 24, 2004 9:03 AM
> To: Orit Levin
> Cc: sipping; Henning Schulzrinne
> Subject: Re: [Sipping] WGLC Summary for 
> draft-ietf-sipping-conference-package-06
> 
> 
> Hi:
> 
> Some comments on two of the not-agreed issues:
> 
> Orit Levin wrote:
> 
> >  
> >    o  Merge the conf-uris and service-uris under the same element 
> > (they
> > clearly mean different things).
> 
> I agree that these URIs clearly mean different things, but we 
> have the 
> <purpose> element exactly to differentiate their means, so I 
> don't think 
> there is a need to do further differentiation into <service-uris> and 
> <conf-uris>. This is more a aesthetic issue, since it doesn't have an 
> inpact on the functionality.

I oppose putting them together since conference URIs have extremely clear
semantics, and are going to be parsed and used by UAs in call control
operations (INVITEs, REFERs, etc.).  Service URIs, on the other hand, really
don't have any semantics right now - they would just be rendered to the
user.  I would expect most UAs to simply ignore Service URIs until we add
semantics in XCON.

Lets keep them separate as they are now.

> 
> 
> >    o  Add the "purpose" element to the "uri-type" and register with 
> > IANA
> > the "purpose" values used with "service-uris" (leave this 
> job to XCON)
> > 
> 
> The <uri-type> will contain the <purpose> element, since this 
> type will 
> be used by any kind of URI. So, if I understand correctly, you don't 
> want to register with IANA the possible values that will indicate 
> additional services (e.g., CPCP, MPCP, ... you name it). If 
> this is the 
> case, I have no problem with this approach. We just need to make sure 
> that the protocols in XCON (CPCP, MPCP), etc. will register with IANA 
> the token in the <purpose> element of the conference event package.

I agree that we will likely need to set up some IANA registries for elements
in the conference package.  However, I'd rather do it once in XCON than do
it now (when we have only one field, and only one value to register), then
go back to IANA again in 6 months and do it all again.  Lets save work and
do it only once.

> 
> - Miguel
> -- 
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Research Center      Helsinki, Finland
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 25 02:54:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10298
	for <sipping-web-archive@ietf.org>; Thu, 25 Nov 2004 02:54:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXEWQ-0003mV-B2
	for sipping-web-archive@ietf.org; Thu, 25 Nov 2004 02:58:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXEOo-0000bi-6G; Thu, 25 Nov 2004 02:50:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXEMb-0008QQ-Ht
	for sipping@megatron.ietf.org; Thu, 25 Nov 2004 02:48:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09766
	for <sipping@ietf.org>; Thu, 25 Nov 2004 02:48:24 -0500 (EST)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXEQc-0003db-Cu
	for sipping@ietf.org; Thu, 25 Nov 2004 02:52:35 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAP7mBF05124; Thu, 25 Nov 2004 09:48:12 +0200 (EET)
X-Scanned: Thu, 25 Nov 2004 09:50:57 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iAP7ovCj024127;
	Thu, 25 Nov 2004 09:50:57 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00VOAiv4; Thu, 25 Nov 2004 09:50:55 EET
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAP7lsa21997; Thu, 25 Nov 2004 09:47:54 +0200 (EET)
Received: from [172.21.38.233] ([172.21.38.233]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 25 Nov 2004 09:47:50 +0200
Message-ID: <41A58E26.8060907@nokia.com>
Date: Thu, 25 Nov 2004 09:47:50 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Johnston, Alan" <Alan.Johnston@mci.com>
Subject: Re: [Sipping] WGLC Summary
	for	draft-ietf-sipping-conference-package-06
References: <EB7597BFB1C65844898A6D153DE09DB50895AB@DGEXCH02.mcilink.com>
In-Reply-To: <EB7597BFB1C65844898A6D153DE09DB50895AB@DGEXCH02.mcilink.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Nov 2004 07:47:50.0705 (UTC)
	FILETIME=[104B6A10:01C4D2C3]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit
Cc: Orit Levin <oritl@microsoft.com>, sipping <sipping@ietf.org>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: 7bit

Alan, I don't quite agree with you. Let me see if we are all speaking 
about the same thing.

On one side, we have an issue related to how to assign semantics to a 
URI. The idea is that the focus can include a URI indicating what can 
the UA do with that URI. For instance, the focus can say: here is the 
URI that you can use to join this conference (and can be a sip, h323, 
tel or alike URI). Another example is the URI that a UA can use to do 
CPCP operations, get a web page information, etc.

Is there a commonality among all of them: In my opinion, yes, there is 
one: all are URIs and we need to indicate what can the UA do with this 
URI, that is the <purpose> element.

With this approach in the conference event package, one can design a 
smart UA, that subscribe to the conference event package, and gets a 
collection of URIs where the UA can start a CPCP session, floor control, 
etc. You name it. Everything is automatic because the URI indicates its 
purpose, and the values of these purposes are well known tokens 
registered with IANA.

In this model there is no need to distinguish <service-uris> from 
<conference-uris>, because that distinction is provided by the <purpose> 
element that comes together with the <uri> element. All of them are a 
bunch of uris with a specific purpose. And the semantics are clear 
through this <purpose> element.

I hope we can agree on the above. If we do, then we need to solve 
another issue: how do we move forward from where we are today to the 
above described scenario. What we need to do today is to open the IANA 
registry for the values of <purpose> element. Today we can register 
tokens for "conference" (what we call so far conference-uris) and 
"web-page". Perhaps "recording" as well (the uri of the recorded 
session). I agree we don't need to register other purpose for other 
actions that are still under discussion in XCON (I am referring to CPCP, 
  MPCP, floor control, etc.). This can be done by the respective 
CPCP/MPCP/BFCP drafts, if/when required).

BR,

       Miguel

Johnston, Alan wrote:

> Miguel,
> 
> See my comments below.
> 
> Thanks,
> Alan Johnston
> sip:alan@sipstation.com
> 
> 
>>-----Original Message-----
>>From: sipping-bounces@ietf.org 
>>[mailto:sipping-bounces@ietf.org] On Behalf Of Miguel Garcia
>>Sent: Wednesday, November 24, 2004 9:03 AM
>>To: Orit Levin
>>Cc: sipping; Henning Schulzrinne
>>Subject: Re: [Sipping] WGLC Summary for 
>>draft-ietf-sipping-conference-package-06
>>
>>
>>Hi:
>>
>>Some comments on two of the not-agreed issues:
>>
>>Orit Levin wrote:
>>
>>
>>> 
>>>   o  Merge the conf-uris and service-uris under the same element 
>>>(they
>>>clearly mean different things).
>>
>>I agree that these URIs clearly mean different things, but we 
>>have the 
>><purpose> element exactly to differentiate their means, so I 
>>don't think 
>>there is a need to do further differentiation into <service-uris> and 
>><conf-uris>. This is more a aesthetic issue, since it doesn't have an 
>>inpact on the functionality.
> 
> 
> I oppose putting them together since conference URIs have extremely clear
> semantics, and are going to be parsed and used by UAs in call control
> operations (INVITEs, REFERs, etc.).  Service URIs, on the other hand, really
> don't have any semantics right now - they would just be rendered to the
> user.  I would expect most UAs to simply ignore Service URIs until we add
> semantics in XCON.
> 
> Lets keep them separate as they are now.
> 
> 
>>
>>>   o  Add the "purpose" element to the "uri-type" and register with 
>>>IANA
>>>the "purpose" values used with "service-uris" (leave this 
>>
>>job to XCON)
>>
>>The <uri-type> will contain the <purpose> element, since this 
>>type will 
>>be used by any kind of URI. So, if I understand correctly, you don't 
>>want to register with IANA the possible values that will indicate 
>>additional services (e.g., CPCP, MPCP, ... you name it). If 
>>this is the 
>>case, I have no problem with this approach. We just need to make sure 
>>that the protocols in XCON (CPCP, MPCP), etc. will register with IANA 
>>the token in the <purpose> element of the conference event package.
> 
> 
> I agree that we will likely need to set up some IANA registries for elements
> in the conference package.  However, I'd rather do it once in XCON than do
> it now (when we have only one field, and only one value to register), then
> go back to IANA again in 6 months and do it all again.  Lets save work and
> do it only once.
> 
> 
>>- Miguel
>>-- 
>>Miguel A. Garcia           tel:+358-50-4804586
>>Nokia Research Center      Helsinki, Finland
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current 
>>sip Use sip@ietf.org for new developments of core SIP
>>

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 25 04:30:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20347
	for <sipping-web-archive@ietf.org>; Thu, 25 Nov 2004 04:30:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXG1T-0006LQ-Tm
	for sipping-web-archive@ietf.org; Thu, 25 Nov 2004 04:34:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXFq2-00017Z-Qy; Thu, 25 Nov 2004 04:22:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFlR-0007rv-7s
	for sipping@megatron.ietf.org; Thu, 25 Nov 2004 04:18:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19176
	for <sipping@ietf.org>; Thu, 25 Nov 2004 04:18:07 -0500 (EST)
Received: from smtp.dataconnection.com ([192.91.191.4] helo=smtp.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFpT-00063h-Vc
	for sipping@ietf.org; Thu, 25 Nov 2004 04:22:20 -0500
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <XHBYPJND>; Thu, 25 Nov 2004 09:17:32 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F803E53299@baker.datcon.co.uk>
From: "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
To: "'Rohan Mahy'" <rohan@ekabal.com>
Subject: RE: AW: [Sipping] Comments on the FSM in dialog package -05 
Date: Thu, 25 Nov 2004 09:17:27 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: SIPPING WG <sipping@ietf.org>,
        "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

Rohan,

I have to disagree with your response below.  RFC3261 clearly distinguishes
a BYE, which terminates an INVITE initiated dialog, from other SIP requests.
In particular, Section 12.2.1.2 is clear that a failed OPTIONS does not
terminate a dialog although it should cause the UA to terminate the dialog
by sending a BYE.

Comparisons with RFC3265 should take account of the fact that in some
respects a NOTIFY is like a BYE and _not_ like an OPTIONS.  RFC3265 and
RFC3261 are then consistent in that, if the dialog ending request (NOTIFY
or BYE) fails with 408/481, then the dialog is assumed terminated.

In conclusion, I believe that the dialog is _not_ terminated until the
BYE has completed (2XX response or 408/481) and the dialog package state 
must reflect this.

Paul D Smith
Network Protocols Group 
Data Connection Ltd (DCL)
Tel: +44 20 8366 1177  Email: paul.d.smith@dataconnection.com 
Fax: +44 20 8363 1039  Web:   http://www.dataconnection.com

-----Original Message-----
From: Rohan Mahy [mailto:rohan@ekabal.com]
Sent: 10 November 2004 15:02
To: SIP Public Folder (E-mail)
Subject: Re: AW: [Sipping] Comments on the FSM in dialog package -05 


Hi,

If you want to propose specific language for a change to RFC 3261 that 
would get incorporated if we do an errata, please send a short note to 
the SIP list with the current text and the proposed text.

many thanks,
-rohan

On Nov 10, 2004, at 3:33, Tan Ya-Ching wrote:
> Hi,
>
> Thanks for your answer. My further comments below :
>
>>>   But RFC 3261 (12.2.1.2 Processing the Responses) states that :
>>>
>>>   "If the response for a request within a dialog is a 481
>>>   (Call/Transaction Does Not Exist) or a 408 (Request Timeout), the
>>>   UAC SHOULD terminate the dialog.  A UAC SHOULD also terminate a
>>>   dialog if no response at all is received for the request (the 
>>> client
>>>   transaction would inform the TU about the timeout.)
>>>
>>>      For INVITE initiated dialogs, terminating the dialog consists of
>>>      sending a BYE."
>>>
>>>   It is stated specifically that terminating the dialog consists of
>>>   sending a BYE. Therefore, the "error" event and "timeout"
>>>   event in the FSM should not directly lead to the terminated
>>>   state. Only the "local-bye" and "remote-bye" events could lead to
>>>   the terminated state.
>
>> No, according to RFC 3261 section 12.2.1.2 which you quote above, if I
>> send a reINVITE, OPTIONS, PRACK, INFO, UPDATE, or other in-dialog
>> request and get a 408, timeout, or 481, then the state of the dialog
>> moves to terminated.
>
> If that is so, why doesn't RFC 3261 quoted above simply state that
> "the dialog terminates" instead of "the UAC SHOULD terminate the 
> dialog",
> and as I pointed above, it further clarifies that "terminating the
> dialog consists of sending a BYE".
>
> For similar situation in RFC 3265 :
>
> "If a NOTIFY request receives a 481 response, the notifier MUST
> remove the corresponding subscription..."  and
> "If a subscription's destruction leaves no other application state
> associated with the dialog, the dialog terminates".
>
> There it is clear that the dialog simply terminates, with no
> further action required from the UAC.
>
> Ya-Ching


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Thu Nov 25 05:49:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27635
	for <sipping-web-archive@ietf.org>; Thu, 25 Nov 2004 05:49:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXHFf-0008A9-H5
	for sipping-web-archive@ietf.org; Thu, 25 Nov 2004 05:53:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXH7i-0002Iq-2B; Thu, 25 Nov 2004 05:45:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXH4W-0001QP-0J
	for sipping@megatron.ietf.org; Thu, 25 Nov 2004 05:41:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27151
	for <sipping@ietf.org>; Thu, 25 Nov 2004 05:41:53 -0500 (EST)
Received: from [212.179.22.140] (helo=imss.audiocodes.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXH8Y-00083I-BU
	for sipping@ietf.org; Thu, 25 Nov 2004 05:46:07 -0500
Received: from aclmsg.corp.audiocodes.com ([10.1.0.8]) by imss with InterScan
	Messaging Security Suite; Thu, 25 Nov 2004 13:48:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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] Document Action: 'Transcoding Services Invocation in
	the Session Initiation Protocol (SIP) Using Third Party Call
	Control (3pcc)' to Informational RFC 
Date: Thu, 25 Nov 2004 12:42:07 +0200
Message-ID: <79B4F738DDD4EF4F85A4641A0FE5EFD6288587@aclmsg.corp.audiocodes.com>
Thread-Topic: [Sipping] Document Action: 'Transcoding Services Invocation in
	the Session Initiation Protocol (SIP) Using Third Party Call
	Control (3pcc)' to Informational RFC 
Thread-Index: AcTSRlSHqmJOmkJMTWSwn86KVoMLtAAkYDJgAADaxMA=
From: "Nachum Frid" <Nachumf@audiocodes.com>
To: "sipping mailing list" <sipping@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable




The Trascoding function can also be implemented by using 2 party
conference mechanism as described in
draft-burger-sipping-netann-10.txt.=0D
The transcoding session is established there by sending two INVITEs to
Transcoding server, with common "conf=3DID" in SIP URI.


Nachum
AudioCodes


-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of The IESG
Sent: Wednesday, November 24, 2004 6:33 PM
To: IETF-Announce
Cc: sipping chair; Internet Architecture Board; sipping chair; sipping
mailing list; sipping chair; RFC Editor
Subject: [Sipping] Document Action: 'Transcoding Services Invocation in
the Session Initiation Protocol (SIP) Using Third Party Call Control
(3pcc)' to Informational RFC=0D

The IESG has approved the following document:

- 'Transcoding Services Invocation in the Session Initiation Protocol
(SIP)=0D
   Using Third Party Call Control (3pcc) '
   <draft-ietf-sipping-transc-3pcc-02.txt> as an Informational RFC

This document is the product of the Session Initiation Proposal
Investigation=0D
Working Group.=0D

=0D

***************************************************************************=
*********************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity=
 to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and=
 may be unlawful.

If you have received this email in error please notify=
 postmaster@audiocodes.com and permanently delete the e-mail and files.


***************************************************************************=
********************************

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Sun Nov 28 01:32:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28489
	for <sipping-web-archive@ietf.org>; Sun, 28 Nov 2004 01:32:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYIgA-00058K-Ft
	for sipping-web-archive@ietf.org; Sun, 28 Nov 2004 01:37:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYIS3-0004Aa-CC; Sun, 28 Nov 2004 01:22:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYIPY-0003fe-QG
	for sipping@megatron.ietf.org; Sun, 28 Nov 2004 01:19:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27640
	for <sipping@ietf.org>; Sun, 28 Nov 2004 01:19:47 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYITs-0004id-C9
	for sipping@ietf.org; Sun, 28 Nov 2004 01:24:35 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Sat, 27 Nov 2004 22:19:00 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sat, 27 Nov 2004 22:19:00 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 27 Nov 2004 22:19:05 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03C4F4DA@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: Summary of changes for draft-ietf-sipping-conference-package-07
Thread-Index: AcTVEilI+XPsqDrgTmCyZcerUR4h5Q==
From: "Orit Levin" <oritl@microsoft.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 28 Nov 2004 06:19:00.0715 (UTC)
	FILETIME=[269CBBB0:01C4D512]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Subject: [Sipping] Summary of changes for
	draft-ietf-sipping-conference-package-07
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============1886579280=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa

This is a multi-part message in MIME format.

--===============1886579280==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D512.2424B9A2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D512.2424B9A2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

WGLC has ended for draft-ietf-sipping-conference-package-06.

I have incorporated the posted comments in the draft.

They resulted in the following changes since -06:

   o  Whispers are removed.
   o  The version-type is redefined as "unsignedInt".
   o  The <user> elements are grouped in a container named <users>.

   o  The <purpose> element is added to the uri-type and "web-page"
value is defined to be used with <service-uris>.
   o  The <sidebar-by-val> elements are grouped in a container named
<sidebars-by-val>.
   o  The attribute 'entity' of media-type is renamed to 'id'.
   o  The media-state-type is redefined to use SDP values "recvonly",
      "sendonly", "sendrecv", and "inactive".
   o  Sub-elements <snd-state>, and <rcv-state> of media-type are
      removed.
   o  Sub-element <src> of media-type is renamed to <src-id>.

   o  Media sub-elements and types with "state" string are renamed to
contain "status" string instead.

   o  Sub-element <dialog-id> of <sip> is renamed to <call-id>.
   o  The extended-type is removed and the standard XML extension
      conventions are used instead.
   o  Descriptive text and editorial nits are added throughout the
document.

   o  The XML elements and attributes are styled in the descriptive text
according to Miguel's suggestions.

   o  Changes history is removed.

=20

No other major issues have been identified.

I have submitted the draft-ietf-sipping-conference-package-07 and, I
believe, it is ready for the next step in the process.

Best Regards,

Orit.

=20


------_=_NextPart_001_01C4D512.2424B9A2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
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=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>WGLC
has ended for =
draft-ietf-sipping-conference-package-06.</span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>I have
incorporated the posted comments in the draft.</span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>They
resulted in the following changes since -06:</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
o&nbsp; Whispers are removed.<br>
&nbsp;&nbsp; o&nbsp; The version-type is redefined as =
&quot;unsignedInt&quot;.<br>
&nbsp;&nbsp; o&nbsp; The &lt;user&gt; elements are grouped in a =
container named
&lt;users&gt;.</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
o&nbsp; The &lt;purpose&gt; element is added to the uri-type and =
&quot;web-page&quot;
value is defined to be used with &lt;service-uris&gt;.<br>
&nbsp;&nbsp; o&nbsp; The &lt;sidebar-by-val&gt; elements are grouped in =
a
container named &lt;sidebars-by-val&gt;.<br>
&nbsp;&nbsp; o&nbsp; The attribute &#8216;entity&#8217; of media-type is
renamed to &#8216;id&#8217;.<br>
&nbsp;&nbsp; o&nbsp; The media-state-type is redefined to use SDP values
&quot;recvonly&quot;,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;sendonly&quot;, =
&quot;sendrecv&quot;, and
&quot;inactive&quot;.<br>
&nbsp;&nbsp; o&nbsp; Sub-elements &lt;snd-state&gt;, and =
&lt;rcv-state&gt; of media-type
are<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; removed.<br>
&nbsp;&nbsp; o&nbsp; Sub-element &lt;src&gt; of media-type is renamed to =
&lt;src-id&gt;.</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
o&nbsp; Media sub-elements and types with &quot;state&quot; string are =
renamed
to contain &quot;status&quot; string instead.</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;
o&nbsp; Sub-element &lt;dialog-id&gt; of &lt;sip&gt; is renamed to =
&lt;call-id&gt;.<br>
&nbsp;&nbsp; o&nbsp; The extended-type is removed and the standard XML =
extension<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; conventions are used instead.<br>
&nbsp;&nbsp; o&nbsp; Descriptive text&nbsp;and editorial nits =
are&nbsp;added
throughout the document.</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;o&nbsp;
The XML elements and attributes are styled in the descriptive text =
according to
Miguel's suggestions.</span></font></p>

<p class=3DMsoPlainText style=3D'margin:0in;margin-bottom:.0001pt'><font =
size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;o&nbsp;
Changes history is removed.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>No&nbsp;other major issues&nbsp;have been =
identified.</span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>I
have submitted the draft-ietf-sipping-conference-package-07 and, I =
believe,
it&nbsp;is&nbsp;ready for the&nbsp;next step in the =
process.</span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Best
Regards,</span></font></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Orit.</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>

</div>

</body>

</html>

------_=_NextPart_001_01C4D512.2424B9A2--


--===============1886579280==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============1886579280==--



From sipping-bounces@ietf.org  Mon Nov 29 07:17:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11816
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 07:17:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYkXz-0007OJ-Nu
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 07:22:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYkLH-00052C-5p; Mon, 29 Nov 2004 07:09:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYkDo-0003Aq-KR
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 07:01:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02676
	for <sipping@ietf.org>; Mon, 29 Nov 2004 05:16:10 -0500 (EST)
Received: from [212.117.129.245] (helo=fep10.012.net.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYieg-0004m9-Rh
	for sipping@ietf.org; Mon, 29 Nov 2004 05:21:15 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep10.012.net.il with ESMTP
	id <20041129101129.XQKB17592.fep10@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 12:11:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Sipping] Conference speaker control
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 12:11:47 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6A3B@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0Q
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Johnston, Alan" <Alan.Johnston@mci.com>,
        "Oliver Schwaneberg" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "sipping" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable

Hi Alan,
The approach described in the SIP conference package section 6.1.7.3
describes how a RTP mixer will behave, Most conference bridges are not
RTP mixers and will not supply the list of contribution resources.
The current draft is missing this function that identify the current
talked as well as who is being seen in each of the sub windows in a
multi window view.=20
I expect that there will be more information when the package will be
extended as a result of the work in the XCON group.
Roni Even

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Johnston, Alan
Sent: Monday, November 22, 2004 10:23 PM
To: 'Oliver Schwaneberg'; sipping
Subject: RE: [Sipping] Conference speaker controll

Hi Oliver,

An RTP (SSRC) approach is possible using the SIP conference package.
See
Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.  This
has
the advantage of being synchronized with the media (unlike a SIP NOTIFY
approach) but does require the RTP mixer to include SSRC identifiers.

Thanks,
Alan Johnston
sip:alan@sipstation.com

> -----Original Message-----
> From: sipping-bounces@ietf.org=20
> [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> Sent: Monday, November 22, 2004 9:27 AM
> To: sipping
> Subject: [Sipping] Conference speaker controll
>=20
>=20
> Hi everybody!
> I'm new here and I like to know if there's any approach to=20
> determine which participant of an conference is actually talking?
>=20
> For example:
> If you're using a central mixer it would be possible to scan=20
> for talking participants (silence sound suppression, level=20
> detection, etc.). In that case the Mixer could send=20
> NOTIFY-Messages in order to inform every participant about=20
> the talking-state of every other participant.
>=20
> So back to my question: Is there already something like this?
>=20
> Thank you in advance!
>=20
> Oliver Schwaneberg
>=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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov 29 08:28:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18802
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 08:28:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYlfF-00011Q-JA
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 08:34:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYlVJ-0003rX-Gb; Mon, 29 Nov 2004 08:23:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYlJt-0001YM-H0
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 08:11:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17069
	for <sipping@ietf.org>; Mon, 29 Nov 2004 08:11:56 -0500 (EST)
Message-Id: <200411291311.IAA17069@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYlOd-0000Z6-Nz
	for sipping@ietf.org; Mon, 29 Nov 2004 08:17:02 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CYmEW-0005qr-Cy; Mon, 29 Nov 2004 07:10:28 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Johnston, Alan'" <Alan.Johnston@mci.com>,
        "'Oliver Schwaneberg'" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] Conference speaker control
Date: Mon, 29 Nov 2004 08:10:59 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6A3B@IsrExch01.israel.polycom.com>
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmA=
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit

Roni

I'm not following this.  Most conference bridges are not RTP mixers, but if
they aren't RTP mixers than they aren't being used for SIP conferencing.  So
what?  If you have a SIP conference, then you would have an RTP mixing
bridge, you would have SSRCs, and the conference package would work as Alan
suggested, right?  What am I missing here?  Are you suggesting that some SIP
conference bridges don't do this?  If so, should we provide other
mechanisms, or suggest that the bridges should follow the RFC? 

Agree that we need more here than the package as specified provides, but
agree that it's XCON that will work on it.

Brian

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
> Of Even, Roni
> Sent: Monday, November 29, 2004 5:12 AM
> To: Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
> 
> Hi Alan,
> The approach described in the SIP conference package section 6.1.7.3
> describes how a RTP mixer will behave, Most conference bridges are not
> RTP mixers and will not supply the list of contribution resources.
> The current draft is missing this function that identify the current
> talked as well as who is being seen in each of the sub windows in a
> multi window view.
> I expect that there will be more information when the package will be
> extended as a result of the work in the XCON group.
> Roni Even
> 
> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Johnston, Alan
> Sent: Monday, November 22, 2004 10:23 PM
> To: 'Oliver Schwaneberg'; sipping
> Subject: RE: [Sipping] Conference speaker controll
> 
> Hi Oliver,
> 
> An RTP (SSRC) approach is possible using the SIP conference package.
> See
> Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.  This
> has
> the advantage of being synchronized with the media (unlike a SIP NOTIFY
> approach) but does require the RTP mixer to include SSRC identifiers.
> 
> Thanks,
> Alan Johnston
> sip:alan@sipstation.com
> 
> > -----Original Message-----
> > From: sipping-bounces@ietf.org
> > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> > Sent: Monday, November 22, 2004 9:27 AM
> > To: sipping
> > Subject: [Sipping] Conference speaker controll
> >
> >
> > Hi everybody!
> > I'm new here and I like to know if there's any approach to
> > determine which participant of an conference is actually talking?
> >
> > For example:
> > If you're using a central mixer it would be possible to scan
> > for talking participants (silence sound suppression, level
> > detection, etc.). In that case the Mixer could send
> > NOTIFY-Messages in order to inform every participant about
> > the talking-state of every other participant.
> >
> > So back to my question: Is there already something like this?
> >
> > Thank you in advance!
> >
> > Oliver Schwaneberg
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov 29 08:58:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21653
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 08:58:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYm8L-0001ma-1p
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 09:04:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYltt-0000ah-2p; Mon, 29 Nov 2004 08:49:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYloW-00086m-BI
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 08:43:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20403
	for <sipping@ietf.org>; Mon, 29 Nov 2004 08:43:35 -0500 (EST)
Received: from fep4.012.net.il ([212.117.129.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYltQ-0001Nz-J8
	for sipping@ietf.org; Mon, 29 Nov 2004 08:48:41 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep4.012.net.il with ESMTP
	id <20041129134259.WIXC11445.fep4@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 15:42:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Sipping] Conference speaker control
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 15:42:20 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6AB2@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmAAAJr2wA==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Brian Rosen" <br@brianrosen.net>,
        "Johnston, Alan" <Alan.Johnston@mci.com>,
        "Oliver Schwaneberg" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "sipping" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: quoted-printable

Brian,
I will start with my current view of the market.
PSTN bridge do not do RTP so they cab only identify the speaker by
external means.
H.320 conferencing bridges (Video conferencing over ISDN) are not using
RTP and use the control/application layer to specify who the speaker is
and who is being seen.
H.323 conferencing bridges use H.245 means to specify the speaker. The
reasons are that the part that decides who is being seen and who is the
speaker is under the control of what we call the focus and not the RTP
mixer. The bridge is sending more meaningful information then the SSRC
of the current stream like the user name. This applies both to point to
point calls as well as for multipoint calls.

RFC3550 defines mixers and translators in section 7 " In addition to end
systems, RTP supports the notion of "translators" and "mixers", which
could be considered as "intermediate systems" at the RTP level."
These entities are working on the RTP level and are defined to work
without any signaling layer on top of them. That is why RFC3550
describes how they can work without an upper conferencing layer and
explain what they should do with the RTP and RTCP.
We do not have a clear definition of what is a SIP conference bridge but
my assumption is that it has a conferencing application layer on top of
RTP and therefore can give a better description on the application layer
about the speakers. RFC3550 for example do not address multi windows
(Continuous presence) so the contributing sources are not enough to
convey the information about who is being seen in each window.
My suggestion is that we should provide other mechanism to describe the
speaker or who is being viewed that will be based on the conference
application layer and will send the user identification known to the
conference bridge.=20
Roni



-----Original Message-----
From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Monday, November 29, 2004 3:11 PM
To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
Subject: RE: [Sipping] Conference speaker control

Roni

I'm not following this.  Most conference bridges are not RTP mixers, but
if
they aren't RTP mixers than they aren't being used for SIP conferencing.
So
what?  If you have a SIP conference, then you would have an RTP mixing
bridge, you would have SSRCs, and the conference package would work as
Alan
suggested, right?  What am I missing here?  Are you suggesting that some
SIP
conference bridges don't do this?  If so, should we provide other
mechanisms, or suggest that the bridges should follow the RFC?=20

Agree that we need more here than the package as specified provides, but
agree that it's XCON that will work on it.

Brian

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf
> Of Even, Roni
> Sent: Monday, November 29, 2004 5:12 AM
> To: Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
>=20
> Hi Alan,
> The approach described in the SIP conference package section 6.1.7.3
> describes how a RTP mixer will behave, Most conference bridges are not
> RTP mixers and will not supply the list of contribution resources.
> The current draft is missing this function that identify the current
> talked as well as who is being seen in each of the sub windows in a
> multi window view.
> I expect that there will be more information when the package will be
> extended as a result of the work in the XCON group.
> Roni Even
>=20
> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Johnston, Alan
> Sent: Monday, November 22, 2004 10:23 PM
> To: 'Oliver Schwaneberg'; sipping
> Subject: RE: [Sipping] Conference speaker controll
>=20
> Hi Oliver,
>=20
> An RTP (SSRC) approach is possible using the SIP conference package.
> See
> Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.  This
> has
> the advantage of being synchronized with the media (unlike a SIP
NOTIFY
> approach) but does require the RTP mixer to include SSRC identifiers.
>=20
> Thanks,
> Alan Johnston
> sip:alan@sipstation.com
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org
> > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> > Sent: Monday, November 22, 2004 9:27 AM
> > To: sipping
> > Subject: [Sipping] Conference speaker controll
> >
> >
> > Hi everybody!
> > I'm new here and I like to know if there's any approach to
> > determine which participant of an conference is actually talking?
> >
> > For example:
> > If you're using a central mixer it would be possible to scan
> > for talking participants (silence sound suppression, level
> > detection, etc.). In that case the Mixer could send
> > NOTIFY-Messages in order to inform every participant about
> > the talking-state of every other participant.
> >
> > So back to my question: Is there already something like this?
> >
> > Thank you in advance!
> >
> > Oliver Schwaneberg
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
>=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 sipping-bounces@ietf.org  Mon Nov 29 09:15:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23266
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 09:15:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmOk-0002DL-DI
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 09:21:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYm8I-0003UR-UN; Mon, 29 Nov 2004 09:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYm40-0002H9-Or
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 08:59:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21752
	for <sipping@ietf.org>; Mon, 29 Nov 2004 08:59:35 -0500 (EST)
Message-Id: <200411291359.IAA21752@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYm8v-0001mz-Bl
	for sipping@ietf.org; Mon, 29 Nov 2004 09:04:42 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CYmym-00005I-U1; Mon, 29 Nov 2004 07:58:17 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Johnston, Alan'" <Alan.Johnston@mci.com>,
        "'Oliver Schwaneberg'" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] Conference speaker control
Date: Mon, 29 Nov 2004 08:58:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6AB2@IsrExch01.israel.polycom.com>
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmAAAJr2wAABR9LQ
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Content-Transfer-Encoding: 7bit

Roni

I'm leery of providing more than one way to do the same thing.  I'll agree
that the labeling of windows is not covered by existing RTP specs, but I
would hope what we do in XCON does not involve any new system, but merely
extends the information we have to, for example, correlating the SSRCs of
the video stream with the SSRCs of the audio stream, and correlating things
like display names to SSRCs.  We'll have to explore the details, of course,
to see exactly what is needed, and how best to provide it, but I hope we
don't create new mechanisms when existing ones are satisfactory, or can be
made satisfactory with minimal work.

Here in SIPPING, I think that Alan's response is correct, and nothing else
should be said.

Brian

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Monday, November 29, 2004 8:42 AM
> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
> 
> Brian,
> I will start with my current view of the market.
> PSTN bridge do not do RTP so they cab only identify the speaker by
> external means.
> H.320 conferencing bridges (Video conferencing over ISDN) are not using
> RTP and use the control/application layer to specify who the speaker is
> and who is being seen.
> H.323 conferencing bridges use H.245 means to specify the speaker. The
> reasons are that the part that decides who is being seen and who is the
> speaker is under the control of what we call the focus and not the RTP
> mixer. The bridge is sending more meaningful information then the SSRC
> of the current stream like the user name. This applies both to point to
> point calls as well as for multipoint calls.
> 
> RFC3550 defines mixers and translators in section 7 " In addition to end
> systems, RTP supports the notion of "translators" and "mixers", which
> could be considered as "intermediate systems" at the RTP level."
> These entities are working on the RTP level and are defined to work
> without any signaling layer on top of them. That is why RFC3550
> describes how they can work without an upper conferencing layer and
> explain what they should do with the RTP and RTCP.
> We do not have a clear definition of what is a SIP conference bridge but
> my assumption is that it has a conferencing application layer on top of
> RTP and therefore can give a better description on the application layer
> about the speakers. RFC3550 for example do not address multi windows
> (Continuous presence) so the contributing sources are not enough to
> convey the information about who is being seen in each window.
> My suggestion is that we should provide other mechanism to describe the
> speaker or who is being viewed that will be based on the conference
> application layer and will send the user identification known to the
> conference bridge.
> Roni
> 
> 
> 
> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Monday, November 29, 2004 3:11 PM
> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> Subject: RE: [Sipping] Conference speaker control
> 
> Roni
> 
> I'm not following this.  Most conference bridges are not RTP mixers, but
> if
> they aren't RTP mixers than they aren't being used for SIP conferencing.
> So
> what?  If you have a SIP conference, then you would have an RTP mixing
> bridge, you would have SSRCs, and the conference package would work as
> Alan
> suggested, right?  What am I missing here?  Are you suggesting that some
> SIP
> conference bridges don't do this?  If so, should we provide other
> mechanisms, or suggest that the bridges should follow the RFC?
> 
> Agree that we need more here than the package as specified provides, but
> agree that it's XCON that will work on it.
> 
> Brian
> 
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> > Of Even, Roni
> > Sent: Monday, November 29, 2004 5:12 AM
> > To: Johnston, Alan; Oliver Schwaneberg; sipping
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Hi Alan,
> > The approach described in the SIP conference package section 6.1.7.3
> > describes how a RTP mixer will behave, Most conference bridges are not
> > RTP mixers and will not supply the list of contribution resources.
> > The current draft is missing this function that identify the current
> > talked as well as who is being seen in each of the sub windows in a
> > multi window view.
> > I expect that there will be more information when the package will be
> > extended as a result of the work in the XCON group.
> > Roni Even
> >
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf Of Johnston, Alan
> > Sent: Monday, November 22, 2004 10:23 PM
> > To: 'Oliver Schwaneberg'; sipping
> > Subject: RE: [Sipping] Conference speaker controll
> >
> > Hi Oliver,
> >
> > An RTP (SSRC) approach is possible using the SIP conference package.
> > See
> > Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.  This
> > has
> > the advantage of being synchronized with the media (unlike a SIP
> NOTIFY
> > approach) but does require the RTP mixer to include SSRC identifiers.
> >
> > Thanks,
> > Alan Johnston
> > sip:alan@sipstation.com
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org
> > > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> > > Sent: Monday, November 22, 2004 9:27 AM
> > > To: sipping
> > > Subject: [Sipping] Conference speaker controll
> > >
> > >
> > > Hi everybody!
> > > I'm new here and I like to know if there's any approach to
> > > determine which participant of an conference is actually talking?
> > >
> > > For example:
> > > If you're using a central mixer it would be possible to scan
> > > for talking participants (silence sound suppression, level
> > > detection, etc.). In that case the Mixer could send
> > > NOTIFY-Messages in order to inform every participant about
> > > the talking-state of every other participant.
> > >
> > > So back to my question: Is there already something like this?
> > >
> > > Thank you in advance!
> > >
> > > Oliver Schwaneberg
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov 29 09:37:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25179
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 09:37:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmk5-0002ok-Ba
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 09:43:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYmXq-0000O0-Ex; Mon, 29 Nov 2004 09:30:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmFn-0004sb-8p
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 09:11:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23006
	for <sipping@ietf.org>; Mon, 29 Nov 2004 09:11:45 -0500 (EST)
Received: from fep14.012.net.il ([212.117.129.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmKh-00026m-MC
	for sipping@ietf.org; Mon, 29 Nov 2004 09:16:52 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep14.012.net.il with ESMTP
	id <20041129140654.YDKZ13819.fep14@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 16:06:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Sipping] Conference speaker control
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 16:11:15 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6ACF@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmAAAJr2wAABR9LQAACP4DA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Brian Rosen" <br@brianrosen.net>,
        "Johnston, Alan" <Alan.Johnston@mci.com>,
        "Oliver Schwaneberg" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "sipping" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Content-Transfer-Encoding: quoted-printable

Brian,
I am sorry to continue to argument. I thought the view in my reply was
clear. I think that since SIP has a dialog between two endpoint and not
just an RTP session, and since the meaningful information that needs to
be displayed to the user is who is speaking and not what is the ssrc of
the stream that it received, it will make more sense to have this
information coming from a SIP conference bridge as the speaker
indication.
Roni=20

-----Original Message-----
From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Monday, November 29, 2004 3:59 PM
To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
Subject: RE: [Sipping] Conference speaker control

Roni

I'm leery of providing more than one way to do the same thing.  I'll
agree
that the labeling of windows is not covered by existing RTP specs, but I
would hope what we do in XCON does not involve any new system, but
merely
extends the information we have to, for example, correlating the SSRCs
of
the video stream with the SSRCs of the audio stream, and correlating
things
like display names to SSRCs.  We'll have to explore the details, of
course,
to see exactly what is needed, and how best to provide it, but I hope we
don't create new mechanisms when existing ones are satisfactory, or can
be
made satisfactory with minimal work.

Here in SIPPING, I think that Alan's response is correct, and nothing
else
should be said.

Brian

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Monday, November 29, 2004 8:42 AM
> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
>=20
> Brian,
> I will start with my current view of the market.
> PSTN bridge do not do RTP so they cab only identify the speaker by
> external means.
> H.320 conferencing bridges (Video conferencing over ISDN) are not
using
> RTP and use the control/application layer to specify who the speaker
is
> and who is being seen.
> H.323 conferencing bridges use H.245 means to specify the speaker. The
> reasons are that the part that decides who is being seen and who is
the
> speaker is under the control of what we call the focus and not the RTP
> mixer. The bridge is sending more meaningful information then the SSRC
> of the current stream like the user name. This applies both to point
to
> point calls as well as for multipoint calls.
>=20
> RFC3550 defines mixers and translators in section 7 " In addition to
end
> systems, RTP supports the notion of "translators" and "mixers", which
> could be considered as "intermediate systems" at the RTP level."
> These entities are working on the RTP level and are defined to work
> without any signaling layer on top of them. That is why RFC3550
> describes how they can work without an upper conferencing layer and
> explain what they should do with the RTP and RTCP.
> We do not have a clear definition of what is a SIP conference bridge
but
> my assumption is that it has a conferencing application layer on top
of
> RTP and therefore can give a better description on the application
layer
> about the speakers. RFC3550 for example do not address multi windows
> (Continuous presence) so the contributing sources are not enough to
> convey the information about who is being seen in each window.
> My suggestion is that we should provide other mechanism to describe
the
> speaker or who is being viewed that will be based on the conference
> application layer and will send the user identification known to the
> conference bridge.
> Roni
>=20
>=20
>=20
> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Monday, November 29, 2004 3:11 PM
> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>=20
> Roni
>=20
> I'm not following this.  Most conference bridges are not RTP mixers,
but
> if
> they aren't RTP mixers than they aren't being used for SIP
conferencing.
> So
> what?  If you have a SIP conference, then you would have an RTP mixing
> bridge, you would have SSRCs, and the conference package would work as
> Alan
> suggested, right?  What am I missing here?  Are you suggesting that
some
> SIP
> conference bridges don't do this?  If so, should we provide other
> mechanisms, or suggest that the bridges should follow the RFC?
>=20
> Agree that we need more here than the package as specified provides,
but
> agree that it's XCON that will work on it.
>=20
> Brian
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> > Of Even, Roni
> > Sent: Monday, November 29, 2004 5:12 AM
> > To: Johnston, Alan; Oliver Schwaneberg; sipping
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Hi Alan,
> > The approach described in the SIP conference package section 6.1.7.3
> > describes how a RTP mixer will behave, Most conference bridges are
not
> > RTP mixers and will not supply the list of contribution resources.
> > The current draft is missing this function that identify the current
> > talked as well as who is being seen in each of the sub windows in a
> > multi window view.
> > I expect that there will be more information when the package will
be
> > extended as a result of the work in the XCON group.
> > Roni Even
> >
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf Of Johnston, Alan
> > Sent: Monday, November 22, 2004 10:23 PM
> > To: 'Oliver Schwaneberg'; sipping
> > Subject: RE: [Sipping] Conference speaker controll
> >
> > Hi Oliver,
> >
> > An RTP (SSRC) approach is possible using the SIP conference package.
> > See
> > Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.
This
> > has
> > the advantage of being synchronized with the media (unlike a SIP
> NOTIFY
> > approach) but does require the RTP mixer to include SSRC
identifiers.
> >
> > Thanks,
> > Alan Johnston
> > sip:alan@sipstation.com
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org
> > > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> > > Sent: Monday, November 22, 2004 9:27 AM
> > > To: sipping
> > > Subject: [Sipping] Conference speaker controll
> > >
> > >
> > > Hi everybody!
> > > I'm new here and I like to know if there's any approach to
> > > determine which participant of an conference is actually talking?
> > >
> > > For example:
> > > If you're using a central mixer it would be possible to scan
> > > for talking participants (silence sound suppression, level
> > > detection, etc.). In that case the Mixer could send
> > > NOTIFY-Messages in order to inform every participant about
> > > the talking-state of every other participant.
> > >
> > > So back to my question: Is there already something like this?
> > >
> > > Thank you in advance!
> > >
> > > Oliver Schwaneberg
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list
https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the 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
> >
>=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 sipping-bounces@ietf.org  Mon Nov 29 09:48:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26098
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 09:48:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmu7-00033S-Ck
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 09:53:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYmc5-0001jp-Au; Mon, 29 Nov 2004 09:34:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmRl-00079O-Us
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 09:24:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23987
	for <sipping@ietf.org>; Mon, 29 Nov 2004 09:24:08 -0500 (EST)
Message-Id: <200411291424.JAA23987@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmWg-0002Qu-Iw
	for sipping@ietf.org; Mon, 29 Nov 2004 09:29:15 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CYnMa-0001kd-Lv; Mon, 29 Nov 2004 08:22:53 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Johnston, Alan'" <Alan.Johnston@mci.com>,
        "'Oliver Schwaneberg'" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] Conference speaker control
Date: Mon, 29 Nov 2004 09:23:23 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6ACF@IsrExch01.israel.polycom.com>
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmAAAJr2wAABR9LQAACP4DAAAITJcA==
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Content-Transfer-Encoding: 7bit

Roni

Are you proposing to change the SIP Conference Package?

Brian

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Monday, November 29, 2004 9:11 AM
> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
> 
> Brian,
> I am sorry to continue to argument. I thought the view in my reply was
> clear. I think that since SIP has a dialog between two endpoint and not
> just an RTP session, and since the meaningful information that needs to
> be displayed to the user is who is speaking and not what is the ssrc of
> the stream that it received, it will make more sense to have this
> information coming from a SIP conference bridge as the speaker
> indication.
> Roni
> 
> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Monday, November 29, 2004 3:59 PM
> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> Subject: RE: [Sipping] Conference speaker control
> 
> Roni
> 
> I'm leery of providing more than one way to do the same thing.  I'll
> agree
> that the labeling of windows is not covered by existing RTP specs, but I
> would hope what we do in XCON does not involve any new system, but
> merely
> extends the information we have to, for example, correlating the SSRCs
> of
> the video stream with the SSRCs of the audio stream, and correlating
> things
> like display names to SSRCs.  We'll have to explore the details, of
> course,
> to see exactly what is needed, and how best to provide it, but I hope we
> don't create new mechanisms when existing ones are satisfactory, or can
> be
> made satisfactory with minimal work.
> 
> Here in SIPPING, I think that Alan's response is correct, and nothing
> else
> should be said.
> 
> Brian
> 
> > -----Original Message-----
> > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > Sent: Monday, November 29, 2004 8:42 AM
> > To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Brian,
> > I will start with my current view of the market.
> > PSTN bridge do not do RTP so they cab only identify the speaker by
> > external means.
> > H.320 conferencing bridges (Video conferencing over ISDN) are not
> using
> > RTP and use the control/application layer to specify who the speaker
> is
> > and who is being seen.
> > H.323 conferencing bridges use H.245 means to specify the speaker. The
> > reasons are that the part that decides who is being seen and who is
> the
> > speaker is under the control of what we call the focus and not the RTP
> > mixer. The bridge is sending more meaningful information then the SSRC
> > of the current stream like the user name. This applies both to point
> to
> > point calls as well as for multipoint calls.
> >
> > RFC3550 defines mixers and translators in section 7 " In addition to
> end
> > systems, RTP supports the notion of "translators" and "mixers", which
> > could be considered as "intermediate systems" at the RTP level."
> > These entities are working on the RTP level and are defined to work
> > without any signaling layer on top of them. That is why RFC3550
> > describes how they can work without an upper conferencing layer and
> > explain what they should do with the RTP and RTCP.
> > We do not have a clear definition of what is a SIP conference bridge
> but
> > my assumption is that it has a conferencing application layer on top
> of
> > RTP and therefore can give a better description on the application
> layer
> > about the speakers. RFC3550 for example do not address multi windows
> > (Continuous presence) so the contributing sources are not enough to
> > convey the information about who is being seen in each window.
> > My suggestion is that we should provide other mechanism to describe
> the
> > speaker or who is being viewed that will be based on the conference
> > application layer and will send the user identification known to the
> > conference bridge.
> > Roni
> >
> >
> >
> > -----Original Message-----
> > From: Brian Rosen [mailto:br@brianrosen.net]
> > Sent: Monday, November 29, 2004 3:11 PM
> > To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Roni
> >
> > I'm not following this.  Most conference bridges are not RTP mixers,
> but
> > if
> > they aren't RTP mixers than they aren't being used for SIP
> conferencing.
> > So
> > what?  If you have a SIP conference, then you would have an RTP mixing
> > bridge, you would have SSRCs, and the conference package would work as
> > Alan
> > suggested, right?  What am I missing here?  Are you suggesting that
> some
> > SIP
> > conference bridges don't do this?  If so, should we provide other
> > mechanisms, or suggest that the bridges should follow the RFC?
> >
> > Agree that we need more here than the package as specified provides,
> but
> > agree that it's XCON that will work on it.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf
> > > Of Even, Roni
> > > Sent: Monday, November 29, 2004 5:12 AM
> > > To: Johnston, Alan; Oliver Schwaneberg; sipping
> > > Subject: RE: [Sipping] Conference speaker control
> > >
> > > Hi Alan,
> > > The approach described in the SIP conference package section 6.1.7.3
> > > describes how a RTP mixer will behave, Most conference bridges are
> not
> > > RTP mixers and will not supply the list of contribution resources.
> > > The current draft is missing this function that identify the current
> > > talked as well as who is being seen in each of the sub windows in a
> > > multi window view.
> > > I expect that there will be more information when the package will
> be
> > > extended as a result of the work in the XCON group.
> > > Roni Even
> > >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > > Behalf Of Johnston, Alan
> > > Sent: Monday, November 22, 2004 10:23 PM
> > > To: 'Oliver Schwaneberg'; sipping
> > > Subject: RE: [Sipping] Conference speaker controll
> > >
> > > Hi Oliver,
> > >
> > > An RTP (SSRC) approach is possible using the SIP conference package.
> > > See
> > > Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.
> This
> > > has
> > > the advantage of being synchronized with the media (unlike a SIP
> > NOTIFY
> > > approach) but does require the RTP mixer to include SSRC
> identifiers.
> > >
> > > Thanks,
> > > Alan Johnston
> > > sip:alan@sipstation.com
> > >
> > > > -----Original Message-----
> > > > From: sipping-bounces@ietf.org
> > > > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver Schwaneberg
> > > > Sent: Monday, November 22, 2004 9:27 AM
> > > > To: sipping
> > > > Subject: [Sipping] Conference speaker controll
> > > >
> > > >
> > > > Hi everybody!
> > > > I'm new here and I like to know if there's any approach to
> > > > determine which participant of an conference is actually talking?
> > > >
> > > > For example:
> > > > If you're using a central mixer it would be possible to scan
> > > > for talking participants (silence sound suppression, level
> > > > detection, etc.). In that case the Mixer could send
> > > > NOTIFY-Messages in order to inform every participant about
> > > > the talking-state of every other participant.
> > > >
> > > > So back to my question: Is there already something like this?
> > > >
> > > > Thank you in advance!
> > > >
> > > > Oliver Schwaneberg
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the 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 sipping-bounces@ietf.org  Mon Nov 29 09:53:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26633
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 09:53:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYmz8-0003EU-Pj
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 09:58:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYmox-0004Dt-Dp; Mon, 29 Nov 2004 09:48:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmZi-0000zV-Fi
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 09:32:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24864
	for <sipping@ietf.org>; Mon, 29 Nov 2004 09:32:21 -0500 (EST)
Received: from fep10.012.net.il ([212.117.129.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmec-0002ga-W0
	for sipping@ietf.org; Mon, 29 Nov 2004 09:37:27 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep10.012.net.il with ESMTP
	id <20041129143131.YSIW17592.fep10@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 16:31:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Sipping] Conference speaker control
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 16:31:49 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6ADA@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTQ1FtSbSHZSMOdQ4KRwtZMaPjr9gFJjx0QAAYbvmAAAJr2wAABR9LQAACP4DAAAITJcAAAP2TQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Brian Rosen" <br@brianrosen.net>,
        "Johnston, Alan" <Alan.Johnston@mci.com>,
        "Oliver Schwaneberg" <oliver.schwaneberg@fokus.fraunhofer.de>,
        "sipping" <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935
Content-Transfer-Encoding: quoted-printable

Brian,
My view is that it should include this information and I talked with
Orit about it. I think that Orit suggested adding the speaker
information when we extend it for XCON
Roni

-----Original Message-----
From: Brian Rosen [mailto:br@brianrosen.net]=20
Sent: Monday, November 29, 2004 4:23 PM
To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
Subject: RE: [Sipping] Conference speaker control

Roni

Are you proposing to change the SIP Conference Package?

Brian

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Monday, November 29, 2004 9:11 AM
> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> Subject: RE: [Sipping] Conference speaker control
>=20
> Brian,
> I am sorry to continue to argument. I thought the view in my reply was
> clear. I think that since SIP has a dialog between two endpoint and
not
> just an RTP session, and since the meaningful information that needs
to
> be displayed to the user is who is speaking and not what is the ssrc
of
> the stream that it received, it will make more sense to have this
> information coming from a SIP conference bridge as the speaker
> indication.
> Roni
>=20
> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Monday, November 29, 2004 3:59 PM
> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>=20
> Roni
>=20
> I'm leery of providing more than one way to do the same thing.  I'll
> agree
> that the labeling of windows is not covered by existing RTP specs, but
I
> would hope what we do in XCON does not involve any new system, but
> merely
> extends the information we have to, for example, correlating the SSRCs
> of
> the video stream with the SSRCs of the audio stream, and correlating
> things
> like display names to SSRCs.  We'll have to explore the details, of
> course,
> to see exactly what is needed, and how best to provide it, but I hope
we
> don't create new mechanisms when existing ones are satisfactory, or
can
> be
> made satisfactory with minimal work.
>=20
> Here in SIPPING, I think that Alan's response is correct, and nothing
> else
> should be said.
>=20
> Brian
>=20
> > -----Original Message-----
> > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > Sent: Monday, November 29, 2004 8:42 AM
> > To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Brian,
> > I will start with my current view of the market.
> > PSTN bridge do not do RTP so they cab only identify the speaker by
> > external means.
> > H.320 conferencing bridges (Video conferencing over ISDN) are not
> using
> > RTP and use the control/application layer to specify who the speaker
> is
> > and who is being seen.
> > H.323 conferencing bridges use H.245 means to specify the speaker.
The
> > reasons are that the part that decides who is being seen and who is
> the
> > speaker is under the control of what we call the focus and not the
RTP
> > mixer. The bridge is sending more meaningful information then the
SSRC
> > of the current stream like the user name. This applies both to point
> to
> > point calls as well as for multipoint calls.
> >
> > RFC3550 defines mixers and translators in section 7 " In addition to
> end
> > systems, RTP supports the notion of "translators" and "mixers",
which
> > could be considered as "intermediate systems" at the RTP level."
> > These entities are working on the RTP level and are defined to work
> > without any signaling layer on top of them. That is why RFC3550
> > describes how they can work without an upper conferencing layer and
> > explain what they should do with the RTP and RTCP.
> > We do not have a clear definition of what is a SIP conference bridge
> but
> > my assumption is that it has a conferencing application layer on top
> of
> > RTP and therefore can give a better description on the application
> layer
> > about the speakers. RFC3550 for example do not address multi windows
> > (Continuous presence) so the contributing sources are not enough to
> > convey the information about who is being seen in each window.
> > My suggestion is that we should provide other mechanism to describe
> the
> > speaker or who is being viewed that will be based on the conference
> > application layer and will send the user identification known to the
> > conference bridge.
> > Roni
> >
> >
> >
> > -----Original Message-----
> > From: Brian Rosen [mailto:br@brianrosen.net]
> > Sent: Monday, November 29, 2004 3:11 PM
> > To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Roni
> >
> > I'm not following this.  Most conference bridges are not RTP mixers,
> but
> > if
> > they aren't RTP mixers than they aren't being used for SIP
> conferencing.
> > So
> > what?  If you have a SIP conference, then you would have an RTP
mixing
> > bridge, you would have SSRCs, and the conference package would work
as
> > Alan
> > suggested, right?  What am I missing here?  Are you suggesting that
> some
> > SIP
> > conference bridges don't do this?  If so, should we provide other
> > mechanisms, or suggest that the bridges should follow the RFC?
> >
> > Agree that we need more here than the package as specified provides,
> but
> > agree that it's XCON that will work on it.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
On
> > Behalf
> > > Of Even, Roni
> > > Sent: Monday, November 29, 2004 5:12 AM
> > > To: Johnston, Alan; Oliver Schwaneberg; sipping
> > > Subject: RE: [Sipping] Conference speaker control
> > >
> > > Hi Alan,
> > > The approach described in the SIP conference package section
6.1.7.3
> > > describes how a RTP mixer will behave, Most conference bridges are
> not
> > > RTP mixers and will not supply the list of contribution resources.
> > > The current draft is missing this function that identify the
current
> > > talked as well as who is being seen in each of the sub windows in
a
> > > multi window view.
> > > I expect that there will be more information when the package will
> be
> > > extended as a result of the work in the XCON group.
> > > Roni Even
> > >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
On
> > > Behalf Of Johnston, Alan
> > > Sent: Monday, November 22, 2004 10:23 PM
> > > To: 'Oliver Schwaneberg'; sipping
> > > Subject: RE: [Sipping] Conference speaker controll
> > >
> > > Hi Oliver,
> > >
> > > An RTP (SSRC) approach is possible using the SIP conference
package.
> > > See
> > > Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.
> This
> > > has
> > > the advantage of being synchronized with the media (unlike a SIP
> > NOTIFY
> > > approach) but does require the RTP mixer to include SSRC
> identifiers.
> > >
> > > Thanks,
> > > Alan Johnston
> > > sip:alan@sipstation.com
> > >
> > > > -----Original Message-----
> > > > From: sipping-bounces@ietf.org
> > > > [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver
Schwaneberg
> > > > Sent: Monday, November 22, 2004 9:27 AM
> > > > To: sipping
> > > > Subject: [Sipping] Conference speaker controll
> > > >
> > > >
> > > > Hi everybody!
> > > > I'm new here and I like to know if there's any approach to
> > > > determine which participant of an conference is actually
talking?
> > > >
> > > > For example:
> > > > If you're using a central mixer it would be possible to scan
> > > > for talking participants (silence sound suppression, level
> > > > detection, etc.). In that case the Mixer could send
> > > > NOTIFY-Messages in order to inform every participant about
> > > > the talking-state of every other participant.
> > > >
> > > > So back to my question: Is there already something like this?
> > > >
> > > > Thank you in advance!
> > > >
> > > > Oliver Schwaneberg
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the 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
> > >
> >
> >
> >
> >
>=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 sipping-bounces@ietf.org  Mon Nov 29 10:26:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01080
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 10:26:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYnVS-000476-Oa
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 10:32:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYnH5-0006O7-6V; Mon, 29 Nov 2004 10:17:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYnBn-0004I5-J5
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 10:11:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28832
	for <sipping@ietf.org>; Mon, 29 Nov 2004 10:11:41 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYnGY-0003iE-Kl
	for sipping@ietf.org; Mon, 29 Nov 2004 10:16:49 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iATFBVh5021547
	for <sipping@ietf.org>; Mon, 29 Nov 2004 16:11:31 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 29 Nov 2004 16:11:29 +0100
Received: from [147.214.34.68] (E-A75D10B0ED7B4.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt611.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id WHLTSHHR; Mon, 29 Nov 2004 16:11:29 +0100
Message-ID: <41AB3C20.3090706@ericsson.com>
Date: Mon, 29 Nov 2004 16:11:28 +0100
X-Sybari-Trust: 3f0939ab a5e9b67f 2b3f5727 00000139
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [Sipping] Conference speaker control
References: <144ED8561CE90C41A3E5908EDECE315C5C6ACF@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6ACF@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Nov 2004 15:11:29.0283 (UTC)
	FILETIME=[B3DB1530:01C4D625]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

Hi Roni,

Sorry if I do not have a full picture of the architecture of the 
conferencing. Please enlighten me if I overstep any previous agreements.


Even, Roni wrote:

> Brian,
> I am sorry to continue to argument. I thought the view in my reply was
> clear. I think that since SIP has a dialog between two endpoint and not
> just an RTP session, and since the meaningful information that needs to
> be displayed to the user is who is speaking and not what is the ssrc of
> the stream that it received, it will make more sense to have this
> information coming from a SIP conference bridge as the speaker
> indication.

RTP with RTCP does have the mechanism to provide a receiver with the 
name or at least the CNAME for all SSRCs that are used in all media 
streams. That way one can identify the actual media senders. It might be 
beneficial depending on the conferencing side functions to bind the 
CNAME to some RTP/RTCP external user identification. Thus including 
CNAME in the state package may be beneficial, instead of needing to 
provide SSRC for all participants in all media streams. It would reduce 
the data  points with a factor equal to the number of media.

Is the issue that you don't think media reception from a specific SSRC a 
good indication that the source is active? Otherwise I don't see the 
reason to not utilize the functionality present in RTP/RTCP.

In regards to RTP mixer I would like to point out that the conference 
bridge must not necessarily be a mixer, it could be a relay. If the 
bridge simply forwards all packets from all participants RTP and RTCP to 
  everybody, no mixing is necessary. The downside is that the media 
amount gets increased every time more than one transmits data. This of 
course has its issue with users that has a limited bandwidth. The higher 
the bit-rate of the media the more sensible it seems to do mixing. But 
mixing T.140 conference text seems rather unnecessary.

cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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 sipping-bounces@ietf.org  Mon Nov 29 10:37:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02196
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 10:37:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYnfa-0004Lo-8L
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 10:42:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYnRj-000234-LO; Mon, 29 Nov 2004 10:28:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYnJx-0007VB-CT
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 10:20:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00093
	for <sipping@ietf.org>; Mon, 29 Nov 2004 10:20:07 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYnOr-0003vt-FE
	for sipping@ietf.org; Mon, 29 Nov 2004 10:25:15 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 29 Nov 2004 07:23:58 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iATFJMAC022512;
	Mon, 29 Nov 2004 07:19:23 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iATFJ7oI024712;
	Mon, 29 Nov 2004 07:19:07 -0800
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6ADA@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C5C6ADA@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0FAE5064-421A-11D9-8CD3-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Conference speaker control
Date: Mon, 29 Nov 2004 10:19:28 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101741549.482440"; x:"432200"; a:"rsa-sha1"; b:"nofws:10653";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"Waqr5M87HUHO/Z+HEfAo80bcKkGTL/AH3wMX5XjLVQYg09B9h9bBeuGYChovN"
	"uHy2aax1Z3TuBj7awIX9IBk/FG1uER+7j+vjKebjVvSBb4CeqVpp/OTmIt/XK"
	"r26C+F+ajCd++0q8Vzy29aT5GocYqpJRRqliaCBk9ufsZyTBo=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Conference speaker control";
	c:"Date: Mon, 29 Nov 2004 10:19:28 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7118f330e2af0a096ba071c5e99ca10e
Content-Transfer-Encoding: 7bit
Cc: "Johnston, Alan" <Alan.Johnston@mci.com>, sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e267523e0685e5aa2dbbdde4b659686
Content-Transfer-Encoding: 7bit

I come down pretty strongly on the side of simply declaring that 
SIP/XCON conference bridges use RTP in the media plane and hence mix 
using RFC2550 mixing procedures. This means they include CSRCs in the 
output stream(s).

Following from this, it seems that the conference control and info 
protocol machinery should indicate who is/are speaking by referencing 
the CSRCs of the contributing streams. The actual identity could either 
be derived from the SDES of the input stream or a purely SIP control 
plane mechanism.

Remember that this applies to video as well in the case of video mixers 
that do compositing.

I'd further like to note that there are a number of very good reasons 
why an XCOM-compliant conference bridge ought to be an 
RFC3550-compliant RTP mixer/translator - the speaker identification 
machinery is only one of many.

Dave.
On Nov 29, 2004, at 9:31 AM, Even, Roni wrote:

> Brian,
> My view is that it should include this information and I talked with
> Orit about it. I think that Orit suggested adding the speaker
> information when we extend it for XCON
> Roni
>
> -----Original Message-----
> From: Brian Rosen [mailto:br@brianrosen.net]
> Sent: Monday, November 29, 2004 4:23 PM
> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>
> Roni
>
> Are you proposing to change the SIP Conference Package?
>
> Brian
>
>> -----Original Message-----
>> From: Even, Roni [mailto:roni.even@polycom.co.il]
>> Sent: Monday, November 29, 2004 9:11 AM
>> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
>> Subject: RE: [Sipping] Conference speaker control
>>
>> Brian,
>> I am sorry to continue to argument. I thought the view in my reply was
>> clear. I think that since SIP has a dialog between two endpoint and
> not
>> just an RTP session, and since the meaningful information that needs
> to
>> be displayed to the user is who is speaking and not what is the ssrc
> of
>> the stream that it received, it will make more sense to have this
>> information coming from a SIP conference bridge as the speaker
>> indication.
>> Roni
>>
>> -----Original Message-----
>> From: Brian Rosen [mailto:br@brianrosen.net]
>> Sent: Monday, November 29, 2004 3:59 PM
>> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
>> Subject: RE: [Sipping] Conference speaker control
>>
>> Roni
>>
>> I'm leery of providing more than one way to do the same thing.  I'll
>> agree
>> that the labeling of windows is not covered by existing RTP specs, but
> I
>> would hope what we do in XCON does not involve any new system, but
>> merely
>> extends the information we have to, for example, correlating the SSRCs
>> of
>> the video stream with the SSRCs of the audio stream, and correlating
>> things
>> like display names to SSRCs.  We'll have to explore the details, of
>> course,
>> to see exactly what is needed, and how best to provide it, but I hope
> we
>> don't create new mechanisms when existing ones are satisfactory, or
> can
>> be
>> made satisfactory with minimal work.
>>
>> Here in SIPPING, I think that Alan's response is correct, and nothing
>> else
>> should be said.
>>
>> Brian
>>
>>> -----Original Message-----
>>> From: Even, Roni [mailto:roni.even@polycom.co.il]
>>> Sent: Monday, November 29, 2004 8:42 AM
>>> To: Brian Rosen; Johnston, Alan; Oliver Schwaneberg; sipping
>>> Subject: RE: [Sipping] Conference speaker control
>>>
>>> Brian,
>>> I will start with my current view of the market.
>>> PSTN bridge do not do RTP so they cab only identify the speaker by
>>> external means.
>>> H.320 conferencing bridges (Video conferencing over ISDN) are not
>> using
>>> RTP and use the control/application layer to specify who the speaker
>> is
>>> and who is being seen.
>>> H.323 conferencing bridges use H.245 means to specify the speaker.
> The
>>> reasons are that the part that decides who is being seen and who is
>> the
>>> speaker is under the control of what we call the focus and not the
> RTP
>>> mixer. The bridge is sending more meaningful information then the
> SSRC
>>> of the current stream like the user name. This applies both to point
>> to
>>> point calls as well as for multipoint calls.
>>>
>>> RFC3550 defines mixers and translators in section 7 " In addition to
>> end
>>> systems, RTP supports the notion of "translators" and "mixers",
> which
>>> could be considered as "intermediate systems" at the RTP level."
>>> These entities are working on the RTP level and are defined to work
>>> without any signaling layer on top of them. That is why RFC3550
>>> describes how they can work without an upper conferencing layer and
>>> explain what they should do with the RTP and RTCP.
>>> We do not have a clear definition of what is a SIP conference bridge
>> but
>>> my assumption is that it has a conferencing application layer on top
>> of
>>> RTP and therefore can give a better description on the application
>> layer
>>> about the speakers. RFC3550 for example do not address multi windows
>>> (Continuous presence) so the contributing sources are not enough to
>>> convey the information about who is being seen in each window.
>>> My suggestion is that we should provide other mechanism to describe
>> the
>>> speaker or who is being viewed that will be based on the conference
>>> application layer and will send the user identification known to the
>>> conference bridge.
>>> Roni
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Brian Rosen [mailto:br@brianrosen.net]
>>> Sent: Monday, November 29, 2004 3:11 PM
>>> To: Even, Roni; 'Johnston, Alan'; 'Oliver Schwaneberg'; 'sipping'
>>> Subject: RE: [Sipping] Conference speaker control
>>>
>>> Roni
>>>
>>> I'm not following this.  Most conference bridges are not RTP mixers,
>> but
>>> if
>>> they aren't RTP mixers than they aren't being used for SIP
>> conferencing.
>>> So
>>> what?  If you have a SIP conference, then you would have an RTP
> mixing
>>> bridge, you would have SSRCs, and the conference package would work
> as
>>> Alan
>>> suggested, right?  What am I missing here?  Are you suggesting that
>> some
>>> SIP
>>> conference bridges don't do this?  If so, should we provide other
>>> mechanisms, or suggest that the bridges should follow the RFC?
>>>
>>> Agree that we need more here than the package as specified provides,
>> but
>>> agree that it's XCON that will work on it.
>>>
>>> Brian
>>>
>>>> -----Original Message-----
>>>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
> On
>>> Behalf
>>>> Of Even, Roni
>>>> Sent: Monday, November 29, 2004 5:12 AM
>>>> To: Johnston, Alan; Oliver Schwaneberg; sipping
>>>> Subject: RE: [Sipping] Conference speaker control
>>>>
>>>> Hi Alan,
>>>> The approach described in the SIP conference package section
> 6.1.7.3
>>>> describes how a RTP mixer will behave, Most conference bridges are
>> not
>>>> RTP mixers and will not supply the list of contribution resources.
>>>> The current draft is missing this function that identify the
> current
>>>> talked as well as who is being seen in each of the sub windows in
> a
>>>> multi window view.
>>>> I expect that there will be more information when the package will
>> be
>>>> extended as a result of the work in the XCON group.
>>>> Roni Even
>>>>
>>>> -----Original Message-----
>>>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
> On
>>>> Behalf Of Johnston, Alan
>>>> Sent: Monday, November 22, 2004 10:23 PM
>>>> To: 'Oliver Schwaneberg'; sipping
>>>> Subject: RE: [Sipping] Conference speaker controll
>>>>
>>>> Hi Oliver,
>>>>
>>>> An RTP (SSRC) approach is possible using the SIP conference
> package.
>>>> See
>>>> Section 6.1.7.3 of draft-ietf-sipping-conference-package-06.txt.
>> This
>>>> has
>>>> the advantage of being synchronized with the media (unlike a SIP
>>> NOTIFY
>>>> approach) but does require the RTP mixer to include SSRC
>> identifiers.
>>>>
>>>> Thanks,
>>>> Alan Johnston
>>>> sip:alan@sipstation.com
>>>>
>>>>> -----Original Message-----
>>>>> From: sipping-bounces@ietf.org
>>>>> [mailto:sipping-bounces@ietf.org] On Behalf Of Oliver
> Schwaneberg
>>>>> Sent: Monday, November 22, 2004 9:27 AM
>>>>> To: sipping
>>>>> Subject: [Sipping] Conference speaker controll
>>>>>
>>>>>
>>>>> Hi everybody!
>>>>> I'm new here and I like to know if there's any approach to
>>>>> determine which participant of an conference is actually
> talking?
>>>>>
>>>>> For example:
>>>>> If you're using a central mixer it would be possible to scan
>>>>> for talking participants (silence sound suppression, level
>>>>> detection, etc.). In that case the Mixer could send
>>>>> NOTIFY-Messages in order to inform every participant about
>>>>> the talking-state of every other participant.
>>>>>
>>>>> So back to my question: Is there already something like this?
>>>>>
>>>>> Thank you in advance!
>>>>>
>>>>> Oliver Schwaneberg
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Sipping mailing list
>> https://www1.ietf.org/mailman/listinfo/sipping
>>>>> This list is for NEW development of the 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
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Mon Nov 29 10:47:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03038
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 10:47:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYnpc-0004ah-R8
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 10:52:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYnXL-0003dL-VP; Mon, 29 Nov 2004 10:34:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYnQX-0001XI-HF
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 10:26:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01076
	for <sipping@ietf.org>; Mon, 29 Nov 2004 10:26:55 -0500 (EST)
Received: from fep10.012.net.il ([212.117.129.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYnVR-00045p-JT
	for sipping@ietf.org; Mon, 29 Nov 2004 10:32:03 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep10.012.net.il with ESMTP
	id <20041129152600.YXXM17592.fep10@isrexch01.israel.polycom.com>;
	Mon, 29 Nov 2004 17:26:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Sipping] Conference speaker control
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 17:26:16 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C5C6B04@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTWJf9XFCd8+FkISXuoJpOJYrku4gAAJaIA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: quoted-printable
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: quoted-printable

Magnus,
I am not saying that RTP using SSRC does not have a mechanism to
identify the source of the streams. What I am trying to say is that we
are not talking about a pure RTP mixer but we are talking about a SIP
based conferencing server and in XCON the scope is even wider, it may be
a PSTN bridge bellow.=20
So first of all there is no requirement defined that the mixer in SIP
conferencing or XCON should be a RTP mixer per RFC3550. Even if we do it
for SIPPING then we will have a problem for PSTN Bridge (example of
usage if for audio-graphic conference) and it will break for XCON.
Roni Even




-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Monday, November 29, 2004 5:11 PM
To: Even, Roni
Cc: sipping
Subject: Re: [Sipping] Conference speaker control

Hi Roni,

Sorry if I do not have a full picture of the architecture of the=20
conferencing. Please enlighten me if I overstep any previous agreements.


Even, Roni wrote:

> Brian,
> I am sorry to continue to argument. I thought the view in my reply was
> clear. I think that since SIP has a dialog between two endpoint and
not
> just an RTP session, and since the meaningful information that needs
to
> be displayed to the user is who is speaking and not what is the ssrc
of
> the stream that it received, it will make more sense to have this
> information coming from a SIP conference bridge as the speaker
> indication.

RTP with RTCP does have the mechanism to provide a receiver with the=20
name or at least the CNAME for all SSRCs that are used in all media=20
streams. That way one can identify the actual media senders. It might be

beneficial depending on the conferencing side functions to bind the=20
CNAME to some RTP/RTCP external user identification. Thus including=20
CNAME in the state package may be beneficial, instead of needing to=20
provide SSRC for all participants in all media streams. It would reduce=20
the data  points with a factor equal to the number of media.

Is the issue that you don't think media reception from a specific SSRC a

good indication that the source is active? Otherwise I don't see the=20
reason to not utilize the functionality present in RTP/RTCP.

In regards to RTP mixer I would like to point out that the conference=20
bridge must not necessarily be a mixer, it could be a relay. If the=20
bridge simply forwards all packets from all participants RTP and RTCP to

  everybody, no mixing is necessary. The downside is that the media=20
amount gets increased every time more than one transmits data. This of=20
course has its issue with users that has a limited bandwidth. The higher

the bit-rate of the media the more sensible it seems to do mixing. But=20
mixing T.140 conference text seems rather unnecessary.

cheers

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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 sipping-bounces@ietf.org  Mon Nov 29 11:08:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04921
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 11:08:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYo9U-00055a-16
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 11:13:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYnmw-00074n-RI; Mon, 29 Nov 2004 10:50:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYni1-0005cd-VR
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 10:45:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02831
	for <sipping@ietf.org>; Mon, 29 Nov 2004 10:45:00 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYnmn-0004Wy-71
	for sipping@ietf.org; Mon, 29 Nov 2004 10:50:07 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iATFinR2004815
	for <sipping@ietf.org>; Mon, 29 Nov 2004 16:44:49 +0100
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 29 Nov 2004 16:44:49 +0100
Received: from [147.214.34.68] (E-A75D10B0ED7B4.ki.sw.ericsson.se
	[147.214.34.68]) by esealnt613.al.sw.ericsson.se with SMTP
	(Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id X4Z4SA3K; Mon, 29 Nov 2004 16:44:49 +0100
Message-ID: <41AB43F0.4070208@ericsson.com>
Date: Mon, 29 Nov 2004 16:44:48 +0100
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: "Even, Roni" <roni.even@polycom.co.il>
Subject: Re: [Sipping] Conference speaker control
References: <144ED8561CE90C41A3E5908EDECE315C5C6B04@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C5C6B04@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Nov 2004 15:44:49.0315 (UTC)
	FILETIME=[5BF7BF30:01C4D62A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit

Hi Roni,

Lets see if I understand this correctly. You are worried about PSTN or 
other gateways that are receiving more than one source over the same 
circuit and in which cases the gateway can't separate the different 
sources within the CS to IP gateway. As long as the PSTN gateway 
receives the different circuit switched sources in the same conference 
on different circuits, it is able to assign them different SSRCs and IDs.

If the above is the case, how would adding any other mechanism help? The 
gateway can still not identify the original sources, or am I 
misunderstanding something about the setup?

My understanding of the setup you are concern is:


CS1 --\
        -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
CS2 --/                  ^               ^
                          |               |
                         CS5           Client 4

In this case Client 3 and 4 would not be able to determine that what is 
beyond the gateway is in fact three client. CS1 and CS2 will be bunched 
together under one source identifier? While CS5 can be identified as it 
connects directly with the gateway and uses a separate CS line into the 
gateway, thus allowing the gateway to give them separate IDs.

It should also not be a problem if the protocol used on the CS side 
provides identities, then the gateway can provide different identifiers 
for the different CS side users.

Cheers

Magnus

Even, Roni wrote:

> Magnus,
> I am not saying that RTP using SSRC does not have a mechanism to
> identify the source of the streams. What I am trying to say is that we
> are not talking about a pure RTP mixer but we are talking about a SIP
> based conferencing server and in XCON the scope is even wider, it may be
> a PSTN bridge bellow.
> So first of all there is no requirement defined that the mixer in SIP
> conferencing or XCON should be a RTP mixer per RFC3550. Even if we do it
> for SIPPING then we will have a problem for PSTN Bridge (example of
> usage if for audio-graphic conference) and it will break for XCON.
> Roni Even


-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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 sipping-bounces@ietf.org  Mon Nov 29 20:54:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08223
	for <sipping-web-archive@ietf.org>; Mon, 29 Nov 2004 20:54:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYxIX-0005k5-7s
	for sipping-web-archive@ietf.org; Mon, 29 Nov 2004 20:59:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYxA8-0004Dt-14; Mon, 29 Nov 2004 20:50:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYx8P-0003vU-FW
	for sipping@megatron.ietf.org; Mon, 29 Nov 2004 20:48:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07904
	for <sipping@ietf.org>; Mon, 29 Nov 2004 20:48:52 -0500 (EST)
Received: from omzesmtp04.mci.com ([199.249.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYxDL-0005do-ST
	for sipping@ietf.org; Mon, 29 Nov 2004 20:54:05 -0500
Received: from pmismtp01.mcilink.com ([166.38.62.36])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I7Y00L6NYCHMF@firewall.mci.com> for sipping@ietf.org;
	Tue, 30 Nov 2004 01:48:17 +0000 (GMT)
Received: from pmismtp01.mcilink.com by pmismtp01.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I7Y00601YBXS7@pmismtp01.mcilink.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 01:48:17 +0000 (GMT)
Received: from dgexch50.wcomnet.com ([166.38.58.238])
	by pmismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I7Y0061QYCBJV@pmismtp01.mcilink.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 01:48:11 +0000 (GMT)
Received: by DGEXCH50.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <X5H06WTH>; Tue, 30 Nov 2004 01:48:11 +0000
Content-return: allowed
Date: Tue, 30 Nov 2004 01:48:10 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
To: sipping <sipping@ietf.org>
Message-id: <EB7597BFB1C65844898A6D153DE09DB50895C5@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Orit Levin <oritl@microsoft.com>
Subject: [Sipping] Changes in draft-ietf-sipping-cc-conferencing-06.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

All,

Based on WGLC feedback, I have updated cc-conferencing and submitted as
draft-ietf-sipping-cc-conferencing-06.txt.

Changes from version -05 include:

 - Updated conference package examples to match latest schema
 - Clarified focus should act as a notifier
 - Fixed formatting errors in Refer-To header fields
 - Fixed SDP nits
 - Renamed section headings for more clarity
 - Added note about UA support of redirections
 - Added clarification about rendering conference package info to user
 - Corrected GRUU informative reference
 - Updated references
 - Misc wording changes

I believe the draft is now ready for IETF Last Call with the other SIP
conferencing drafts.

Thanks,
Alan Johnston
MCI
sip:alan@sipstation.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 sipping-bounces@ietf.org  Tue Nov 30 03:55:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22393
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 03:55:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ3sO-0005Te-EL
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 04:00:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ3l8-0007mP-0U; Tue, 30 Nov 2004 03:53:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ3fy-0005yO-LG
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 03:47:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21807
	for <sipping@ietf.org>; Tue, 30 Nov 2004 03:47:56 -0500 (EST)
Received: from fep2.012.net.il ([212.117.129.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ3l2-0005J5-JN
	for sipping@ietf.org; Tue, 30 Nov 2004 03:53:13 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep2.012.net.il with ESMTP
	id <20041130084714.GBDZ9868.fep2@isrexch01.israel.polycom.com>;
	Tue, 30 Nov 2004 10:47:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Conference speaker control
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Nov 2004 10:45:59 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C7090AF@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTWKvXtPmbv77nEToKg4F9J0NdQPAAjRh2Q
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: quoted-printable

Magnus,
The problem you stated is correct but this is not what I meant. In XCON
conference server can be composed of a conference/media policy server
and a focus that can be an application server that handle conference
policy and some web collaboration while the mixer is a PSTN bridge.=20
A participant in such a conference is using a PSTN phone and a PC for
web collaboration and conference control. The PC can subscribe to the
conference package but since the audio is PSTN there are no RTP or SSRC.
Even for IP conferencing making an assumption that all streams in a
conference are RTP streams is not always right, so ssrc cannot be used
to describe who is sourcing each stream in an application that uses a
mix of RTP and non RTP streams.
Roni Even

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Monday, November 29, 2004 5:45 PM
To: Even, Roni
Cc: sipping
Subject: Re: [Sipping] Conference speaker control

Hi Roni,

Lets see if I understand this correctly. You are worried about PSTN or=20
other gateways that are receiving more than one source over the same=20
circuit and in which cases the gateway can't separate the different=20
sources within the CS to IP gateway. As long as the PSTN gateway=20
receives the different circuit switched sources in the same conference=20
on different circuits, it is able to assign them different SSRCs and
IDs.

If the above is the case, how would adding any other mechanism help? The

gateway can still not identify the original sources, or am I=20
misunderstanding something about the setup?

My understanding of the setup you are concern is:


CS1 --\
        -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
CS2 --/                  ^               ^
                          |               |
                         CS5           Client 4

In this case Client 3 and 4 would not be able to determine that what is=20
beyond the gateway is in fact three client. CS1 and CS2 will be bunched=20
together under one source identifier? While CS5 can be identified as it=20
connects directly with the gateway and uses a separate CS line into the=20
gateway, thus allowing the gateway to give them separate IDs.

It should also not be a problem if the protocol used on the CS side=20
provides identities, then the gateway can provide different identifiers=20
for the different CS side users.

Cheers

Magnus

Even, Roni wrote:

> Magnus,
> I am not saying that RTP using SSRC does not have a mechanism to
> identify the source of the streams. What I am trying to say is that we
> are not talking about a pure RTP mixer but we are talking about a SIP
> based conferencing server and in XCON the scope is even wider, it may
be
> a PSTN bridge bellow.
> So first of all there is no requirement defined that the mixer in SIP
> conferencing or XCON should be a RTP mixer per RFC3550. Even if we do
it
> for SIPPING then we will have a problem for PSTN Bridge (example of
> usage if for audio-graphic conference) and it will break for XCON.
> Roni Even


--=20

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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 sipping-bounces@ietf.org  Tue Nov 30 05:35:42 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02801
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 05:35:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ5RM-0007n4-JU
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 05:41:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ5HO-00045v-PN; Tue, 30 Nov 2004 05:30:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ56W-0001WI-FG
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 05:19:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01243
	for <sipping@ietf.org>; Tue, 30 Nov 2004 05:19:26 -0500 (EST)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ5Ba-0007J2-P7
	for sipping@ietf.org; Tue, 30 Nov 2004 05:24:44 -0500
Received: from RajeshK ([127.0.0.1])
	by vmail.vsnl.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May
	14 2003)) with SMTP id <0I7Z00KN4LYAXY@vmail.vsnl.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 15:48:11 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.169.3)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Tue,
	30 Nov 2004 15:48:11 +0530 (IST)
Date: Tue, 30 Nov 2004 15:48:31 +0530
From: Rajesh <rajeshkalagarla@tataelxsi.co.in>
To: sipping@ietf.org
Message-id: <00ea01c4d6c5$f1a4fe80$3b46010a@telxsi.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Subject: [Sipping] Multiple conferences in SIP
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0179352496=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176

This is a multi-part message in MIME format.

--===============0179352496==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_gABvg9uuGMDX2oYx/y3lZA)"

This is a multi-part message in MIME format.

--Boundary_(ID_gABvg9uuGMDX2oYx/y3lZA)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi Alan,

 thanks for giving reply. my query here is, if focus is hosting multiple
conferences,and is in a proxy domain, how the behavior of focus with proxy?
I mean -- is it get registered with multiple contact-Uri's, where each Uri
corresponds to a particular conference.

 if so, focus has to get registered with one other Uri (generic - not
containing any conference id as part of that )-- which will be turned out
into a new conference when it gets a new call. (the Q is, how focus will
create a New conference starting with a Dial-In Call, proxy also there as
part of the call)

thanks & regards,
Rajesh.Kalagarla



  -----Original Message-----
  From: Johnston, Alan [mailto:Alan.Johnston@mci.com]
  Sent: Monday, November 29, 2004 9:03 PM
  To: 'Rajesh'; oritl@microsoft.com
  Subject: RE: Distinguishing Simultaneous Conferences..


  Hi Rajesh,

  You are correct, each conference will have a unique Request-URI.  When
participants dial-in (send an INVITE), they will send it to this unique URI.
Once in the conference, the focus keeps track of participants by tracking
their dialog states.

  Thanks,
  Alan
  sip:alan@sipstation.com
    -----Original Message-----
    From: Rajesh [mailto:rajeshkalagarla@tataelxsi.co.in]
    Sent: Wednesday, November 24, 2004 12:10 AM
    To: Johnston, Alan; oritl@microsoft.com
    Subject: Distinguishing Simultaneous Conferences..


      Hi Alan & Oritl,

       if we are hosting simultaniuos Conferences, is it required to
maintain difference Contact corresponding to each conference
(Conference-Uri).of not how to distinguish the different conferences.

      thanks & regards,
      Rajesh.Kalagarla


--Boundary_(ID_gABvg9uuGMDX2oYx/y3lZA)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!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 5.00.3700.6699" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=833221703-30112004>Hi 
Alan,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;thanks for giving reply. my query here is, if 
focus is hosting multiple conferences,and is in a proxy domain, how the behavior 
of focus with proxy? I mean -- is it get registered with multiple contact-Uri's, 
where each Uri corresponds to a particular conference.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;if so, focus has to get registered with one other 
Uri (generic - not containing any conference id as part of that )-- which will 
be turned out into a new conference when it gets a new call. (the Q is, how 
focus will create a New conference starting with a Dial-In Call, proxy also 
there as part of the call)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=833221703-30112004>thanks 
&amp; regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>Rajesh.Kalagarla</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Johnston, Alan 
  [mailto:Alan.Johnston@mci.com]<BR><B>Sent:</B> Monday, November 29, 2004 9:03 
  PM<BR><B>To:</B> 'Rajesh'; oritl@microsoft.com<BR><B>Subject:</B> RE: 
  Distinguishing Simultaneous Conferences..<BR><BR></DIV></FONT>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial size=2>Hi 
  Rajesh,</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial size=2>You 
  are correct, each conference will have a unique Request-URI.&nbsp; When 
  participants dial-in (send an INVITE), they will send it to this unique 
  URI.&nbsp; Once in the conference, the focus keeps track of participants by 
  tracking their dialog states.</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>Thanks,</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>Alan</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>sip:alan@sipstation.com</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV></DIV>
    <DIV align=left class=OutlookMessageHeader dir=ltr lang=en-us><FONT 
    face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Rajesh 
    [mailto:rajeshkalagarla@tataelxsi.co.in] <BR><B>Sent:</B> Wednesday, 
    November 24, 2004 12:10 AM<BR><B>To:</B> Johnston, Alan; 
    oritl@microsoft.com<BR><B>Subject:</B> Distinguishing Simultaneous 
    Conferences..<BR><BR></FONT></DIV>
    <BLOCKQUOTE 
    style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV><FONT face=Arial size=2><SPAN class=622144411-23112004>Hi Alan &amp; 
      Oritl,</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;<FONT color=#0000ff 
      face=Arial size=2><SPAN class=583570606-24112004>if we are hosting 
      simultaniuos Conferences, is it required to maintain difference Contact 
      corresponding to each conference (Conference-Uri).of not how to 
      distinguish the different conferences.</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2><SPAN class=622144411-23112004>thanks &amp; 
      regards,</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004>Rajesh.Kalagarla</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></FONT></DIV></BODY></HTML>

--Boundary_(ID_gABvg9uuGMDX2oYx/y3lZA)--


--===============0179352496==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0179352496==--



From sipping-bounces@ietf.org  Tue Nov 30 05:54:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04555
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 05:54:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ5jq-0008KT-GQ
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 06:00:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ5V0-0002v7-5X; Tue, 30 Nov 2004 05:44:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ4fB-0002Ja-5Z
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 04:51:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26974
	for <sipping@ietf.org>; Tue, 30 Nov 2004 04:50:50 -0500 (EST)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ4ja-0006f1-RF
	for sipping@ietf.org; Tue, 30 Nov 2004 04:56:08 -0500
Received: from RajeshK ([127.0.0.1])
	by vmail.vsnl.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May
	14 2003)) with SMTP id <0I7Z00K6QKN9R6@vmail.vsnl.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 15:19:58 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.169.3)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Tue,
	30 Nov 2004 15:19:58 +0530 (IST)
Date: Tue, 30 Nov 2004 15:20:20 +0530
From: Rajesh <rajeshkalagarla@tataelxsi.co.in>
To: sipping@ietf.org
Message-id: <00e501c4d6c2$01c05d40$3b46010a@telxsi.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
X-Mailman-Approved-At: Tue, 30 Nov 2004 05:44:45 -0500
Subject: [Sipping] Multiple conferences in SIP
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============0669773701=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176

This is a multi-part message in MIME format.

--===============0669773701==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_fIKdjA2s+JVj9eSOOm8GcQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_fIKdjA2s+JVj9eSOOm8GcQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi Alan,

 thanks for giving reply. my query here is, if focus is hosting multiple
conferences,and is in a proxy domain, how the behavior of focus with proxy?
I mean -- is it get registered with multiple contact-Uri's, where each Uri
corresponds to a particular conference.

 if so, focus has to get registered with one other Uri (generic - not
containing any conference id as part of that )-- which will be turned out
into a new conference when it gets a new call. (the Q is, how focus will
create a New conference starting with a Dial-In Call, proxy also there as
part of the call)

thanks & regards,
Rajesh.Kalagarla



  -----Original Message-----
  From: Johnston, Alan [mailto:Alan.Johnston@mci.com]
  Sent: Monday, November 29, 2004 9:03 PM
  To: 'Rajesh'; oritl@microsoft.com
  Subject: RE: Distinguishing Simultaneous Conferences..


  Hi Rajesh,

  You are correct, each conference will have a unique Request-URI.  When
participants dial-in (send an INVITE), they will send it to this unique URI.
Once in the conference, the focus keeps track of participants by tracking
their dialog states.

  Thanks,
  Alan
  sip:alan@sipstation.com
    -----Original Message-----
    From: Rajesh [mailto:rajeshkalagarla@tataelxsi.co.in]
    Sent: Wednesday, November 24, 2004 12:10 AM
    To: Johnston, Alan; oritl@microsoft.com
    Subject: Distinguishing Simultaneous Conferences..


      Hi Alan & Oritl,

       if we are hosting simultaniuos Conferences, is it required to
maintain difference Contact corresponding to each conference
(Conference-Uri).of not how to distinguish the different conferences.

      thanks & regards,
      Rajesh.Kalagarla


--Boundary_(ID_fIKdjA2s+JVj9eSOOm8GcQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!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 5.00.3700.6699" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=833221703-30112004>Hi 
Alan,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;thanks for giving reply. my query here is, if 
focus is hosting multiple conferences,and is in a proxy domain, how the behavior 
of focus with proxy? I mean -- is it get registered with multiple contact-Uri's, 
where each Uri corresponds to a particular conference.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;if so, focus has to get registered with one other 
Uri (generic - not containing any conference id as part of that )-- which will 
be turned out into a new conference when it gets a new call. (the Q is, how 
focus will create a New conference starting with a Dial-In Call, proxy also 
there as part of the call)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=833221703-30112004>thanks 
&amp; regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>Rajesh.Kalagarla</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=833221703-30112004>&nbsp;</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Johnston, Alan 
  [mailto:Alan.Johnston@mci.com]<BR><B>Sent:</B> Monday, November 29, 2004 9:03 
  PM<BR><B>To:</B> 'Rajesh'; oritl@microsoft.com<BR><B>Subject:</B> RE: 
  Distinguishing Simultaneous Conferences..<BR><BR></DIV></FONT>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial size=2>Hi 
  Rajesh,</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial size=2>You 
  are correct, each conference will have a unique Request-URI.&nbsp; When 
  participants dial-in (send an INVITE), they will send it to this unique 
  URI.&nbsp; Once in the conference, the focus keeps track of participants by 
  tracking their dialog states.</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>Thanks,</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>Alan</FONT></SPAN></DIV>
  <DIV><SPAN class=820163215-29112004><FONT color=#0000ff face=Arial 
  size=2>sip:alan@sipstation.com</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <DIV></DIV>
    <DIV align=left class=OutlookMessageHeader dir=ltr lang=en-us><FONT 
    face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Rajesh 
    [mailto:rajeshkalagarla@tataelxsi.co.in] <BR><B>Sent:</B> Wednesday, 
    November 24, 2004 12:10 AM<BR><B>To:</B> Johnston, Alan; 
    oritl@microsoft.com<BR><B>Subject:</B> Distinguishing Simultaneous 
    Conferences..<BR><BR></FONT></DIV>
    <BLOCKQUOTE 
    style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
      <DIV><FONT face=Arial size=2><SPAN class=622144411-23112004>Hi Alan &amp; 
      Oritl,</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;<FONT color=#0000ff 
      face=Arial size=2><SPAN class=583570606-24112004>if we are hosting 
      simultaniuos Conferences, is it required to maintain difference Contact 
      corresponding to each conference (Conference-Uri).of not how to 
      distinguish the different conferences.</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=Arial size=2><SPAN class=622144411-23112004>thanks &amp; 
      regards,</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004>Rajesh.Kalagarla</SPAN></FONT></DIV>
      <DIV><FONT face=Arial size=2><SPAN 
      class=622144411-23112004></SPAN></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></FONT></DIV></BODY></HTML>

--Boundary_(ID_fIKdjA2s+JVj9eSOOm8GcQ)--


--===============0669773701==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--===============0669773701==--



From sipping-bounces@ietf.org  Tue Nov 30 09:10:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19522
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 09:10:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ8nD-0004Kl-L8
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 09:15:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ8eX-00048c-Dn; Tue, 30 Nov 2004 09:06:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ8bA-0003Q7-7q
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 09:03:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18982
	for <sipping@ietf.org>; Tue, 30 Nov 2004 09:03:18 -0500 (EST)
Message-Id: <200411301403.JAA18982@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ8gH-00049X-TB
	for sipping@ietf.org; Tue, 30 Nov 2004 09:08:38 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CZ9Vt-00026u-LL; Tue, 30 Nov 2004 08:01:57 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Subject: RE: [Sipping] Conference speaker control
Date: Tue, 30 Nov 2004 09:02:36 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C7090AF@IsrExch01.israel.polycom.com>
Thread-Index: AcTWKvXtPmbv77nEToKg4F9J0NdQPAAjRh2QAAsod7A=
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit
Cc: "'sipping'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: 7bit

Roni

This is SIPPING.  If we have PSTN participants in a conference, they come
from some kind of gateway and use SIP signaling.  AFAIK, there is no way
with current IETF protocols to have a conference where the participants are
anything but SIP endpoints using RTP for media streams.

You might ask over in the XCON list whether anyone thinks trying to use XCON
protocols to control a PSTN mixer without RTP is in scope.  XCON is not
limited to SIP, but I'm not sure such a case is something we should be
worried about.  It's clearly not something in SIPPING's charter.

Brian

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
> Of Even, Roni
> Sent: Tuesday, November 30, 2004 3:46 AM
> To: Magnus Westerlund
> Cc: sipping
> Subject: RE: [Sipping] Conference speaker control
> 
> Magnus,
> The problem you stated is correct but this is not what I meant. In XCON
> conference server can be composed of a conference/media policy server
> and a focus that can be an application server that handle conference
> policy and some web collaboration while the mixer is a PSTN bridge.
> A participant in such a conference is using a PSTN phone and a PC for
> web collaboration and conference control. The PC can subscribe to the
> conference package but since the audio is PSTN there are no RTP or SSRC.
> Even for IP conferencing making an assumption that all streams in a
> conference are RTP streams is not always right, so ssrc cannot be used
> to describe who is sourcing each stream in an application that uses a
> mix of RTP and non RTP streams.
> Roni Even
> 
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Monday, November 29, 2004 5:45 PM
> To: Even, Roni
> Cc: sipping
> Subject: Re: [Sipping] Conference speaker control
> 
> Hi Roni,
> 
> Lets see if I understand this correctly. You are worried about PSTN or
> other gateways that are receiving more than one source over the same
> circuit and in which cases the gateway can't separate the different
> sources within the CS to IP gateway. As long as the PSTN gateway
> receives the different circuit switched sources in the same conference
> on different circuits, it is able to assign them different SSRCs and
> IDs.
> 
> If the above is the case, how would adding any other mechanism help? The
> 
> gateway can still not identify the original sources, or am I
> misunderstanding something about the setup?
> 
> My understanding of the setup you are concern is:
> 
> 
> CS1 --\
>         -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
> CS2 --/                  ^               ^
>                           |               |
>                          CS5           Client 4
> 
> In this case Client 3 and 4 would not be able to determine that what is
> beyond the gateway is in fact three client. CS1 and CS2 will be bunched
> together under one source identifier? While CS5 can be identified as it
> connects directly with the gateway and uses a separate CS line into the
> gateway, thus allowing the gateway to give them separate IDs.
> 
> It should also not be a problem if the protocol used on the CS side
> provides identities, then the gateway can provide different identifiers
> for the different CS side users.
> 
> Cheers
> 
> Magnus
> 
> Even, Roni wrote:
> 
> > Magnus,
> > I am not saying that RTP using SSRC does not have a mechanism to
> > identify the source of the streams. What I am trying to say is that we
> > are not talking about a pure RTP mixer but we are talking about a SIP
> > based conferencing server and in XCON the scope is even wider, it may
> be
> > a PSTN bridge bellow.
> > So first of all there is no requirement defined that the mixer in SIP
> > conferencing or XCON should be a RTP mixer per RFC3550. Even if we do
> it
> > for SIPPING then we will have a problem for PSTN Bridge (example of
> > usage if for audio-graphic conference) and it will break for XCON.
> > Roni Even
> 
> 
> --
> 
> Magnus Westerlund
> 
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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 sipping-bounces@ietf.org  Tue Nov 30 10:51:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00281
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 10:51:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZAN5-0006sx-OR
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 10:56:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZA9z-0000cx-Uq; Tue, 30 Nov 2004 10:43:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZA2l-0007dz-4G
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 10:35:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29065
	for <sipping@ietf.org>; Tue, 30 Nov 2004 10:35:52 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZA7t-0006Xc-5S
	for sipping@ietf.org; Tue, 30 Nov 2004 10:41:13 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 30 Nov 2004 08:42:28 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAUFZH9N016158;
	Tue, 30 Nov 2004 07:35:17 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAUFYmvL000720;
	Tue, 30 Nov 2004 07:34:49 -0800
In-Reply-To: <200411301403.JAA18982@ietf.org>
References: <200411301403.JAA18982@ietf.org>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6D5EE2E8-42E5-11D9-8CD3-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Conference speaker control
Date: Tue, 30 Nov 2004 10:35:13 -0500
To: "Brian Rosen" <br@brianrosen.net>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101828892.792896"; x:"432200"; a:"rsa-sha1"; b:"nofws:6434";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"DJz2QIiviame9iWYrEsIhUXvu6dmMrRLBC43ie50jCmMalZHUvNTqweZsR3/8"
	"bX/du/E6SQO0kXCxf7XvdpYdPPvDQWiC7dz4h8lpzOCaGH/mt+owcvR66x3HK"
	"wLmEtJgrHS4auLZhmqYXMHOPZrasi+JxrVbJaFunFNVkc/cao=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Conference speaker control";
	c:"Date: Tue, 30 Nov 2004 10:35:13 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Content-Transfer-Encoding: 7bit
Cc: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
        "'Even,
	Roni'" <roni.even@polycom.co.il>,
        "'sipping'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Content-Transfer-Encoding: 7bit

I tend to agree with Brian, however Roni's use case is interesting and 
should be accommodated if reasonably easy. What is definitely missing 
is a protocol between the the PSTN bridge and either the control plane 
in the focus, or between the PSTN bridge and the SIP participants. If 
we choose the former approach there is protocol work to be done in 
XCON. If we choose the latter approach, we have such a protocol - it's 
RTP. While somewhat artificial, one could have an RTP session from the 
PSTN bridge (or something associated with that bridge (which is 
obviously needed anyway to have the bridge report who is speaking) to 
each participant simply for the purpose of reporting this (and other 
realtime) information.

I don't necessarily advocate any particular approach, but if we do want 
to have PSTN/TDM media paths for audio in scope of XCON or SIPPING, we 
can't just mandate control-plane reporting of active speaker, declare 
victory, and move on. There's work to be done.

Dave.

On Nov 30, 2004, at 9:02 AM, Brian Rosen wrote:

> Roni
>
> This is SIPPING.  If we have PSTN participants in a conference, they 
> come
> from some kind of gateway and use SIP signaling.  AFAIK, there is no 
> way
> with current IETF protocols to have a conference where the 
> participants are
> anything but SIP endpoints using RTP for media streams.
>
> You might ask over in the XCON list whether anyone thinks trying to 
> use XCON
> protocols to control a PSTN mixer without RTP is in scope.  XCON is not
> limited to SIP, but I'm not sure such a case is something we should be
> worried about.  It's clearly not something in SIPPING's charter.
>
> Brian
>
>> -----Original Message-----
>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On 
>> Behalf
>> Of Even, Roni
>> Sent: Tuesday, November 30, 2004 3:46 AM
>> To: Magnus Westerlund
>> Cc: sipping
>> Subject: RE: [Sipping] Conference speaker control
>>
>> Magnus,
>> The problem you stated is correct but this is not what I meant. In 
>> XCON
>> conference server can be composed of a conference/media policy server
>> and a focus that can be an application server that handle conference
>> policy and some web collaboration while the mixer is a PSTN bridge.
>> A participant in such a conference is using a PSTN phone and a PC for
>> web collaboration and conference control. The PC can subscribe to the
>> conference package but since the audio is PSTN there are no RTP or 
>> SSRC.
>> Even for IP conferencing making an assumption that all streams in a
>> conference are RTP streams is not always right, so ssrc cannot be used
>> to describe who is sourcing each stream in an application that uses a
>> mix of RTP and non RTP streams.
>> Roni Even
>>
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: Monday, November 29, 2004 5:45 PM
>> To: Even, Roni
>> Cc: sipping
>> Subject: Re: [Sipping] Conference speaker control
>>
>> Hi Roni,
>>
>> Lets see if I understand this correctly. You are worried about PSTN or
>> other gateways that are receiving more than one source over the same
>> circuit and in which cases the gateway can't separate the different
>> sources within the CS to IP gateway. As long as the PSTN gateway
>> receives the different circuit switched sources in the same conference
>> on different circuits, it is able to assign them different SSRCs and
>> IDs.
>>
>> If the above is the case, how would adding any other mechanism help? 
>> The
>>
>> gateway can still not identify the original sources, or am I
>> misunderstanding something about the setup?
>>
>> My understanding of the setup you are concern is:
>>
>>
>> CS1 --\
>>         -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
>> CS2 --/                  ^               ^
>>                           |               |
>>                          CS5           Client 4
>>
>> In this case Client 3 and 4 would not be able to determine that what 
>> is
>> beyond the gateway is in fact three client. CS1 and CS2 will be 
>> bunched
>> together under one source identifier? While CS5 can be identified as 
>> it
>> connects directly with the gateway and uses a separate CS line into 
>> the
>> gateway, thus allowing the gateway to give them separate IDs.
>>
>> It should also not be a problem if the protocol used on the CS side
>> provides identities, then the gateway can provide different 
>> identifiers
>> for the different CS side users.
>>
>> Cheers
>>
>> Magnus
>>
>> Even, Roni wrote:
>>
>>> Magnus,
>>> I am not saying that RTP using SSRC does not have a mechanism to
>>> identify the source of the streams. What I am trying to say is that 
>>> we
>>> are not talking about a pure RTP mixer but we are talking about a SIP
>>> based conferencing server and in XCON the scope is even wider, it may
>> be
>>> a PSTN bridge bellow.
>>> So first of all there is no requirement defined that the mixer in SIP
>>> conferencing or XCON should be a RTP mixer per RFC3550. Even if we do
>> it
>>> for SIPPING then we will have a problem for PSTN Bridge (example of
>>> usage if for audio-graphic conference) and it will break for XCON.
>>> Roni Even
>>
>>
>> --
>>
>> Magnus Westerlund
>>
>> Multimedia Technologies, Ericsson Research EAB/TVA/A
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone +46 8 4048287
>> Torshamsgatan 23           | Fax   +46 8 7575550
>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Tue Nov 30 13:28:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16941
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 13:28:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZCpD-0002wO-8r
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 13:34:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZCEb-0005d0-7X; Tue, 30 Nov 2004 12:56:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZCAK-0004FD-Id
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 12:51:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13391
	for <sipping@ietf.org>; Tue, 30 Nov 2004 12:51:49 -0500 (EST)
Received: from omzesmtp03.mci.com ([199.249.17.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCFQ-0001wH-8t
	for sipping@ietf.org; Tue, 30 Nov 2004 12:57:12 -0500
Received: from pmismtp02.mcilink.com ([166.38.62.37])
	by firewall.mci.com (Iplanet MTA 5.2)
	with ESMTP id <0I8000M3V6VFY7@firewall.mci.com> for sipping@ietf.org;
	Tue, 30 Nov 2004 17:50:04 +0000 (GMT)
Received: from pmismtp02.mcilink.com by pmismtp02.mcilink.com
	(iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
	with SMTP id <0I8000H016UOOD@pmismtp02.mcilink.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 17:50:03 +0000 (GMT)
Received: from dgexch50.wcomnet.com ([166.38.58.238])
	by pmismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14
	(built Mar
	18 2003)) with ESMTP id <0I8000GPU6VDKI@pmismtp02.mcilink.com> for
	sipping@ietf.org; Tue, 30 Nov 2004 17:50:01 +0000 (GMT)
Received: by DGEXCH50.mcilink.com with Internet Mail Service (5.5.2653.19)
	id <X5H0831D>; Tue, 30 Nov 2004 17:50:01 +0000
Content-return: allowed
Date: Tue, 30 Nov 2004 17:49:52 +0000
From: "Johnston, Alan" <Alan.Johnston@mci.com>
To: sipping <sipping@ietf.org>
Message-id: <EB7597BFB1C65844898A6D153DE09DB50895CE@DGEXCH02.mcilink.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: text/plain; CHARSET=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [Sipping] FW:  XCON Interim Attendance Poll - please respond
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

FYI

-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Johnston, Alan
Sent: Tuesday, November 23, 2004 2:21 PM
To: xcon@ietf.org
Cc: 'Adam@nostrum.com'
Subject: [XCON] XCON Interim Attendance Poll - please respond


All,

The XCON working group interim meeting is being planned for January 5 and
January 6, 2005 in Boston, MA.

The exact location and agenda with hotel information will be posted in about
a week, as will the official announcement on the IETF Announce list.

For the moment, if you plan to attend, or know of people in your
organization who plan to attend, please send an email directly to me
(mailto:alan.johnston@mci.com) (do *not* send to the list) so we can get an
accurate count to finalize the planning.

Please respond in the next week, by November 30.

Thanks,
Alan Johnston
co-chair XCON

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 30 13:36:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17795
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 13:36:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZCwO-0003Ax-2L
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 13:41:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZCnu-0001YV-Mw; Tue, 30 Nov 2004 13:32:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZCKO-0007D5-5m
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 13:02:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14763
	for <sipping@ietf.org>; Tue, 30 Nov 2004 13:02:12 -0500 (EST)
Received: from fep2.012.net.il ([212.117.129.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCPV-0002I1-1c
	for sipping@ietf.org; Tue, 30 Nov 2004 13:07:35 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep2.012.net.il with ESMTP
	id <20041130180129.IMLF9868.fep2@isrexch01.israel.polycom.com>;
	Tue, 30 Nov 2004 20:01:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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] Conference speaker control
Date: Tue, 30 Nov 2004 19:59:28 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C730BF8@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTWKvXtPmbv77nEToKg4F9J0NdQPAAjRh2QAAsod7AACGlv+Q==
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Brian Rosen" <br@brianrosen.net>,
        "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: quoted-printable
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: quoted-printable

Brian,
I know it is SIPPINg and I mentioned that we may extend the conference =
package in XCON.
I am still not sure about the ssrc. Does SIP allows only RTP sessions. =
As far as I know there is no such assumption in SDP.=20
Roni Even

________________________________

From: sipping-bounces@ietf.org on behalf of Brian Rosen
Sent: Tue 11/30/2004 4:02 PM
To: Even, Roni; 'Magnus Westerlund'
Cc: 'sipping'
Subject: RE: [Sipping] Conference speaker control



Roni

This is SIPPING.  If we have PSTN participants in a conference, they =
come
from some kind of gateway and use SIP signaling.  AFAIK, there is no way
with current IETF protocols to have a conference where the participants =
are
anything but SIP endpoints using RTP for media streams.

You might ask over in the XCON list whether anyone thinks trying to use =
XCON
protocols to control a PSTN mixer without RTP is in scope.  XCON is not
limited to SIP, but I'm not sure such a case is something we should be
worried about.  It's clearly not something in SIPPING's charter.

Brian

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On =
Behalf
> Of Even, Roni
> Sent: Tuesday, November 30, 2004 3:46 AM
> To: Magnus Westerlund
> Cc: sipping
> Subject: RE: [Sipping] Conference speaker control
>
> Magnus,
> The problem you stated is correct but this is not what I meant. In =
XCON
> conference server can be composed of a conference/media policy server
> and a focus that can be an application server that handle conference
> policy and some web collaboration while the mixer is a PSTN bridge.
> A participant in such a conference is using a PSTN phone and a PC for
> web collaboration and conference control. The PC can subscribe to the
> conference package but since the audio is PSTN there are no RTP or =
SSRC.
> Even for IP conferencing making an assumption that all streams in a
> conference are RTP streams is not always right, so ssrc cannot be used
> to describe who is sourcing each stream in an application that uses a
> mix of RTP and non RTP streams.
> Roni Even
>
> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Monday, November 29, 2004 5:45 PM
> To: Even, Roni
> Cc: sipping
> Subject: Re: [Sipping] Conference speaker control
>
> Hi Roni,
>
> Lets see if I understand this correctly. You are worried about PSTN or
> other gateways that are receiving more than one source over the same
> circuit and in which cases the gateway can't separate the different
> sources within the CS to IP gateway. As long as the PSTN gateway
> receives the different circuit switched sources in the same conference
> on different circuits, it is able to assign them different SSRCs and
> IDs.
>
> If the above is the case, how would adding any other mechanism help? =
The
>
> gateway can still not identify the original sources, or am I
> misunderstanding something about the setup?
>
> My understanding of the setup you are concern is:
>
>
> CS1 --\
>         -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
> CS2 --/                  ^               ^
>                           |               |
>                          CS5           Client 4
>
> In this case Client 3 and 4 would not be able to determine that what =
is
> beyond the gateway is in fact three client. CS1 and CS2 will be =
bunched
> together under one source identifier? While CS5 can be identified as =
it
> connects directly with the gateway and uses a separate CS line into =
the
> gateway, thus allowing the gateway to give them separate IDs.
>
> It should also not be a problem if the protocol used on the CS side
> provides identities, then the gateway can provide different =
identifiers
> for the different CS side users.
>
> Cheers
>
> Magnus
>
> Even, Roni wrote:
>
> > Magnus,
> > I am not saying that RTP using SSRC does not have a mechanism to
> > identify the source of the streams. What I am trying to say is that =
we
> > are not talking about a pure RTP mixer but we are talking about a =
SIP
> > based conferencing server and in XCON the scope is even wider, it =
may
> be
> > a PSTN bridge bellow.
> > So first of all there is no requirement defined that the mixer in =
SIP
> > conferencing or XCON should be a RTP mixer per RFC3550. Even if we =
do
> it
> > for SIPPING then we will have a problem for PSTN Bridge (example of
> > usage if for audio-graphic conference) and it will break for XCON.
> > Roni Even
>
>
> --
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 30 14:10:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21411
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 14:10:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZDTX-0004G2-At
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 14:15:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDGC-0002E0-Fx; Tue, 30 Nov 2004 14:02:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZD65-0007Vp-3N; Tue, 30 Nov 2004 13:51:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19482;
	Tue, 30 Nov 2004 13:51:31 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZDBF-0003g6-BT; Tue, 30 Nov 2004 13:56:53 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAUIorS20101; Tue, 30 Nov 2004 13:50:53 -0500 (EST)
Received: from [47.130.24.149] (acart16j.ca.nortel.com [47.130.24.149]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14FSMZH; Tue, 30 Nov 2004 13:50:53 -0500
Message-ID: <41ACC10C.2090206@nortelnetworks.com>
Date: Tue, 30 Nov 2004 13:50:52 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Nguyen, An" <An.Nguyen@ncs.gov>
References: <7F18415E4D63CB45BB9B3A591F68D12D0765166C@emshqs1.ncr.disa.mil>
In-Reply-To: <7F18415E4D63CB45BB9B3A591F68D12D0765166C@emshqs1.ncr.disa.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: iptel@ietf.org, "Jesske, R" <R.Jesske@t-com.net>, sipping@ietf.org
Subject: [Sipping] Re: [Iptel] Calling Party's Category
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

Jonathan, I hope I am stating this correctly.

The Chair's proposal at the meeting was that this draft be dropped, because with 
SIP-T defined, there is no need to define other means in SIP to carry signalling 
destined specifically to the PSTN.  However, if use cases can be provided which 
demonstrate a requirement to be met in the pure SIP environment, work can be done 
(probably in SIPPING) to meet those requirements.

Nguyen, An wrote:
> Mr. Taylor;
> 
> I am just curious ... What is the status of the Internet Draft?
> 
> An
> 
> 
[snip]

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.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 sipping-bounces@ietf.org  Tue Nov 30 14:13:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21656
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 14:13:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZDW5-0004LY-Ky
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 14:18:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDI5-0002qy-4l; Tue, 30 Nov 2004 14:03:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZDBP-0000VI-9K
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 13:57:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20123
	for <sipping@ietf.org>; Tue, 30 Nov 2004 13:57:01 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZDGY-0003rG-6w
	for sipping@ietf.org; Tue, 30 Nov 2004 14:02:23 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-5.cisco.com with ESMTP; 30 Nov 2004 10:56:45 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAUIuP9N015541;
	Tue, 30 Nov 2004 10:56:25 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com
	[10.32.245.156])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAUItwDp002622;
	Tue, 30 Nov 2004 10:55:59 -0800
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730BF8@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C730BF8@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <88537760-4301-11D9-8CD3-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Conference speaker control
Date: Tue, 30 Nov 2004 13:56:24 -0500
To: "Even, Roni" <roni.even@polycom.co.il>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1101840960.502208"; x:"432200"; a:"rsa-sha1"; b:"nofws:7490";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"DNah8AiefekY2t7kF3HCh41q27Jn8GSEYTSJVIFylIzRpa41bHA+kCc2tyXJQ"
	"2YITjC3GZG305grPMiljf+ZOlYjnp8luKznIHHw97fT4lFqSntyoK3LMn0NDT"
	"Mhv9LeF+VcPdTvDkFiO/rFdBdlN03Qfeex21iB622DvsFI5Ho=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Conference speaker control";
	c:"Date: Tue, 30 Nov 2004 13:56:24 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>,
        sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Content-Transfer-Encoding: 7bit


On Nov 30, 2004, at 12:59 PM, Even, Roni wrote:

> Brian,
> I know it is SIPPINg and I mentioned that we may extend the conference 
> package in XCON.
> I am still not sure about the ssrc. Does SIP allows only RTP sessions. 
> As far as I know there is no such assumption in SDP.

That's not the point. The point is whether we assume that the media 
sessions are "self-describing" in terms of providing the identity 
(directly or indirectly) of the source of the data arriving *now*. RTP 
does that, both directly and through mixers. MSRP does that, both 
directly and through relays/chat rooms. A separate PSTN stream arriving 
at a POTs phone does not.

If we make this "self-describing media sessions" assumption then we 
reach a different set of requirements for speaker 
identification/control than if we do not.

I would argue that this is a very good assumption to make since it 
simplifies a number of things and makes the system less sensitive to 
whether there are centralized media processing resources or not (as 
opposed to centralized control plane focus which XCON explicitly is 
restricted to).

For better or worse this means that media streams that aren't 
themselves self-describing need some kind of "helper" element. This 
could be in the control plane, of course, and might be simpler there. 
On the other hand, for symmetry with the way the rest of the system 
works, I'd argue that keeping this a media plane function is a good 
idea, even if complicates the legacy bridges.

Dave.


> Roni Even
>
> ________________________________
>
> From: sipping-bounces@ietf.org on behalf of Brian Rosen
> Sent: Tue 11/30/2004 4:02 PM
> To: Even, Roni; 'Magnus Westerlund'
> Cc: 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>
>
>
> Roni
>
> This is SIPPING.  If we have PSTN participants in a conference, they 
> come
> from some kind of gateway and use SIP signaling.  AFAIK, there is no 
> way
> with current IETF protocols to have a conference where the 
> participants are
> anything but SIP endpoints using RTP for media streams.
>
> You might ask over in the XCON list whether anyone thinks trying to 
> use XCON
> protocols to control a PSTN mixer without RTP is in scope.  XCON is not
> limited to SIP, but I'm not sure such a case is something we should be
> worried about.  It's clearly not something in SIPPING's charter.
>
> Brian
>
>> -----Original Message-----
>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On 
>> Behalf
>> Of Even, Roni
>> Sent: Tuesday, November 30, 2004 3:46 AM
>> To: Magnus Westerlund
>> Cc: sipping
>> Subject: RE: [Sipping] Conference speaker control
>>
>> Magnus,
>> The problem you stated is correct but this is not what I meant. In 
>> XCON
>> conference server can be composed of a conference/media policy server
>> and a focus that can be an application server that handle conference
>> policy and some web collaboration while the mixer is a PSTN bridge.
>> A participant in such a conference is using a PSTN phone and a PC for
>> web collaboration and conference control. The PC can subscribe to the
>> conference package but since the audio is PSTN there are no RTP or 
>> SSRC.
>> Even for IP conferencing making an assumption that all streams in a
>> conference are RTP streams is not always right, so ssrc cannot be used
>> to describe who is sourcing each stream in an application that uses a
>> mix of RTP and non RTP streams.
>> Roni Even
>>
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: Monday, November 29, 2004 5:45 PM
>> To: Even, Roni
>> Cc: sipping
>> Subject: Re: [Sipping] Conference speaker control
>>
>> Hi Roni,
>>
>> Lets see if I understand this correctly. You are worried about PSTN or
>> other gateways that are receiving more than one source over the same
>> circuit and in which cases the gateway can't separate the different
>> sources within the CS to IP gateway. As long as the PSTN gateway
>> receives the different circuit switched sources in the same conference
>> on different circuits, it is able to assign them different SSRCs and
>> IDs.
>>
>> If the above is the case, how would adding any other mechanism help? 
>> The
>>
>> gateway can still not identify the original sources, or am I
>> misunderstanding something about the setup?
>>
>> My understanding of the setup you are concern is:
>>
>>
>> CS1 --\
>>         -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
>> CS2 --/                  ^               ^
>>                           |               |
>>                          CS5           Client 4
>>
>> In this case Client 3 and 4 would not be able to determine that what 
>> is
>> beyond the gateway is in fact three client. CS1 and CS2 will be 
>> bunched
>> together under one source identifier? While CS5 can be identified as 
>> it
>> connects directly with the gateway and uses a separate CS line into 
>> the
>> gateway, thus allowing the gateway to give them separate IDs.
>>
>> It should also not be a problem if the protocol used on the CS side
>> provides identities, then the gateway can provide different 
>> identifiers
>> for the different CS side users.
>>
>> Cheers
>>
>> Magnus
>>
>> Even, Roni wrote:
>>
>>> Magnus,
>>> I am not saying that RTP using SSRC does not have a mechanism to
>>> identify the source of the streams. What I am trying to say is that 
>>> we
>>> are not talking about a pure RTP mixer but we are talking about a SIP
>>> based conferencing server and in XCON the scope is even wider, it may
>> be
>>> a PSTN bridge bellow.
>>> So first of all there is no requirement defined that the mixer in SIP
>>> conferencing or XCON should be a RTP mixer per RFC3550. Even if we do
>> it
>>> for SIPPING then we will have a problem for PSTN Bridge (example of
>>> usage if for audio-graphic conference) and it will break for XCON.
>>> Roni Even
>>
>>
>> --
>>
>> Magnus Westerlund
>>
>> Multimedia Technologies, Ericsson Research EAB/TVA/A
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone +46 8 4048287
>> Torshamsgatan 23           | Fax   +46 8 7575550
>> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
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 sipping-bounces@ietf.org  Tue Nov 30 14:43:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25663
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 14:43:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZDz8-0005Fk-RW
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 14:48:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDky-0002rw-Sb; Tue, 30 Nov 2004 14:33:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZDW7-00079s-1t
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 14:18:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22093
	for <sipping@ietf.org>; Tue, 30 Nov 2004 14:18:25 -0500 (EST)
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZDbH-0004VU-9o
	for sipping@ietf.org; Tue, 30 Nov 2004 14:23:47 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUJIKv10093; Tue, 30 Nov 2004 21:18:20 +0200 (EET)
X-Scanned: Tue, 30 Nov 2004 21:18:03 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iAUJI3Yd009422;
	Tue, 30 Nov 2004 21:18:03 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00Z4dGiE; Tue, 30 Nov 2004 21:18:02 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUJI1a01827; Tue, 30 Nov 2004 21:18:01 +0200 (EET)
Received: from [10.163.23.234] ([10.163.23.234]) by esebh001.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 30 Nov 2004 21:17:55 +0200
Message-ID: <41ACC764.2030906@nokia.com>
Date: Tue, 30 Nov 2004 21:17:56 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Subject: Re: [Sipping] URIs in conference event package.
References: <419B3AE1.30103@nokia.com>
In-Reply-To: <419B3AE1.30103@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Nov 2004 19:17:55.0556 (UTC)
	FILETIME=[4B930A40:01C4D711]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Content-Transfer-Encoding: 7bit
Cc: Alan Johnston <alan.johnston@mci.com>, Orit Levin <oritl@microsoft.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
Content-Transfer-Encoding: 7bit

Hi:

A few days ago I submitted some comments to the conference event 
package. I was proposing to add a <purpose> element to a uri <entry>, so 
that it was possible to describe what service is behind that URI. The 
idea I had in mind is that my UA can receive a notification of the 
conference event package and my UA can automatically do certain actions, 
such as establishing a cpcp session or opening a web browser to display 
extra information.

To do this, we don't only need to add a <purpose> element, but we need 
to list a collection of values and the semantics associated to them. For 
instance, the focus needs to indicate "this is the URI where you can 
initiate a BFCP session"; then my UA can initiate a BFCP session if it 
is able to do it.

So the point is that we need to list the different values that the 
<purpose> element can take, otherwise, different focus can encode 
different values, and UAs will not be able to interpret them.

Further more, it is clear that we need extensibility, since there are 
protocols associated to a conference that are still under development.

Having an extensible list of possible values defined in the XML schema 
is hard, as it has been discussed in SIMPLE. Therefore, my 
recommendation was to define the <purpose> element as a string, and open 
an IANA registration of values. Each value will indicate the purpose of 
this URI and perhaps the protocol that can be used to access it.

I would like to know if the working group would have a problem if the 
conference package adds a <purpose> element in the URI <entry> 
definition, the values of <purpose> will be registered with IANA.

Regards,

             Miguel


Miguel Garcia wrote:

> On reviewing the conference event package, I found several places where 
> URIs try to represent different aspects of the conference.
> 
> Specifically, the current event package defines these three types of 
> URIs within the <conference-description> element:
> 
> <web-page>
> <conf-uris>
> <service-uris>
> 
> The <web-page> element is clear, it is just a displayable web page URI. 
> The <conf-uris> is also clear, is just a URI where a participant can 
> join the conference.
> The <service-uris> is tricky. It pretends to be a URI that gives you 
> access to other "things", such as CPCP, or MPCP, or access rules. 
> However, there are no semantics associated with this element, so the 
> software can only display this information to the user, and let him take 
> an action about that URI.
> 
> I think this can be improved by having some automatic way of indicating 
> to the software what is the purpose of a URI. Also, I think we can group 
> all these URIs in a single element that contains a number of entries. 
> The idea: a single <uris> element that includes one or more <entry> 
> elements, which include a <uri> and a new <purpose> elements that 
> indicate what is the purpose of that URI. The <purpose> element contains 
> a token, such as "conference" (the actual conference uri), "information" 
> (e.g., web page), "cpcp" (uri to do cpcp), "mpcp" (uri to do mpcp), 
> "conference-event" (the actual uri to subscribe to this package) , 
> "floor-control", "sidebars" or any other token that is required.
> 
> If we follow this scheme, there is no need for 3 different elements 
> anymore, just one. And we get a standardized <purpose> element, so the 
> software can get the information of where to do the appropriate action 
> (e.g., start a floor control session).
> 
> An example of my proposal, including a couple of conference uris (sip 
> and tel URLs), a CPCP URI and a web page:
> 
> <conference-info entity="sips:conf233@example.com" state="partial" 
> version="5" >
>  <conference-description>
>    <subject>Agenda: This month's target</subject>
>    <uris>
>      <entry>
>        <uri>sip:conf34@conf.example.com</uri>
>        <purpose>conference</purpose>
>      </entry>
> 
>      <entry>
>        <uri>tel:+1-555-7777</uri>
>        <purpose>conference</purpose>
>      </entry>
> 
>      <entry>
>        <uri>http://salesgroup.example.com/policies/meeting.xml</uri>
>        <purpose>cpcp</purpose>
>      </entry>
> 
>      <entry>
>        <uri>http://info.example.com/conf/conf32.html</uri>
>        <purpose>information</purpose>
>      </entry>
>   </uris>
> </conference-description>
> 
> In my opinion, this is elegant and precise. The only drawback is that 
> this requires to open an IANA registration for values of the <purpose> 
> elements of URIs, but I don't see a big issue with this. It also 
> requires to allocate semantics to each of these tokens.
> 
> The relevant part of the XML schema will look like this:
> 
>      <!--
>        CONFERENCE URI TYPE
>      -->
>      <xs:complexType name="uri-type">
>        <xs:sequence>
>           <xs:element name="uri" type="xs:anyURI"/>
>           <xs:element name="label" type="xs:string" minOccurs="0"/>
>           <xs:element name="purpose" type="xs:string"
>                       maxOccurs="unbounded"/>
>           <xs:element name="modified" type="execution-type"
>                       minOccurs="0"/>
>           <xs:element name="extended" type="extended-type" minOccurs="0"
>                       maxOccurs="unbounded"/>
>        </xs:sequence>
>        <xs:anyAttribute/>
>      </xs:complexType>
> 
> 
> The draft will also need to open an IANA registry for the values of the 
> <purpose> element in this XML document. The initial values could be:
> - information: web page containing additional conference information
> - cpcp: URL to do CPCP actions
> - mpcp: URL to do MPCP actions (if MPCP requires URLs)
> - floor-control: URL to initiate a floor-control session
> - conference-event: not required, just for completeness. URL to 
> subscribe to the conference event package of this conference.
> - access-rules? Is this one needed
> 
> One thing, though: I first thought about using substitution groups in 
> the XML schema, but due to the discussion in SIMPLE about how to create 
> extensible tokens, I believe the IANA registry and a text string is what 
> we are looking for. But we should apply the same output as in SIMPLE 
> documents.
> 
> But in essence, what is the feeling of the working group about this 
> proposal?
> 
> Regards,
> 
>           Miguel

-- 
Miguel A. Garcia           tel:+358-50-4804586
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 30 14:47:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26027
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 14:47:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZE2y-0005Lu-Ew
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 14:52:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDl0-0002sg-TA; Tue, 30 Nov 2004 14:33:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZDXH-0007Dh-Pn
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 14:19:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22218
	for <sipping@ietf.org>; Tue, 30 Nov 2004 14:19:37 -0500 (EST)
Message-Id: <200411301919.OAA22218@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZDcR-0004WN-NX
	for sipping@ietf.org; Tue, 30 Nov 2004 14:25:00 -0500
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CZERz-0005mO-1t; Tue, 30 Nov 2004 13:18:15 -0700
From: "Brian Rosen" <br@brianrosen.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>,
        "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
Subject: RE: [Sipping] Conference speaker control
Date: Tue, 30 Nov 2004 14:18:54 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C730BF8@IsrExch01.israel.polycom.com>
Thread-Index: AcTWKvXtPmbv77nEToKg4F9J0NdQPAAjRh2QAAsod7AACGlv+QACvUmQ
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Content-Transfer-Encoding: 7bit
Cc: "'sipping'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: 7bit

Brian

There is no requirement to use RTP, there is merely no existing alternative.

Brian


> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Tuesday, November 30, 2004 12:59 PM
> To: Brian Rosen; Magnus Westerlund
> Cc: sipping
> Subject: RE: [Sipping] Conference speaker control
> 
> Brian,
> I know it is SIPPINg and I mentioned that we may extend the conference
> package in XCON.
> I am still not sure about the ssrc. Does SIP allows only RTP sessions. As
> far as I know there is no such assumption in SDP.
> Roni Even
> 
> ________________________________
> 
> From: sipping-bounces@ietf.org on behalf of Brian Rosen
> Sent: Tue 11/30/2004 4:02 PM
> To: Even, Roni; 'Magnus Westerlund'
> Cc: 'sipping'
> Subject: RE: [Sipping] Conference speaker control
> 
> 
> 
> Roni
> 
> This is SIPPING.  If we have PSTN participants in a conference, they come
> from some kind of gateway and use SIP signaling.  AFAIK, there is no way
> with current IETF protocols to have a conference where the participants
> are
> anything but SIP endpoints using RTP for media streams.
> 
> You might ask over in the XCON list whether anyone thinks trying to use
> XCON
> protocols to control a PSTN mixer without RTP is in scope.  XCON is not
> limited to SIP, but I'm not sure such a case is something we should be
> worried about.  It's clearly not something in SIPPING's charter.
> 
> Brian
> 
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> > Of Even, Roni
> > Sent: Tuesday, November 30, 2004 3:46 AM
> > To: Magnus Westerlund
> > Cc: sipping
> > Subject: RE: [Sipping] Conference speaker control
> >
> > Magnus,
> > The problem you stated is correct but this is not what I meant. In XCON
> > conference server can be composed of a conference/media policy server
> > and a focus that can be an application server that handle conference
> > policy and some web collaboration while the mixer is a PSTN bridge.
> > A participant in such a conference is using a PSTN phone and a PC for
> > web collaboration and conference control. The PC can subscribe to the
> > conference package but since the audio is PSTN there are no RTP or SSRC.
> > Even for IP conferencing making an assumption that all streams in a
> > conference are RTP streams is not always right, so ssrc cannot be used
> > to describe who is sourcing each stream in an application that uses a
> > mix of RTP and non RTP streams.
> > Roni Even
> >
> > -----Original Message-----
> > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > Sent: Monday, November 29, 2004 5:45 PM
> > To: Even, Roni
> > Cc: sipping
> > Subject: Re: [Sipping] Conference speaker control
> >
> > Hi Roni,
> >
> > Lets see if I understand this correctly. You are worried about PSTN or
> > other gateways that are receiving more than one source over the same
> > circuit and in which cases the gateway can't separate the different
> > sources within the CS to IP gateway. As long as the PSTN gateway
> > receives the different circuit switched sources in the same conference
> > on different circuits, it is able to assign them different SSRCs and
> > IDs.
> >
> > If the above is the case, how would adding any other mechanism help? The
> >
> > gateway can still not identify the original sources, or am I
> > misunderstanding something about the setup?
> >
> > My understanding of the setup you are concern is:
> >
> >
> > CS1 --\
> >         -> CS Bridge -> Gateway ->  IP Conf Bridge -> Client 3
> > CS2 --/                  ^               ^
> >                           |               |
> >                          CS5           Client 4
> >
> > In this case Client 3 and 4 would not be able to determine that what is
> > beyond the gateway is in fact three client. CS1 and CS2 will be bunched
> > together under one source identifier? While CS5 can be identified as it
> > connects directly with the gateway and uses a separate CS line into the
> > gateway, thus allowing the gateway to give them separate IDs.
> >
> > It should also not be a problem if the protocol used on the CS side
> > provides identities, then the gateway can provide different identifiers
> > for the different CS side users.
> >
> > Cheers
> >
> > Magnus
> >
> > Even, Roni wrote:
> >
> > > Magnus,
> > > I am not saying that RTP using SSRC does not have a mechanism to
> > > identify the source of the streams. What I am trying to say is that we
> > > are not talking about a pure RTP mixer but we are talking about a SIP
> > > based conferencing server and in XCON the scope is even wider, it may
> > be
> > > a PSTN bridge bellow.
> > > So first of all there is no requirement defined that the mixer in SIP
> > > conferencing or XCON should be a RTP mixer per RFC3550. Even if we do
> > it
> > > for SIPPING then we will have a problem for PSTN Bridge (example of
> > > usage if for audio-graphic conference) and it will break for XCON.
> > > Roni Even
> >
> >
> > --
> >
> > Magnus Westerlund
> >
> > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > ----------------------------------------------------------------------
> > Ericsson AB                | Phone +46 8 4048287
> > Torshamsgatan 23           | Fax   +46 8 7575550
> > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.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
> 
> 
> 




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 sipping-bounces@ietf.org  Tue Nov 30 14:47:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26174
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 14:47:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZE3t-0005OK-7S
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 14:53:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDlB-0002vs-RR; Tue, 30 Nov 2004 14:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZDat-0007yD-2e; Tue, 30 Nov 2004 14:23:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22593;
	Tue, 30 Nov 2004 14:23:21 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZDg2-0004cy-Kk; Tue, 30 Nov 2004 14:28:44 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 30 Nov 2004 12:29:57 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAUJMKAC013433;
	Tue, 30 Nov 2004 11:22:21 -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 LAA22216;
	Tue, 30 Nov 2004 11:22:43 -0800 (PST)
Message-Id: <4.3.2.7.2.20041130132024.03056f00@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 30 Nov 2004 13:22:53 -0600
To: sip@ietf.org, sipping@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Sipping] Any talk of an Interim for SIP or SIPPING?
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Hey

Is there any serious talk about having an interim meeting for SIP or SIPPING?

Just trying to plan travel schedules in advance, and say the XCON 
announcement (knowing it,SIP, SIPPING and SIMPLE were thrown in together 
for one super meeting last May).

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 sipping-bounces@ietf.org  Tue Nov 30 16:54:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17762
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 16:54:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZG2U-0003TE-6P
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 17:00:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZEeu-0002OX-S3; Tue, 30 Nov 2004 15:31:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZELT-0007rq-UM; Tue, 30 Nov 2004 15:11:32 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28970;
	Tue, 30 Nov 2004 15:11:30 -0500 (EST)
Message-Id: <200411302011.PAA28970@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 30 Nov 2004 15:11:29 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-conference-package-07.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--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		: A Session Initiation Protocol (SIP) Event Package for                           Conference State
	Author(s)	: J. Rosenberg, et al.
	Filename	: draft-ietf-sipping-conference-package-07.txt
	Pages		: 46
	Date		: 2004-11-30
	
This document defines a conference event package for the Session
   Initiation Protocol (SIP) Events framework, along with a data format
   used in notifications for this package.  The conference package
   allows users to subscribe to a conference URI.  Notifications are
   sent about changes in the membership of this conference and
   optionally about changes in the state of additional conference
   components.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-conference-package-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-conference-package-07.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-conference-package-07.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: <2004-11-30111501.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-conference-package-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-conference-package-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--NextPart--





From sipping-bounces@ietf.org  Tue Nov 30 16:55:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18059
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 16:55:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZG3f-0003ag-L4
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 17:01:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZEf1-0002R9-Tf; Tue, 30 Nov 2004 15:31:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZELZ-0007st-VO; Tue, 30 Nov 2004 15:11:40 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28986;
	Tue, 30 Nov 2004 15:11:35 -0500 (EST)
Message-Id: <200411302011.PAA28986@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 30 Nov 2004 15:11:35 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-cc-conferencing-06.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--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 Call Control 
                          - Conferencing for User Agents
	Author(s)	: A. Johnston, O. Levin
	Filename	: draft-ietf-sipping-cc-conferencing-06.txt
	Pages		: 39
	Date		: 2004-11-30
	
This specification defines conferencing call control features for the
   Session Initiation Protocol (SIP).  This document builds on the
   Conferencing Requirements and Framework documents to define how a
   tightly coupled SIP conference works.  The approach is explored from
   different user agent (UA) types perspective: conference-unaware,
   conference-aware and focus UAs.  The use of URIs in conferencing,
   OPTIONS for capabilities discovery, and call control using REFER are
   covered in detail with example call flow diagrams.  The usage of the
   isfocus feature tag is defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-conferencing-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-cc-conferencing-06.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-cc-conferencing-06.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: <2004-11-30111512.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-cc-conferencing-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-cc-conferencing-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
--NextPart--





From sipping-bounces@ietf.org  Tue Nov 30 17:29:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23160
	for <sipping-web-archive@ietf.org>; Tue, 30 Nov 2004 17:29:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZGa6-0005BG-Vc
	for sipping-web-archive@ietf.org; Tue, 30 Nov 2004 17:34:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZGAc-0005Tt-Lx; Tue, 30 Nov 2004 17:08:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZEsL-00020V-BZ
	for sipping@megatron.ietf.org; Tue, 30 Nov 2004 15:45:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02712
	for <sipping@ietf.org>; Tue, 30 Nov 2004 15:45:27 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZExW-00070X-5k
	for sipping@ietf.org; Tue, 30 Nov 2004 15:50:50 -0500
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 30 Nov 2004 12:45:03 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1277); 
	Tue, 30 Nov 2004 12:44:56 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.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] URIs in conference event package.
Date: Tue, 30 Nov 2004 12:44:54 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03CAFB15@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] URIs in conference event package.
Thread-Index: AcTXEWC6Wi61PIgETKOlounsKreebgACW+6Q
X-Priority: 1
Priority: Urgent
Importance: high
From: "Orit Levin" <oritl@microsoft.com>
To: "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, "sipping" <sipping@ietf.org>
X-OriginalArrivalTime: 30 Nov 2004 20:44:56.0147 (UTC)
	FILETIME=[734A0230:01C4D71D]
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1
Content-Transfer-Encoding: quoted-printable
Cc: Alan Johnston <alan.johnston@mci.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 2a9ffb6f997442a3b543bcdaf483b990
Content-Transfer-Encoding: quoted-printable

To complete the "poll", I am including the "IANA Consideration" text
proposed by Miguel in earlier email exchanges (with slight editorial
changes). Please review the text.

If I don't hear any opposition in the following two days, I will include
the text, remove the currently "stand-alone" recording element from the
schema, and resubmit it as -08.

Thanks a lot,
Orit.

-------------


This document instructs IANA to open a new "purpose of URI" sub-registry
under the registry of SIP parameters
(http://www.iana.org/assignments/sip-parameters):

       purpose of URI

The purpose of URI is an XML element encoded in the conference event
package (draft-ietf-sipping-conference-package). The value of the
<purpose> element indicates the intended purpose of an associated URI.

This sub-registry is defined as a table that contains three columns:

Value: the token under registration.

Description: A descriptive text that indicates what is the intended
usage of the URI.

Document: A reference to the document defining the registration.

This specification instructs IANA to create this table with an initial
entry.  The resulting table would look like:

Value         Description                                   Document
-------       --------------------------------------------  ----------

participation The URI can be used to join the conference    [RFC XXXX]
streaming     The URI can be used to access the streamed    [RFC XXXX]
              conference data  =20
event         The URI can be used to subscribe to the       [RFC XXXX]
              conference event package
recording     The URI can be used to access the recorded    [RFC XXXX]
              conference data
web-page      The URI can be used to access a web page      [RFC XXXX]
              that contains additional information of
              the conference

New values of the purpose of URI are registered by the IANA when a
specification becomes available, according to the definition of
Specification Required in RFC 2434. The IANA Considerations section of
the specification must include the following information, which appears
in the IANA registry along with the specification of the publication:

Value: the value of the <purpose> element to be registered.
Description: a short description of the intended usage of the URI.
-------------=20

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]=20
> Sent: Tuesday, November 30, 2004 11:18 AM
> To: sipping
> Cc: Alan Johnston; Orit Levin
> Subject: Re: [Sipping] URIs in conference event package.
>=20
> Hi:
>=20
> A few days ago I submitted some comments to the conference=20
> event package. I was proposing to add a <purpose> element to=20
> a uri <entry>, so that it was possible to describe what=20
> service is behind that URI. The idea I had in mind is that my=20
> UA can receive a notification of the conference event package=20
> and my UA can automatically do certain actions, such as=20
> establishing a cpcp session or opening a web browser to=20
> display extra information.
>=20
> To do this, we don't only need to add a <purpose> element,=20
> but we need to list a collection of values and the semantics=20
> associated to them. For instance, the focus needs to indicate=20
> "this is the URI where you can initiate a BFCP session"; then=20
> my UA can initiate a BFCP session if it is able to do it.
>=20
> So the point is that we need to list the different values=20
> that the <purpose> element can take, otherwise, different=20
> focus can encode different values, and UAs will not be able=20
> to interpret them.
>=20
> Further more, it is clear that we need extensibility, since=20
> there are protocols associated to a conference that are still=20
> under development.
>=20
> Having an extensible list of possible values defined in the=20
> XML schema is hard, as it has been discussed in SIMPLE.=20
> Therefore, my recommendation was to define the <purpose>=20
> element as a string, and open an IANA registration of values.=20
> Each value will indicate the purpose of this URI and perhaps=20
> the protocol that can be used to access it.
>=20
> I would like to know if the working group would have a=20
> problem if the conference package adds a <purpose> element in=20
> the URI <entry> definition, the values of <purpose> will be=20
> registered with IANA.
>=20
> Regards,
>=20
>              Miguel
>=20
>=20
> Miguel Garcia wrote:
>=20
> > On reviewing the conference event package, I found several places=20
> > where URIs try to represent different aspects of the conference.
> >=20
> > Specifically, the current event package defines these three=20
> types of=20
> > URIs within the <conference-description> element:
> >=20
> > <web-page>
> > <conf-uris>
> > <service-uris>
> >=20
> > The <web-page> element is clear, it is just a displayable=20
> web page URI.=20
> > The <conf-uris> is also clear, is just a URI where a=20
> participant can=20
> > join the conference.
> > The <service-uris> is tricky. It pretends to be a URI that=20
> gives you=20
> > access to other "things", such as CPCP, or MPCP, or access rules.
> > However, there are no semantics associated with this=20
> element, so the=20
> > software can only display this information to the user, and let him=20
> > take an action about that URI.
> >=20
> > I think this can be improved by having some automatic way of=20
> > indicating to the software what is the purpose of a URI.=20
> Also, I think=20
> > we can group all these URIs in a single element that=20
> contains a number of entries.
> > The idea: a single <uris> element that includes one or more <entry>=20
> > elements, which include a <uri> and a new <purpose> elements that=20
> > indicate what is the purpose of that URI. The <purpose> element=20
> > contains a token, such as "conference" (the actual=20
> conference uri), "information"
> > (e.g., web page), "cpcp" (uri to do cpcp), "mpcp" (uri to do mpcp),=20
> > "conference-event" (the actual uri to subscribe to this package) ,=20
> > "floor-control", "sidebars" or any other token that is required.
> >=20
> > If we follow this scheme, there is no need for 3 different elements=20
> > anymore, just one. And we get a standardized <purpose>=20
> element, so the=20
> > software can get the information of where to do the=20
> appropriate action=20
> > (e.g., start a floor control session).
> >=20
> > An example of my proposal, including a couple of conference=20
> uris (sip=20
> > and tel URLs), a CPCP URI and a web page:
> >=20
> > <conference-info entity=3D"sips:conf233@example.com" =
state=3D"partial"=20
> > version=3D"5" >
> >  <conference-description>
> >    <subject>Agenda: This month's target</subject>
> >    <uris>
> >      <entry>
> >        <uri>sip:conf34@conf.example.com</uri>
> >        <purpose>conference</purpose>
> >      </entry>
> >=20
> >      <entry>
> >        <uri>tel:+1-555-7777</uri>
> >        <purpose>conference</purpose>
> >      </entry>
> >=20
> >      <entry>
> >        <uri>http://salesgroup.example.com/policies/meeting.xml</uri>
> >        <purpose>cpcp</purpose>
> >      </entry>
> >=20
> >      <entry>
> >        <uri>http://info.example.com/conf/conf32.html</uri>
> >        <purpose>information</purpose>
> >      </entry>
> >   </uris>
> > </conference-description>
> >=20
> > In my opinion, this is elegant and precise. The only=20
> drawback is that=20
> > this requires to open an IANA registration for values of=20
> the <purpose>=20
> > elements of URIs, but I don't see a big issue with this. It also=20
> > requires to allocate semantics to each of these tokens.
> >=20
> > The relevant part of the XML schema will look like this:
> >=20
> >      <!--
> >        CONFERENCE URI TYPE
> >      -->
> >      <xs:complexType name=3D"uri-type">
> >        <xs:sequence>
> >           <xs:element name=3D"uri" type=3D"xs:anyURI"/>
> >           <xs:element name=3D"label" type=3D"xs:string" =
minOccurs=3D"0"/>
> >           <xs:element name=3D"purpose" type=3D"xs:string"
> >                       maxOccurs=3D"unbounded"/>
> >           <xs:element name=3D"modified" type=3D"execution-type"
> >                       minOccurs=3D"0"/>
> >           <xs:element name=3D"extended" type=3D"extended-type"=20
> minOccurs=3D"0"
> >                       maxOccurs=3D"unbounded"/>
> >        </xs:sequence>
> >        <xs:anyAttribute/>
> >      </xs:complexType>
> >=20
> >=20
> > The draft will also need to open an IANA registry for the values of=20
> > the <purpose> element in this XML document. The initial=20
> values could be:
> > - information: web page containing additional conference information
> > - cpcp: URL to do CPCP actions
> > - mpcp: URL to do MPCP actions (if MPCP requires URLs)
> > - floor-control: URL to initiate a floor-control session
> > - conference-event: not required, just for completeness. URL to=20
> > subscribe to the conference event package of this conference.
> > - access-rules? Is this one needed
> >=20
> > One thing, though: I first thought about using substitution=20
> groups in=20
> > the XML schema, but due to the discussion in SIMPLE about how to=20
> > create extensible tokens, I believe the IANA registry and a text=20
> > string is what we are looking for. But we should apply the=20
> same output=20
> > as in SIMPLE documents.
> >=20
> > But in essence, what is the feeling of the working group about this=20
> > proposal?
> >=20
> > Regards,
> >=20
> >           Miguel
>=20
> --=20
> Miguel A. Garcia           tel:+358-50-4804586
> Nokia Research Center      Helsinki, Finland
>=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


