From mailman-bounces@ietf.org  Wed Dec  1 06:25: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 GAA15442
	for <sipping-web-archive@ietf.org>; Wed, 1 Dec 2004 06:25:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZSgu-0005yb-NS
	for sipping-web-archive@ietf.org; Wed, 01 Dec 2004 06:30:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZRu0-0004Wm-De
	for sipping-web-archive@ietf.org; Wed, 01 Dec 2004 05:40:04 -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.3857.1101896941.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:29:01 -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  Wed Dec  1 15: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 PAA22720
	for <sipping-web-archive@ietf.org>; Wed, 1 Dec 2004 15:51:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZbX1-0003im-Mw
	for sipping-web-archive@ietf.org; Wed, 01 Dec 2004 15:57:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZZxm-0003iz-7l; Wed, 01 Dec 2004 14:16:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZZEF-0000Fl-PH
	for sipping@megatron.ietf.org; Wed, 01 Dec 2004 13:29: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 NAA06574
	for <sipping@ietf.org>; Wed, 1 Dec 2004 13:29:25 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZZJc-0007Zl-E6
	for sipping@ietf.org; Wed, 01 Dec 2004 13:35:01 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iB1ISs402646
	for <sipping@ietf.org>; Wed, 1 Dec 2004 13:28:54 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQM2M5X5>; Wed, 1 Dec 2004 13:28:54 -0500
Message-ID: <0CCD4D34B2952A48AB838DF2D5C840D7027BC6F4@zcarhxm0.corp.nortel.com>
From: "Joe Zebarth" <zebarth@nortelnetworks.com>
To: sipping@ietf.org
Date: Wed, 1 Dec 2004 13:28:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Subject: [Sipping] Comments on
	draft-ietf-sipping-app-interaction-framework-03
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="===============0791606461=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d

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.

--===============0791606461==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D7D3.9761FE28"

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_01C4D7D3.9761FE28
Content-Type: text/plain

Colleagues

The following are a few comments that I have with respect to
draft-ietf-sipping-app-interaction-framework-03.

Would it be worth noting in the abstract and/or the introduction that this
document is providing IANA registration for a new "SIP Option Tag" and a new
"Header Field Parameter"?

Is there an inconsistency between Figure 1 which shows the "user interface"
on the network side of the user device and the definition "Focusless User
Interface: A user interface which has no ability to perform focus
determination.  An example of a focusless user interface is a keypad on a
telephone."  So if the definition is correct should Figure 1 show a "user
interface" on the user side of the "user device".  If so, should we consider
a new term that is less confusing for the functionality currently labeled as
"user interface" in Figure 1?

In the definition for "Barge-In", possibly the last sentence should come to
the front.  Minor rewording would be required if this is done.

On page 18 the words "the markup waits".  I observe that the term "markup"
is not in the definitions section, should it be added or is there a better
term for this functionality?
  


Kindest Regards

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



------_=_NextPart_001_01C4D7D3.9761FE28
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>Comments on =
draft-ietf-sipping-app-interaction-framework-03</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">The following are a few comments that =
I have with respect to =
draft-ietf-sipping-app-interaction-framework-03.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Would it be worth noting in the =
abstract and/or the introduction that this document is providing IANA =
registration for a new &quot;SIP Option Tag&quot; and a new =
&quot;Header Field Parameter&quot;?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is there an inconsistency between =
Figure 1 which shows the &quot;user interface&quot; on the network side =
of the user device and the definition &quot;Focusless User Interface: A =
user interface which has no ability to perform focus =
determination.&nbsp; An example of a focusless user interface is a =
keypad on a telephone.&quot;&nbsp; So if the definition is correct =
should Figure 1 show a &quot;user interface&quot; on the user side of =
the &quot;user device&quot;.&nbsp; If so, should we consider a new term =
that is less confusing for the functionality currently labeled as =
&quot;user interface&quot; in Figure 1?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In the definition for =
&quot;Barge-In&quot;, possibly the last sentence should come to the =
front.&nbsp; Minor rewording would be required if this is =
done.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">On page 18 the words &quot;the markup =
waits&quot;.&nbsp; I observe that the term &quot;markup&quot; is not in =
the definitions section, should it be added or is there a better term =
for this functionality?</FONT></P>

<P><FONT FACE=3D"Times New Roman">&nbsp; </FONT>
</P>
<BR>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C4D7D3.9761FE28--


--===============0791606461==
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
--===============0791606461==--



From sipping-bounces@ietf.org  Thu Dec  2 14:51:46 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 OAA21599
	for <sipping-web-archive@ietf.org>; Thu, 2 Dec 2004 14:51:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZx50-0005G4-KC
	for sipping-web-archive@ietf.org; Thu, 02 Dec 2004 14:57:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZutK-00027H-0m; Thu, 02 Dec 2004 12:37:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZqg3-00008M-Cc
	for sipping@megatron.ietf.org; Thu, 02 Dec 2004 08:07: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 IAA12478
	for <sipping@ietf.org>; Thu, 2 Dec 2004 08:07:17 -0500 (EST)
Received: from fep10.012.net.il ([212.117.129.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZqlY-0001km-6A
	for sipping@ietf.org; Thu, 02 Dec 2004 08:13:02 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep10.012.net.il with ESMTP
	id <20041202130616.NKWB17592.fep10@isrexch01.israel.polycom.com>;
	Thu, 2 Dec 2004 15:06:16 +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] Conference speaker control
Date: Thu, 2 Dec 2004 15:06:32 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C709623@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTWKvXtPmbv77nEToKg4F9J0NdQPAAjRh2QAAsod7AACGlv+QACvUmQAFeUaMA=
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: a492040269d440726bfd84680622cee7
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: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: quoted-printable

Hi,
What about sending media over tcp based on the comedia draft, this is
not RTP.
Roni

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Brian Rosen
Sent: Tuesday, November 30, 2004 9:19 PM
To: Even, Roni; 'Magnus Westerlund'
Cc: 'sipping'
Subject: RE: [Sipping] Conference speaker control

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
>=20
> 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
>=20
> ________________________________
>=20
> 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
>=20
>=20
>=20
> Roni
>=20
> 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.
>=20
> 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.
>=20
> Brian
>=20
> > -----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
> >
>=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




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 Dec  2 16:09: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 QAA29616
	for <sipping-web-archive@ietf.org>; Thu, 2 Dec 2004 16:09:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZyHi-0007Cz-QF
	for sipping-web-archive@ietf.org; Thu, 02 Dec 2004 16:14:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZuwp-0005Rq-JI; Thu, 02 Dec 2004 12:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZrPA-0002MV-CZ
	for sipping@megatron.ietf.org; Thu, 02 Dec 2004 08:53: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 IAA18425
	for <sipping@ietf.org>; Thu, 2 Dec 2004 08:53:54 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZrUc-0003m5-Gg
	for sipping@ietf.org; Thu, 02 Dec 2004 08:59:40 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB2DrnvD010800
	for <sipping@ietf.org>; Thu, 2 Dec 2004 14:53:49 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Dec 2004 14:53:47 +0100
Received: from [147.214.34.68] (research-1fd0e1.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 X8A3D361; Thu, 2 Dec 2004 14:49:46 +0100
Message-ID: <41AF1D7A.8070905@ericsson.com>
Date: Thu, 02 Dec 2004 14:49:46 +0100
X-Sybari-Trust: ae691940 96d33411 638159be 00000138
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: <144ED8561CE90C41A3E5908EDECE315C709623@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C709623@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2004 13:53:47.0977 (UTC)
	FILETIME=[58BD7B90:01C4D876]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Hi Roni,

Even, Roni wrote:

> Hi,
> What about sending media over tcp based on the comedia draft, this is
> not RTP.

It may or it may not. Any media over TCP will need some type of framing, 
either if it is a HTTP download of a progressive media stream, or if it 
is RTP over TCP. There is actually a generic RTP over TCP proposal 
including protocol identifier for SDP in:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-contrans-03.txt

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  Thu Dec  2 21:19: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 VAA27781
	for <sipping-web-archive@ietf.org>; Thu, 2 Dec 2004 21:19:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca38i-0006Ax-Ve
	for sipping-web-archive@ietf.org; Thu, 02 Dec 2004 21:25:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca0Q3-0004De-G9; Thu, 02 Dec 2004 18:31:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZxUT-0003Jk-AX
	for sipping@megatron.ietf.org; Thu, 02 Dec 2004 15:23: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 PAA24817
	for <sipping@ietf.org>; Thu, 2 Dec 2004 15:23: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 1CZxa0-0005v5-GD
	for sipping@ietf.org; Thu, 02 Dec 2004 15:29:36 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 02 Dec 2004 12:29:46 -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 iB2KN72O002124;
	Thu, 2 Dec 2004 12:23:08 -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 iB2KLH2Q020579;
	Thu, 2 Dec 2004 12:22:21 -0800
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C709623@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C709623@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EBC65558-449F-11D9-8CD3-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Conference speaker control
Date: Thu, 2 Dec 2004 15:22:43 -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:"1102018955.115981"; x:"432200"; a:"rsa-sha1"; b:"nofws:7505";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"ac5TyupOM62fC76WosedMFAShURJRf2cJODLcfIgh0vRhSdljJCejuwIkJ8Kj"
	"NKBC1nBadrYwQ25d+OIUPRKyt/p0CSjeLwDBstV/mKpHC2ehFoWwDTL/FeWfY"
	"cYUZdAUoWduk+j8dEKoJdB86qcztYJm+unXquYmXkWN3T3j34=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Conference speaker control";
	c:"Date: Thu, 2 Dec 2004 15:22:43 -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: 36fb765c89ed47dab364ab702a78e8fd
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: 7698d1420ecbbce1995432e99bb6d1a1
Content-Transfer-Encoding: 7bit

Huh? There's a spec for RTP over TCP.

On Dec 2, 2004, at 8:06 AM, Even, Roni wrote:

> Hi,
> What about sending media over tcp based on the comedia draft, this is
> not RTP.
> Roni
>
> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Brian Rosen
> Sent: Tuesday, November 30, 2004 9:19 PM
> To: Even, Roni; 'Magnus Westerlund'
> Cc: 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>
> 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
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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  Fri Dec  3 07:55: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 HAA00358
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 07:55:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaD3V-0002Ql-0g
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 08:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaAd1-0005Dr-SM; Fri, 03 Dec 2004 05:25:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca8yb-0001Km-Vy
	for sipping@megatron.ietf.org; Fri, 03 Dec 2004 03:39: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 DAA12286
	for <sipping@ietf.org>; Fri, 3 Dec 2004 03:39:40 -0500 (EST)
Received: from fep14.012.net.il ([212.117.129.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca94I-0005sL-LO
	for sipping@ietf.org; Fri, 03 Dec 2004 03:45:35 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep14.012.net.il with ESMTP
	id <20041203083442.QCQU13819.fep14@isrexch01.israel.polycom.com>;
	Fri, 3 Dec 2004 10:34:42 +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] Conference speaker control
Date: Fri, 3 Dec 2004 10:39:04 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C70976A@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTY4n8vYkOwNEaKSaGtXhqgi3vn+AAMOHtA
From: "Even, Roni" <roni.even@polycom.co.il>
To: "David R Oran" <oran@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8068004c042dabd7f1301bcc80e039df
Content-Transfer-Encoding: quoted-printable
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: 3.0 (+++)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b
Content-Transfer-Encoding: quoted-printable

Hi,=20
This is from the comedia draft, is it RTP, it does not say so.

           m=3Dimage 54111 TCP t38
           c=3DIN IP4 192.0.2.2
           a=3Dsetup:passive
           a=3Dconnection:new

Roni

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of David R Oran
Sent: Thursday, December 02, 2004 10:23 PM
To: Even, Roni
Cc: Magnus Westerlund; sipping
Subject: Re: [Sipping] Conference speaker control

Huh? There's a spec for RTP over TCP.

On Dec 2, 2004, at 8:06 AM, Even, Roni wrote:

> Hi,
> What about sending media over tcp based on the comedia draft, this is
> not RTP.
> Roni
>
> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Brian Rosen
> Sent: Tuesday, November 30, 2004 9:19 PM
> To: Even, Roni; 'Magnus Westerlund'
> Cc: 'sipping'
> Subject: RE: [Sipping] Conference speaker control
>
> 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
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  3 08:35:47 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 IAA02985
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 08:35:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaDgj-0003F7-DF
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 08:41:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaAqo-00083s-MH; Fri, 03 Dec 2004 05:39:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca9Sl-0004Wm-QJ
	for sipping@megatron.ietf.org; Fri, 03 Dec 2004 04:10: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 EAA14151
	for <sipping@ietf.org>; Fri, 3 Dec 2004 04:10:50 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca9YE-0006ZN-Cx
	for sipping@ietf.org; Fri, 03 Dec 2004 04:16:45 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB39AZh5019326
	for <sipping@ietf.org>; Fri, 3 Dec 2004 10:10:35 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 10:10:35 +0100
Received: from [147.214.34.68] (research-1fd0e1.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 X8A3JGVN; Fri, 3 Dec 2004 10:10:35 +0100
Message-ID: <41B02D8A.7060908@ericsson.com>
Date: Fri, 03 Dec 2004 10:10:34 +0100
X-Sybari-Trust: 5012238a 96d33411 638159be 00000138
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: <144ED8561CE90C41A3E5908EDECE315C70976A@IsrExch01.israel.polycom.com>
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C70976A@IsrExch01.israel.polycom.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Dec 2004 09:10:35.0080 (UTC)
	FILETIME=[F298EC80:01C4D917]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, David R Oran <oran@cisco.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

Even, Roni wrote:
> Hi,
> This is from the comedia draft, is it RTP, it does not say so.
> 
>            m=image 54111 TCP t38
>            c=IN IP4 192.0.2.2
>            a=setup:passive
>            a=connection:new
> 
> Roni

No, that is clearly T38 over TCP which has a mode that is not RTP, 
however if you look in the RTP over TCP draft:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-contrans-03.txt

You can find the following SDP:
v=0
o=first 2520644554 2838152170 IN IP4 first.example.net
s=Example
t=0 0
c=IN IP4 192.0.2.105
m=audio 9 TCP/RTP/AVP 11
a=setup:active
a=connid:1

It is also this draft that register the RTP over TCP SDP protocol 
identifier.


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  Fri Dec  3 12:55: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 MAA08229
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 12:55:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaHkC-0004QM-8R
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 13:01:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDRB-0001ff-P9; Fri, 03 Dec 2004 08:25:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaCL0-0003KF-Tj; Fri, 03 Dec 2004 07:15:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27927;
	Fri, 3 Dec 2004 07:15:00 -0500 (EST)
Message-Id: <200412031215.HAA27927@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 03 Dec 2004 07:15:00 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-list-conferencing-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.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--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		: Conference Establishment Using Request-Contained
                          Lists in the Session Initiation Protocol (SIP)
	Author(s)	: G. Camarillo, A. Johnston
	Filename	: draft-ietf-sipping-uri-list-conferencing-02.txt
	Pages		: 9
	Date		: 2004-12-2
	
This document describes how to create a conference using SIP URI-list
   services. In particular, we describe a mechanism that allows a client
   to provide a conference server with the initial list of participants
   using an INVITE-contained URI-list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-list-conferencing-02.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-uri-list-conferencing-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-uri-list-conferencing-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-uri-list-conferencing-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-12-2115509.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  Fri Dec  3 12:57: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 MAA08809
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 12:57:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaHmi-0004cn-ER
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 13:04:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDRF-0001hf-Tf; Fri, 03 Dec 2004 08:25:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaCL5-0003KY-25; Fri, 03 Dec 2004 07:15:07 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27934;
	Fri, 3 Dec 2004 07:15:04 -0500 (EST)
Message-Id: <200412031215.HAA27934@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 03 Dec 2004 07:15:04 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-list-message-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.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		: Multiple-Recipient MESSAGE Requests in the Session
                          Initiation Protocol (SIP)
	Author(s)	: M. Garcia-Martin, G. Camarillo
	Filename	: draft-ietf-sipping-uri-list-message-02.txt
	Pages		: 20
	Date		: 2004-12-2
	
This document specifies how to request a SIP URI-list service to send
   a copy of a MESSAGE to a set of destinations.  The client sends a SIP
   MESSAGE request with a URI-list to the MESSAGE URI-list service,
   which sends a similar MESSAGE request to each of the URIs included in
   the list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-list-message-02.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-uri-list-message-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-uri-list-message-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-uri-list-message-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-12-2115527.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  Fri Dec  3 13:00: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 NAA09445
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 13:00:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaHp5-0004qp-2T
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 13:06:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDRM-0001jf-I3; Fri, 03 Dec 2004 08:25:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaCL9-0003Ka-3K; Fri, 03 Dec 2004 07:15:11 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27942;
	Fri, 3 Dec 2004 07:15:08 -0500 (EST)
Message-Id: <200412031215.HAA27942@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 03 Dec 2004 07:15:08 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-multiple-refer-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.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		: Refering to Multiple Resources in the Session
                          Initiation Protocol (SIP)
	Author(s)	: G. Camarillo, et al.
	Filename	: draft-ietf-sipping-multiple-refer-02.txt
	Pages		: 12
	Date		: 2004-12-2
	
This document defines extensions to the SIP REFER method so that this
   method can be used to refer servers to multiple resources.  These
   extensions include the use of pointers to Uniform Resource Identifier
   (URI)-lists in the Refer-To header field and the "multiple-refer" SIP
   option-tag.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-multiple-refer-02.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-multiple-refer-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-multiple-refer-02.txt

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

Content-Type: text/plain
Content-ID: <2004-12-2115542.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  Fri Dec  3 13:03: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 NAA10201
	for <sipping-web-archive@ietf.org>; Fri, 3 Dec 2004 13:03:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaHsQ-00057j-3m
	for sipping-web-archive@ietf.org; Fri, 03 Dec 2004 13:09:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDRS-0001mN-N2; Fri, 03 Dec 2004 08:25:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaCLE-0003Kc-BT; Fri, 03 Dec 2004 07:15:16 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27949;
	Fri, 3 Dec 2004 07:15:13 -0500 (EST)
Message-Id: <200412031215.HAA27949@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 03 Dec 2004 07:15:13 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-services-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.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		: Requirements and Framework for Session Initiation 
                          Protocol (SIP)Uniform Resource Identifier (URI)-List 
                          Services
	Author(s)	: G. Camarillo, A. Roach
	Filename	: draft-ietf-sipping-uri-services-02.txt
	Pages		: 11
	Date		: 2004-12-2
	
This document describes the need for SIP URI-list services and
   provides requirements for their invocation.  Additionaly, it defines
   a framework for SIP URI-List services which includes security
   considerations applicable to these services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-uri-services-02.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-uri-services-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-uri-services-02.txt

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

Content-Type: text/plain
Content-ID: <2004-12-2115552.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  Sat Dec  4 09:06: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 JAA01279
	for <sipping-web-archive@ietf.org>; Sat, 4 Dec 2004 09:06:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Caaeh-0001Ra-Oq
	for sipping-web-archive@ietf.org; Sat, 04 Dec 2004 09:13:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaaXT-0002NO-V7; Sat, 04 Dec 2004 09:05:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaaX7-00027X-9B
	for sipping@megatron.ietf.org; Sat, 04 Dec 2004 09:05: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 JAA01233
	for <sipping@ietf.org>; Sat, 4 Dec 2004 09:05:07 -0500 (EST)
Received: from fep4.012.net.il ([212.117.129.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Caacz-0001OT-G3
	for sipping@ietf.org; Sat, 04 Dec 2004 09:11:18 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep4.012.net.il with ESMTP
	id <20041204140421.SDUL11445.fep4@isrexch01.israel.polycom.com>;
	Sat, 4 Dec 2004 16:04:21 +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] Conference speaker control
Date: Sat, 4 Dec 2004 16:04:20 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C7097C5@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTZPxWKM+ZlDnuXRve5oQ3CK9zC5AAysXpQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable
Cc: David R Oran <oran@cisco.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: 3.0 (+++)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable

Magnus,
The whole discussion is about the SIP conference package that suggests
that a SIP user will know the source of the stream based on SSRC. So if
there are media sessions that are not RTP is a SIP call then SSRC does
not work.=20
Roni

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Magnus Westerlund
Sent: Friday, December 03, 2004 11:11 AM
To: Even, Roni
Cc: sipping; David R Oran
Subject: Re: [Sipping] Conference speaker control

Even, Roni wrote:
> Hi,
> This is from the comedia draft, is it RTP, it does not say so.
>=20
>            m=3Dimage 54111 TCP t38
>            c=3DIN IP4 192.0.2.2
>            a=3Dsetup:passive
>            a=3Dconnection:new
>=20
> Roni

No, that is clearly T38 over TCP which has a mode that is not RTP,=20
however if you look in the RTP over TCP draft:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-contrans-
03.txt

You can find the following SDP:
v=3D0
o=3Dfirst 2520644554 2838152170 IN IP4 first.example.net
s=3DExample
t=3D0 0
c=3DIN IP4 192.0.2.105
m=3Daudio 9 TCP/RTP/AVP 11
a=3Dsetup:active
a=3Dconnid:1

It is also this draft that register the RTP over TCP SDP protocol=20
identifier.


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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  4 13:49: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 NAA15719
	for <sipping-web-archive@ietf.org>; Sat, 4 Dec 2004 13:49:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Caf4A-0006FU-Kv
	for sipping-web-archive@ietf.org; Sat, 04 Dec 2004 13:55:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaewF-0000be-5V; Sat, 04 Dec 2004 13:47:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaetK-0008Kr-B9
	for sipping@megatron.ietf.org; Sat, 04 Dec 2004 13:44: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 NAA15540
	for <sipping@ietf.org>; Sat, 4 Dec 2004 13:44:20 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaezJ-00069m-T3
	for sipping@ietf.org; Sat, 04 Dec 2004 13:50:34 -0500
Received: from lion.cs.columbia.edu
	(IDENT:GNjMvRIEU9bkBIuYJxE/GKIOjReRDzhv@lion.cs.columbia.edu
	[128.59.16.120])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id iB4IiITO012195
	for <sipping@ietf.org>; Sat, 4 Dec 2004 13:44:19 -0500 (EST)
Received: from [128.59.16.206] (chairpc.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by lion.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id iB4IiGiP005854
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 4 Dec 2004 13:44:16 -0500
Message-ID: <41B2057B.8050209@cs.columbia.edu>
Date: Sat, 04 Dec 2004 13:44:11 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sip-implementors@cs.columbia.edu, sipping <sipping@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0,
	Antispam-Data: 2004.12.4.4
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: Kundan Singh <kns10@cs.columbia.edu>,
        Salman Abdul Baset <sa2086@cs.columbia.edu>
Subject: [Sipping] Technical reports on Skype protocol analysis and SIP in
 peer-to-peer mode
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: 7bit

We have written two technical reports that might be of interest to 
members of the list. Both can be found at 
http://www1.cs.columbia.edu/~library/2004.html

     Peer-to-Peer Internet Telephony using SIP
     Kundan Singh and Henning Schulzrinne

describes how SIP, with trivial modifications, can operate as a fully 
peer-to-peer protocol, i.e., without per-domain servers. We describe a 
hybrid scenario where parts are in p2p mode, while others follow the 
more "traditional" proxy mode.

     An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol
     Salman A. Baset and Henning Schulzrinne

attempts to analyze how Skype works, constrained by the encryption of 
the protocol exchanges.

We would appreciate comments on these documents.

Henning

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  4 18:21: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 SAA01394
	for <sipping-web-archive@ietf.org>; Sat, 4 Dec 2004 18:21:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CajJX-0002fo-Et
	for sipping-web-archive@ietf.org; Sat, 04 Dec 2004 18:27:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Caih9-0002An-21; Sat, 04 Dec 2004 17:48:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaiC3-0002T6-Nt
	for sipping@megatron.ietf.org; Sat, 04 Dec 2004 17:16: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 RAA26124
	for <sipping@ietf.org>; Sat, 4 Dec 2004 17:15:53 -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 1CaiI5-0001Rs-A4
	for sipping@ietf.org; Sat, 04 Dec 2004 17:22:09 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 04 Dec 2004 15:23:19 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iB4MFCIT018973;
	Sat, 4 Dec 2004 14:15:13 -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 iB4MEYZO002118;
	Sat, 4 Dec 2004 14:14:35 -0800
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C7097C5@IsrExch01.israel.polycom.com>
References: <144ED8561CE90C41A3E5908EDECE315C7097C5@IsrExch01.israel.polycom.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F9E23D2B-4641-11D9-B1B5-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Conference speaker control
Date: Sat, 4 Dec 2004 17:15:16 -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:"1102198476.984989"; x:"432200"; a:"rsa-sha1"; b:"nofws:3345";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"d9RMsbPPusv6JGaRHOGaw5ZACPeyDivJ7YM8iNgUCW1d/yp0/077FwOxFI5+d"
	"26S96qiJq6Hr83rXtQ1xkNswxp7dTaOI5Sj8Qh4ao1B3oPHHMxM3ECYxurjLF"
	"0IVCfjbmZAn+a6/3f3v91bF7+w6ipqHD0oXGDCUyMMW2Mxyk0=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Conference speaker control";
	c:"Date: Sat, 4 Dec 2004 17:15:16 -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: e1b0e72ff1bbd457ceef31828f216a86
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: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit


On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:

> Magnus,
> The whole discussion is about the SIP conference package that suggests
> that a SIP user will know the source of the stream based on SSRC. So if
> there are media sessions that are not RTP is a SIP call then SSRC does
> not work.
> Roni
>
While this is strictly true, that's not the point. The point is whether  
the conferencing work ought to rely on a "correlator" in or associated  
with the media stream, and have arrivals on the media stream trigger  
any UI behavior, in order to identify the  
source(s)/speakers/arm-wavers/typers/gas-emitters.

I believe it should. In the case of RTP, this is the SSRC or the CNAME  
or both.

If the conferencing system wishes to accommodate a media session  
without this identification capability there has to be some way to do  
the correlation. I'm suggesting that emulating the media session by  
actually always having one to the UA is a good way to do this rather  
than sending speaker identification messages in realtime over the  
conferencing control protocols.

What do others think? This is important enough that other folks ought  
to weigh in here.

Dave.

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Magnus Westerlund
> Sent: Friday, December 03, 2004 11:11 AM
> To: Even, Roni
> Cc: sipping; David R Oran
> Subject: Re: [Sipping] Conference speaker control
>
> Even, Roni wrote:
>> Hi,
>> This is from the comedia draft, is it RTP, it does not say so.
>>
>>            m=image 54111 TCP t38
>>            c=IN IP4 192.0.2.2
>>            a=setup:passive
>>            a=connection:new
>>
>> Roni
>
> No, that is clearly T38 over TCP which has a mode that is not RTP,
> however if you look in the RTP over TCP draft:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing- 
> contrans-
> 03.txt
>
> You can find the following SDP:
> v=0
> o=first 2520644554 2838152170 IN IP4 first.example.net
> s=Example
> t=0 0
> c=IN IP4 192.0.2.105
> m=audio 9 TCP/RTP/AVP 11
> a=setup:active
> a=connid:1
>
> It is also this draft that register the RTP over TCP SDP protocol
> identifier.
>
>
> 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
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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  Sat Dec  4 20:53: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 UAA09064
	for <sipping-web-archive@ietf.org>; Sat, 4 Dec 2004 20:53:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Calh5-0005MK-T8
	for sipping-web-archive@ietf.org; Sat, 04 Dec 2004 21:00:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cal8z-0007zn-0I; Sat, 04 Dec 2004 20:24:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CakkH-00017I-SS
	for sipping@megatron.ietf.org; Sat, 04 Dec 2004 19:59: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 TAA06159
	for <sipping@ietf.org>; Sat, 4 Dec 2004 19:59:24 -0500 (EST)
Received: from lakermmtao11.cox.net ([68.230.240.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CakqK-0004Ro-H4
	for sipping@ietf.org; Sat, 04 Dec 2004 20:05:41 -0500
Received: from ip68-96-222-27.hr.hr.cox.net ([68.110.148.106])
	by lakermmtao11.cox.net
	(InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id
	<20041205005849.YRBU1654.lakermmtao11.cox.net@ip68-96-222-27.hr.hr.cox.net>;
	Sat, 4 Dec 2004 19:58:49 -0500
From: David Bryan <sip@bryan.cx>
To: sip-implementors@cs.columbia.edu, sipping@ietf.org
Content-Type: text/plain
Message-Id: <1102208267.25763.4.camel@knuth>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Sat, 04 Dec 2004 19:57:47 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Subject: [Sipping] P2P and 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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

Apologies if this is a duplicate post. I mistakenly sent the first one
from a non-subscribed account...

Hello Henning,

I have been working on a P2P SIP project as well. You may have seen
some the early internal William & Mary documents and talks from Nov.
2003 and onward on the web (I've been using the name SOSIMPLE). It
looks like your approach is extremely similar -- derived from a DHT
such as Chord.

Additionally, several of us (myself, Cullen Jennings, Adam Roach and a
few others) also discussed this topic quite a bit at IETF in Washington
and have had ongoing discussions about it. We are currently fleshing out
the details. I've started working on an experimental draft on the
subject, and have submitted to a few academic conferences for
publication.

I'd love for you, Kindan Singh, and anyone else who is interested to
work together on this.

--David Bryan

> From: Henning Schulzrinne <hgs@cs.columbia.edu>
> To: sip-implementors@cs.columbia.edu, sipping <sipping@ietf.org>
> Date: Sat, 04 Dec 2004 13:44:11 -0500
> Subject: [Sipping] Technical reports on Skype protocol analysis and
SIP in
> peer-to-peer mode
> We have written two technical reports that might be of interest to
> members of the list. Both can be found at
> http://www1.cs.columbia.edu/~library/2004.html
>
>    Peer-to-Peer Internet Telephony using SIP
>    Kundan Singh and Henning Schulzrinne
>
> describes how SIP, with trivial modifications, can operate as a fully
> peer-to-peer protocol, i.e., without per-domain servers. We describe a
> hybrid scenario where parts are in p2p mode, while others follow the
> more "traditional" proxy mode.
>
>    An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol
>    Salman A. Baset and Henning Schulzrinne
>
> attempts to analyze how Skype works, constrained by the encryption of
> the protocol exchanges.
>
> We would appreciate comments on these documents.
>
> Henning

--
David Bryan
sip@bryan.cx
bryan@cs.wm.edu
http://www.cs.wm.edu/~bryan


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  6 00:54: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 AAA16684
	for <sipping-web-archive@ietf.org>; Mon, 6 Dec 2004 00:54:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbBvZ-0001Ls-3k
	for sipping-web-archive@ietf.org; Mon, 06 Dec 2004 01:00:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbBeS-0008SQ-FH; Mon, 06 Dec 2004 00:43:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbBYX-000725-Rw
	for sipping@megatron.ietf.org; Mon, 06 Dec 2004 00:37:06 -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 AAA14901
	for <sipping@ietf.org>; Mon, 6 Dec 2004 00:37:02 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.197])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbBep-00010q-Bc
	for sipping@ietf.org; Mon, 06 Dec 2004 00:43:36 -0500
Received: by wproxy.gmail.com with SMTP id 71so75206wri
	for <sipping@ietf.org>; Sun, 05 Dec 2004 21:36:33 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=IlWHkhNIYKJKGyyIYw/FE3hwGK2OMKfOVImgI9kfUiVgihGzP/BFWOU7xUqrVw9oYBexuXMX+nG7gG4ek1LekX961JWJamg4mr8jY2JxLYV8TJf1RMefqk/5Sexvt+lorcjH/88lXrVVr5AUE1xqEWjRJLmRKCNpH1SA/H7pdjg=
Received: by 10.54.37.61 with SMTP id k61mr131738wrk;
	Sun, 05 Dec 2004 21:36:33 -0800 (PST)
Received: by 10.54.18.49 with HTTP; Sun, 5 Dec 2004 21:36:33 -0800 (PST)
Message-ID: <91d26620041205213625ef974c@mail.gmail.com>
Date: Mon, 6 Dec 2004 14:36:33 +0900
From: NC Reddy <ncreddy75@gmail.com>
To: sipping@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.9 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Subject: [Sipping] How to support CFT (conformation Tone) in SIP network?
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: NC Reddy <ncreddy75@gmail.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.9 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

Hi, 
   Pls find the problem as follows and suggest your recommendation
solution for it.

Back ground:
We have to provide for new service to calling party (i.e caller) named
as CFT (Confirmation Tone) for to know either off-net call or on-net
call by distinctive ringing at calling party. So calling party knows
that whether he/she want to continue the call or not.

Off-net call: it means the call outside the service provider domain.
On-net call: it means the call is inside service provider domain.

So by giving CFT tone to calling party he knows that what's the type
of call he started, so depends the type of the call he may  continue
or not. If the call is on-net it's free call and if it's off-net it
charged according to service provider billing.

Problem:
We have to send CFT information to calling party before the call
initiating towards the called party i.e before ringing at called party
side.
So we are thinking use INFO method pre-dialog establishment i.e before
18X msges. And INFO has the information about the called party type
i.e off-net/on-net.

But according SIP standards INFO method for mid-call session
information i.e after 18x. So instead of modifying the standard SIP
behavior, can we pass that information in 183 session in progress
msg??

pls throw some light on this kind of problems.

Thanks and Regards
Channa

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  6 03:29: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 DAA11731
	for <sipping-web-archive@ietf.org>; Mon, 6 Dec 2004 03:29:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbELf-0004Hr-JH
	for sipping-web-archive@ietf.org; Mon, 06 Dec 2004 03:35:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbECS-0000cZ-AC; Mon, 06 Dec 2004 03:26:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbE7h-0008Hk-Oo
	for sipping@megatron.ietf.org; Mon, 06 Dec 2004 03: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 DAA10933
	for <sipping@ietf.org>; Mon, 6 Dec 2004 03:21:32 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbEE1-00046v-BT
	for sipping@ietf.org; Mon, 06 Dec 2004 03:28:05 -0500
Received: from [192.168.0.108] (adsl-209-30-33-13.dsl.rcsntx.swbell.net
	[209.30.33.13]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iB68LQaU024588
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 6 Dec 2004 02:21:28 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <41B41680.2040906@nostrum.com>
Date: Mon, 06 Dec 2004 02:21:20 -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: NC Reddy <ncreddy75@gmail.com>
Subject: Re: [Sipping] How to support CFT (conformation Tone) in SIP network?
References: <91d26620041205213625ef974c@mail.gmail.com>
In-Reply-To: <91d26620041205213625ef974c@mail.gmail.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: 25620135586de10c627e3628c432b04a
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: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit

You probably want to take this to the sip implementors list; this is 
exactly the kind of question that it's meant for.

That said, I'll point out that you're approaching this the wrong way. 
You're trying to figure out how to apply a very PSTN-like solution to 
the problem to a SIP network. This usually leads to frustration.

Instead, you need to go back to what your requirements are, and figure 
out how they can be met using SIP mechanisms.

 From what you've written, I infer that your fundamental requirement is 
something like: "Users must be able to determine, prior to a call being 
established, whether they are willing to complete off-net calls."

Then, a SIP-like way to solve this kind of problem would be for the user 
to indicate -- before the INVITE is sent -- whether they are willing to 
initiate calls that terminate off-net. This indication would be present 
in the INVITE itself.

But, in any case, you'll need to extend the protocol to support what you 
propose. There isn't a way, using currently defined mechanisms, to do 
what you want. I would suggest that, if you decide to extend the 
protocol, you do it here instead of coming up with some proprietary 
solution that is unlikely to work in the wild.

/a

NC Reddy wrote:

>Hi, 
>   Pls find the problem as follows and suggest your recommendation
>solution for it.
>
>Back ground:
>We have to provide for new service to calling party (i.e caller) named
>as CFT (Confirmation Tone) for to know either off-net call or on-net
>call by distinctive ringing at calling party. So calling party knows
>that whether he/she want to continue the call or not.
>
>Off-net call: it means the call outside the service provider domain.
>On-net call: it means the call is inside service provider domain.
>
>So by giving CFT tone to calling party he knows that what's the type
>of call he started, so depends the type of the call he may  continue
>or not. If the call is on-net it's free call and if it's off-net it
>charged according to service provider billing.
>
>Problem:
>We have to send CFT information to calling party before the call
>initiating towards the called party i.e before ringing at called party
>side.
>So we are thinking use INFO method pre-dialog establishment i.e before
>18X msges. And INFO has the information about the called party type
>i.e off-net/on-net.
>
>But according SIP standards INFO method for mid-call session
>information i.e after 18x. So instead of modifying the standard SIP
>behavior, can we pass that information in 183 session in progress
>msg??
>
>pls throw some light on this kind of problems.
>
>Thanks and Regards
>Channa
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 Dec  6 10:51: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 KAA23869
	for <sipping-web-archive@ietf.org>; Mon, 6 Dec 2004 10:51:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbLFG-00080C-E1
	for sipping-web-archive@ietf.org; Mon, 06 Dec 2004 10:57:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbL7S-0005ax-Mk; Mon, 06 Dec 2004 10:49:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbL3L-0004RS-1y
	for sipping@megatron.ietf.org; Mon, 06 Dec 2004 10:45: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 KAA23249
	for <sipping@ietf.org>; Mon, 6 Dec 2004 10:45:28 -0500 (EST)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbL9i-0007pc-JQ
	for sipping@ietf.org; Mon, 06 Dec 2004 10:52:07 -0500
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
	(PMDF V6.0-24 #40642) id <0I8B007014ZQ3M@siemenscomms.co.uk> for
	sipping@ietf.org; Mon, 06 Dec 2004 15:43:02 +0000 (GMT)
Received: from ntht206e.siemenscomms.co.uk ([137.223.247.52])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0I8B0065Y4ZPIY@siemenscomms.co.uk>; Mon,
	06 Dec 2004 15:43:01 +0000 (GMT)
Received: by ntht206e.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <X5HYBKYH>; Mon, 06 Dec 2004 15:44:54 +0000
Content-return: allowed
Date: Mon, 06 Dec 2004 15:44:51 +0000
From: "Elwell, John" <john.elwell@siemens.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <50B1CBA96870A34799A506B2313F26670252D617@ntht201e>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7BIT
Cc: "'Jesske, R'" <R.Jesske@t-com.net>,
        "Mcmillen,
	C Joanne \(Joanne\)" <joanne@avaya.com>
Subject: [Sipping] draft-elwell-sipping-redirection-reason-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: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7BIT

This draft was published just before IETF61, but I failed to draw people's
attention to it at the time. Compared with draft 00, it focuses on a single
solution (extending the Reason header). From responses I received, this
appeared to be the preferred solution.

I would appreciate comments on the draft and opinions as to whether it
should be adopted as a SIP or SIPPING work item.

John (john.elwell@siemens.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 Dec  6 12:57: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 MAA04664
	for <sipping-web-archive@ietf.org>; Mon, 6 Dec 2004 12:57:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbND1-0002V1-P6
	for sipping-web-archive@ietf.org; Mon, 06 Dec 2004 13:03:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbN3B-0002PK-WF; Mon, 06 Dec 2004 12:53:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMwM-0001KX-3A
	for sipping@megatron.ietf.org; Mon, 06 Dec 2004 12:46: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 MAA03928
	for <sipping@ietf.org>; Mon, 6 Dec 2004 12:46:23 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbN2j-0002HJ-Oi
	for sipping@ietf.org; Mon, 06 Dec 2004 12:53:03 -0500
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Dec 2004 09:45:50 -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); 
	Mon, 6 Dec 2004 09:45:52 -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] Conference speaker control
Date: Mon, 6 Dec 2004 09:45:50 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03D7C4FA@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTaWFEXRt0dQr00TyWaOpcUyNk4PgBYFhrg
From: "Orit Levin" <oritl@microsoft.com>
To: "David R Oran" <oran@cisco.com>, "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 06 Dec 2004 17:45:52.0079 (UTC)
	FILETIME=[6DCDD5F0:01C4DBBB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable
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: 200d029292fbb60d25b263122ced50fc
Content-Transfer-Encoding: quoted-printable

I believe that the "architecturally right" way of providing the "current
speaker identification" is by including enough information in the
media/data streams and letting the endpoints to make the correlation.
Hence the Conference Event package uses a generalized "src-id"
placeholder to hold RTP's ssrc and others to come. Hence the push to
have a meaningful and easy to use source identification in MSRP.

Unfortunately, today RTP MCUs don't implement the RTP mixer
functionality and don't necessarily include the ssrc information of the
mixed sources. Also, in PSTN - there is no way to have this information
(as Roni points out).

Technically, it is really easy to add the "current speaker"
identification to the Conference Event package itself. The problem is
how feasible this solution would be for free-going conferences with the
"current speaker" being changed all the time. My feeling is that going
forward in XCON it is worthwhile to add the information to the package
but use it by the focus for strictly controlled conferences only.

Orit.

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf
> Of David R Oran
> Sent: Saturday, December 04, 2004 2:15 PM
> To: Even, Roni
> Cc: Magnus Westerlund; sipping
> Subject: Re: [Sipping] Conference speaker control
>=20
>=20
> On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:
>=20
> > Magnus,
> > The whole discussion is about the SIP conference package that
suggests
> > that a SIP user will know the source of the stream based on SSRC. So
if
> > there are media sessions that are not RTP is a SIP call then SSRC
does
> > not work.
> > Roni
> >
> While this is strictly true, that's not the point. The point is
whether
> the conferencing work ought to rely on a "correlator" in or associated
> with the media stream, and have arrivals on the media stream trigger
> any UI behavior, in order to identify the
> source(s)/speakers/arm-wavers/typers/gas-emitters.
>=20
> I believe it should. In the case of RTP, this is the SSRC or the CNAME
> or both.
>=20
> If the conferencing system wishes to accommodate a media session
> without this identification capability there has to be some way to do
> the correlation. I'm suggesting that emulating the media session by
> actually always having one to the UA is a good way to do this rather
> than sending speaker identification messages in realtime over the
> conferencing control protocols.
>=20
> What do others think? This is important enough that other folks ought
> to weigh in here.
>=20
> Dave.
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf Of Magnus Westerlund
> > Sent: Friday, December 03, 2004 11:11 AM
> > To: Even, Roni
> > Cc: sipping; David R Oran
> > Subject: Re: [Sipping] Conference speaker control
> >
> > Even, Roni wrote:
> >> Hi,
> >> This is from the comedia draft, is it RTP, it does not say so.
> >>
> >>            m=3Dimage 54111 TCP t38
> >>            c=3DIN IP4 192.0.2.2
> >>            a=3Dsetup:passive
> >>            a=3Dconnection:new
> >>
> >> Roni
> >
> > No, that is clearly T38 over TCP which has a mode that is not RTP,
> > however if you look in the RTP over TCP draft:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-
> > contrans-
> > 03.txt
> >
> > You can find the following SDP:
> > v=3D0
> > o=3Dfirst 2520644554 2838152170 IN IP4 first.example.net
> > s=3DExample
> > t=3D0 0
> > c=3DIN IP4 192.0.2.105
> > m=3Daudio 9 TCP/RTP/AVP 11
> > a=3Dsetup:active
> > a=3Dconnid:1
> >
> > It is also this draft that register the RTP over TCP SDP protocol
> > identifier.
> >
> >
> > 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
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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


From sipping-bounces@ietf.org  Tue Dec  7 08:11: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 IAA25917
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 08:11:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbfEE-0002mm-IG
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 08:18:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbevp-0005ko-18; Tue, 07 Dec 2004 07:59:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbeqL-0004S3-Uc; Tue, 07 Dec 2004 07:53: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 HAA23913;
	Tue, 7 Dec 2004 07:53:24 -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 1Cbewu-00025k-Sf; Tue, 07 Dec 2004 08:00:13 -0500
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <YNNTPACZ>; Tue, 7 Dec 2004 12:52:48 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
From: "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
To: SIPPING WG <sipping@ietf.org>
Subject: FW: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
Date: Tue, 7 Dec 2004 12:52:51 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4DC5B.A9202F90"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b
Cc: SIP WG <sip@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

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_01C4DC5B.A9202F90
Content-Type: text/plain;
	charset="iso-8859-1"

Apologies - this e-mail should have gone to the SIPPING WG!

Paul DS.

-----Original Message-----
From: Paul D.Smith 
Sent: 07 December 2004 12:52
To: SIP Public Folder (E-mail)
Subject: RE: [Sipping] I-D
ACTION:draft-ietf-sipping-dialog-package-05.txt


Rohan,

As per my earlier post to the group, I have to disagree with your
assertion that a 408 or 481 failure of _any_ mid-dialog request
terminates the dialog (section 3.7.1 of this draft).

  "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)."

RFC3261 is quite clear in distinguishing between BYE requests and other
requests.  The failure of a non-BYE request does not cause a dialog to
terminate although it should be taken as a prompt to the UA to end the
dialog
by sending a BYE.  To put it another way, non-BYE requests are not dialog
terminating, regardless of the status code of any resulting response.

If you believe this is not the case, can you please explain the meaning of
the following sections of RFC3261.

12.3 Termination of a Dialog

   Independent of the method, if a request outside of a dialog generates
   a non-2xx final response, any early dialogs created through
   provisional responses to that request are terminated.  The mechanism
   for terminating confirmed dialogs is method specific.  In this
   specification, the BYE method terminates a session and the dialog
   associated with it.  See Section 15 for details.

12.2.1.2 Processing the Responses

   ...

   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.

I believe this is a serious issue because it potentially means that there
would be two concepts of the state of a dialog, one RFC3261 compliant and
a second, compliant to this draft.  I therefore believe this should be
resolved quickly and look forward to readong your response.

Regards,
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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: 23 November 2004 21:11
To: SIP Public Folder (E-mail)
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt


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_000_01C4DC5B.A9202F90
Content-Type: message/rfc822

To: 
Subject: 
Date: Tue, 7 Dec 2004 12:52:48 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C4DC5B.A9202F90"


------_=_NextPart_002_01C4DC5B.A9202F90
Content-Type: text/plain



------_=_NextPart_002_01C4DC5B.A9202F90
Content-Type: application/octet-stream;
	name="ATT79302.txt"
Content-Disposition: attachment;
	filename="ATT79302.txt"

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

------_=_NextPart_002_01C4DC5B.A9202F90
Content-Type: message/external-body; site="internet-drafts";
	dir="draft-ietf-sipping-dialog-package-05.txt";
	mode="ftp.ietf.org"; access-type="anon-ftp"



------_=_NextPart_002_01C4DC5B.A9202F90--

------_=_NextPart_000_01C4DC5B.A9202F90
Content-Type: text/plain;
	name="ATT79303.txt"
Content-Disposition: attachment;
	filename="ATT79303.txt"

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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_01C4DC5B.A9202F90
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_01C4DC5B.A9202F90--



From sipping-bounces@ietf.org  Tue Dec  7 08:28: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 IAA27846
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 08:28:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbfVM-0003Lt-F7
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 08:35:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbfFs-00021G-Eb; Tue, 07 Dec 2004 08:19:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbfDd-00016N-3v
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 08:17: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 IAA26455
	for <sipping@ietf.org>; Tue, 7 Dec 2004 08:17:27 -0500 (EST)
Received: from cluster-b.mailcontrol.com ([217.68.146.190]
	helo=rly16b.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbfKC-0002vZ-Ay
	for sipping@ietf.org; Tue, 07 Dec 2004 08:24:16 -0500
Received: from GBNEWP0758M.eu.ubiquity.net (news.ubiquity.net [194.202.146.92])
	by rly16b.srv.mailcontrol.com (MailControl) with ESMTP id
	iB7DGlYA026538; Tue, 7 Dec 2004 13:16:47 GMT
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Conference speaker control
Date: Tue, 7 Dec 2004 13:15:21 -0000
Message-ID: <45730E094814E44488F789C1CDED27AE02BDF895@gbnewp0758m.eu.ubiquity.net>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTaWFEXRt0dQr00TyWaOpcUyNk4PgBYFhrgAClsyHA=
From: "Chris Boulton" <cboulton@ubiquity.net>
To: "Orit Levin" <oritl@microsoft.com>, "David R Oran" <oran@cisco.com>,
        "Even, Roni" <roni.even@polycom.co.il>
X-Scanned-By: MailControl A-05-00-05 (www.mailcontrol.com)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: quoted-printable
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: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: quoted-printable

<<Comment in-line>>

I believe that the "architecturally right" way of providing the "current
speaker identification" is by including enough information in the
media/data streams and letting the endpoints to make the correlation.
Hence the Conference Event package uses a generalized "src-id"
placeholder to hold RTP's ssrc and others to come. Hence the push to
have a meaningful and easy to use source identification in MSRP.

Unfortunately, today RTP MCUs don't implement the RTP mixer
functionality and don't necessarily include the ssrc information of the
mixed sources. Also, in PSTN - there is no way to have this information
(as Roni points out).

Technically, it is really easy to add the "current speaker"
identification to the Conference Event package itself. The problem is
how feasible this solution would be for free-going conferences with the
"current speaker" being changed all the time. My feeling is that going
forward in XCON it is worthwhile to add the information to the package
but use it by the focus for strictly controlled conferences only.

[Chris Boulton] Agreed that this should be included and that it will not
always be that useful.  It might be worth while including appropriate
attributes that allow the current speaker to be controlled e.g. timeout
(if no update is received then return to default) + this could help to
enforce rate limitation.

Chris.


Orit.

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf
> Of David R Oran
> Sent: Saturday, December 04, 2004 2:15 PM
> To: Even, Roni
> Cc: Magnus Westerlund; sipping
> Subject: Re: [Sipping] Conference speaker control
>=20
>=20
> On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:
>=20
> > Magnus,
> > The whole discussion is about the SIP conference package that
suggests
> > that a SIP user will know the source of the stream based on SSRC. So
if
> > there are media sessions that are not RTP is a SIP call then SSRC
does
> > not work.
> > Roni
> >
> While this is strictly true, that's not the point. The point is
whether
> the conferencing work ought to rely on a "correlator" in or associated
> with the media stream, and have arrivals on the media stream trigger
> any UI behavior, in order to identify the
> source(s)/speakers/arm-wavers/typers/gas-emitters.
>=20
> I believe it should. In the case of RTP, this is the SSRC or the CNAME
> or both.
>=20
> If the conferencing system wishes to accommodate a media session
> without this identification capability there has to be some way to do
> the correlation. I'm suggesting that emulating the media session by
> actually always having one to the UA is a good way to do this rather
> than sending speaker identification messages in realtime over the
> conferencing control protocols.
>=20
> What do others think? This is important enough that other folks ought
> to weigh in here.
>=20
> Dave.
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf Of Magnus Westerlund
> > Sent: Friday, December 03, 2004 11:11 AM
> > To: Even, Roni
> > Cc: sipping; David R Oran
> > Subject: Re: [Sipping] Conference speaker control
> >
> > Even, Roni wrote:
> >> Hi,
> >> This is from the comedia draft, is it RTP, it does not say so.
> >>
> >>            m=3Dimage 54111 TCP t38
> >>            c=3DIN IP4 192.0.2.2
> >>            a=3Dsetup:passive
> >>            a=3Dconnection:new
> >>
> >> Roni
> >
> > No, that is clearly T38 over TCP which has a mode that is not RTP,
> > however if you look in the RTP over TCP draft:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-
> > contrans-
> > 03.txt
> >
> > You can find the following SDP:
> > v=3D0
> > o=3Dfirst 2520644554 2838152170 IN IP4 first.example.net
> > s=3DExample
> > t=3D0 0
> > c=3DIN IP4 192.0.2.105
> > m=3Daudio 9 TCP/RTP/AVP 11
> > a=3Dsetup:active
> > a=3Dconnid:1
> >
> > It is also this draft that register the RTP over TCP SDP protocol
> > identifier.
> >
> >
> > 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
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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


This email and any attached files are confidential and copyright protected.=
  If you are not the addressee, any dissemination, distribution or copying =
of this communication is strictly prohibited.  Unless otherwise expressly a=
greed in writing, nothing stated in this communication shall be legally bin=
ding.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  7 08:36: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 IAA28455
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 08:36:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbfcp-0003XD-Il
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 08:43:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbfGk-0002Lw-Dv; Tue, 07 Dec 2004 08:20:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbfFT-0001dW-GO
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 08:19: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 IAA27067
	for <sipping@ietf.org>; Tue, 7 Dec 2004 08:19:22 -0500 (EST)
Received: from fep14.012.net.il ([212.117.129.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbfM1-000336-Sf
	for sipping@ietf.org; Tue, 07 Dec 2004 08:26:11 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep14.012.net.il with ESMTP
	id <20041207131419.KAIY13819.fep14@isrexch01.israel.polycom.com>;
	Tue, 7 Dec 2004 15:14:19 +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] Conference speaker control
Date: Tue, 7 Dec 2004 15:18:44 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C709EE6@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTaWFEXRt0dQr00TyWaOpcUyNk4PgBYFhrgACmFPEA=
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Orit Levin" <oritl@microsoft.com>, "David R Oran" <oran@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: quoted-printable
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: 3.0 (+++)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Content-Transfer-Encoding: quoted-printable

Orit,
I am not sure I understand your concern. Is it the number of
notifications on change of speakers by the event package that bother
you.
For this case it is typically handled by having a minimum time that a
user must "speak" before he is announced as the current speaker. This
has to do with not having to do very fast video switch for voice
activated video switch scenarios
Roni=20

-----Original Message-----
From: Orit Levin [mailto:oritl@microsoft.com]=20
Sent: Monday, December 06, 2004 7:46 PM
To: David R Oran; Even, Roni
Cc: Magnus Westerlund; sipping
Subject: RE: [Sipping] Conference speaker control

I believe that the "architecturally right" way of providing the "current
speaker identification" is by including enough information in the
media/data streams and letting the endpoints to make the correlation.
Hence the Conference Event package uses a generalized "src-id"
placeholder to hold RTP's ssrc and others to come. Hence the push to
have a meaningful and easy to use source identification in MSRP.

Unfortunately, today RTP MCUs don't implement the RTP mixer
functionality and don't necessarily include the ssrc information of the
mixed sources. Also, in PSTN - there is no way to have this information
(as Roni points out).

Technically, it is really easy to add the "current speaker"
identification to the Conference Event package itself. The problem is
how feasible this solution would be for free-going conferences with the
"current speaker" being changed all the time. My feeling is that going
forward in XCON it is worthwhile to add the information to the package
but use it by the focus for strictly controlled conferences only.

Orit.

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf
> Of David R Oran
> Sent: Saturday, December 04, 2004 2:15 PM
> To: Even, Roni
> Cc: Magnus Westerlund; sipping
> Subject: Re: [Sipping] Conference speaker control
>=20
>=20
> On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:
>=20
> > Magnus,
> > The whole discussion is about the SIP conference package that
suggests
> > that a SIP user will know the source of the stream based on SSRC. So
if
> > there are media sessions that are not RTP is a SIP call then SSRC
does
> > not work.
> > Roni
> >
> While this is strictly true, that's not the point. The point is
whether
> the conferencing work ought to rely on a "correlator" in or associated
> with the media stream, and have arrivals on the media stream trigger
> any UI behavior, in order to identify the
> source(s)/speakers/arm-wavers/typers/gas-emitters.
>=20
> I believe it should. In the case of RTP, this is the SSRC or the CNAME
> or both.
>=20
> If the conferencing system wishes to accommodate a media session
> without this identification capability there has to be some way to do
> the correlation. I'm suggesting that emulating the media session by
> actually always having one to the UA is a good way to do this rather
> than sending speaker identification messages in realtime over the
> conferencing control protocols.
>=20
> What do others think? This is important enough that other folks ought
> to weigh in here.
>=20
> Dave.
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf Of Magnus Westerlund
> > Sent: Friday, December 03, 2004 11:11 AM
> > To: Even, Roni
> > Cc: sipping; David R Oran
> > Subject: Re: [Sipping] Conference speaker control
> >
> > Even, Roni wrote:
> >> Hi,
> >> This is from the comedia draft, is it RTP, it does not say so.
> >>
> >>            m=3Dimage 54111 TCP t38
> >>            c=3DIN IP4 192.0.2.2
> >>            a=3Dsetup:passive
> >>            a=3Dconnection:new
> >>
> >> Roni
> >
> > No, that is clearly T38 over TCP which has a mode that is not RTP,
> > however if you look in the RTP over TCP draft:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-
> > contrans-
> > 03.txt
> >
> > You can find the following SDP:
> > v=3D0
> > o=3Dfirst 2520644554 2838152170 IN IP4 first.example.net
> > s=3DExample
> > t=3D0 0
> > c=3DIN IP4 192.0.2.105
> > m=3Daudio 9 TCP/RTP/AVP 11
> > a=3Dsetup:active
> > a=3Dconnid:1
> >
> > It is also this draft that register the RTP over TCP SDP protocol
> > identifier.
> >
> >
> > 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
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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


From sipping-bounces@ietf.org  Tue Dec  7 09:15: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 JAA03010
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 09:15:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbgDz-0004Zf-Ht
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 09:21:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbg23-0003IX-IX; Tue, 07 Dec 2004 09:09:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbftb-0000mm-9t
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 09:00: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 JAA01104
	for <sipping@ietf.org>; Tue, 7 Dec 2004 09:00:49 -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 1Cbg0A-00049u-MX
	for sipping@ietf.org; Tue, 07 Dec 2004 09:07:39 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 07 Dec 2004 07:08:47 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iB7E0ED9014419;
	Tue, 7 Dec 2004 06:00:14 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-1-7.cisco.com [10.86.240.7])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANN06519;
	Tue, 7 Dec 2004 09:00:15 -0500 (EST)
Message-ID: <41B5B76F.9070300@cisco.com>
Date: Tue, 07 Dec 2004 09:00:15 -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 D.Smith" <Paul.D.Smith@dataconnection.com>
Subject: Re: FW: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
References: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9
Content-Transfer-Encoding: 7bit
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: 6907f330301e69261fa73bed91449a20
Content-Transfer-Encoding: 7bit

inline.

	Paul Kyzivat

Paul D.Smith wrote:
> Apologies - this e-mail should have gone to the SIPPING WG!
> 
> Paul DS.
> 
> -----Original Message-----
> From: Paul D.Smith 
> Sent: 07 December 2004 12:52
> To: SIP Public Folder (E-mail)
> Subject: RE: [Sipping] I-D
> ACTION:draft-ietf-sipping-dialog-package-05.txt
> 
> 
> Rohan,
> 
> As per my earlier post to the group, I have to disagree with your
> assertion that a 408 or 481 failure of _any_ mid-dialog request
> terminates the dialog (section 3.7.1 of this draft).
> 
>   "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)."
> 
> RFC3261 is quite clear in distinguishing between BYE requests and other
> requests.  The failure of a non-BYE request does not cause a dialog to
> terminate although it should be taken as a prompt to the UA to end the
> dialog
> by sending a BYE.  To put it another way, non-BYE requests are not dialog
> terminating, regardless of the status code of any resulting response.
> 
> If you believe this is not the case, can you please explain the meaning of
> the following sections of RFC3261.
> 
> 12.3 Termination of a Dialog
> 
>    Independent of the method, if a request outside of a dialog generates
>    a non-2xx final response, any early dialogs created through
>    provisional responses to that request are terminated.  The mechanism
>    for terminating confirmed dialogs is method specific.  In this
>    specification, the BYE method terminates a session and the dialog
>    associated with it.  See Section 15 for details.
> 
> 12.2.1.2 Processing the Responses
> 
>    ...
> 
>    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.

In the case of 481 responses, I have always assumed that the recipient 
should interpret this as meaning the dialog is already gone. (If you 
have already received a 481 response, what is the point of sending a 
BYE? It will simply get another 481 response.)

The exception here would be if you got a 481 response to a CANCEL or a 
PRACK, which could simply mean there was no matching transaction rather 
than dialog.

That logic doesn't necessarily extend to 408, since that could reflect a 
transient condition.

> I believe this is a serious issue because it potentially means that there
> would be two concepts of the state of a dialog, one RFC3261 compliant and
> a second, compliant to this draft.  I therefore believe this should be
> resolved quickly and look forward to readong your response.
> 
> Regards,
> 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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: 23 November 2004 21:11
> To: SIP Public Folder (E-mail)
> Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
> 
> 
> 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.
> 
> -------------------------------------------------------------------------
> CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
> -------------------------------------------------------------------------
> In order to maintain computing infrastructure integrity, Cisco Systems
> Enterprise Messaging Services and InfoSec teams have set a mail policy
> disallowing executable attachments in email.
> 
> This message contained an executable attachment type that is prohibited 
> by this policy. The attachment has been removed from this message and 
> copied to quarantine by our systems. It will be held in quarantine for
> seven days in the event that the content needs to be retrieved.
> 
> Please be aware many viruses attempt to look like legitimate email or 
> notifications from anti-virus systems. We will clearly mark a seperation
> between our notifications and the original email as follows:
> 
>   "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"
> 
> For further reference information about viruses and email antivirus 
> efforts within Cisco, please visit:
> 
> http://wwwin.cisco.com/it/ems/services/antiviral
> 
> If your concern isn't addressed by the information in this notification 
> or the above web page, you may open a support request:
> 
> http://wwwin.cisco.com/support/
> 
> Select "Messaging", "Email-Related", "Mail Routing"
> 
> Please include in the text of your case the following information:
> 
> * Full headers of the message. Documentation on displaying the full 
> headers is available at this URL:
> 
> http://wwwin.cisco.com/support/library/faqs/solution002471.html 
> 
> * This unique quarantine identifier: iB7DAW1C021076
> 
> If the matter is urgent, you may follow up by calling one of the below 
> referenced numbers. Please make every effort to provide the above 
> requested information via the support web tool prior to calling as it 
> will greatly aid the resolution of your issue.
> 
> Americas:
> 1 408 526 8888
> 
> Asiapac
> +61 2 8446 8888
> 
> EMEA
> +31 20 485 4888
> 
> Japan
> +81 3 5549 6888
> 
> US (Toll Free)
> 1| 800| 888| 8187| (ext.68888)
> 
> Thank you for your cooperation,
> 
> Enterprise Messaging Services
> Cisco Systems, Inc
> 
> 
> ------------------------------------------------------------------------
> 
> Date:
> Tue, 7 Dec 2004 12:52:48 -0000
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Dec  7 11:45: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 LAA22268
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 11:45:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbiZE-0008Nt-DD
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 11: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 1CbiF1-0001IJ-TD; Tue, 07 Dec 2004 11:31:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbi5u-0002bQ-2T
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 11:21: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 LAA19664
	for <sipping@ietf.org>; Tue, 7 Dec 2004 11:21:39 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbiCU-0007sU-KV
	for sipping@ietf.org; Tue, 07 Dec 2004 11:28:31 -0500
Received: from [192.168.0.100] (c-24-1-68-89.client.comcast.net [24.1.68.89])
	(authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iB7GLWo9076963
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Tue, 7 Dec 2004 10:21:33 -0600 (CST)
	(envelope-from rjsparks@nostrum.com)
In-Reply-To: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
References: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <105311F8-486C-11D9-8F23-000D93326732@nostrum.com>
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [Sip] FW: [Sipping] I-D
	ACTION:draft-ietf-sipping-dialog-package-05.txt
Date: Tue, 7 Dec 2004 10:21:35 -0600
To: "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Content-Transfer-Encoding: 7bit
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.1 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit

Paul -

The text you quote from 3261 looks pretty specific to me
and agrees with what Rohan writes.

There's more - please look at
draft-sparks-sipping-dialogusage-00 for a some discussion
of what 408 and 481 do to usages.

RjS

On Dec 7, 2004, at 6:52 AM, Paul D.Smith wrote:

> Apologies - this e-mail should have gone to the SIPPING WG!
>
> Paul DS.
>
> -----Original Message-----
> From: Paul D.Smith
> Sent: 07 December 2004 12:52
> To: SIP Public Folder (E-mail)
> Subject: RE: [Sipping] I-D
> ACTION:draft-ietf-sipping-dialog-package-05.txt
>
>
> Rohan,
>
> As per my earlier post to the group, I have to disagree with your
> assertion that a 408 or 481 failure of _any_ mid-dialog request
> terminates the dialog (section 3.7.1 of this draft).
>
>   "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)."
>
> RFC3261 is quite clear in distinguishing between BYE requests and other
> requests.  The failure of a non-BYE request does not cause a dialog to
> terminate although it should be taken as a prompt to the UA to end the
> dialog
> by sending a BYE.  To put it another way, non-BYE requests are not  
> dialog
> terminating, regardless of the status code of any resulting response.
>
> If you believe this is not the case, can you please explain the  
> meaning of
> the following sections of RFC3261.
>
> 12.3 Termination of a Dialog
>
>    Independent of the method, if a request outside of a dialog  
> generates
>    a non-2xx final response, any early dialogs created through
>    provisional responses to that request are terminated.  The mechanism
>    for terminating confirmed dialogs is method specific.  In this
>    specification, the BYE method terminates a session and the dialog
>    associated with it.  See Section 15 for details.
>
> 12.2.1.2 Processing the Responses
>
>    ...
>
>    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.
>
> I believe this is a serious issue because it potentially means that  
> there
> would be two concepts of the state of a dialog, one RFC3261 compliant  
> and
> a second, compliant to this draft.  I therefore believe this should be
> resolved quickly and look forward to readong your response.
>
> Regards,
> 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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: 23 November 2004 21:11
> To: SIP Public Folder (E-mail)
> Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
>
>
> 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.
>
>
> Date: December 7, 2004 6:52:48 AM CST
> To: Subject:
>
>
>
> <ATT79302.txt>
>
>
> <ATT79303.txt>_______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of 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 Dec  7 12:30:46 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 MAA27379
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 12:30:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbjHO-00013v-CU
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 12:37:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbish-0006Bw-2d; Tue, 07 Dec 2004 12:12:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbidH-0008UI-Ph
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 11:56: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 LAA23693
	for <sipping@ietf.org>; Tue, 7 Dec 2004 11:56:09 -0500 (EST)
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbijq-0000DG-EW
	for sipping@ietf.org; Tue, 07 Dec 2004 12:03:00 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Dec 2004 08:55:37 -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, 7 Dec 2004 08:55:37 -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] Conference speaker control
Date: Tue, 7 Dec 2004 08:55:36 -0800
Message-ID: <DD07841287D0AD428833021705E0D14E03DC7D69@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Conference speaker control
Thread-Index: AcTaWFEXRt0dQr00TyWaOpcUyNk4PgBYFhrgACmFPEAAB571IA==
From: "Orit Levin" <oritl@microsoft.com>
To: "Even, Roni" <roni.even@polycom.co.il>
X-OriginalArrivalTime: 07 Dec 2004 16:55:37.0663 (UTC)
	FILETIME=[937C34F0:01C4DC7D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c
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: 0.0 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Content-Transfer-Encoding: quoted-printable

Roni,
My concern was about conferences with no floor control and no video.

Orit.

> -----Original Message-----
> From: Even, Roni [mailto:roni.even@polycom.co.il]
> Sent: Tuesday, December 07, 2004 5:19 AM
> To: Orit Levin; David R Oran
> Cc: Magnus Westerlund; sipping
> Subject: RE: [Sipping] Conference speaker control
>=20
> Orit,
> I am not sure I understand your concern. Is it the number of
> notifications on change of speakers by the event package that bother
> you.
> For this case it is typically handled by having a minimum time that a
> user must "speak" before he is announced as the current speaker. This
> has to do with not having to do very fast video switch for voice
> activated video switch scenarios
> Roni
>=20
> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Monday, December 06, 2004 7:46 PM
> To: David R Oran; Even, Roni
> Cc: Magnus Westerlund; sipping
> Subject: RE: [Sipping] Conference speaker control
>=20
> I believe that the "architecturally right" way of providing the
"current
> speaker identification" is by including enough information in the
> media/data streams and letting the endpoints to make the correlation.
> Hence the Conference Event package uses a generalized "src-id"
> placeholder to hold RTP's ssrc and others to come. Hence the push to
> have a meaningful and easy to use source identification in MSRP.
>=20
> Unfortunately, today RTP MCUs don't implement the RTP mixer
> functionality and don't necessarily include the ssrc information of
the
> mixed sources. Also, in PSTN - there is no way to have this
information
> (as Roni points out).
>=20
> Technically, it is really easy to add the "current speaker"
> identification to the Conference Event package itself. The problem is
> how feasible this solution would be for free-going conferences with
the
> "current speaker" being changed all the time. My feeling is that going
> forward in XCON it is worthwhile to add the information to the package
> but use it by the focus for strictly controlled conferences only.
>=20
> Orit.
>=20
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> > Of David R Oran
> > Sent: Saturday, December 04, 2004 2:15 PM
> > To: Even, Roni
> > Cc: Magnus Westerlund; sipping
> > Subject: Re: [Sipping] Conference speaker control
> >
> >
> > On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:
> >
> > > Magnus,
> > > The whole discussion is about the SIP conference package that
> suggests
> > > that a SIP user will know the source of the stream based on SSRC.
So
> if
> > > there are media sessions that are not RTP is a SIP call then SSRC
> does
> > > not work.
> > > Roni
> > >
> > While this is strictly true, that's not the point. The point is
> whether
> > the conferencing work ought to rely on a "correlator" in or
associated
> > with the media stream, and have arrivals on the media stream trigger
> > any UI behavior, in order to identify the
> > source(s)/speakers/arm-wavers/typers/gas-emitters.
> >
> > I believe it should. In the case of RTP, this is the SSRC or the
CNAME
> > or both.
> >
> > If the conferencing system wishes to accommodate a media session
> > without this identification capability there has to be some way to
do
> > the correlation. I'm suggesting that emulating the media session by
> > actually always having one to the UA is a good way to do this rather
> > than sending speaker identification messages in realtime over the
> > conferencing control protocols.
> >
> > What do others think? This is important enough that other folks
ought
> > to weigh in here.
> >
> > Dave.
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
On
> > > Behalf Of Magnus Westerlund
> > > Sent: Friday, December 03, 2004 11:11 AM
> > > To: Even, Roni
> > > Cc: sipping; David R Oran
> > > Subject: Re: [Sipping] Conference speaker control
> > >
> > > Even, Roni wrote:
> > >> Hi,
> > >> This is from the comedia draft, is it RTP, it does not say so.
> > >>
> > >>            m=3Dimage 54111 TCP t38
> > >>            c=3DIN IP4 192.0.2.2
> > >>            a=3Dsetup:passive
> > >>            a=3Dconnection:new
> > >>
> > >> Roni
> > >
> > > No, that is clearly T38 over TCP which has a mode that is not RTP,
> > > however if you look in the RTP over TCP draft:
> > > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-
> > > contrans-
> > > 03.txt
> > >
> > > You can find the following SDP:
> > > v=3D0
> > > o=3Dfirst 2520644554 2838152170 IN IP4 first.example.net
> > > s=3DExample
> > > t=3D0 0
> > > c=3DIN IP4 192.0.2.105
> > > m=3Daudio 9 TCP/RTP/AVP 11
> > > a=3Dsetup:active
> > > a=3Dconnid:1
> > >
> > > It is also this draft that register the RTP over TCP SDP protocol
> > > identifier.
> > >
> > >
> > > 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
> > >
> > > _______________________________________________
> > > Sipping mailing list
https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the 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

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec  7 14:21: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 OAA08695
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 14:21:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbl0F-0003np-Ly
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 14:28:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbknF-0003gs-EE; Tue, 07 Dec 2004 14:14:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbkfJ-0001mu-D9
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 14:06: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 OAA07204
	for <sipping@ietf.org>; Tue, 7 Dec 2004 14:06:23 -0500 (EST)
Received: from voyager.coretrek.no ([212.33.142.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbklu-0003RC-Bh
	for sipping@ietf.org; Tue, 07 Dec 2004 14:13:16 -0500
Received: from localhost (localhost [127.0.0.1])
	by voyager.coretrek.no (Postfix) with ESMTP
	id B5B4CA951C; Tue,  7 Dec 2004 20:05:49 +0100 (CET)
Received: from [192.168.1.67] (unknown [82.196.203.62])
	by voyager.coretrek.no (Postfix) with ESMTP
	id 89945A950E; Tue,  7 Dec 2004 20:05:48 +0100 (CET)
In-Reply-To: <105311F8-486C-11D9-8F23-000D93326732@nostrum.com>
References: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
	<105311F8-486C-11D9-8F23-000D93326732@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <00DBF9BB-4883-11D9-9E70-000D93C60BA0@telio.no>
Content-Transfer-Encoding: 7bit
From: Hisham Khartabil <hisham.khartabil@telio.no>
Subject: Re: [Sip] FW: [Sipping] I-D
	ACTION:draft-ietf-sipping-dialog-package-05.txt
Date: Tue, 7 Dec 2004 20:05:47 +0100
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS perl-11 (CoreTrek clamav patch 1)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Content-Transfer-Encoding: 7bit
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: a743e34ab8eb08259de9a7307caed594
Content-Transfer-Encoding: 7bit


On Dec 7, 2004, at 5:21 PM, Robert Sparks wrote:

> Paul -
>
> The text you quote from 3261 looks pretty specific to me
> and agrees with what Rohan writes.

Its look pretty specific to me also, but to what Paul Smith said.

"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."

This clearly says what Paul is stating.

Hisham

>
> There's more - please look at
> draft-sparks-sipping-dialogusage-00 for a some discussion
> of what 408 and 481 do to usages.
>
> RjS
>
> On Dec 7, 2004, at 6:52 AM, Paul D.Smith wrote:
>
>> Apologies - this e-mail should have gone to the SIPPING WG!
>>
>> Paul DS.
>>
>> -----Original Message-----
>> From: Paul D.Smith
>> Sent: 07 December 2004 12:52
>> To: SIP Public Folder (E-mail)
>> Subject: RE: [Sipping] I-D
>> ACTION:draft-ietf-sipping-dialog-package-05.txt
>>
>>
>> Rohan,
>>
>> As per my earlier post to the group, I have to disagree with your
>> assertion that a 408 or 481 failure of _any_ mid-dialog request
>> terminates the dialog (section 3.7.1 of this draft).
>>
>>   "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)."
>>
>> RFC3261 is quite clear in distinguishing between BYE requests and  
>> other
>> requests.  The failure of a non-BYE request does not cause a dialog to
>> terminate although it should be taken as a prompt to the UA to end the
>> dialog
>> by sending a BYE.  To put it another way, non-BYE requests are not  
>> dialog
>> terminating, regardless of the status code of any resulting response.
>>
>> If you believe this is not the case, can you please explain the  
>> meaning of
>> the following sections of RFC3261.
>>
>> 12.3 Termination of a Dialog
>>
>>    Independent of the method, if a request outside of a dialog  
>> generates
>>    a non-2xx final response, any early dialogs created through
>>    provisional responses to that request are terminated.  The  
>> mechanism
>>    for terminating confirmed dialogs is method specific.  In this
>>    specification, the BYE method terminates a session and the dialog
>>    associated with it.  See Section 15 for details.
>>
>> 12.2.1.2 Processing the Responses
>>
>>    ...
>>
>>    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.
>>
>> I believe this is a serious issue because it potentially means that  
>> there
>> would be two concepts of the state of a dialog, one RFC3261 compliant  
>> and
>> a second, compliant to this draft.  I therefore believe this should be
>> resolved quickly and look forward to readong your response.
>>
>> Regards,
>> 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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> Sent: 23 November 2004 21:11
>> To: SIP Public Folder (E-mail)
>> Subject: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-package-05.txt
>>
>>
>> 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.
>>
>>
>> Date: December 7, 2004 6:52:48 AM CST
>> To: Subject:
>>
>>
>>
>> <ATT79302.txt>
>>
>>
>> <ATT79303.txt>_______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of 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 Dec  7 14:46: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 OAA12189
	for <sipping-web-archive@ietf.org>; Tue, 7 Dec 2004 14:46:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CblP8-0004Zg-PX
	for sipping-web-archive@ietf.org; Tue, 07 Dec 2004 14:53:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbl8y-0007nH-BL; Tue, 07 Dec 2004 14:37:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbl3u-0006Km-SO
	for sipping@megatron.ietf.org; Tue, 07 Dec 2004 14:31: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 OAA10189
	for <sipping@ietf.org>; Tue, 7 Dec 2004 14:31:49 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CblAW-00047k-G8
	for sipping@ietf.org; Tue, 07 Dec 2004 14:38:41 -0500
Received: from [192.168.0.100] (c-24-1-68-89.client.comcast.net [24.1.68.89])
	(authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iB7JVgKF093094
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Tue, 7 Dec 2004 13:31:44 -0600 (CST)
	(envelope-from rjsparks@nostrum.com)
In-Reply-To: <00DBF9BB-4883-11D9-9E70-000D93C60BA0@telio.no>
References: <53F74F5A7B94D511841C00B0D0AB16F803E5330A@baker.datcon.co.uk>
	<105311F8-486C-11D9-8F23-000D93326732@nostrum.com>
	<00DBF9BB-4883-11D9-9E70-000D93C60BA0@telio.no>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A10ED3A6-4886-11D9-8F23-000D93326732@nostrum.com>
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [Sip] FW: [Sipping] I-D
	ACTION:draft-ietf-sipping-dialog-package-05.txt
Date: Tue, 7 Dec 2004 13:31:44 -0600
To: Hisham Khartabil <hisham.khartabil@telio.no>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Content-Transfer-Encoding: 7bit
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.1 (/)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
Content-Transfer-Encoding: 7bit

Then we should file a bug against that text in 3261.

I dug though this pretty hard when putting together the dialogusage  
draft.
I'll go through again and find the other parts of the text that support  
the
dialog being gone with the response (though it may be later in the  
week).

While I can see some potential issues with 408, 481 is really  
cut-and-dried.
A BYE will not gain you anything but another failed transaction.

RjS

On Dec 7, 2004, at 1:05 PM, Hisham Khartabil wrote:

>
> On Dec 7, 2004, at 5:21 PM, Robert Sparks wrote:
>
>> Paul -
>>
>> The text you quote from 3261 looks pretty specific to me
>> and agrees with what Rohan writes.
>
> Its look pretty specific to me also, but to what Paul Smith said.
>
> "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."
>
> This clearly says what Paul is stating.
>
> Hisham
>
>>
>> There's more - please look at
>> draft-sparks-sipping-dialogusage-00 for a some discussion
>> of what 408 and 481 do to usages.
>>
>> RjS
>>
>> On Dec 7, 2004, at 6:52 AM, Paul D.Smith wrote:
>>
>>> Apologies - this e-mail should have gone to the SIPPING WG!
>>>
>>> Paul DS.
>>>
>>> -----Original Message-----
>>> From: Paul D.Smith
>>> Sent: 07 December 2004 12:52
>>> To: SIP Public Folder (E-mail)
>>> Subject: RE: [Sipping] I-D
>>> ACTION:draft-ietf-sipping-dialog-package-05.txt
>>>
>>>
>>> Rohan,
>>>
>>> As per my earlier post to the group, I have to disagree with your
>>> assertion that a 408 or 481 failure of _any_ mid-dialog request
>>> terminates the dialog (section 3.7.1 of this draft).
>>>
>>>   "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)."
>>>
>>> RFC3261 is quite clear in distinguishing between BYE requests and  
>>> other
>>> requests.  The failure of a non-BYE request does not cause a dialog  
>>> to
>>> terminate although it should be taken as a prompt to the UA to end  
>>> the
>>> dialog
>>> by sending a BYE.  To put it another way, non-BYE requests are not  
>>> dialog
>>> terminating, regardless of the status code of any resulting response.
>>>
>>> If you believe this is not the case, can you please explain the  
>>> meaning of
>>> the following sections of RFC3261.
>>>
>>> 12.3 Termination of a Dialog
>>>
>>>    Independent of the method, if a request outside of a dialog  
>>> generates
>>>    a non-2xx final response, any early dialogs created through
>>>    provisional responses to that request are terminated.  The  
>>> mechanism
>>>    for terminating confirmed dialogs is method specific.  In this
>>>    specification, the BYE method terminates a session and the dialog
>>>    associated with it.  See Section 15 for details.
>>>
>>> 12.2.1.2 Processing the Responses
>>>
>>>    ...
>>>
>>>    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.
>>>
>>> I believe this is a serious issue because it potentially means that  
>>> there
>>> would be two concepts of the state of a dialog, one RFC3261  
>>> compliant and
>>> a second, compliant to this draft.  I therefore believe this should  
>>> be
>>> resolved quickly and look forward to readong your response.
>>>
>>> Regards,
>>> 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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>>> Sent: 23 November 2004 21:11
>>> To: SIP Public Folder (E-mail)
>>> Subject: [Sipping] I-D  
>>> ACTION:draft-ietf-sipping-dialog-package-05.txt
>>>
>>>
>>> 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.
>>>
>>>
>>> Date: December 7, 2004 6:52:48 AM CST
>>> To: Subject:
>>>
>>>
>>>
>>> <ATT79302.txt>
>>>
>>>
>>> <ATT79303.txt>_______________________________________________
>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of 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  Wed Dec  8 07:05: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 HAA16781
	for <sipping-web-archive@ietf.org>; Wed, 8 Dec 2004 07:05:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc0gV-0003MI-61
	for sipping-web-archive@ietf.org; Wed, 08 Dec 2004 07:12:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc0V8-0001OU-KJ; Wed, 08 Dec 2004 07:00:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc0PK-0000id-SM; Wed, 08 Dec 2004 06: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 GAA16217;
	Wed, 8 Dec 2004 06:54:55 -0500 (EST)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc0Vu-0003Bo-SN; Wed, 08 Dec 2004 07:01:57 -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 ESMTP id <0I8E00M3FJQ7P2@vmail.vsnl.com>; Wed,
	08 Dec 2004 17:24:08 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.169.3)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Wed,
	08 Dec 2004 17:24:08 +0530 (IST)
Date: Wed, 08 Dec 2004 17:24:27 +0530
From: Rajesh Kalagarla <rajeshkalagarla@tataelxsi.co.in>
To: sipping@ietf.org
Cc: sipping-request@ietf.org
Message-id: <41B6EB73.000003.01948@RAJESHK>
MIME-version: 1.0
X-Mailer: IncrediMail (3501710)
X-Priority: 3
X-FID: 00E77C6A-D75E-46E9-AC37-B88870FE1A1E
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 17cf8eab1d6bbd2874a56f9e3554d91d
Subject: [Sipping] Call downspeeding 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="===============0431608524=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6


--===============0431608524==
Content-type: multipart/related;
	boundary="Boundary_(ID_cy/47zCTynQE0ELcJvlGIw)";
	type="multipart/alternative"


--Boundary_(ID_cy/47zCTynQE0ELcJvlGIw)
Content-type: multipart/alternative;
	boundary="Boundary_(ID_YCkW5CbiOp4CtXfPFJBUPA)"


--Boundary_(ID_YCkW5CbiOp4CtXfPFJBUPA)
Content-type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All,=0D
 =0D
 Can anybody help me in handling the down speeding with a codec? =0D
 When we are offering/Accepting a call we have to mention the bandwidth
param as part of embedded sdp (it is mostly CT =96 conference total =96 i=
s it
the total i/c and o/g channel bandwidth of that particular call?).=0D
if a specific o/g channel has to be down speeded, we have to change the
attributes of that codec in the re-invite? Or we have to change the CT in
the re-invite?=0D
 =0D
Thanks & regards,=20=

--Boundary_(ID_YCkW5CbiOp4CtXfPFJBUPA)
Content-type: Text/HTML; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-=
1">
<META content=3D"IncrediMail 1.0" name=3DGENERATOR>
<!--IncrdiXMLRemarkStart>
<IncrdiX-Info>
<X-FID>00E77C6A-D75E-46E9-AC37-B88870FE1A1E</X-FID>
<X-FVER>2.0</X-FVER>
<X-FIT>Letter</X-FIT>
<X-FILE>Letter\spiral_sight.imf</X-FILE>
<X-FCOL>Hi Tech</X-FCOL>
<X-FCAT>Technologies</X-FCAT>
<X-FDIS>Spiral Sight</X-FDIS>
<X-Extensions>SU1CTDEsNDEsgUmBSYGBLJ2dNJkkTSidjSxNiZksxU0kNJWdTTDBwcGdgTg=
shSSFLEksSU1CTDIsMCwsSU1CTDMsMCws</X-Extensions>
<X-BG>5B9892F9-9EE3-4768-82F4-D2B9CEA41197</X-BG>
<X-BGT>no-repeat</X-BGT>
<X-BGC>#396594</X-BGC>
<X-BGPX>center</X-BGPX>
<X-BGPY>center</X-BGPY>
<X-ASN>2D6C0820-4542-11D4-BA40-0050DAC68030</X-ASN>
<X-ASNF>0</X-ASNF>
<X-ASH>2D6C0820-4542-11D4-BA40-0050DAC68030</X-ASH>
<X-ASHF>1</X-ASHF>
<X-AN>A5BE2A00-37CC-11D4-BA36-0050DAC68030</X-AN>
<X-ANF>0</X-ANF>
<X-AP>A5BE2A00-37CC-11D4-BA36-0050DAC68030</X-AP>
<X-APF>1</X-APF>
<X-AD>C4E44520-2BF7-11D4-BA28-0050DAC68030</X-AD>
<X-ADF>0</X-ADF>
<X-AUTO>X-ASN,X-ASH,X-AN,X-AP,X-AD</X-AUTO>
<X-CNT>;</X-CNT>
</IncrdiX-Info>
<IncrdiXMLRemarkEnd-->
</HEAD>
<BODY style=3D"BACKGROUND-POSITION: center center; FONT-SIZE: 12pt; MARGI=
N: 0px 10px 10px; COLOR: #f0f0f0; BACKGROUND-REPEAT: no-repeat; FONT-FAMI=
LY: Arial" text=3D#f0f0f0 vLink=3D#80ffff aLink=3D#80ffff link=3D#80ffff =
bgProperties=3Dfixed bgColor=3D#396594 background=3Dcid:5B9892F9-9EE3-476=
8-82F4-D2B9CEA41197 scroll=3Dyes SIGCOLOR=3D"16777215">
<TABLE id=3DINCREDIMAINTABLE cellSpacing=3D0 cellPadding=3D2 width=3D"100=
%" border=3D0>
<TBODY>
<TR>
<TD id=3DINCREDITEXTREGION style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 0px=
; PADDING-BOTTOM: 0px; CURSOR: auto; PADDING-TOP: 0px" vAlign=3Dtop width=
=3D"100%">
<DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman" color=3D#000000>Hi All,</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman"><FONT color=3D#000000>&nbsp;<?xml:namespace prefix =3D o ns =3D =
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman"><FONT color=3D#000000><SPAN style=3D"mso-spacerun: yes">&nbsp;</=
SPAN>Can anybody help me in handling the down speeding with a codec? </FO=
NT></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman"><FONT color=3D#000000><SPAN style=3D"mso-spacerun: yes">&nbsp;</=
SPAN>When we are offering/Accepting a call we have to mention the bandwid=
th param as part of embedded sdp (it is mostly CT =96 conference total =96=
 is it the total i/c and o/g channel bandwidth of that particular call?).=
</FONT></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman" color=3D#000000>if a specific o/g channel has to be down speeded=
, we have to change the attributes of that codec in the re-invite? Or we =
have to change the CT in the re-invite?</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times Ne=
w Roman"><FONT color=3D#000000>&nbsp;<o:p></o:p></FONT></FONT></P><SPAN s=
tyle=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font=
-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-languag=
e: EN-US; mso-bidi-language: AR-SA"><FONT color=3D#000000>Thanks &amp; re=
gards,</FONT></SPAN>&nbsp;</DIV></TD></TR>
<TR>
<TD id=3DINCREDIFOOTER width=3D"100%">
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100%">
<TBODY>
<TR>
<TD width=3D"100%"></TD>
<TD id=3DINCREDISOUND vAlign=3Dbottom align=3Dmiddle></TD>
<TD id=3DINCREDIANIM vAlign=3Dbottom align=3Dmiddle></TD></TR></TBODY></T=
ABLE></TD></TR></TBODY></TABLE><SPAN id=3DIncrediStamp><SPAN ltr??><A hre=
f=3D"http://www.incredimail.com/index.asp?id=3D409&amp;lang=3D9"><IMG alt=
=3D"" hspace=3D0 src=3D"cid:CD51C9B9-76B4-4285-BFF1-DCD9EC2F8EA4" align=3D=
baseline border=3D0></A></SPAN></SPAN></BODY></HTML>=

--Boundary_(ID_YCkW5CbiOp4CtXfPFJBUPA)--

--Boundary_(ID_cy/47zCTynQE0ELcJvlGIw)
Content-id: <CD51C9B9-76B4-4285-BFF1-DCD9EC2F8EA4>
Content-type: image/gif; name=IMSTP.gif
Content-transfer-encoding: base64
Content-disposition: attachment; filename=IMSTP.gif
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhDAJMAMQAAHYdAP/yACLVxP/7nAAA//AHy/7SAPy1AJ5IDPWYAP/93aA0Ad9xAfwMDP/5
eP///7Crm9rQvfejmv3Bav+D7ebh1K1zJv+uNP/6Mc2XAAqDg/tvaNewAL2NPgAAAAAAACH/C05F
VFNDQVBFMi4wAwEAAAAh+QQJHgAfACwAAAAADAJMAAAF/+AnjmRpnmiqrmzrvnAsz3Rt33iu73zv
/8CgcEgsGo/IpHLJbL480Kh0Sq1ar9isdsvter/gsHhMLpvP6LR6zW6XnfC4fE6v2+/4vH7P7/v/
gIGCg4SFhoeIiYqLjI2Oj5CRkpOUlZaXmJmam5ydnp+goaKjpKWmp6ipqqusd1BFUZKvH7MyBAQi
tym6rb2HVCLAwVPDUibCNLW1QcuQs88eu7e4udS8J9fY1NU42b7fM8200cPlJeIk6OHkR+rO5OrX
1tsq3iXZ9rb04PxP7CPK4P0zh0LcK2jpYo2LFbAhO2IAFUZUaKxcM4TFHgq0OHChxnEEPUY0hy4f
L3nTuP99sIdv2zSXuE6mVNmvZguDH0Ge65jw2MGfJDcGBagTI8YTAYNKHFpUKLSlTYst1NkzKlUS
JufRjMlVG1atK+ellEnTptmCEJEJQzaRotO3BI8yNcozLlykd+mGrKqXatq79/apJPs1X9iXhAkP
Bnu28U6fV3GqkGy1r9WRlTXyTHrZJ+e+6tbmHb237IjE+16iaFlNddjCMw07tkmZc1W0kDMz7az7
qm+/gD3nBF23NmneJrIuDvw6OT3Fp58Lnk0d8225pW9jJm43bu+LHT8LxSt+bvGH5tMj37q8+crm
LKWzd++ecfWzlDlWZJuRe8aE0TjU1nYCobNMRb9pJ1L/W+MJR6Bdbu3mHEpbxQYTc9FFRyFsGd7n
4YcJgijiiCS6QwhiKKao4oostuiibCTGKOOMNNZo44045qjjjjz26OOPQAYp5JBEFmnkkUgmqeSS
TDbp5JNQRinllFRWaeWVWGapZQ8CHJAADAJU8IEAGtjQQAMqFKDmmhS02aaablKgAgIkGGAAAHgC
sMCeDDDBwJ4L5JnnCHjW9Oeeghb6AwB9inBooIk6CsCWMSRwwAlhimDpCAIIMKanIwQQwAebYlqm
CGeeoMGqchbwAZwNUBBrAW22gMCtdtqZgAJQAOBBBA78icQCDAygwLHIHvvnpB8woCgKCCxA5wvM
Nnsr/wKJVmsDA9feKqgPzn5ArLHJIrtsD9WOW64CFnRwrQjaUrqCnZiCGsCXJKhZgqidXlqvCqtq
QGYBFbg68Jq0wgDAAQjk6iUABgwQQAQRKDCAsEOoa/EAAzjgMQYY3MtAAviGewICogYQbwqFIlAs
sgAoyyi2NbhM7rrcrlwDns4acCzHHX8cssp66iwDs7d2YMHGHbf7wNNP3/qB0fKWQC8JnYqgrwlb
T81s1l5jfYABqq7aKZmvvqrm1R+I2gIDXiZgAMN2HnAAxBdcMMAFEUhg8QJCLDAAnhs7MHTKliYg
Mb5TmxCtpQaozMLML1vsQNCGYwDAvTTDYPPPl3ucuf+oCXRuA6N29gw0BpGn7CzJdlMdAwJQP2BB
AA4EYEHtvE9btQtbg931CTy76nWezuYZ8PIBn61AwGqrDWec09fq+NwJ9ApF3HYfcMEEev8M+A+C
Mwp07imTbveui6eA8twGOCA7vAiQyzH66advQALzk4BtzPfLX/721z8VQExUqVtY6w4gKga8rnt3
ywHteHc73fGudhbQU7Sy9azfDY8EKTMBowgFgAzgDACDA4DAzsZCBXTJbK9KgPHW1AA11dBNLKub
ngJQNy9B8AAR4BiyxseDBRwLhRwTGQNFxcD1WYyHjCtBoLAnPxbULwJ4wp8FLBAoAYqqgPVTQBa9
SMb/AqZAWgiUGKPGxsBlWeqHZnQf7zTwtC1ekHeCA5oegRZHSqWsbvAKQLcSICqQdetyAFSh8wTg
wgAIbFVak+EMbRgrORkwAQywkwLhmChsIUB8RTSW+RbnJQUwcH9zK+UAdGW0BRwAUlZMYQI6sLkA
LIADXhqcACM3vzBaLFpk3KXkZiAtO4lqcTw7QCZReC+7GWABc+ujFHcHNTrS0Y4PIJMALpgtBz4x
AIP7XQvkNrepCbJ2KBPVBKOGyGM5YIUBEEA8takB46FpTDX0l9tWsEZl3smHY8PT0wAw0KcJDpQ5
OKgYO9ZMVY6tYU5c5f7457hhxnJhuawgB7DHMQsY/xOBvHTfAM6WOwQQMph/DGkMysdBQe0pAxMw
ANzYCE2KymABE+hA7bRpO2pa84IWeNjUDpDEuVlUnPMi2wfWCTWUMTVquCPXO13owhUmoJ4joFUF
zlQAriZMBa6E3Q/vBAAIFPQBBH1AHpWlAwb8jKFyi6gtu0XXhhFRBCgzY/0AEFRscWBwd8tT/UAK
UgKeTAFPEwAE5InSAbIyBm5dAMUo5oGAUayliXrmDBgggadus6dPCxhQLQU4iEnMmV9E6grA9lQP
RK12roXq5X4mMAN06qqQJEENX1XDrtIqTiKE2xu7J9O0mvUBHjCrnhYQVWMN4K40OGgATZpK9gky
AP8MeAAdmzq2BEhLWiM76pzEKFC0ZvBuT5MABJI5Nh7mynf+y2Y2BRABAbSuse61E3xZIDhbzlFg
Bp1sZVc1WVcaFgY4lcAEnvqAhlGTp71L3KQw2l01qlYFYFtA7ejo2nVyOGqRm+3zsrnC3GrNhvZ8
Ew5PAE0f5kqTx9WeB3yVvssZq1El4JkL3Ho/B9a1Ww1EJ/wil0Qe6lWUodWAArBVutC6Fk/OjBz8
bDqC/wnKA2HC7x+7G0e3+veOD6iAhqsJ4DAbWLMwYEAERvZKIduJmne0AMnkNj481c3Cv8tUCgRG
qjEnFsDrhLBJD+XW5wnsqlfNFw0t2QIAkNNSPBT/VXJ3N+NK0zhlIBPiAHyHJ+aKkr/OvdjCgrzd
BqfPx8wdcnEH5YJPDu7PAz3Ag7dLYSnnKl6fJOiq0AoAxmr5xUdWgC0rcMcKiJnYF6wARh/b6gkk
b2a3Cmqu4HxBk76RynlioDSfBLYTdC27GzZouKP2MD0VWgMHeOSpuNbV3fKzbh+V9AMgUGlL17LG
QpzWqDEqXhZvbJlGxW5TUQrvO8kgjBPAwO7IhFbY0Y7hDUctdiNH5TDSrsx4sq+W3XsvMG7slcYO
ecgXtgCRj9y9YzN4q0c2gQk4GoIfNYAFnnqr9aV8ZZvbNpOEZ7wS6It/f7rgArxb7TnXUpmGJlOZ
/7qtaODmcMjpS66le4UnL+YbXlwOLH83ljIDNxCYZGQAyjV5cAU4YAIMS0CsYcc/qL3cbmIPQAOk
XK1POmDhn+X1vRtrTJWvwNWnBRSioGw3wSOKiUOOIwIq0PI7DVfi7u1WUNkYZZz7/UrBA9UHRbg/
P6s1cZ4fOiH5l7LZagC3nxKB3bodJ+txHurHrLevEkU0Qc1W30atuhhXYESGdv2Vt2IuGV859su3
2uypxBMCfkiyPM3Zbg1wYPTJjlezM4x3B9y4UY0PLctRXplwR+1M4+3Mm7/gk41/uapzBdKxEpf7
C9P5kTYvghCW4G4jI5ngH7//xJEeZA5gMWZzKv+psnqgIgICQH+EUnApMwBTx0EbsAESMIENAAAB
qG8KxGaCxHtmhz9Esz8H4AAN82K6InwFt212VzfPl0rrM2diNTbRF31GVmXW13axlnL3FUx2M4NW
1IEB4CUOFH73pUxBCHeZlHjnZ3YxRSyq5lgkaGvmRwI5d2H1t08kcDcu6II/5EP+p0zChzsBCD2o
ck+YooDw0kP35YC+MmPZsgENEIEboAASYIGbdobL52isdkZBkz6bw0YiuIXEsmVR6DkM1UPut4XO
5DEMMH1+Vz9o13x4AjvxhlI7yH0n0zEpB0Fwk4MyZYTjV3nnt4eBgoMEx36pRH0LKH9XMiofcDf/
cSNcAMV8YsU/X4g7z5NuOwAx7xd79iYoZ/KLETiHF4h1ZLU5n3ZGPpgyAEBdDDR4y5VyKDeISegA
UgZzL4aIOHgxDcCDS1WDWRhlOehFqcSN4+UxQOhAm7hLM1WJp2iJ3ecxtrReS6R97agtfaiKWeKK
3PN+DtM9EgYBtRiAKrRuKnA1CggxLNg6z9WLvvKLDnkmFrhkhPIw3RNOyAiPfKiMQJNSS5SQ7mhA
ZpdSLyaSPcQ/UNZ31RIz1NiCYjWJ4jiOH+k/HWiI7SWO6EhIHql4PihZ60VOT9iPqfZ+KUmOVIgC
CKl/kniNXOgsEBABATk4BFmQSnWQhmhMq0R1/774i4niMQbAafFnKSgkO9CEkV8UWJszkjvYfqAY
AxDjgZHGd/vzbGeZkovIgmznLG65SzAJRvGTOyRYikp5AMKmeH1pSxQDkHvyeD/kLJkklF6zShFU
lCdGTv5yQMrUT4joXXvSlE5ZY2KkVC2ANgb0fdC4kGyIJ784Y88XghcDXxDDP8vXbyQwLvgDUXsn
QCFDk9F0NMWSl43FOoE1jpE5NQ7pgs6yAGSZPkNjiD8IRr2pPz8Zb7lpl4N5fs8pWRRTARAAkJgF
TY1ZfnmCTJJZApRJKDyUSZDCQQuwnRVQYKVXRSjAdAgIKnomhXZmc9DIP6fpARCphXbjMdA1VP+Q
1j/I6QAm2Zz4VZI7GKCtlpxw+TAQtYOuqZ445aCOBUEb6AIFml/YGGVqSVq5w6BnBI/YiWzGFgHG
tp3biURTtqCOdloxOZ5T4zAcU1YqeqLG9jTt2ZmuQzXyWQJMV3WitHwtyUuniSgZ8IJLZDJS2F4F
xCjHhKDBNJ0tyEbyt0YuKY4Mc5LENZyoIgEbsIiiY6GFpJbgSS1ix4KGJ3hsloncs3wO8EpoKiqS
RWzHlWxItJKSiIWLE6OqJZ99GDE1imwXZFbtWYvVsnlWyE+nNTbJs5oUd5oVOGeS5gEIxKCu1EG8
FzFSWopV2ow20DB2Fp0quHwKykD79QEPuXH/0fhGGeoCehJNeLJHReWFe/Kp3hWnfQRNdBoBTxMB
d/oAvopEkClWtiQ3P7ibMoo1B/gqCiQ3fCSstdOUv/qFxZUqisqKjHovkBgxjNKSted8+klQFuAB
xXUy0jQzVQeYn6qsNIA6fCU3CZBBnQQ3K8k97qpbZ0KP1QU5XspPWEisXRcttdh1b2cpEEVlk5NJ
hjmt2zmsHVOsbxRNXqJDfyome9asauJoqBStwLqdtcOjhpUqLsA2TQqJ4AQxYrSaEpMBneZosfVk
ByZFOsex4QiddimJCvuuCeAAHIAnFkCrY9qvXMYyyBpMgamzcdSH/MN+0VI/Ivi0zKkyj8W0/0tL
TpJ1R3k0ACzJZcv2r1Xzo1nVczmGk4rDMZ4HNU5pTDZlhiZgsgvYPT9olj/on6uUKAP1mkazjDzb
d4VliFrYcTpgWno0t+CoKyRDcfNjs/EWmHGDrDtrQDxUbt6FADa2J6JyOd9FqXpLjEIFq1iLoidK
m1wbuDb1LUjFc95GtmWrK0DzJ6J7qLmys/zCKc3aaDk5NZRpt4I0e0dpNC5zOj7Zj/64gjObAwj5
hPwoiYI7OcNLvF2ruK0mWPxDiy7FRAx0PlMETke1jJgUuUabQDyjR1rIbBeWeSc2A46Gk3r0bEfY
fCYgKhibelU4OdjzbPBCMpObhRuJuHvrp//8lLgs+LjMC7/o4pOyyLzHG8DQS8DttcAsw3WamSie
NrdGdTHKaMCEojjoc7WEpEdxWr7cio9QooD2pzAIvEdQlHG3awLCs6g5lL3HqCfP+5PetbfNezpD
R6qzGyhA4L1P+EdQZDqwSl1/iUBDbEYLIzECRKuGi1oGKpfZwsTARi07zMOdR8JacsL6ioBReTzP
a5Jf08JWM5Uka78Ta4/qR4Je4sPQ0py5OHQ46DAmSQRAbMNEzJZG/ISl00dv16FjRcdLBMiymK5y
rLx1vKwzQLJiCy/ZIgNsc8b0Szyom2OYJbmfm4uXfASYpcXHw0EzYGWd3MnaNsqCkqqwuskkirzK
rNzKrvzKsBzLsjzLtFzLtnzLuJzLurzLvNzLvvzLKRACACH5BAUeAB8ALAIAAgAHAkIAAAX/oCeO
ZGmeaKqubOu+cCzPdG3feK7vfO//t49wSCwaj8ikcslsOp/QqHRKrVqv2Kx2y+16v+CweEwum8/o
tHrNbrvf8Lh8Tq/b7/i8fs/v+/+AgYKDhIWGh4iJiouMjY6PkJGSk5SVlpeYmZqbnJ2en6CbImUj
kaMfp1IEBEKrSa6hsZcmQrS1JbckRrZUqalhv4+nwx6vq6ytyLBHy8zIyVjNstNkwajFt9lF1kTc
U97A2JXESMvKz0rSRc3qqujU8GDWvtjz4kf219q59br0/+JwDdHVjSBBfcHI8RvYL5s9evoiLtSm
cN07aB/MHcOojt2zYx9ZwQI5pF28k1ny/1G8tw8fy2vFSimsSDPizIZIINo8uLLnTn4sb8YcpfKm
s6MZz5VMytSIR47nNo5UirLqFlu8sAosaBCnUYkVfX51ydDnLq9ozW5L+xOo2JdNLUK1aBIkyaZT
ieSNa7VvlXy/VOZ8+XVs2LY0uek8zDUgW8ZAH0tWW/IiXqqV66KbetdjZ8t+Qzcp6visEtJv9x0u
HJRw6bYuF08muzY1Yrh6Le+V5qrdU74Yg4se/td1WYnHB5u+bbYm69rQmQ+WbXs5KtvPkedeejm4
SMyVt8cFb0448fPKoyMUyIth1+al3IOND/M1McX3DoLTzpM97vrHJRbfWE5tNFcyewH3W/9SGtEV
EnoQRojFfhJWaOGFXFAYiF0cdujhhyCGKKJJGJZo4okopqjiiiy26OKLMMYo44w01mjjjTjmqOOO
PPbo449ABinkkEQWaeSRSCap5JJMNunkk0gmcEATAlTAQQJLCCAAEwV06SUFYILZZZgUKIEAEQYY
AMCaACzgJgNtMODmAmyyeR4DAAwhp5t1rgkGAHAKsSedfQqaJ5RqCLCmllsK4acUGkRaZgEfjNkA
BZcWAGYTCHSaZpoJKCACAB5E4ICcaSzAwAAKtNoqnoDS+aeenSLQ56FSMFBrp3WOsSaeAbDqKgau
KiDnmrJmgauqwhZrQQe1OoooGr9qaQT/rE9EqoEAGhRQAaVCeDkmFAAcgMCnByQAgAEDBBBBBAoM
gCoZzLY6QAIMJJCAAwbgaUACyW7hJwKrugrAq4Da6sSZBDdbrLEKfwFomsA6YDG/DmCgMZ76HnAA
rlUc2mkHFsQ7wAAOPPvAyit3+gHI01rRZRKAZsmxEtoyqkGlCXhJBQPpJmCAuWl6vO4FFwxwQQQS
xLtAF48KsUCzAUiZQLtCp7nuvzBbkXDB8TqAssUaA1B1xEqsKSzKY2eMQQBnd33FunBTXK4BcB/g
9sdSHqCm3FMgwPIDFgTgQAAWDK74mTFnMXOalYKb566OrsmrrWtqq3nOWiqgbeQ9f0nm/5hhHnFu
uqOKELTHB1wwQdL2Pq1FzUNMbe+9HoeKtd9+Fw24FAAgsDbKcBdvfABcmzmA2sQfb3zyAhuAQN3t
ThyA3hjw7TGov0MhuOKFI6744BbAvAAChN7auLVHCAD5zJMPbmsGAXzfcryZM6q/AAoIcECk4arU
Bw7gpQZ0yYClQ8LWPrYA5A0tXbfCXKtk573zMU5aQ8DXAUx2gOulK17I05fQevexLAgvAms6HNws
YAE6OQ9ugBNeq9D3whp2TwrnwluwqvYrvX1sdxQroRXstzINrIyF4wPfsk7GxCae7IZFmpmWAtC+
nRWBiC2r3/gQYC8AbKtz/BNAALYFQP8BzixyBWjApcqUNnxpjXdGA8DK5PgAOh7Mad5zAOv8RLsP
WE0BHZTeA3UHqo59amhQXILw1pSADpgtAAvgQLqW5zy8dU14rEIZAhJQw+NZUgvpuxWb3JSBCfSL
hEBLJBIWkDiWGdGISHwAtwQwPguoq3J1YgADQBgsVQbpjNszgBHYJwQseqBlgztmy4TlgC8GQIxa
IuMQGjBNcBEzbUA7AAPUlK44QmCO4HyA7fC4MD0OLQB5wlXfdOe3031wAIWU0iGhF7jl5W4A4ePA
0K6GzzQVz58gEx4tBaDCTnryk1eY2gLe9S4PaOtdorzVLaWwgAl0YHCzJFwrX1lLCBr/oVwnQ14H
fTkkKX0AckW45gIGZ8Rj2q+lLRNbq5rZv/59MQFWjFyZ1JhGA2pqCQtYHevMRcdvPsAD32zTAsQm
rEBx6nr/QtsH3Kk75O3qqptkXd3SRMEoLNICROWAPeskvK1uFXoy1EAFImDQF35qolVgACSTyLKF
NvSh71oAV6fAAAlgkZYaLWKkaimlrjqKXR5EaMy4JYTiGQFgGN3WA+yX0cni600D2JYBtITTMkbO
gJXyKQLJ9FGg9Y11ajJq6jxAquIxlZxNeCQ6ieCp3IFwAfhyZcs02MG6+Q2u3lMAm+ZYvo+tTAIQ
6KHfHJgmxnGxf7KEQFsP2lwrTG2u/3StwEqzG1R6OqGiEpgAFidrgFZWVn5W61q5tnc1khaJfY69
luKMKE6WsgwBEGwTA4w4S27ldAhpBNcaNbWpI+i1m4dEauJYy+DWGu+1Tn1ZHz+6pikNAau78hgD
Bofbjj2vd4adatSMIEM63hcACcBihXsnUq6ltQKydN90P+zdKOwSkjAeXwW0m2PFVWC9e4UCAyKQ
rwNst2WfamUSbakvA4T4ZSRcXuOaoK82jQ+3R76vCAEgNm1GSgA4xekQPPZZNsY2a1JCHtyOCQEG
u1m2AdDYyeKFuQayqnt3Y9zUNlxEcT5Qm7pCn6qW+8/eARcBFput6fDHUg2US8kPiP/Uepd7yFs9
IAIynvFZ1UQFGQ7AyDsOdajLtQBRj7rFNTbTBGCVsE6BNcl0tew65VYuNbt3WijOMm7TpWt98dBw
wtLA//w7ZguL1oCNolnR/Fk8pDZ4VGty3mtrvV5FK3u2B7sAn8VJwqHmrk063GrvcIU+/Cr2wqya
AAaUzK2OUZa1fdOhP9UVPDZxi9manvetp2oyPc6JTys28r9dCNVxP4FgCZjABFA8VGaXF4udyp3B
j2A2rT0JpU2YEqAuO6fTCtxNHasy3GT6Zc8KwVo8JfCmqkTxZYd7AG9ucLRvdTJ1/bZcI1bgSHeJ
tD0FE11WUxe+njc0ixezxQ64pAL/HDABcyVgZQLwQMjp2G7UHhJ5AJhABSaQ9AqHe8b+5DQOOfjn
bGYTb2cP9/Ymzqmtm5LhDf+n9GoFVjiyvQjrEmKT3CdMJ2hcX/kSobe7GXRtNnDkrNJAZwFcgGuq
PEzJJsIC8Q1zUpGKtX3awAYkwPkGrEtd54y2cJlQa3m9Tp5yBzrAtkd0ttNpn0kn8dIfaDlvV5mR
HSP0OYWn8A50QOEV1rRvsR64sF0PX2Yn9PV0mU1Au9yXXFS4muTZu6s70Nt/NjreEQklxiIB40L4
WAZEmPvqDzL36mqgxhwQr5IzPmQuL17loZ35Bmh+AwqQQLno7bci1y+2sZJweHN1/4fEa0X3dc9H
BEF1PnLDRfyyT4Y0VORXfjpkLrw3ARO4cCw2Yx5DfGNnTn+mTcqHPGanS8F0d4q0dKakKgf4dcw1
T9enfUOQd/v2I9eEJn03ZutFgQOILhIIABBweIbDfp8DBWf0UUWjfDD3Zn2iRmqkefoHQdLDN3bi
BAAwALtWdOaHSHr1KZ4UTDBDbaZDPEmIfYNndXDjThBIfj/HgYG0b8JjMenCfEDjgiQ4VL6FgsqT
aHRSfQZFgGC4fXrXfZF3hENARYf1QB22hawjJXgCAREghIbjOf8TBYYoedmnQ1goc3XihJ7oeRDk
N2wSLKMXW0snJ2cocBt4UIGId/8jJXv8IlJW54ODJ2/4ZUjxFG926FYdKHZetXQPGHduRYfXp4dJ
4ICHswDJ1Vv59kAyaDbAxSTxVQSXGEwvgzfaBCipqC9zAomR+GDCZXI3SC5lqIkGwImk4ol9EjS2
EooeI2VNsAAKUDQAp1RA0y6dlInlto/5Ym0zuHSp54WbJpAixQANYILV13D4lo8P5IG/mGgwyJBh
Z3XQB4yQFAHJlTXzVIBGJotsV3E12CPTqAQmBTl00y9OFlFtAgEQsFZ59WDLsy0VMAQ3eInKlonB
som34oQAMH6Cpy+Yoz1XqEp6BYLy10R/mInsAk+IdT20ZgAFVTfCJ1JOuCrlN4v/05WEDuk9UBmV
U1mGCuCPitSVF4mRHZeK2bhNFClh8DSIU2ZSS3CSafJELMmSOxYBO7YyLimJ7JcnxFST4EJ6dsdi
90J/AOCEUid4uaMr16gu+CWWScAsh9OLBOk8b1OGvIM56NMrFLcqXjldb1OMfYKL1vdCoVmGThk4
nkl0G4lvl/lnoQKZx7iadoWXLBlKfaJXarl2bII1Idk4ZrM9TAQAPaY437RWQmgxMKNGWNBAbCJP
OmR5a+IBaoRiFMhrM9hNshmZiTaVxdg3kIRD3emdRZMADSABG2CQgeedxdiBF0RREImZtShvg2Rk
yQgFS5WM75Jjd7ljdZlcJ1N0/+BJJ1cDVb8ZMwvkN8N5aYMDiSvzjcaDJ0XAnDgYBdF2Z+aGNwmA
eUrVk7nnWxLqKMvlXoAyla+ZO9R3ayXqhkLznZ/YYZp2miHIfVRQon82cP9WZN3mbj70ZAokVxcJ
Y0alY1coNhDIOyiGNb44ZdQYmEigKB6koE90aXU5OBBaPABgk4foQEQwjpLXLtsDKy2KTmzieSK0
Zh4gUl0VVDn3XbvIkCjagT7KBOcCdilGfUFjntXpa19Znx30nsBzYL3pRO0yNIMSp7ymRySlV3Cz
UA86pAx6hQEqVJDUokjKpEfwOMJkiFVyN7nHRFnGMldKglnqpEUAN8MUeXiHNf+3xy4TgwESpS6s
RTge0C8BFZLWk5VJmHs0Cjzb1JpJyDW/soZV5ijb1Iznd6k1SoVMVDzn4yYvRKASdzrRiE1446gs
U5cRUEdsc6RImi6+w6Re+gF8FzlduiUo9i8dw0Rygpd3KYmplgTeJ5i310sGIFwH0C4ZgCw9qUzH
9HkgEzA1mjUS2YiGVK3k0mQJUD5kxSufci4HCzLpmpRlGLEhc3xbgzflpknlhproxD0vg7FPkK5O
tq1XxkQoKk/8p6zTIkWqSpP/VQQmyUnqyk8nw2py5YUIK68vq0B/5kFsoqPw1CdzBLB4B6hTQLJq
9oKwKXg8hAVrwkKEejHoAir/GqpeGhluHJmyV3ux+8RI58NU0Apsz3qmRgtlXzuyWbNQoRaJnvlp
bPi0EtamT6KlKdWzJ2UAe5qL+YqUhzRRM4Oq5Ppfl0ihPkuRDMBkn1o/0gmytBVhXpO18smGjgu1
V4OZBSh4XUtxkju5hiS3OMQmm4RibVInh9eBTOQAr7dDErtJ+eJLJIuzTUS58YqpTOB4Tsqc1umR
vGpocBW4iGgEBSC4QsCc84qJc8gmhRN0ItSshRSGSzo3TRaCE7hcxSowGml7mhtCeJa9Eri9tUt6
JlM19YgsO7R2wQKk6HS9M3g1KgS7vtZEekS5VbOztguzjUW8RGC3L9O580RvuklguESQN6l6uDkp
XNMLrP8isCFrv0mLWwr8VgysLJu0kf8UQlKlQBUckWoWVTUIUi9EqFHKeg6ALyp5hZsGuxAcwQt8
oHvXKCM5soz0v1UYwNRkBEVjof+yPaQLnZk7wdPjlrOThfOUX2IQPP7rweSywRuZYr8Jd2iJfUDX
W1GsvSRKxJlLt/e7v6Z6BHC5BFqjPlbAcsDDmXMrShQnsn+ikmZwwjXKxliAOSc8xyM1x2T1xhG1
xUcQAgA7

--Boundary_(ID_cy/47zCTynQE0ELcJvlGIw)
Content-id: <5B9892F9-9EE3-4768-82F4-D2B9CEA41197>
Content-type: Image/jpeg; name=2.jpg
Content-transfer-encoding: base64
Content-disposition: attachment; filename=2.jpg
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAHgAA/+4ADkFkb2JlAGTAAAAAAf/b
AIQAEAsLCwwLEAwMEBcPDQ8XGxQQEBQbHxcXFxcXHx4XGhoaGhceHiMlJyUjHi8vMzMvL0BAQEBA
QEBAQEBAQEBAQAERDw8RExEVEhIVFBEUERQaFBYWFBomGhocGhomMCMeHh4eIzArLicnJy4rNTUw
MDU1QEA/QEBAQEBAQEBAQEBA/8AAEQgBHwFvAwEiAAIRAQMRAf/EAHEAAQEBAQEBAAAAAAAAAAAA
AAABAgMEBQEBAQEBAAAAAAAAAAAAAAAAAAECBBAAAgIBAwMDBAEFAQEBAAAAAAERAjEhQRJRYQNx
kSKBweEyE6Gx0UIE8CPxEQEBAQADAAAAAAAAAAAAAAAAEQExQQL/2gAMAwEAAhEDEQA/APnAA7nE
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABUBANCuAGwWRpA
USgJLK50GnT+pXxhaPHXuBE3qSX1NLjD0eOvf0JNej9/wAbcvXcS4WpbceT0eev4Hx4rR5e/p2Ai
bhiX1KuMW0eOvddiTXo/f8AG3L1EuFqW3Hk9Hl7/AIHx4rR5e/p2AibhiX1KuMW0eOvddiTXo/f8
AG3L1EuFqW3Hk9Hl7/gfHitHl7+nYCJufcS+pa8Zw8Pft6E+PR+/4ANuXqJcLUtuPJ6PL3/A+PFa
PL39OwETc+4l9S14zh4e/b0J8ej9/wAAG316CXGd0W3GcPC37eg+PF6PK39ewETcrUS+pa8eS0eV
v+CusKeLj1/BBlt9eglxndG70SUxsp1xp6Gv468WlLto4+j7Ack22iHStVpZbNaT+DDpZKWtAIA1
GdAUAAAAAAAAAAAAAAqIEAgrRCsBGgScr/I2CygEPt7ldXCxjqupkrwvT7gVVcPGOq6k4vt7oLD9
PuQDdqvk8Ze6HF8VjL3XYzb9n6sf6r1f2ILWri2MdV1ROL7e6Cxb0+6IUbvV8rYy90HV8VjL3XYz
f9n6sf6r1f2ILWri2MdV1ROL7e6Cxb0+6IUbvV8rYy90HV8VjL3XYzf9n6sf6r1f2ILWrnbD3XQn
F9vdCufo/wCxCjd6vlbGXug6visZe67Gb/s/Vj/Ver+xBa1c7Ye66E4vt7oVz9H/AGCTeFJRq1XO
2FuuhpeG3Fqa8pXxlTuH/HorTLSl9NA7wnKVmmosvqRVpWraWlWmoba19RyXLk8vRqVDOdXN03uz
IR0fJN41STlroVWuqPEqIcroznbP0X9gv1fqvuBunJONIcTqjKu1WO8kp+9fVEA6O9WnMtvC6fUn
BNVddG5n6GAm1qgK019cMhrnMJpQvuW1Zl1xLSQGAAUAAAAAAAACohVkCSVsmhXACdAm5X+BpAUS
tNwEvt7FdnCxjoupNOj9yvjC0eOvf0AKzh4x0XUnJ9vZFXGHo8de/oT49H7/AIINWs+Txl7IcnxW
MvZdiWdeT0eXv+A3XitHl7+nYArOLYx0XVE5Pt7IqdYto8de67GZr0fv+CjV7PlbGXshzfFYy9l2
Jd15PR5e/wCCN14rR5e/p2INKzi2MdF1Rnm+3sgnWLaPHXuuxJr0fv8AgDV7vk8ZeyDu+Kxl7LsS
7rzejz1/BuiXFX4t1l79l2AzWznbD2XQnJ9vZBWo7OKtaPSe3oSa9H7/AIA1az5PGXsi8nxWMvZd
jNnXlbR5e/4E04rR5e/p2A343a1oSTbT2XQ0rOteL+FpmYWo8da1tq4tD0b7ehl3dZo5jo3P2Cte
byTxWjaSm0LoY5Pi8ZWy7izrOHhb9vQJ14vR5W/r2CLWz5rGVsjPJ9vZGqceS0eVv+CfHo/f8AW1
nO2Fsug5Pi8ZWy7i3GcPC37eg+PF6PK39ewErZ8ljK2Rk3XjyWjyt/wYAAAoFrZ1/JABqOS0/acG
Spw5K/lhRCIMgAoAAAAABUQIBBWiFYCNAk5X+RsFlAIfb3K6uFjHVdTJXhen3Aqq4eMdV1Jxfb3Q
WH6fczIG71fJ4y90Rp8VjL3XYzd/J+rI38V6v7EG1VxbGOq6ozD7e6Mp6W9PuiSUbvV8rYy90HV8
FjL3XYzd/O3qyP8AVer+xBtVcWxjquqM8X290K4t6fdGSjpar5vGXujfkq1StJThuGmsaGPjzu3r
EwsTqZs5qn3f2INVq52w910Jxfb3RK5+j/sQo3ar5PGXujVfFa1dGlDb1a7GLfvb1Z1VVWiVrJO0
6Rs4IN8bTyvRPR/JNdPU5WVrOXHuhFq2dX0f9jIG7Vc7YW66BVfF4yt13M2z9F/Yq/R+q+4GqVfJ
Yyt0Ti+3uiU/ZeqIUbtVzthbroOL4vGVuu5L5+i/sT/R+q+5BqtXyWMrdGC0/ZeqMlFC1YLXr0A3
otCNJ+pG0vqE0yDJU4+5bKfl/QyBqyUysPoZLXXTLePUgAAFAAAAAAkskAFliX/5EAFl/wDkhyfb
2RCNgXm+3sjPN9vZEbJIGne28eyM87dvZEIBrm+3shzfb2RgoGubzp7Ic7Y09kZAGldrp7Ic329k
ZAHR3sqapfJzMIzzt29kLNuE3MKNCEGldrp7IvJ9vZGSlGk7WtCSbfZHZu7/AH8ctbwjjRW5J1yt
TVl5KzZaLs5IFvLZudFthE5vt7IxLeCqlijTu+3sifyPt7Iv8RlpVab1T0fYDS8jnb2Q5vt7ILj2
ae/c0lVr+4Gf5H29kOb7eyLFTMa+qkgqu86eyMyRogV0pV3xhZbN8eGj3M0m3ida5nVdjXkhVr45
1qob7sEc2xItR1StKae6IB0rDz9TIq3MddC2iQiFeusQjJpaprpqiiAAAAAAAAAAAAQAzLZWZbAj
BGAAAAgAAFAAhVqyFrPSQG5UQoFEkkmQOnjsotV6ct0bVa1q1V8m/ojPjdazKXLKbxoV/wDQ7KGk
vREBJbaM1zqtLaT7HJ+RPRmH5JXYtI9C8iw8o5XtM9Njk2TkSrmNq0PEp5ReT6nORLCx05scmY1E
gjfL/wDRMmJEgjrVqUa+PL5PTsc6TImQOtp8nybVaLRGLVdHD1nDNcqWrXk3XjpBm9+TUKKrRAVM
2/1nc5I6JTUIhVnMEBUUFtkgAAAAAAAAAjBGBGZZWZAMhSAUhSAAAAAAAtd/QhUs+gAAADVURIsp
AdKLS1o5WWES3J0s/Ikl/rtr2MVtZ2So4Zpqk/Nu9uiwTVxxCo2da+M7rxpKI1ESvHarXqxWjbU6
Jnbz+RckktVE9yOrl6OHqmsp7MLVr4acbKJslP8AWC2rXg7JQlaEvSH/AJL4V5FZNrRqLP8AwdWq
KVs9X9CpXjd4Se+v+DEi9+Vm0oWy7EI21IIjSTkDSfFR1LBmzTeh0opQTWUpcNpd2dP/AJqrq7cu
kLDC8ab1wpenYylS7dVXi40cyNGUbproc0dKMIFIilRp7aRoQPC0+oIAAKAAAAACMyysgGSFZACI
UjyAAAAAAAAAOjhe0GFlHRLKjRog5gFwUDOrNfQKcsCcHEnp8fjmqv5H2UZZzlNQd/FevFVupjEC
JWuFeKtXRYhiNDolyXK/xosJGGVNfP8AN+52pZ2SZn/prFp6nAy3zj2O0YOPm8j4tddDm0mtDEBc
xGEUQFVHRKKz1FKTtJqyz0A5nbwqTlGp6fBUqa06WSVl7nPyWulsuW6Wp63W1dKWTe9Tz+WyskuM
NPYiV5jp43rHUxZamvHhgUqIUqNPFdfoQrmFrOhCAACgAABGUgEZkrMgHkhXqiAQMBgAwAAAAAAC
10sjcpNTr2MLK6mrOGn0IJDnXRg1fZqWnv1MlFRqCIq1CKlqbroyJLobqkB35/yRp8sI3FE1SOT3
Zwo+Nk1lHfnXNU+T/p6BHm/6PFKaWvE8Uan1rrjThGr1seTy/wDL/tPHlhE1rzvTyojqbdXVurys
hBphVNKs6IqUs2vj69QUSisLclkWQk7FGa1lnr8adUnjoPD4Fx5WcKYR6FHj+FvlR6pkTXO7o2rN
ury1/g83kfKzfVno/wCpqaw5SUJnlswjm8mkorJl5NpfHX6BURoQaqpeJW8FQvn/AAZK8kAAAAAA
BCkYGWZZpmWAW6IVZI8gQPAGwAAAAAAAABGra6mTac07kF1us/rol1MoUbT01nqaaSs0nMblBI6J
GUjrVAEjSTnv1NJGqoIyqs0tDTW25OL/ANV/lgV3s9G5Rq9Va3JtcDnrug69XBBi/jTV/Is20Rx8
fgetraVrn1PV/Jxqq6abkV1ajrZw5meoWvNeiqk6buNTN/G63dcnqtxfGq1Ser7jycFZvNm8ILXK
v/Op4t/PpsdfH4U/G3EOr19DaSd15JSro31M18jra29WBtOtV/HfTddmS3krConMbnG0ty3qy0SC
M+ayaUHByd/ItTnAHNVbZuyhoVWX0DYA0nCf9DK10Rqz0VZlIoyAAAAAAAAAAMswzbMsDJbZIyv9
UBkbAbMAAQAUgAoIUAbT04mCp6pgIO9ErVxqpbt/Y5taprHU1WE1Oq3RBqqO1URUd27KI22NVQHS
lUbXsZpiDTTwBVZL8GZn/BYIBLN7LGDlZPdnYxZFHB9sGZ9jpapzaAqfsVPqSrSeuC2tOmwGuSX6
4YTMlQBmlpV7MiyitywMX2MM3fY5xIBaVl74IW2eoQGqrNk446kbbcvJq7X6qHG6MEAAFAAAAAAA
AEZlmzLAwx/qw0Fv6AZC3KRAQpAwAAAFIUAENioDpRTXuaS1M101O3HDIOnjaUSpjVHR0iOr1aOd
VJ6fEoanG0gTx1j6nX+PQrrMRE7wE9gM8SWobagSUcGiNHa1Tm0BwujlZHpsjjZAciwGXYAjSU4M
pG1oojUCv46KNdzJQBm5lwq92bsp1mEc2nZxVSQZSbcbm9Kra04fRhLildPXp3MttuWBAAUAAAAA
AAAAAAIygDDRFk00Z3AyyLJqy1ZncCAAAAABSFAGqmdzdUBtHbxytOpyS1O1FIHalGsnVCkJJMNa
9iDdbRPfJuqULSW3r2OSLLWAN66y8OJIR2+KrGDWmqS+MZAhiyN6JJ2yyusrp3A4NHG6PQ0pifqY
vWqmSjystatqdi2aiI1MrIGpj9WEQqAoiTX8dob6Z6lf/wA7Q38epBi9ZaqlHruc5VVD/aZNXu4S
TemsnJgG5cvcAFAAAAAAAAAAAAAAAAEI0aIBmy1MbnRoy0BghprUjAgAAFIUAsnSqOaOtQN1yenx
V3PPRHrooQGjdW3o8GEdEgK6x3JBpOBo9W9SDEEZojKHN6TrBvmtXrL2OTBB0uqvjD0gzeii0qEs
MbGbIDj5fHEbSlL9TLpVcpUJYt1L5Ecocw9AOllRcX2Uo3yUvWU8LocWlV5kOzYHS3leqronk5Nh
sy2BGyAFAAAAAAAAAAAAAAAAAAAAAAMtGgBzaI0dGjLQHOCQbgjQGSlggFqdUc6rU6VA7eJSz0HL
wrSTsgNVR0WhmqNMCAAAm16EdtIgEZBXxjTJmFGdehJI2Ub+MZ1LbjGjOXIvIDPksoiDz2bb1Ot2
cbMBIkzIAskIAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgoAy0Ro2SAMQSDpBIAiRupINVyB6KaJI6Ve
pwVjdbAehWLyOPMcwOslk5cyfyAdWzLZz5kdwNOxnkYdjLsBt2HM5OxOQG7WObYbIAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKiADUmuRzKBvmXmcxqB05k5mNQBvkTkZIBpskkAFkgAAAA
AAAAAAAAAAAAAAAAf//Z

--Boundary_(ID_cy/47zCTynQE0ELcJvlGIw)--


--===============0431608524==
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
--===============0431608524==--



From sipping-bounces@ietf.org  Wed Dec  8 07: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 HAA17916
	for <sipping-web-archive@ietf.org>; Wed, 8 Dec 2004 07:27:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc11D-0003im-31
	for sipping-web-archive@ietf.org; Wed, 08 Dec 2004 07:34:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc0q1-0004Ru-N4; Wed, 08 Dec 2004 07:22:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc0pQ-0004Gv-9L
	for sipping@megatron.ietf.org; Wed, 08 Dec 2004 07:21: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 HAA17649
	for <sipping@ietf.org>; Wed, 8 Dec 2004 07:21:55 -0500 (EST)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc0wB-0003cF-04
	for sipping@ietf.org; Wed, 08 Dec 2004 07:28:56 -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 <0I8E00K89KTYFR@vmail.vsnl.com> for
	sipping@ietf.org; Wed, 08 Dec 2004 17:47:59 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.169.3)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Wed,
	08 Dec 2004 17:47:59 +0530 (IST)
Date: Wed, 08 Dec 2004 17:48:21 +0530
From: Rajesh <rajeshkalagarla@tataelxsi.co.in>
To: sipping@ietf.org
Message-id: <000001c4dd20$02774780$3b46010a@telxsi.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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.2 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Subject: [Sipping] Call down speeding 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="===============0927216995=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f

This is a multi-part message in MIME format.

--===============0927216995==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_ZeNpoM0J5Oe5GJVce7MD1w)"

This is a multi-part message in MIME format.

--Boundary_(ID_ZeNpoM0J5Oe5GJVce7MD1w)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE


Hi All,



 Can anybody help me in handling the down speeding with a codec?

 When we are offering/Accepting a call we have to mention the bandwid=
th
param as part of embedded sdp (it is mostly CT =96 conference total =
=96 is it
the total i/c and o/g channel bandwidth of that particular call?).

if a specific o/g channel has to be down speeded, we have to change t=
he
attributes of that codec in the re-invite? Or we have to change the C=
T in
the re-invite?



Thanks & regards,
Rajesh.Kalagarla


--Boundary_(ID_ZeNpoM0J5Oe5GJVce7MD1w)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE

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


<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><FONT face=3DAria=
l size=3D2>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Time=
s New Roman">Hi=20
All,</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT=20
face=3D"Times New Roman">&nbsp;<?xml:namespace prefix =3D o ns =3D=
=20
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT=20
face=3D"Times New Roman"><SPAN style=3D"mso-spacerun: yes">&nbsp;</SP=
AN>Can anybody=20
help me in handling the down speeding with a codec? </FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT=20
face=3D"Times New Roman"><SPAN style=3D"mso-spacerun: yes">&nbsp;</SP=
AN>When we are=20
offering/Accepting a call we have to mention the bandwidth param as p=
art of=20
embedded sdp (it is mostly CT - conference total - is it the total i/=
c and o/g=20
channel bandwidth of that particular call?).</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Time=
s New Roman">if a=20
specific o/g channel has to be down speeded, we have to change the at=
tributes of=20
that codec in the re-invite? Or we have to change the CT in the=20
re-invite?</FONT></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></P><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast=
-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareas=
t-language: EN-US; mso-bidi-language: AR-SA">Thanks=20
&amp; regards,</SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D078261712-08122004><FONT face=3D"Times New Roman"=
=20
size=3D3>Rajesh.Kalagarla</FONT></SPAN></DIV>
<DIV><SPAN class=3D078261712-08122004><FONT face=3D"Times New Roman"=
=20
size=3D3></FONT></SPAN>&nbsp;</DIV></FONT></BODY></HTML>


--Boundary_(ID_ZeNpoM0J5Oe5GJVce7MD1w)--


--===============0927216995==
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
--===============0927216995==--



From sipping-bounces@ietf.org  Wed Dec  8 08:01: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 IAA19948
	for <sipping-web-archive@ietf.org>; Wed, 8 Dec 2004 08:01:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc1YG-0004Uf-Qh
	for sipping-web-archive@ietf.org; Wed, 08 Dec 2004 08:08:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc1O7-0001x9-NV; Wed, 08 Dec 2004 07:57:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc1K4-0001RE-Mc
	for sipping@megatron.ietf.org; Wed, 08 Dec 2004 07:53: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 HAA19368
	for <sipping@ietf.org>; Wed, 8 Dec 2004 07:53:34 -0500 (EST)
Received: from fep4.012.net.il ([212.117.129.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc1Qo-0004Cn-Jj
	for sipping@ietf.org; Wed, 08 Dec 2004 08:00:36 -0500
Received: from isrexch01.israel.polycom.com ([212.199.61.2])
	by fep4.012.net.il with ESMTP
	id <20041208125256.LMXC11445.fep4@isrexch01.israel.polycom.com>;
	Wed, 8 Dec 2004 14:52:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Call down speeding in sip
Date: Wed, 8 Dec 2004 14:52:55 +0200
Message-ID: <144ED8561CE90C41A3E5908EDECE315C821D50@IsrExch01.israel.polycom.com>
Thread-Topic: [Sipping] Call down speeding in sip
Thread-Index: AcTdI54QI6NtgYQhQIiKS5kDwBpjXQAAROzQ
From: "Even, Roni" <roni.even@polycom.co.il>
To: "Rajesh" <rajeshkalagarla@tataelxsi.co.in>, <sipping@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
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="===============1399217400=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.2 (+++)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b

This is a multi-part message in MIME format.

--===============1399217400==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4DD24.DC9A073F"

This is a multi-part message in MIME format.

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

Hi,

Look at using RFC3890 TIAS for codec speed.

Roni Even

=20

________________________________

From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Rajesh
Sent: Wednesday, December 08, 2004 2:18 PM
To: sipping@ietf.org
Subject: [Sipping] Call down speeding in sip

=20

=20

Hi All,

=20

 Can anybody help me in handling the down speeding with a codec?=20

 When we are offering/Accepting a call we have to mention the bandwidth
param as part of embedded sdp (it is mostly CT - conference total - is
it the total i/c and o/g channel bandwidth of that particular call?).

if a specific o/g channel has to be down speeded, we have to change the
attributes of that codec in the re-invite? Or we have to change the CT
in the re-invite?

=20

Thanks & regards,=20

Rajesh.Kalagarla

=20


------_=_NextPart_001_01C4DD24.DC9A073F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
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)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Look at using RFC3890 TIAS for =
codec
speed.<o:p></o:p></span></font></p>

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

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

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Rajesh<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, December =
08, 2004
2:18 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] Call =
down
speeding in sip</span></font><o:p></o:p></p>

</div>

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

<div>

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

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi All,<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;Can anybody help me in handling the down speeding with a =
codec? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;When we are offering/Accepting a call we have to mention =
the bandwidth
param as part of embedded sdp (it is mostly CT - conference total - is =
it the
total i/c and o/g channel bandwidth of that particular =
call?).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>if a specific o/g channel has to be down speeded, we have to =
change the
attributes of that codec in the re-invite? Or we have to change the CT =
in the
re-invite?<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thanks &amp; regards,</span></font><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></fo=
nt></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Rajesh.Kalagarla</span></font><font size=3D2 face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

<div>

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C4DD24.DC9A073F--


--===============1399217400==
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
--===============1399217400==--



From sipping-bounces@ietf.org  Wed Dec  8 12:24: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 MAA16003
	for <sipping-web-archive@ietf.org>; Wed, 8 Dec 2004 12:24:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc5f9-0002j0-0n
	for sipping-web-archive@ietf.org; Wed, 08 Dec 2004 12:32:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc5My-0006Fa-Ol; Wed, 08 Dec 2004 12:12:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc58A-0002Rt-Se
	for sipping@megatron.ietf.org; Wed, 08 Dec 2004 11:57: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 LAA14002
	for <sipping@ietf.org>; Wed, 8 Dec 2004 11:57:32 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc5Ey-00027T-O0
	for sipping@ietf.org; Wed, 08 Dec 2004 12:04:37 -0500
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 08 Dec 2004 18:04:33 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB8GuwGb018073; 
	Wed, 8 Dec 2004 17:56:59 +0100 (MET)
Received: from [10.0.1.3] (sjc-vpn1-851.cisco.com [10.21.99.83])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUO89953;
	Wed, 8 Dec 2004 08:56:56 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Wed, 08 Dec 2004 08:57:01 -0800
Subject: Re: [Sipping] Conference speaker control
From: Cullen Jennings <fluffy@cisco.com>
To: Orit Levin <oritl@microsoft.com>, Roni Even <roni.even@polycom.co.il>
Message-ID: <BDDC725D.1D83B%fluffy@cisco.com>
In-Reply-To: <DD07841287D0AD428833021705E0D14E03DC7D69@RED-MSG-52.redmond.corp.microsoft.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
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: a492040269d440726bfd84680622cee7
Content-Transfer-Encoding: 7bit


Sending the speaker updates (which are very frequent) in SIP would be a ton
of notifies - much more than any page mode IM system would end up doing
which we felt was a bad use of SIP as a transport. Using the conference
package, without some form of compression, would result in very large
notifies. The latency would be crap compared to the in media approach where
it is exactly synchronized with the media.

If you want some way other than an in media approach to get get this
information, seems like something along the lines of BFCP would work out
much better. 


On 12/7/04 8:55 AM, "Orit Levin" <oritl@microsoft.com> wrote:

> Roni,
> My concern was about conferences with no floor control and no video.
> 
> Orit.
> 
>> -----Original Message-----
>> From: Even, Roni [mailto:roni.even@polycom.co.il]
>> Sent: Tuesday, December 07, 2004 5:19 AM
>> To: Orit Levin; David R Oran
>> Cc: Magnus Westerlund; sipping
>> Subject: RE: [Sipping] Conference speaker control
>> 
>> Orit,
>> I am not sure I understand your concern. Is it the number of
>> notifications on change of speakers by the event package that bother
>> you.
>> For this case it is typically handled by having a minimum time that a
>> user must "speak" before he is announced as the current speaker. This
>> has to do with not having to do very fast video switch for voice
>> activated video switch scenarios
>> Roni
>> 
>> -----Original Message-----
>> From: Orit Levin [mailto:oritl@microsoft.com]
>> Sent: Monday, December 06, 2004 7:46 PM
>> To: David R Oran; Even, Roni
>> Cc: Magnus Westerlund; sipping
>> Subject: RE: [Sipping] Conference speaker control
>> 
>> I believe that the "architecturally right" way of providing the
> "current
>> speaker identification" is by including enough information in the
>> media/data streams and letting the endpoints to make the correlation.
>> Hence the Conference Event package uses a generalized "src-id"
>> placeholder to hold RTP's ssrc and others to come. Hence the push to
>> have a meaningful and easy to use source identification in MSRP.
>> 
>> Unfortunately, today RTP MCUs don't implement the RTP mixer
>> functionality and don't necessarily include the ssrc information of
> the
>> mixed sources. Also, in PSTN - there is no way to have this
> information
>> (as Roni points out).
>> 
>> Technically, it is really easy to add the "current speaker"
>> identification to the Conference Event package itself. The problem is
>> how feasible this solution would be for free-going conferences with
> the
>> "current speaker" being changed all the time. My feeling is that going
>> forward in XCON it is worthwhile to add the information to the package
>> but use it by the focus for strictly controlled conferences only.
>> 
>> Orit.
>> 
>>> -----Original Message-----
>>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
>> Behalf
>>> Of David R Oran
>>> Sent: Saturday, December 04, 2004 2:15 PM
>>> To: Even, Roni
>>> Cc: Magnus Westerlund; sipping
>>> Subject: Re: [Sipping] Conference speaker control
>>> 
>>> 
>>> On Dec 4, 2004, at 9:04 AM, Even, Roni wrote:
>>> 
>>>> Magnus,
>>>> The whole discussion is about the SIP conference package that
>> suggests
>>>> that a SIP user will know the source of the stream based on SSRC.
> So
>> if
>>>> there are media sessions that are not RTP is a SIP call then SSRC
>> does
>>>> not work.
>>>> Roni
>>>> 
>>> While this is strictly true, that's not the point. The point is
>> whether
>>> the conferencing work ought to rely on a "correlator" in or
> associated
>>> with the media stream, and have arrivals on the media stream trigger
>>> any UI behavior, in order to identify the
>>> source(s)/speakers/arm-wavers/typers/gas-emitters.
>>> 
>>> I believe it should. In the case of RTP, this is the SSRC or the
> CNAME
>>> or both.
>>> 
>>> If the conferencing system wishes to accommodate a media session
>>> without this identification capability there has to be some way to
> do
>>> the correlation. I'm suggesting that emulating the media session by
>>> actually always having one to the UA is a good way to do this rather
>>> than sending speaker identification messages in realtime over the
>>> conferencing control protocols.
>>> 
>>> What do others think? This is important enough that other folks
> ought
>>> to weigh in here.
>>> 
>>> Dave.
>>> 
>>>> -----Original Message-----
>>>> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]
> On
>>>> Behalf Of Magnus Westerlund
>>>> Sent: Friday, December 03, 2004 11:11 AM
>>>> To: Even, Roni
>>>> Cc: sipping; David R Oran
>>>> Subject: Re: [Sipping] Conference speaker control
>>>> 
>>>> Even, Roni wrote:
>>>>> Hi,
>>>>> This is from the comedia draft, is it RTP, it does not say so.
>>>>> 
>>>>>            m=image 54111 TCP t38
>>>>>            c=IN IP4 192.0.2.2
>>>>>            a=setup:passive
>>>>>            a=connection:new
>>>>> 
>>>>> Roni
>>>> 
>>>> No, that is clearly T38 over TCP which has a mode that is not RTP,
>>>> however if you look in the RTP over TCP draft:
>>>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-framing-
>>>> contrans-
>>>> 03.txt
>>>> 
>>>> You can find the following SDP:
>>>> v=0
>>>> o=first 2520644554 2838152170 IN IP4 first.example.net
>>>> s=Example
>>>> t=0 0
>>>> c=IN IP4 192.0.2.105
>>>> m=audio 9 TCP/RTP/AVP 11
>>>> a=setup:active
>>>> a=connid:1
>>>> 
>>>> It is also this draft that register the RTP over TCP SDP protocol
>>>> identifier.
>>>> 
>>>> 
>>>> 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
>>>> 
>>>> _______________________________________________
>>>> Sipping mailing list
> https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the 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
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Dec  8 17:17: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 RAA14044
	for <sipping-web-archive@ietf.org>; Wed, 8 Dec 2004 17:17:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcAEi-0002aC-7u
	for sipping-web-archive@ietf.org; Wed, 08 Dec 2004 17:24:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9j4-0006yA-93; Wed, 08 Dec 2004 16:51:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc9Ej-0008ES-PL; Wed, 08 Dec 2004 16:20:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04419;
	Wed, 8 Dec 2004 16:20:35 -0500 (EST)
Message-Id: <200412082120.QAA04419@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Dec 2004 16:20:35 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-conference-package-08.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: 6e922792024732fb1bb6f346e63517e4

--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-08.txt
	Pages		: 43
	Date		: 2004-12-8
	
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-08.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-08.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-08.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-12-8164826.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-conference-package-08.txt

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

Content-Type: text/plain
Content-ID: <2004-12-8164826.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  Thu Dec  9 16:41: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 QAA12996
	for <sipping-web-archive@ietf.org>; Thu, 9 Dec 2004 16:41:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcW9j-0001X0-Qu
	for sipping-web-archive@ietf.org; Thu, 09 Dec 2004 16: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 1CcVMF-0005A6-KI; Thu, 09 Dec 2004 15:57:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcVA0-000794-8b; Thu, 09 Dec 2004 15:45:12 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02550;
	Thu, 9 Dec 2004 15:45:10 -0500 (EST)
Message-Id: <200412092045.PAA02550@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 09 Dec 2004 15:45:10 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-e2m-sec-reqs-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: 1a1bf7677bfe77d8af1ebe0e91045c5b

--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		: Requirements for End-to-middle Security for the Session Initiation Protocol (SIP)
	Author(s)	: K. Ono, S. Tachimoto
	Filename	: draft-ietf-sipping-e2m-sec-reqs-05.txt
	Pages		: 14
	Date		: 2004-12-9
	
A SIP User Agent (UA) does not always trust all intermediaries in its
   request path to inspect its message bodies and/or headers contained
   in its message. The UA might want to protect the message bodies and/
   or headers from intermediaries except those that provide services
   based on its content.  This situation requires a mechanism called
   'end-to-middle security' to secure information passed between the UA
   and intermediaries, which does not interfere with end-to-end
   security. This document defines a set of requirements for a mechanism
   to achieve end-to-middle security.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-reqs-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-e2m-sec-reqs-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-e2m-sec-reqs-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-12-9155940.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-e2m-sec-reqs-05.txt

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

Content-Type: text/plain
Content-ID: <2004-12-9155940.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  Sat Dec 11 06:50: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 GAA15865
	for <sipping-web-archive@ietf.org>; Sat, 11 Dec 2004 06:50:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cd5tI-0000cB-5R
	for sipping-web-archive@ietf.org; Sat, 11 Dec 2004 06:58:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cd5i1-0007AJ-FR; Sat, 11 Dec 2004 06:46:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cd5gp-0006pS-Bs
	for sipping@megatron.ietf.org; Sat, 11 Dec 2004 06:45: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 GAA15498
	for <sipping@ietf.org>; Sat, 11 Dec 2004 06:45:28 -0500 (EST)
Received: from harjus.tutpro.com ([192.98.100.3] ident=Debian-exim)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cd5oD-0000X0-Ao
	for sipping@ietf.org; Sat, 11 Dec 2004 06:53:09 -0500
Received: from jh by harjus.tutpro.com with local (Exim 4.34)
	id 1Cd5gl-0000fx-LQ
	for sipping@ietf.org; Sat, 11 Dec 2004 13:45:27 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16826.56791.642388.604389@harjus.tutpro.com>
Date: Sat, 11 Dec 2004 13:45:27 +0200
To: sipping@ietf.org
X-Mailer: VM 7.19 under Emacs 21.3.1
From: Juha Heinanen <jh@tutpro.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Subject: [Sipping] caller's language preference
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


is there a way for the caller to tell, which language it prefers the
callee to use when it answers the call?  for example, the callee can be
an announcement or ivr server.

i checked draft-ietf-sip-callerprefs and it seems to use contact
parameters/accept-contact header for similar, but not quite the same
purpose.

in the application i described in above, there is only one contact
registered and the proxy plays no role in the game.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 11 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 OAA13606
	for <sipping-web-archive@ietf.org>; Sat, 11 Dec 2004 14:43:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdDGs-0000mF-Cm
	for sipping-web-archive@ietf.org; Sat, 11 Dec 2004 14:51:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdD5W-0000fl-Fg; Sat, 11 Dec 2004 14:39:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdCvc-00075d-FR
	for sipping@megatron.ietf.org; Sat, 11 Dec 2004 14:29: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 OAA12371
	for <sipping@ietf.org>; Sat, 11 Dec 2004 14:29: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 1CdD34-0000R6-Jd
	for sipping@ietf.org; Sat, 11 Dec 2004 14:36:59 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 11 Dec 2004 11:33:55 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBBJSbm6020092;
	Sat, 11 Dec 2004 11:28:41 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn1-439.cisco.com [10.21.97.183])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUR49252;
	Sat, 11 Dec 2004 11:28:36 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Sat, 11 Dec 2004 11:25:16 -0800
Subject: Re: [Sipping] PUBLISH in SIP Performance Report Event
From: Cullen Jennings <fluffy@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>,
        Paul H Kyzivat <pkyzivat@cisco.com>, sipping <sipping@ietf.org>
Message-ID: <BDE0899C.1F290%fluffy@cisco.com>
In-Reply-To: <419D3B52.6060701@softarmor.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: Adam Roach <adam@nostrum.com>, Aki Niemi <aki.niemi@nokia.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: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit


Just hypothetically if we did have a response code that say's don't send me
that publish ... I'm not sure it would work out all that well

Let say A send publish to B and B sends back a error saying "I will not eat
it Sam I am". What is A supposed to do. Cache this forever on it's
infinitely long Turing tape? Seriously, I doubt anyone will do anything with
this error except just discard it. How could B say, you know I just upgraded
my software and now I really would like to get those publishes that I used
to refuse?


On 11/18/04 4:16 PM, "Dean Willis" <dean.willis@softarmor.com> wrote:

> 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


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 11 16:06: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 QAA20634
	for <sipping-web-archive@ietf.org>; Sat, 11 Dec 2004 16:06:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdEZX-0002ht-NO
	for sipping-web-archive@ietf.org; Sat, 11 Dec 2004 16:14:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdEQP-0002Sa-Lw; Sat, 11 Dec 2004 16:05:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdEL2-00081Z-BW
	for sipping@megatron.ietf.org; Sat, 11 Dec 2004 15: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 PAA19919
	for <sipping@ietf.org>; Sat, 11 Dec 2004 15:59:33 -0500 (EST)
Received: from av2-2-sn3.vrr.skanova.net ([81.228.9.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdESU-0002SH-ST
	for sipping@ietf.org; Sat, 11 Dec 2004 16:07:19 -0500
Received: by av2-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 9A81138262; Sat, 11 Dec 2004 21:59:02 +0100 (CET)
Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net
	[81.228.9.177]) by av2-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 8A26F37E7F; Sat, 11 Dec 2004 21:59:02 +0100 (CET)
Received: from vit (h79n2fls31o265.telia.com [217.208.189.79])
	by smtp1-1-sn3.vrr.skanova.net (Postfix) with SMTP id 5D32638012;
	Sat, 11 Dec 2004 21:59:02 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: <sipping@ietf.org>, "Juha Heinanen" <jh@tutpro.com>
Subject: RE: [Sipping] caller's language preference
Date: Sat, 11 Dec 2004 21:59:00 +0100
Message-ID: <GHEPIJKACEKDGLKODIGJKEAMDLAA.gunnar.hellstrom@omnitor.se>
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.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <16826.56791.642388.604389@harjus.tutpro.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: Toip list <toip@snowshore.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: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit

Juha,
We are just discussing very similar topics in the toip (text over IP ) list, where I
entered this comment:
-----------------------------------------
Yes, Language can be used in the Accept header for acceptance or refusal of invites with
specific languages. ( though, it seems that that is the language of the information about
the session, but I am not sure on that conclusion. )

More advanced, we can use the language and media feature tags in the preferences and
capabilities negotiation framework. I think that for many of the service invocation
requirements expressed in RFC 3351, we can describe how they can be achieved by applying
the existing framework of preferences and capability negotiation.

There is a whole structure of preference and capability negotiation mechanisms available,
and we need to  recommend a subset of them for invocation of services of interest for
accessibility purposes.

It seems that the following rfc:s are central to the mechanisms: 3841 3840 2703 2538 2533
2506. And of course SIP rfc 3261 itself.
-------------------------------------
It is draft-ietf-sipping-toip-00 and its refinement that we are discussing. Part of the
problem we are working on is to discover when users have disparate language or media
preferences or capabilities and then invoke translation services.

This is not an answer on your question. But it is an indication that it is important that
similar usage habits are developed for the quite rich set of already standardised
mechanisms.

Part of the scope for sipping-toip is to find when there is a need for conversion between
speech and real time text or sign language, but for all the three media of audio, text and
video, the language tag is a valid extra piece of information that influences the service
invocation.

Can we start structuring the problem and give good valid examples and recommendations for
what mechanism to use for the different cases?

1. Where does a caller express preferences and capabilities for language and media?

2. Where does a callee express preferences and capabilities for language and media?

3. How is the level of acceptance for deviations from the preferences expressed?
( E.g. "I prefer to communicate in French, but can accept English for short and simple
calls." )

4. Where does a service express offered capabilities for language and media?

5. How can rules for call setup be implemented to be based on matching preferences and
capabilities?

6. How can routing and service invocation be included in the model.

7. How does preferences and capabilities expressed at registration interrelate with
similar functions in Invite?

8. In what groups and documents do we establish such harmonised usage habits for the
mechanisms?

9. Will the concept of routing and service invocation based on matching preferences and
capabilities be managable by human users? Will they understand and remember to influence
the settings so that the intended convenience is achieved? Or will it have the opposite
effect: "Oh, complicated service, why is an expensive Japanese interpreter included in the
call when we manage our conversation in Spanish very well both of us? Ah, I forgot to
reset the phone after getting it back yesterday."



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


>-----Original Message-----
>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
>Behalf Of Juha Heinanen
>Sent: Saturday, December 11, 2004 12:45 PM
>To: sipping@ietf.org
>Subject: [Sipping] caller's language preference
>
>
>
>is there a way for the caller to tell, which language it prefers the
>callee to use when it answers the call?  for example, the callee can be
>an announcement or ivr server.
>
>i checked draft-ietf-sip-callerprefs and it seems to use contact
>parameters/accept-contact header for similar, but not quite the same
>purpose.
>
>in the application i described in above, there is only one contact
>registered and the proxy plays no role in the game.
>
>-- juha
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 Dec 12 19:38: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 TAA17325
	for <sipping-web-archive@ietf.org>; Sun, 12 Dec 2004 19:38:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdeMJ-0004Pb-NH
	for sipping-web-archive@ietf.org; Sun, 12 Dec 2004 19: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 1CdeBL-0002za-5i; Sun, 12 Dec 2004 19:35:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdeAF-0002mS-Sb
	for sipping@megatron.ietf.org; Sun, 12 Dec 2004 19:34: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 TAA17098
	for <sipping@ietf.org>; Sun, 12 Dec 2004 19:34:08 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdeHw-0004J7-N1
	for sipping@ietf.org; Sun, 12 Dec 2004 19:42:10 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-4.cisco.com with ESMTP; 12 Dec 2004 16:34:08 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBD0Xb5M001598;
	Sun, 12 Dec 2004 16:33:37 -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 QAA00553;
	Sun, 12 Dec 2004 16:33:36 -0800 (PST)
Message-Id: <4.3.2.7.2.20041212183240.0398bcd8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 12 Dec 2004 18:33:48 -0600
To: Juha Heinanen <jh@tutpro.com>, sipping@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping] caller's language preference
In-Reply-To: <16826.56791.642388.604389@harjus.tutpro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.1 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

Juha

What about the "Accept-Language" header (section 20.3 of 3261)?

At 01:45 PM 12/11/2004 +0200, Juha Heinanen wrote:

>is there a way for the caller to tell, which language it prefers the
>callee to use when it answers the call?  for example, the callee can be
>an announcement or ivr server.
>
>i checked draft-ietf-sip-callerprefs and it seems to use contact
>parameters/accept-contact header for similar, but not quite the same
>purpose.
>
>in the application i described in above, there is only one contact
>registered and the proxy plays no role in the game.
>
>-- juha
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


cheers,
James

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

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


From sipping-bounces@ietf.org  Mon Dec 13 02:29: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 CAA05247
	for <sipping-web-archive@ietf.org>; Mon, 13 Dec 2004 02:29:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdklf-0005NY-TR
	for sipping-web-archive@ietf.org; Mon, 13 Dec 2004 02:37:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdkU8-0000gr-Kw; Mon, 13 Dec 2004 02:19:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdkSr-000842-9P
	for sipping@megatron.ietf.org; Mon, 13 Dec 2004 02:17: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 CAA03631
	for <sipping@ietf.org>; Mon, 13 Dec 2004 02:17:48 -0500 (EST)
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdkac-00057p-D1
	for sipping@ietf.org; Mon, 13 Dec 2004 02:25:50 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBD7HVj19758; Mon, 13 Dec 2004 09:17:31 +0200 (EET)
X-Scanned: Mon, 13 Dec 2004 09:13:34 +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 iBD7DYKb031127;
	Mon, 13 Dec 2004 09:13:34 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00O3Xysc; Mon, 13 Dec 2004 09:13:32 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
	iBD7DCa18919; Mon, 13 Dec 2004 09:13:12 +0200 (EET)
Received: from [172.21.35.181] ([172.21.35.181]) by esebh003.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 13 Dec 2004 09:13:08 +0200
Message-ID: <41BD4105.2010002@nokia.com>
Date: Mon, 13 Dec 2004 09:13:09 +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: Sharon Fridman <Sharon.Fridman@followap.com>
References: <8993B20049600A40B0AEAFD6F736C9DF263AA9@MHAIFA.followap.com>
In-Reply-To: <8993B20049600A40B0AEAFD6F736C9DF263AA9@MHAIFA.followap.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2004 07:13:08.0556 (UTC)
	FILETIME=[32AC30C0:01C4E0E3]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: Hisham.Khartabil@telio.no, Markus.Isomaki@nokia.com, sipping@ietf.org,
        Gonzalo.Camarillo@ericsson.com, Aki.Niemi@nokia.com
Subject: [Sipping] Re: draft-ietf-sipping-multiple-refer-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: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

Definitely. Thanks for the hint.

- Miguel

Sharon Fridman wrote:

> Hi Guys,
> 
>  
> 
> Small nit in above draft - Figure 4 method should be BYE rather than REFER.
> 
>  
> 
> Thanks,
> 
> --Fridy / Followap
> 

-- 
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 Dec 13 03:01: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 DAA07469
	for <sipping-web-archive@ietf.org>; Mon, 13 Dec 2004 03:01:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdlHM-00066i-S0
	for sipping-web-archive@ietf.org; Mon, 13 Dec 2004 03:10:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdkzE-0003ZO-P7; Mon, 13 Dec 2004 02:51:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cdkuo-0002Fh-9j
	for sipping@megatron.ietf.org; Mon, 13 Dec 2004 02:46: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 CAA06400
	for <sipping@ietf.org>; Mon, 13 Dec 2004 02:46:41 -0500 (EST)
Received: from harjus.tutpro.com ([192.98.100.3] ident=Debian-exim)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdl2Z-0005kK-Rx
	for sipping@ietf.org; Mon, 13 Dec 2004 02:54:44 -0500
Received: from jh by harjus.tutpro.com with local (Exim 4.34)
	id 1Cdkuk-0000V1-Jy; Mon, 13 Dec 2004 09:46:38 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16829.18654.549045.823292@harjus.tutpro.com>
Date: Mon, 13 Dec 2004 09:46:38 +0200
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping] caller's language preference
In-Reply-To: <4.3.2.7.2.20041212183240.0398bcd8@localhost>
References: <16826.56791.642388.604389@harjus.tutpro.com>
	<4.3.2.7.2.20041212183240.0398bcd8@localhost>
X-Mailer: VM 7.19 under Emacs 21.3.1
From: Juha Heinanen <jh@tutpro.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
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: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

James M. Polk writes:

 > What about the "Accept-Language" header (section 20.3 of 3261)?

i guess that it is closest to what i want, but currently the text only
covers the language used in signaling.

-- juha

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 13 08:07: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 IAA04049
	for <sipping-web-archive@ietf.org>; Mon, 13 Dec 2004 08:07:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdq3U-0004vp-Ax
	for sipping-web-archive@ietf.org; Mon, 13 Dec 2004 08:16:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdpjg-0005nN-LF; Mon, 13 Dec 2004 07:55:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdpdN-0004Xc-HS
	for sipping@megatron.ietf.org; Mon, 13 Dec 2004 07:49: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 HAA01257
	for <sipping@ietf.org>; Mon, 13 Dec 2004 07:49:00 -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 1CdplB-0004Go-Ca
	for sipping@ietf.org; Mon, 13 Dec 2004 07:57:06 -0500
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72)
	id <YZYC9AT1>; Mon, 13 Dec 2004 12:48:20 -0000
Message-ID: <53F74F5A7B94D511841C00B0D0AB16F803E5334C@baker.datcon.co.uk>
From: "Paul D.Smith" <Paul.D.Smith@dataconnection.com>
To: "'Robert Sparks'" <rjsparks@nostrum.com>,
        "'Rohan Mahy'" <rohan@ekabal.com>
Subject: RE: [Sip] FW: [Sipping] I-D ACTION:draft-ietf-sipping-dialog-pack
	age-05.txt
Date: Mon, 13 Dec 2004 12:48:12 -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: f5932bfc8385127f631fc458a872feb1
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: abda3837e791065a13ac6f11cf8e625a

Robert, Rohan,

Having given this some more thought, I think I understand where you are
coming from, although I believe we are at risk of creating more problems
for SIP interoperability and, more importantly, the stability of calls
established with SIP devices.

RFC3261, section 12.2.1 states the following.

   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.

This is a reasonable statement.  In this case a 481 means "there is no
dialog" and clearly we expect this to be a permanent state.  Whether we
class the dialog as terminated before, or after, the BYE is a minor issue.

However, RFCs 3262 and 3265 have changed the use of 481 status codes.
RFC3262 states:

   If a PRACK request is received by the UA core that does not match any
   unacknowledged reliable provisional response, the UAS MUST respond to
   the PRACK with a 481 response.

RFC3265 states:

                              Designers of such mechanisms are also
   warned to make a distinction between sending a NOTIFY message to a
   subscriber who is aware of the subscription, and sending a NOTIFY
   message to an unsuspecting node.  The latter behavior is invalid, and
   MUST receive a "481 Subscription does not exist" response (unless
   some other 400- or 500-class error code is more applicable), as
   described in section 3.2.4.                                   

In both of these, the 481 is _NOT_ indicating that the dialog is flawed,
rather it is a transaction or subscription specific error.

Now consider my user, busily talking on their SIP phone.  The arrival of
an errant PRACK or NOTIFY probably has no affect on their call.  And if
it does, then they are in a position to determine this and terminated the
dialog.  But the combination of RFC3261, and your assertion that 481 must
mean "dialog is terminated" results in their call being dropped, despite
there really being no reason why it should.

I hope this has got across my concerns regarding "481 means terminated
dialog".  I appreciate that at least some of this might be tidied up in
later versions of specifications, but SIP hardware is already using the
current specifications, and will not adopt new behaviour for some time.
Until that time, having all 481 responses cause dialogs to end will
contribute to poor perception of SIP hardware as dialogs fail
unnecessarily.

Regards,
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: Robert Sparks [mailto:rjsparks@nostrum.com]
Sent: 07 December 2004 19:32
To: SIP Public Folder (E-mail)
Subject: Re: [Sip] FW: [Sipping] I-D
ACTION:draft-ietf-sipping-dialog-package-05.txt


Then we should file a bug against that text in 3261.

I dug though this pretty hard when putting together the dialogusage  
draft.
I'll go through again and find the other parts of the text that support  
the
dialog being gone with the response (though it may be later in the  
week).

While I can see some potential issues with 408, 481 is really  
cut-and-dried.
A BYE will not gain you anything but another failed transaction.

RjS

On Dec 7, 2004, at 1:05 PM, Hisham Khartabil wrote:

>
> On Dec 7, 2004, at 5:21 PM, Robert Sparks wrote:
>
>> Paul -
>>
>> The text you quote from 3261 looks pretty specific to me
>> and agrees with what Rohan writes.
>
> Its look pretty specific to me also, but to what Paul Smith said.
>
> "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."
>
> This clearly says what Paul is stating.
>
> Hisham
>
>>
>> There's more - please look at
>> draft-sparks-sipping-dialogusage-00 for a some discussion
>> of what 408 and 481 do to usages.
>>
>> RjS
>>
>> On Dec 7, 2004, at 6:52 AM, Paul D.Smith wrote:
>>
>>> Apologies - this e-mail should have gone to the SIPPING WG!
>>>
>>> Paul DS.
>>>
>>> -----Original Message-----
>>> From: Paul D.Smith
>>> Sent: 07 December 2004 12:52
>>> To: SIP Public Folder (E-mail)
>>> Subject: RE: [Sipping] I-D
>>> ACTION:draft-ietf-sipping-dialog-package-05.txt
>>>
>>>
>>> Rohan,
>>>
>>> As per my earlier post to the group, I have to disagree with your
>>> assertion that a 408 or 481 failure of _any_ mid-dialog request
>>> terminates the dialog (section 3.7.1 of this draft).
>>>
>>>   "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)."
>>>
>>> RFC3261 is quite clear in distinguishing between BYE requests and  
>>> other
>>> requests.  The failure of a non-BYE request does not cause a dialog  
>>> to
>>> terminate although it should be taken as a prompt to the UA to end  
>>> the
>>> dialog
>>> by sending a BYE.  To put it another way, non-BYE requests are not  
>>> dialog
>>> terminating, regardless of the status code of any resulting response.
>>>
>>> If you believe this is not the case, can you please explain the  
>>> meaning of
>>> the following sections of RFC3261.
>>>
>>> 12.3 Termination of a Dialog
>>>
>>>    Independent of the method, if a request outside of a dialog  
>>> generates
>>>    a non-2xx final response, any early dialogs created through
>>>    provisional responses to that request are terminated.  The  
>>> mechanism
>>>    for terminating confirmed dialogs is method specific.  In this
>>>    specification, the BYE method terminates a session and the dialog
>>>    associated with it.  See Section 15 for details.
>>>
>>> 12.2.1.2 Processing the Responses
>>>
>>>    ...
>>>
>>>    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.
>>>
>>> I believe this is a serious issue because it potentially means that  
>>> there
>>> would be two concepts of the state of a dialog, one RFC3261  
>>> compliant and
>>> a second, compliant to this draft.  I therefore believe this should  
>>> be
>>> resolved quickly and look forward to readong your response.
>>>
>>> Regards,
>>> 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: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>>> Sent: 23 November 2004 21:11
>>> To: SIP Public Folder (E-mail)
>>> Subject: [Sipping] I-D  
>>> ACTION:draft-ietf-sipping-dialog-package-05.txt
>>>
>>>
>>> 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.
>>>
>>>
>>> Date: December 7, 2004 6:52:48 AM CST
>>> To: Subject:
>>>
>>>
>>>
>>> <ATT79302.txt>
>>>
>>>
>>> <ATT79303.txt>_______________________________________________
>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of 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 Dec 14 04:28: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 EAA06407
	for <sipping-web-archive@ietf.org>; Tue, 14 Dec 2004 04:28:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ce96c-0002Xx-Eg
	for sipping-web-archive@ietf.org; Tue, 14 Dec 2004 04:36:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ce8pc-000846-16; Tue, 14 Dec 2004 04:18:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CakUa-0005ld-E5
	for sipping@megatron.ietf.org; Sat, 04 Dec 2004 19:43: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 TAA05479
	for <sipping@ietf.org>; Sat, 4 Dec 2004 19:43:08 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.198])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CakaZ-0004B4-Vq
	for sipping@ietf.org; Sat, 04 Dec 2004 19:49:27 -0500
Received: by rproxy.gmail.com with SMTP id q1so64968rnf
	for <sipping@ietf.org>; Sat, 04 Dec 2004 16:43:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=jZZTxe3LyKGK0dHPV+bSTJUK9+uX5GKwBmWnaxEuMLxUA/x23la4yNA0MEZDTRT+RCNVeuxs3jmPw4+iHK/slbDEnscTqU9wstdzvpSzijuSzEmCQ9lxr4D4CbFH/fbqQoCQmG9wjpL+2nupogmS+oIe0YHwuilubtDDddom84I=
Received: by 10.38.181.62 with SMTP id d62mr444903rnf;
	Sat, 04 Dec 2004 16:43:06 -0800 (PST)
Received: by 10.38.209.70 with HTTP; Sat, 4 Dec 2004 16:43:06 -0800 (PST)
Message-ID: <8b27699304120416432bdec05f@mail.gmail.com>
Date: Sat, 4 Dec 2004 19:43:06 -0500
From: "David A. Bryan" <davidbryan@gmail.com>
To: sipping@ietf.org, sip-implementors@cs.columbia.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 14 Dec 2004 04:18:54 -0500
Subject: [Sipping] P2P SIP
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bryan@ethernot.org
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

Hello Henning,

I have been working on a P2P SIP project as well. You may have seen
some the early internal William & Mary documents and talks from Nov.
2003 and onward on the web (I've been using the name SOSIMPLE). It
looks like your approach is extremely similar -- derived from a DHT
such as Chord.

Additionally, several of us (myself, Cullen Jennings, Adam Roach and a
few others) also discussed this topic quite a bit at IETF in
Washington and have had ongoing discussions about it. We are currently
fleshing out the details. I've started working on an experimental
draft on the subject, and have submitted to a few academic conferences
for publication.

I'd love for you, Kindan Singh, and anyone else who is interested to
work together on this.

--David Bryan

> From: Henning Schulzrinne <hgs@cs.columbia.edu>
> To: sip-implementors@cs.columbia.edu, sipping <sipping@ietf.org>
> Date: Sat, 04 Dec 2004 13:44:11 -0500
> Subject: [Sipping] Technical reports on Skype protocol analysis and SIP in 
> peer-to-peer mode
> We have written two technical reports that might be of interest to
> members of the list. Both can be found at
> http://www1.cs.columbia.edu/~library/2004.html
> 
>    Peer-to-Peer Internet Telephony using SIP
>    Kundan Singh and Henning Schulzrinne
> 
> describes how SIP, with trivial modifications, can operate as a fully
> peer-to-peer protocol, i.e., without per-domain servers. We describe a
> hybrid scenario where parts are in p2p mode, while others follow the
> more "traditional" proxy mode.
> 
>    An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol
>    Salman A. Baset and Henning Schulzrinne
>
> attempts to analyze how Skype works, constrained by the encryption of
> the protocol exchanges.
> 
> We would appreciate comments on these documents.
> 
> Henning

-- 
David Bryan
bryan@ethernot.org
bryan@cs.wm.edu
http://www.cs.wm.edu/~bryan

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 14 14:28: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 OAA07928
	for <sipping-web-archive@ietf.org>; Tue, 14 Dec 2004 14:28:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeIU0-0003IN-2f
	for sipping-web-archive@ietf.org; Tue, 14 Dec 2004 14: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 1CeIHS-0008NK-82; Tue, 14 Dec 2004 14:24:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeI6p-0006O8-Cq
	for sipping@megatron.ietf.org; Tue, 14 Dec 2004 14:13: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 OAA05897
	for <sipping@ietf.org>; Tue, 14 Dec 2004 14:13:18 -0500 (EST)
Received: from figas.ekabal.com ([204.61.215.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeIEs-0002nB-F2
	for sipping@ietf.org; Tue, 14 Dec 2004 14:21:40 -0500
Received: from [172.16.16.141] ([66.236.111.254]) (authenticated)
	by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id iBEJCFX01048;
	Tue, 14 Dec 2004 11:12:20 -0800
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <012C2808-4E04-11D9-8CEB-000D93C60450@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Date: Tue, 14 Dec 2004 11:11:49 -0800
To: sipping@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>,
        Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] WGLC for configuration 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

Hi,

I'd like to start a Working Group Last Call for:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-config- 
framework-05.txt

This WGLC will end on January 10, 2005.

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  Wed Dec 15 09:53: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 JAA05079
	for <sipping-web-archive@ietf.org>; Wed, 15 Dec 2004 09:53:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeafD-0007bx-FT
	for sipping-web-archive@ietf.org; Wed, 15 Dec 2004 10:02:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeaHo-0007MW-TR; Wed, 15 Dec 2004 09:37:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cea8f-0005G8-0H
	for sipping@megatron.ietf.org; Wed, 15 Dec 2004 09:28: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 JAA03484
	for <sipping@ietf.org>; Wed, 15 Dec 2004 09:28:22 -0500 (EST)
Received: from smtp7.clb.oleane.net ([213.56.31.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeaGt-0006wx-RV
	for sipping@ietf.org; Wed, 15 Dec 2004 09:36:56 -0500
Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be
	forged)) by smtp7.clb.oleane.net with ESMTP id iBFERe3L017135
	for <sipping@ietf.org>; Wed, 15 Dec 2004 15:27:52 +0100
Message-Id: <200412151427.iBFERe3L017135@smtp7.clb.oleane.net>
From: "Gunter" <g.palmer@dial.oleane.com>
To: <sipping@ietf.org>
Date: Wed, 15 Dec 2004 15:27:51 +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: AcTiskHKHZSGabAWSoGzFTaGvTLXug==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Subject: [Sipping] WiMAX Summit'05 - Paris - France
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="===============0658356777=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221

This is a multi-part message in MIME format.

--===============0658356777==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_03EE_01C4E2BA.A3E254D0"

This is a multi-part message in MIME format.

------=_NextPart_000_03EE_01C4E2BA.A3E254D0
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 to be organised in Paris next 5-8 April 2005.

 

Get all details at:

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

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<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";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* 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><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><strong><b><font size=3D1 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Arial'>&#8226; =
</span></font></b></strong><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.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 WiMAX Summit to be organised in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>
next 5-8 April 2005.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Get all details =
at:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.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><span
title=3D"http://www.upperside.fr/wimax05/wimax2005intro.htm">http://www.u=
pperside.fr/wimax05/wimax2005intro.htm</span></span></a></span></font><fo=
nt
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.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>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_03EE_01C4E2BA.A3E254D0--



--===============0658356777==
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
--===============0658356777==--




From sipping-bounces@ietf.org  Wed Dec 15 16:46: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 QAA19699
	for <sipping-web-archive@ietf.org>; Wed, 15 Dec 2004 16:46:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ceh78-0004PR-EG
	for sipping-web-archive@ietf.org; Wed, 15 Dec 2004 16:55:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cegpi-0006oD-My; Wed, 15 Dec 2004 16:37:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CegNK-0005Yo-6W
	for sipping@megatron.ietf.org; Wed, 15 Dec 2004 16:07: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 QAA11200
	for <sipping@ietf.org>; Wed, 15 Dec 2004 16:07:55 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CegVa-0001ni-58
	for sipping@ietf.org; Wed, 15 Dec 2004 16:16:32 -0500
Received: from [192.168.0.108] (adsl-209-30-33-13.dsl.rcsntx.swbell.net
	[209.30.33.13]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBFL2nom076164
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 15 Dec 2004 15:02:51 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41C0A678.5080208@nostrum.com>
Date: Wed, 15 Dec 2004 15:02:48 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@brooktrout.com>
Subject: Re: [Sipping] comments on throttle-01
References: <EDD694D47377D7119C8400D0B77FD331A338A3@nhmail2.eng.brooktrout.com>
In-Reply-To: <EDD694D47377D7119C8400D0B77FD331A338A3@nhmail2.eng.brooktrout.com>
X-Enigmail-Version: 0.89.5.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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: SIPPING WG <sipping@ietf.org>, Aki Niemi <aki.niemi@nokia.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: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

Eric Burger wrote:

>...I still don't get the value of a (future) RFC on the topic.  Why
>not just refer people to a Buffer Theory textbook and be done with it?
>There is no protocol stuff going on in here, really.
>  
>

I would argue that the protocol element to this -- and it is an 
important one -- is the ability for a subscriber to request throttling. 
The draft also needs to precisely describe what these throttle requests 
mean, which is where a bulk of the current text comes from -- but there 
is a distinct protocol element to it.

During the creation of the document that is now RFC3265, there was a 
distinct belief that, in certain circumstances, the subscriber should 
have the ability to request throttling of notification (see section 
4.4.3, for example). Back in Vienna, by accepting the throttling 
requirements, the working group made a decision to define a 
cross-package throttling mechanism.

I think Aki's draft is a really good basis for moving this work forward. 
Given the text in the current document, I have a clear picture of how I 
would sit down and implement a server that supports this extension.

As to the open issue, I think this draft should leave out suggestions of 
recommended throttle intervals, as they will vary not just from package 
to package, but from application to application.

As this document necessarily extends RFC3265, I would personally like to 
see this work handed off to the SIP working group for completion there.

/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  Wed Dec 15 16:48: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 QAA19924
	for <sipping-web-archive@ietf.org>; Wed, 15 Dec 2004 16:48:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ceh9C-0004UJ-D8
	for sipping-web-archive@ietf.org; Wed, 15 Dec 2004 16:57:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CegqJ-0007US-RO; Wed, 15 Dec 2004 16:37:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CegY2-0003Rk-G8
	for sipping@megatron.ietf.org; Wed, 15 Dec 2004 16:19:06 -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 QAA13337
	for <sipping@ietf.org>; Wed, 15 Dec 2004 16:18:59 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeggJ-0002Qn-5Z
	for sipping@ietf.org; Wed, 15 Dec 2004 16:27:36 -0500
Received: from [192.168.0.108] (adsl-209-30-33-13.dsl.rcsntx.swbell.net
	[209.30.33.13]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBFLItVO077928
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 15 Dec 2004 15:18:57 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41C0AA3E.1060707@nostrum.com>
Date: Wed, 15 Dec 2004 15:18:54 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] Comments on event-throttle 01
References: <BD3283C1.C8D2%fluffy@cisco.com>
In-Reply-To: <BD3283C1.C8D2%fluffy@cisco.com>
X-Enigmail-Version: 0.89.5.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: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, "aki.niemi@nokia.com" <aki.niemi@nokia.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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

Cullen Jennings wrote:

>Not clear if the goal of this is to limit the number of  messages or limit
>the bandwidth of messages. The merging of partial states to a full state may
>make the problem worse not better.
>  
>

I'm not sure I understand this argument. It may be that we've read 
section 3.1.4 differently than each other -- but, as far as I can tell, 
the intention isn't to merge several partial states into a full state as 
much as it is to merge several partial states into a single partial state.

Concretely: consider the SIP overhead of sending a NOTIFY and getting a 
200 response to it to be X bytes.

Now, consider that Client A has subscribed to Client C, with a throttle. 
Client B has also subscribed, but without a throttle.

Now, client C publishes three notifications, of sizes N, M, and P, 
respectively.

Client B gets these in separate messages, for a total of 3X + N + M + P 
bytes.

Client A gets these in a single message, for a total of X + N + M + P bytes.

The total savings is 2X bytes.

That's the worst case scenario, in which all three notifications that C 
sends are for different parts of the state. In the case that any of 
these publications refer to the same part of the state, savings are even 
more substantial.

Or maybe I'm missing the scenario that you're talking about. Can you 
outline a concrete example (similar to what I've done above) that shows 
that the number of bytes can actually *increase* when using the throttle 
mechanism? (Of course, I'm ignoring the "Supported" header and other 
protocol additions used to actually effect the throttles as being 
insignificant; certainly, these aren't the increases you are worried 
about, right?)

/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  Tue Dec 21 02:29: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 CAA11190
	for <sipping-web-archive@ietf.org>; Tue, 21 Dec 2004 02:29:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgec7-0003aw-Tt
	for sipping-web-archive@ietf.org; Tue, 21 Dec 2004 02:39:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgeN8-0004X3-MA; Tue, 21 Dec 2004 02:23:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgeL3-0003Ql-OA
	for sipping@megatron.ietf.org; Tue, 21 Dec 2004 02:21: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 CAA10162
	for <sipping@ietf.org>; Tue, 21 Dec 2004 02:21:43 -0500 (EST)
Received: from vmail.vsnl.com ([203.199.113.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgeUI-0003Nk-Pn
	for sipping@ietf.org; Tue, 21 Dec 2004 02:31:29 -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 <0I9200I9C9R11T@vmail.vsnl.com> for
	sipping@ietf.org; Tue, 21 Dec 2004 12:51:01 +0530 (IST)
Received: from ([tataelxsi.co.in (203.197.169.3)])
	by vmail.vsnl.com	(InterScan E-Mail VirusWall Unix); Tue,
	21 Dec 2004 12:51:01 +0530 (IST)
Date: Tue, 21 Dec 2004 12:51:23 +0530
From: Rajesh <rajeshkalagarla@tataelxsi.co.in>
To: sipping@ietf.org
Message-id: <008f01c4e72d$af316110$3b46010a@telxsi.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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.8 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: sreeram.kanumuri@wipro.com
Subject: [Sipping] Codec specific attributes in SDP
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="===============1739179203=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

This is a multi-part message in MIME format.

--===============1739179203==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_qDBdcQVEPk/y5xJ/rBP/LQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_qDBdcQVEPk/y5xJ/rBP/LQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi All,

 As per RFC 2327 we can represent attributes for the total m line scope
(direction parameter).if my system is having Different Tx Video codec list
and different Rx video codec list - how can I represent all of them as part
of an SDP? can we keep two m lines with one m line representing SENDONLY and
another m line with RECVONLY? -- my mixed protocol video conferencing server
is having this issue (in Server Active state Tx Video and Rx Video may not
be equal all the time becoz of DSP computation limitations).

thanks & regards,
Rajesh

--Boundary_(ID_qDBdcQVEPk/y5xJ/rBP/LQ)
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 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>Hi 
All,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=580221007-21122004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>&nbsp;As per RFC 
2327 we can represent attributes for the total m line scope (direction 
parameter).if my system is having Different Tx Video codec list and different Rx 
video codec list - how can I represent all of them as part of an SDP? can we 
keep two m lines with one m line representing SENDONLY and another m line 
with&nbsp;RECVONLY? -- my mixed protocol video conferencing server is having 
this issue (in Server Active state Tx Video and Rx Video may not be equal all 
the time becoz of DSP computation limitations).</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=580221007-21122004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>thanks &amp; 
regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=580221007-21122004>Rajesh</SPAN></FONT></DIV></BODY></HTML>

--Boundary_(ID_qDBdcQVEPk/y5xJ/rBP/LQ)--


--===============1739179203==
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
--===============1739179203==--



From sipping-bounces@ietf.org  Tue Dec 21 03:30: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 DAA15348
	for <sipping-web-archive@ietf.org>; Tue, 21 Dec 2004 03:30:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgfZU-00058O-8c
	for sipping-web-archive@ietf.org; Tue, 21 Dec 2004 03:40:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgfOF-0001IQ-2q; Tue, 21 Dec 2004 03:29:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgfLw-0000TZ-8R
	for sipping@megatron.ietf.org; Tue, 21 Dec 2004 03:26: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 DAA15064
	for <sipping@ietf.org>; Tue, 21 Dec 2004 03:26:42 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgfVK-00052r-Q6
	for sipping@ietf.org; Tue, 21 Dec 2004 03:36:29 -0500
Received: from ci0026exch001u.wins.lucent.com (h135-252-18-18.lucent.com
	[135.252.18.18])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBL8QJeb027867
	for <sipping@ietf.org>; Tue, 21 Dec 2004 02:26:26 -0600 (CST)
Received: by ci0026exch001u.bj.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X7BGYLT0>; Tue, 21 Dec 2004 16:26:18 +0800
Message-ID: <31C0F08B0D18D511ACC800508BAE7B4709A1D0D9@ci0026exch001u.bj.lucent.com>
From: "Zhu, Hong Ru (Judy)" <hongruzhu@lucent.com>
To: "'Rajesh'" <rajeshkalagarla@tataelxsi.co.in>, sipping@ietf.org
Subject: RE: [Sipping] Codec specific attributes in SDP
Date: Tue, 21 Dec 2004 16:26:11 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: sreeram.kanumuri@wipro.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>
Content-Type: multipart/mixed; boundary="===============2137016429=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e

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.

--===============2137016429==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4E736.B9EC0700"

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_01C4E736.B9EC0700
Content-Type: text/plain;
	charset="iso-8859-1"

Sorry for the bother. 
But who can do me a favor to tell me how many codecs in SIP and IMS now? 
 
Thanks so much
 
Judy

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On Behalf Of
Rajesh
Sent: 2004?12?21? 15:21
To: sipping@ietf.org
Cc: sreeram.kanumuri@wipro.com
Subject: [Sipping] Codec specific attributes in SDP


Hi All,
 
 As per RFC 2327 we can represent attributes for the total m line scope
(direction parameter).if my system is having Different Tx Video codec list
and different Rx video codec list - how can I represent all of them as part
of an SDP? can we keep two m lines with one m line representing SENDONLY and
another m line with RECVONLY? -- my mixed protocol video conferencing server
is having this issue (in Server Active state Tx Video and Rx Video may not
be equal all the time becoz of DSP computation limitations).
 
thanks & regards,
Rajesh


------_=_NextPart_001_01C4E736.B9EC0700
Content-Type: text/html;
	charset="iso-8859-1"

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


<META content="MSHTML 6.00.2800.1480" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff size=2>Sorry for 
the bother. </FONT></SPAN></DIV>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff size=2>But who 
can do me a favor to tell me how many codecs in SIP and IMS now? 
</FONT></SPAN></DIV>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff size=2>Thanks so 
much</FONT></SPAN></DIV>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=556392508-21122004><FONT face=&#23435;&#20307; color=#0000ff 
size=2>Judy</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> sipping-bounces@ietf.org 
  [mailto:sipping-bounces@ietf.org]<B>On Behalf Of </B>Rajesh<BR><B>Sent:</B> 
  2004&#24180;12&#26376;21&#26085; 15:21<BR><B>To:</B> sipping@ietf.org<BR><B>Cc:</B> 
  sreeram.kanumuri@wipro.com<BR><B>Subject:</B> [Sipping] Codec specific 
  attributes in SDP<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>Hi 
  All,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=580221007-21122004></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>&nbsp;As per RFC 
  2327 we can represent attributes for the total m line scope (direction 
  parameter).if my system is having Different Tx Video codec list and different 
  Rx video codec list - how can I represent all of them as part of an SDP? can 
  we keep two m lines with one m line representing SENDONLY and another m line 
  with&nbsp;RECVONLY? -- my mixed protocol video conferencing server is having 
  this issue (in Server Active state Tx Video and Rx Video may not be equal all 
  the time becoz of DSP computation limitations).</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=580221007-21122004></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN class=580221007-21122004>thanks &amp; 
  regards,</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=580221007-21122004>Rajesh</SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4E736.B9EC0700--


--===============2137016429==
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
--===============2137016429==--



From sipping-bounces@ietf.org  Tue Dec 21 13:38: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 NAA06965
	for <sipping-web-archive@ietf.org>; Tue, 21 Dec 2004 13:38:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgp3X-0003Wb-Eo
	for sipping-web-archive@ietf.org; Tue, 21 Dec 2004 13:48:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgosJ-0006Ly-VS; Tue, 21 Dec 2004 13:36:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgomZ-0004yP-QD
	for sipping@megatron.ietf.org; Tue, 21 Dec 2004 13:30: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 NAA06403
	for <sipping@ietf.org>; Tue, 21 Dec 2004 13:30:48 -0500 (EST)
Received: from mx02.net.com ([134.56.3.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgow4-0003Hu-J4
	for sipping@ietf.org; Tue, 21 Dec 2004 13:40:42 -0500
Received: from mx02-int.net.com (mx02-int.net.com [134.56.112.14])
	by mx02.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id
	iBLIYUTM017940; Tue, 21 Dec 2004 10:34:31 -0800 (PST)
Received: from fmt-ex01.net.com ([134.56.112.251])
	by mx02-int.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id
	iBLIWfGP025192; Tue, 21 Dec 2004 10:34:18 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sipping] Codec specific attributes in SDP
Date: Tue, 21 Dec 2004 10:29:51 -0800
Message-ID: <985D4DC322E5ED46A3E183D8227094FB03E9182E@fmt-ex01.net.com>
Thread-Topic: [Sipping] Codec specific attributes in SDP
Thread-Index: AcTnLwklruRYTAvQS5mWyXrcvKfI3QAW/Ssg
From: "Sreedhar Pampati" <Sreedhar_Pampati@net.com>
To: "Rajesh" <rajeshkalagarla@tataelxsi.co.in>, <sipping@ietf.org>
X-Spam-Status: No, hits=-0.7 required=8.0 tests=AWL,HTML_70_80,
	HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on fmt-spam02
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: sreeram.kanumuri@wipro.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>
Content-Type: multipart/mixed; boundary="===============1066847949=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7118f330e2af0a096ba071c5e99ca10e

This is a multi-part message in MIME format.

--===============1066847949==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4E78B.0F4BB981"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4E78B.0F4BB981
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Rajesh,
Refer to Section 10 in rfc3264 (An Offer/Answer Model with the Session
Description Protocol (SDP)). That should address your issues.
Cheers,
Sreedhar
=20
-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Rajesh
Sent: Monday, December 20, 2004 11:21 PM
To: sipping@ietf.org
Cc: sreeram.kanumuri@wipro.com
Subject: [Sipping] Codec specific attributes in SDP
=20
Hi All,
=20
 As per RFC 2327 we can represent attributes for the total m line scope
(direction parameter).if my system is having Different Tx Video codec
list and different Rx video codec list - how can I represent all of them
as part of an SDP? can we keep two m lines with one m line representing
SENDONLY and another m line with RECVONLY? -- my mixed protocol video
conferencing server is having this issue (in Server Active state Tx
Video and Rx Video may not be equal all the time becoz of DSP
computation limitations).
=20
thanks & regards,
Rajesh

------_=_NextPart_001_01C4E78B.0F4BB981
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<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=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C4E748.13D4A0E0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-alt:"\FF2D\FF33 \660E\671D";
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-1610612033 1757936891 16 0 131231 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-1610612033 1757936891 16 0 131231 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"MS Mincho";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

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


<p class=3DMsoNormal style=3D'text-indent:6.0pt'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Refer to
Section 10 in rfc3264 (An Offer/Answer Model with the Session =
Description
Protocol (SDP)). That should address your =
issues.<o:p></o:p></span></font></p>

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


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

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

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
sipping-bounces@ietf.org
[mailto:sipping-bounces@ietf.org] <b><span style=3D'font-weight:bold'>On =
Behalf
Of </span></b>Rajesh<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, December =
20, 2004
11:21 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> sipping@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
sreeram.kanumuri@wipro.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Sipping] Codec =
specific
attributes in SDP</span></font></p>

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

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;As per RFC 2327 we =
can
represent attributes for the total m line scope (direction parameter).if =
my
system is having Different Tx Video codec list and different Rx video =
codec
list - how can I represent all of them as part of an SDP? can we keep =
two m
lines with one m line representing SENDONLY and another m line
with&nbsp;RECVONLY? -- my mixed protocol video conferencing server is =
having
this issue (in Server Active state Tx Video and Rx Video may not be =
equal all
the time becoz of DSP computation =
limitations).</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>thanks &amp; =
regards,</span></font><o:p></o:p></p>

</div>

<div>

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

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C4E78B.0F4BB981--


--===============1066847949==
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
--===============1066847949==--



From sipping-bounces@ietf.org  Tue Dec 21 19:30:47 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 TAA25958
	for <sipping-web-archive@ietf.org>; Tue, 21 Dec 2004 19:27:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CguKA-0007Yf-5G
	for sipping-web-archive@ietf.org; Tue, 21 Dec 2004 19:25:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgtkL-0003wX-Q6; Tue, 21 Dec 2004 18:48:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgtc1-0008VC-Ni; Tue, 21 Dec 2004 18:40: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 SAA20893;
	Tue, 21 Dec 2004 18:37:57 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgtW3-00023k-3t; Tue, 21 Dec 2004 18:34:09 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iBLNLpQ23050;
	Tue, 21 Dec 2004 15:21:52 -0800 (PST)
Message-Id: <200412212321.iBLNLpQ23050@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 21 Dec 2004 15:21:51 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: sipping@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sipping] RFC 3960 on Early Media and Ringing Tone Generation in
	the Session Initiation Protocol (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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3960

        Title:      Early Media and Ringing Tone Generation
                    in the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, H. Schulzrinne
        Status:     Informational
        Date:       December 2004
        Mailbox:    Gonzalo.Camarillo@ericsson.com,
                    schulzrinne@cs.columbia.edu
        Pages:      13
        Characters: 31692
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-media-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3960.txt


This document describes how to manage early media in the Session
Initiation Protocol (SIP) using two models: the gateway model and the
application server model.  It also describes the inputs one needs to
consider in defining local policies for ringing tone generation.

This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <041221152032.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3960

--OtherAccess
Content-Type: Message/External-body; name="rfc3960.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041221152032.RFC@RFC-EDITOR.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 Dec 21 19:30: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 TAA25892
	for <sipping-web-archive@ietf.org>; Tue, 21 Dec 2004 19:27:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CguKS-0007aO-EJ
	for sipping-web-archive@ietf.org; Tue, 21 Dec 2004 19:26:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgtkM-0003wd-Ri; Tue, 21 Dec 2004 18:48:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgtc5-0008VC-Iy; Tue, 21 Dec 2004 18:40: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 SAA21026;
	Tue, 21 Dec 2004 18:38:08 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgtUX-0001xG-V6; Tue, 21 Dec 2004 18:32:35 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iBLNKIQ22468;
	Tue, 21 Dec 2004 15:20:18 -0800 (PST)
Message-Id: <200412212320.iBLNKIQ22468@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 21 Dec 2004 15:20:18 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: sipping@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sipping] RFC 3959 on The Early Session Disposition Type for the
	Session Initiation Protocol (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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3959

        Title:      The Early Session Disposition Type for
                    the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    Gonzalo.Camarillo@ericsson.com
        Pages:      11
        Characters: 22160
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-disposition-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3959.txt


This document defines a new disposition type (early-session) for the
Content-Disposition header field in the Session Initiation Protocol
(SIP).  The treatment of "early-session" bodies is similar to the
treatment of "session" bodies.  That is, they follow the offer/answer
model.  Their only difference is that session descriptions whose
disposition type is "early-session" are used to establish early media
sessions within early dialogs, as opposed to regular sessions within
regular dialogs.

This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <041221151847.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3959

--OtherAccess
Content-Type: Message/External-body; name="rfc3959.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <041221151847.RFC@RFC-EDITOR.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  Wed Dec 22 01:22: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 BAA24161
	for <sipping-web-archive@ietf.org>; Wed, 22 Dec 2004 01:22:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch03J-0002wb-Qf
	for sipping-web-archive@ietf.org; Wed, 22 Dec 2004 01:32:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgzfu-0001cB-Ig; Wed, 22 Dec 2004 01:08:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgzb2-00005b-CK
	for sipping@megatron.ietf.org; Wed, 22 Dec 2004 01:03: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 BAA23084
	for <sipping@ietf.org>; Wed, 22 Dec 2004 01:03:38 -0500 (EST)
Received: from web14307.mail.yahoo.com ([216.136.173.83])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cgzkd-0002VM-4U
	for sipping@ietf.org; Wed, 22 Dec 2004 01:13:36 -0500
Received: (qmail 4118 invoked by uid 60001); 22 Dec 2004 06:03:36 -0000
Message-ID: <20041222060336.4116.qmail@web14307.mail.yahoo.com>
Received: from [61.183.207.54] by web14307.mail.yahoo.com via HTTP;
	Wed, 22 Dec 2004 14:03:36 CST
Date: Wed, 22 Dec 2004 14:03:36 +0800 (CST)
From: lan tian <tianlanforever@yahoo.com.cn>
To: Gonzalo.Camarillo@ericsson.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id BAA23084
Subject: [Sipping] About draft-ietf-mmusic-confarch
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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable

Hi,Mr. Gonzalo.Camarillo,

These days i'm reading your book "SIP Demystified",
In Chapter 3.1, you cite a chart about Internet
Multimedia Conferencing Architecture from
"draft-ieft-mmusic-confarch".=20
I'm interested in this chart, so I came to search the
draft in www.ietf.org, but I can find nothing. After I
searched in the google, I know this draft have been
expired for 3 years.
I just want to know if this chart can be cite again,
is it right yet?=20

Anyone can tell me if there are some updated draft
about Multimedia Conferencing Architecture?

Regards
Roger Cheng.




_________________________________________________________
Do You Yahoo!?
=D7=A2=B2=E1=CA=C0=BD=E7=D2=BB=C1=F7=C6=B7=D6=CA=B5=C4=D1=C5=BB=A2=C3=E2=B7=
=D1=B5=E7=D3=CA
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.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  Wed Dec 22 19:30: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 TAA20477
	for <sipping-web-archive@ietf.org>; Wed, 22 Dec 2004 19:30:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChH2E-000090-2Q
	for sipping-web-archive@ietf.org; Wed, 22 Dec 2004 19:40:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChGqI-0001Bl-CV; Wed, 22 Dec 2004 19:28:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChGkV-0000Vi-9c
	for sipping@megatron.ietf.org; Wed, 22 Dec 2004 19:22: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 TAA20172
	for <sipping@ietf.org>; Wed, 22 Dec 2004 19:22:31 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChGuG-0008QB-V9
	for sipping@ietf.org; Wed, 22 Dec 2004 19:32:41 -0500
Received: from [64.101.149.107] ([64.101.149.107]) (authenticated bits=0)
	by nylon.softarmor.com (8.12.11/8.12.11) with ESMTP id iBN0KeZF007387
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Wed, 22 Dec 2004 18:20:41 -0600
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <54E787AA-5478-11D9-B3A8-000D93594350@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Date: Wed, 22 Dec 2004 18:19:38 -0600
To: sipping@ietf.org, Andrew Allen <aallen@RIM.COM>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>,
        Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
        Ileana Leuca <Ileana.Leuca@cingular.com>
Subject: [Sipping] Discussion of the Allen PoC P-headers 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: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit


Sometime soon, OMA is going to ask us to perform expert review and  
publish (as informational) a draft based on:

http://www.ietf.org/internet-drafts/draft-allen-sipping-poc-p-headers 
-00.txt


This draft defines two P-headers (limited function headers with strong  
caveats) used by OMA in their push-to-talk specification, PoC  
(push-to-talk over cellular).

Please review this draft, and if you have guidance, get it to Andrew  
ASAP, as I believe he's working on a revision with more justification  
and other cleanups suggested by people who have responded privately.

A few comments on the draft here:


1) The P-Alerting-Mode header field is used in INVITE and seems to  
indicate a preference, on the part of the caller or his supporting  
applications, that the called party provide either automatic or manual  
answer modes as indicated by the header field's value.

Why is a "caller preferences" approach not usable here?

2) The P-Answer-State header field is used in 1xx or in a 200OK to  
indicate that a B2BUA generated the response on behalf of a UAS that it  
expects (but cannot be certain) will eventually answer, and that the  
media stream may be buffered "in network" pending a final answer. If  
the answer contains SDP, then the generating node is accepting the  
responsibility of buffering the transmitted media until the final  
answer is received, and will deal with the cleanup should the expected  
final answer not arrive.

I alternate between thinking this is clever, and thinking it is evil.

In the case where the response-generating node is also assuming  
responsibility for the buffering, I can't see from this draft how the  
user experience is affected by the presence of the P-Answer-State  
header. They call, get connected, and start talking. MAYBE (if the  
final leg fails) they get some kind of failure notification, after  
they've been talking awhile. Perhaps the response is used to give a  
different confirmation tone to the user, alerting them to a  
higher-than-usual probability of post-answer failure? This usage needs  
to be explained in the draft. I also don't understand the use case here  
with a non-SDP 200OK, although it makes sense with a 183.

In the case where the response-generating node is NOT buffering and we  
insert no SDP, we appear to be using this header field to indicate that  
an upstream node should take responsibility for the buffering, and  
should consequently insert SDP into the response and act as a B2BUA for  
the call. It seems if this occurred, that the response sent back  
upstream from the now-buffering node would need to be a 200 OK, and not  
an intermediate 18x type message. But there's a problem -- since nobody  
with knowledge of the terminating client's capabilities inserted SDP,  
we can't use the "answer" model to determine the client's actual  
capabilities, so we could end up with an unresolvable codec mismatch.

Here's the scenario: UA-A places a PoC call through S-1 and S-2 to UA-B.

UA-A and S-1 only understand AMR, and UA-B only understands the EVRC  
encoding.

S-2 knows that UA-B supports auto-answer, is registered, is not busy,  
and is expected to be able to receive the call (we don't go into HOW it  
knows this). So S-2 returns a 183 with a P-Answer-State=unconfirmed and  
no media, and S-1 decides to buffer the call, returning a 200OK with  
media indicating that it is prepared to receive AMR. UA-A starts  
talking, and S-1 starts buffering. Eventually, UA-B answers, and sends  
a 200 OK containing EVRC SDP back to S-2 and thence to S-1. Rather than  
playing the buffered media on toward UA-B, S-1 is now stuck -- it has  
buffered AMR media, UA-B only understands EVRC, and S-1 doesn't know  
how to convert. This is precisely the reason we have end-to-end  
offer-answer.

Perhaps I read the draft wrong, but if so it could use some clarity on  
this matter, and if not, the mechanism for preventing this error  
condition needs to be better explained. I think that if the usage of  
the header in provisional versus final responses were more clearly  
specified, that this error condition would be either precluded (or  
discovered to be unavoidable, indicating a clear flaw in the design).


3)  The draft has normative text in 4.2.2.1 saying:

"A UAC that receives a 1XX or 2XX response without a P-Answer-State  
Header or containing a P-Answer-State header field containing the  
parameter "Confirmed" SHALL treat it as a "confirmed response"."

I don't believe that it is reasonable for a P-draft to make normative  
statements about how the absence of a a P-header impacts a UAC in  
general. In the general case, a 200 OK is a confirmed response. Perhaps  
something along the lines of:

"A UAC conformant to this specification that receives a response not  
containing a P-Answer-State header field proceeds as if that response  
contained a P-Answer-State header field with the value "confirmed"."



4) Somebody who understands early media much better than I do needs to  
review this draft carefully. Note that we have new RFCs on the topic,  
RFC 3959 and 3960.


--
Dean Willis


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 22 19:34: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 TAA20660
	for <sipping-web-archive@ietf.org>; Wed, 22 Dec 2004 19:34:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChH5Q-0000Du-V3
	for sipping-web-archive@ietf.org; Wed, 22 Dec 2004 19:44:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChGud-0002uN-Uy; Wed, 22 Dec 2004 19:33:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChGs3-0001q8-6q
	for sipping@megatron.ietf.org; Wed, 22 Dec 2004 19:30: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 TAA20452
	for <sipping@ietf.org>; Wed, 22 Dec 2004 19:30:19 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChH1p-00008m-9A
	for sipping@ietf.org; Wed, 22 Dec 2004 19:40:29 -0500
Received: from [64.101.149.107] ([64.101.149.107]) (authenticated bits=0)
	by nylon.softarmor.com (8.12.11/8.12.11) with ESMTP id iBN0VMoE007424
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <sipping@ietf.org>; Wed, 22 Dec 2004 18:31:24 -0600
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <D389FF22-5479-11D9-B3A8-000D93594350@softarmor.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: sipping@ietf.org
From: Dean Willis <dean.willis@softarmor.com>
Date: Wed, 22 Dec 2004 18:30:20 -0600
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Heads up on OMA PoC 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: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit


The draft:

http://www.ietf.org/internet-drafts/draft-garcia-sipping-poc-isb-am 
-01.txt


Defines an event package and data format that OMA is proposing to use  
for push-to-talk support in mobile environments.

Please give it a read, and consider it in relation to the Allen draft  
that I referred to earlier today.

I expect that we'll be asked to provide expert review of this draft, in  
conjunction with review of the to-be-revised Allen draft.

--
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  Thu Dec 23 22:17: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 WAA23072
	for <sipping-web-archive@ietf.org>; Thu, 23 Dec 2004 22:17:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Chg76-0008Qe-Jf
	for sipping-web-archive@ietf.org; Thu, 23 Dec 2004 22: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 1ChfnN-0004NB-Dq; Thu, 23 Dec 2004 22:07:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Chfk4-0003Pn-It
	for sipping@megatron.ietf.org; Thu, 23 Dec 2004 22:03: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 WAA22340
	for <sipping@ietf.org>; Thu, 23 Dec 2004 22:03:46 -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 1Chfu4-0008B4-Oj
	for sipping@ietf.org; Thu, 23 Dec 2004 22:14:09 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 23 Dec 2004 20:11:40 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBO339oB016523;
	Thu, 23 Dec 2004 19:03:11 -0800 (PST)
Received: from [192.168.1.102] (sjc-vpn1-331.cisco.com [10.21.97.75])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUZ78914;
	Thu, 23 Dec 2004 19:03:12 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Wed, 22 Dec 2004 07:51:47 -0800
Subject: Re: [Sipping] Comments on event-throttle 01
From: Cullen Jennings <fluffy@cisco.com>
To: Adam Roach <adam@nostrum.com>
Message-ID: <BDEED813.202A0%fluffy@cisco.com>
In-Reply-To: <41C0AA3E.1060707@nostrum.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, "aki.niemi@nokia.com" <aki.niemi@nokia.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: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit

On 12/15/04 1:18 PM, "Adam Roach" <adam@nostrum.com> wrote:

> Cullen Jennings wrote:
> 
>> Not clear if the goal of this is to limit the number of  messages or limit
>> the bandwidth of messages. The merging of partial states to a full state may
>> make the problem worse not better.
>>  
>> 
> 
> I'm not sure I understand this argument. It may be that we've read
> section 3.1.4 differently than each other -- but, as far as I can tell,
> the intention isn't to merge several partial states into a full state as
> much as it is to merge several partial states into a single partial state.
> 

I hadn't realized that was the idea - that sounds pretty hard to implement
in a way that does not use insane amounts of state. I thought the idea was
that if you exceeded the throttle, then you waited till the next window you
could send and sent the complete state.

The only description in in the draft seems to be the non normative

" Partial-state:  The states of buffered notifications are merged, and
      the resulting notification is sent out.  This policy applies to
      those event packages that carry partial-state notifications."

I think the draft should explain clearly what the Notified is supposed to do
with all the data. 

My question still stands, is the goal to reduce bandwidth or number of
packets?


> Concretely: consider the SIP overhead of sending a NOTIFY and getting a
> 200 response to it to be X bytes.
> 
> Now, consider that Client A has subscribed to Client C, with a throttle.
> Client B has also subscribed, but without a throttle.
> 
> Now, client C publishes three notifications, of sizes N, M, and P,
> respectively.
> 
> Client B gets these in separate messages, for a total of 3X + N + M + P
> bytes.
> 
> Client A gets these in a single message, for a total of X + N + M + P bytes.
> 
> The total savings is 2X bytes.
>

What would the saving have been if I was running these messages over a
compressed TLS connection?
 
> That's the worst case scenario, in which all three notifications that C
> sends are for different parts of the state. In the case that any of
> these publications refer to the same part of the state, savings are even
> more substantial.

Is this part of figuring out, on a per client basis, the continuous partial
merge, checking that it is a valid document, and sending it on at the
appropriate time that sounds pretty challenging. If the draft is going to to
go say that the notifier MUST implement this - I'm find with the whole
thing.

This would be good in that the client would also know they got the all the
information, just some of it was delayed.

> 
> Or maybe I'm missing the scenario that you're talking about. Can you
> outline a concrete example (similar to what I've done above) that shows
> that the number of bytes can actually *increase* when using the throttle
> mechanism? (Of course, I'm ignoring the "Supported" header and other
> protocol additions used to actually effect the throttles as being
> insignificant; certainly, these aren't the increases you are worried
> about, right?)
>

I was actually considering all the SIP headers close to irrelevant after
compression and that the real issue was in the bodies.
 
> /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


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 23 22:21:46 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 WAA23586
	for <sipping-web-archive@ietf.org>; Thu, 23 Dec 2004 22:21:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChgBU-00009O-6S
	for sipping-web-archive@ietf.org; Thu, 23 Dec 2004 22:32:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChfnR-0004Of-0E; Thu, 23 Dec 2004 22:07:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Chfk6-0003Pt-DD
	for sipping@megatron.ietf.org; Thu, 23 Dec 2004 22:03: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 WAA22351
	for <sipping@ietf.org>; Thu, 23 Dec 2004 22:03:47 -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 1Chfu6-0008B6-EA
	for sipping@ietf.org; Thu, 23 Dec 2004 22:14:10 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 23 Dec 2004 20:11:46 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBO33FHp021553
	for <sipping@ietf.org>; Thu, 23 Dec 2004 19:03:21 -0800 (PST)
Received: from [192.168.1.102] (sjc-vpn1-331.cisco.com [10.21.97.75])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUZ78921;
	Thu, 23 Dec 2004 19:03:14 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Wed, 22 Dec 2004 08:06:57 -0800
Subject: Re: [Sipping] WGLC for configuration package -  enrollment 
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDEEDBA1.202A6%fluffy@cisco.com>
In-Reply-To: <012C2808-4E04-11D9-8CEB-000D93C60450@ekabal.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit


One of the goals of this draft is to be able to plug in a new UA and have it
work. I assume that this means we will be transferring things like the
credentials to log on a proxy or turn server over this configuration data. I
think the security aspects of enrolment are not really covered in this. We
might want to have a look at:

draft-pritikin-ttimodel-01.txt
draft-tschofenig-enroll-next-steps-00.txt

I'm particularly interested in making sure there is a way where if the UA
had a deceive specific certificate that was bound to it's instance ID, then
there was a way for the device to use that to authenticate.



On 12/14/04 12:11 PM, "Rohan Mahy" <rohan@ekabal.com> wrote:

> Hi,
> 
> I'd like to start a Working Group Last Call for:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-
> framework-05.txt
> 
> This WGLC will end on January 10, 2005.
> 
> thanks,
> -rohan
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Thu Dec 23 22:24: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 WAA23968
	for <sipping-web-archive@ietf.org>; Thu, 23 Dec 2004 22:24:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChgDu-0000H1-GV
	for sipping-web-archive@ietf.org; Thu, 23 Dec 2004 22:34:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChfnT-0004P5-21; Thu, 23 Dec 2004 22:07:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Chfk9-0003Qo-Tn
	for sipping@megatron.ietf.org; Thu, 23 Dec 2004 22:03: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 WAA22367
	for <sipping@ietf.org>; Thu, 23 Dec 2004 22:03:51 -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 1Chfu6-0008B6-Vp
	for sipping@ietf.org; Thu, 23 Dec 2004 22:14:11 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 23 Dec 2004 20:12:05 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBO33dHn021719;
	Thu, 23 Dec 2004 19:03:40 -0800 (PST)
Received: from [192.168.1.102] (sjc-vpn1-331.cisco.com [10.21.97.75])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AUZ78953;
	Thu, 23 Dec 2004 19:03:38 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Thu, 23 Dec 2004 12:33:51 -0800
Subject: Re: [Sipping] WGLC for configuration package
From: Cullen Jennings <fluffy@cisco.com>
To: Rohan Mahy <rohan@ekabal.com>, sipping <sipping@ietf.org>
Message-ID: <BDF06BAF.202C6%fluffy@cisco.com>
In-Reply-To: <012C2808-4E04-11D9-8CEB-000D93C60450@ekabal.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit
Cc: "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.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: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: 7bit


In a word, I don't think this is ready for WGLC and has several open issues.

I think all this configuration stuff should go to IESG as a bundle and it it
should be WGLC together. It's hard to say the framework is going to need to
be changed as we actually work out the details of how it works.

I send some comments about this back in November and would have hope to see
those incorporated in a revision before this was WGLC - all theses comments
still apply.

My biggest concern is this draft seems to carefully gloss the issues that
the the device/user/applications/local profiles need to all be fetched and
need to be merged. This whole issues and how it works seems like it should
be one of they key parts of the framework.

My second largest concern is that concern is that this has no hope of making
devices and servers that could actually interoperate. The server could send
some URI, perhaps, an LDAP, the client does not have to implement any
particular schemes. I can't tell how the server can discover what the client
supports. I can't see how the client can report an error to the server. I
think we should make HTTP and HTTPS MUST implement and dump the rest.

My third concern is there are way to many options and it's just not clear
they are needed.

I don't understand what application profile is or why it is needed? Why is
Network-user not defined for applications? Why is it needed for others -
Could just the From be used?

Effective-By seems underspecified - does the UA send the OK to the notify
after the UA succeeds in making it effective?

Does the server store one copy of the data for each value of the app-id

I think specify no must implement transports (FTP, HTTP, HTTPS, LDAP, XCAP)
is an absolute disaster for any hope of building equipment that actually
interoperates. 

It says
   When the Event header "profile-type" is "device" and the user agent
   has provided the user's AOR in the "network-user" parameter, the
   profile delivery server MAY set or change the default user associated
   with the device indicated in the SUBSCRIBE URI.
I don't really know what this means. but continues
   This is an
   implementation or policy decision.  The profile delivery server
   SHOULD authenticate the user for the SUBSCIRBE request before
   effecting the default user indicated in the "network-user" parameter.
How does it do this? Again what for? can From be used?
This stuff may be all exactly right, I just don't understand how it works or
what the motivation for it is.

I had some vague recollection we decided to use something like more obtuse
than sipuaconfig.

There is a way to enroll - is there a way to unenroll? How does the
authentication work for enrollment?

Interaction with XCAP paths is pretty vague.

How can the NOTIFY pass credentials to use to fetch the profiles

I think the whole system would be better if we said that the instance id
MUST be a UUID. I know some people don't agree with this and am not
concerned if we don't change this but I have so far not heard a single
argument against why it does not meet every single need we have identified
with one simple mechanism instead of having all kinds of wacky different
things. 

There are many small detail issues but I think they are secondary to points
raised here. As I said in my previous email, I think this is getting close.

Don't get the idea I don't like this - I think that is is absolutely
essential and really good work - just needs a bit more.

Cullen



On 12/14/04 12:11 PM, "Rohan Mahy" <rohan@ekabal.com> wrote:

> Hi,
> 
> I'd like to start a Working Group Last Call for:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-config-
> framework-05.txt
> 
> This WGLC will end on January 10, 2005.
> 
> thanks,
> -rohan
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Fri Dec 24 08:53: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 IAA16210
	for <sipping-web-archive@ietf.org>; Fri, 24 Dec 2004 08:53:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Chq2Y-0003CL-7L
	for sipping-web-archive@ietf.org; Fri, 24 Dec 2004 09:03:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Chpqg-0007LH-7F; Fri, 24 Dec 2004 08:51:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Chpmf-0006dT-Ih
	for sipping@megatron.ietf.org; Fri, 24 Dec 2004 08:47: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 IAA15910
	for <sipping@ietf.org>; Fri, 24 Dec 2004 08:47:07 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Chpwl-00034R-7G
	for sipping@ietf.org; Fri, 24 Dec 2004 08:57:35 -0500
Received: from [192.168.0.108] (adsl-209-30-64-8.dsl.rcsntx.swbell.net
	[209.30.64.8]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBODjqHV004048
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 24 Dec 2004 07:45:53 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41CC1D8E.4030001@nostrum.com>
Date: Fri, 24 Dec 2004 07:45:50 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] Comments on event-throttle 01
References: <BDEED813.202A0%fluffy@cisco.com>
In-Reply-To: <BDEED813.202A0%fluffy@cisco.com>
X-Enigmail-Version: 0.89.5.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.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>, "aki.niemi@nokia.com" <aki.niemi@nokia.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: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit

Cullen Jennings wrote:

>On 12/15/04 1:18 PM, "Adam Roach" <adam@nostrum.com> wrote:
>
>  
>
>> ...[A]s far as I can tell,
>>
>>the intention isn't to merge several partial states into a full state as
>>much as it is to merge several partial states into a single partial state.
>>
>I hadn't realized that was the idea - that sounds pretty hard to implement
>in a way that does not use insane amounts of state.
>

I'm not sure I'd say "insane amounts of state," but it's certainly a 
memory/bandwidth tradeoff.

>My question still stands, is the goal to reduce bandwidth or number of
>packets?
>  
>

I suspect that the answer is bandwidth. At least, it would be for any 
application I'd be inclined to deploy this with.

>>Concretely: consider the SIP overhead of sending a NOTIFY and getting a
>>200 response to it to be X bytes.
>>
>>Now, consider that Client A has subscribed to Client C, with a throttle.
>>Client B has also subscribed, but without a throttle.
>>
>>Now, client C publishes three notifications, of sizes N, M, and P,
>>respectively.
>>
>>Client B gets these in separate messages, for a total of 3X + N + M + P
>>bytes.
>>
>>Client A gets these in a single message, for a total of X + N + M + P bytes.
>>
>>The total savings is 2X bytes.
>>
>What would the saving have been if I was running these messages over a
>compressed TLS connection?
>  
>

I'm assuming you're using deflate. Let's assume about 800 bytes of 
headers, and 4000 bytes of body. (I'm just trying to get my sizes right 
for the "offset" and "length" fields). Replicating the headers would 
take three length/distance codes, with the lengths being (2 * 8 bits + 
13 bits), and the distances being (3 * 16 bits)... or about 10 bytes per 
message, for 20 bytes total. There might also be some incidental savings 
effected because your distance code sizes won't increase as rapidly with 
the headers being absent. So, 10 to 12 bytes is not really a 
*significant* savings (probably only on the order of 2%), but it's still 
not the *expansion* you feared might happen.

And I'll reiterate that this is the worst case scenario. If more than 
one update for the same piece of state arrived during this period, you 
could completely elide all but the final one, which could well result 
savings of several hundred percent, regardless of whether compression is 
employed.

(As an aside, have you actually seen clients running TLS-negotiated 
compression in favor of SigComp? Could you point me to an example?)

> 
>  
>
>>That's the worst case scenario, in which all three notifications that C
>>sends are for different parts of the state. In the case that any of
>>these publications refer to the same part of the state, savings are even
>>more substantial.
>>    
>>
>
>Is this part of figuring out, on a per client basis, the continuous partial
>merge, checking that it is a valid document, and sending it on at the
>appropriate time that sounds pretty challenging.
>

Yes, and it is. So is almost everything else in a practical presence 
server. There are a whole slew of very difficult problems to solve... 
and, actually, once you have the data processing infrastructure in place 
to do things like state composition, you've done most of the work for 
implementing the throttling as it is currently described in the document 
(at least, by my reading of it).

>This would be good in that the client would also know they got the all the
>information, just some of it was delayed.
>  
>

Agreed, and I think such is the intention. I understand that you think 
this point, as well as potentially some related points in the draft are 
unclear, and would encourage you to send text to Aki to clarify any 
points of ambiguity.

/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  Mon Dec 27 17:05: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 RAA08872
	for <sipping-web-archive@ietf.org>; Mon, 27 Dec 2004 17:05:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cj3An-00040B-HX
	for sipping-web-archive@ietf.org; Mon, 27 Dec 2004 17:17:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cj2lY-0000BH-Mq; Mon, 27 Dec 2004 16:51:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cj1xq-0004M4-Lc
	for sipping@megatron.ietf.org; Mon, 27 Dec 2004 15:59: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 PAA22570
	for <sipping@ietf.org>; Mon, 27 Dec 2004 15:59:37 -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 1Cj28c-00072Z-LV
	for sipping@ietf.org; Mon, 27 Dec 2004 16:10:47 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 27 Dec 2004 14:08:14 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBRKx2o9001242
	for <sipping@ietf.org>; Mon, 27 Dec 2004 12:59:03 -0800 (PST)
Received: from [192.168.1.102] (sjc-vpn4-798.cisco.com [10.21.83.29])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AVA58821;
	Mon, 27 Dec 2004 12:59:03 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Mon, 27 Dec 2004 13:59:03 -0700
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BDF5C5A7.20D63%fluffy@cisco.com>
Mime-version: 1.0
Content-type: multipart/mixed;
	boundary="B_3187000744_9345401"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bfe538a859d88717fa3c8a6377d62f90
Subject: [Sipping] compression problems
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: f60fbf3dbcaca652b6d10036f0630412

> 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.

--B_3187000744_9345401
Content-type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit


We seem to be doing a ton of weird things to SIP such as the recent
even-throttle, events lists etc. all in the name of compression.

The issue is basically this, people want to put several SIP messages that
have a lot in common into one sip message for compression reasons. Let's say
all these messages have most of the header and body about the same then a
few parts change - it seems clear that they should not take much more
bandwidth than one message plus the list of things that are different in
each message. 

I think we should go and solve this compression problem as a root issue and
then there would be less need for all kinds of weird things that are being
done in the name of compression. I think the end result would work better
and be easier to implement. One possible approach is just to run some
approximation of arithmetic coding on the stream between and edge proxy and
UA - for example, TLS with compression negotiated would do this. There are
no doubt better approaches that take into account that SIP can have encoding
that is not bitwise exact and take into account structural information and
advanced context pool switches.

Let me make a clear example our of all this - I took the example out of the
lists URI draft with an INVITE with a list to invite three other
participants - I call this message "mix" for when the list plus the original
requests were mixed together. Another way to do with would be to send an
INVITE to create the focus, then send 3 refers to the focus to invite the
other participants. I called these messages "inv", "ref1", "ref2", "ref3",
respectively. 

I don't have a sigcomp engine I can experiment with, but just using gzip as
something that will give a representative compression approximation I get
the compressed size of various messages as :

"mix"  644

independent compression of "inv+3ref" = 458 + 358 + 361 + 361 = 1538

compress of "all" 534

Note the key  factor here - putting what was simple for SIP INV plus 3
refers though a standard compression scheme actually resulted in better
compression that the same compression scheme on list approach.

And both of these was way better than the in depended compression approach
which I think is more representative of how sigcomp works.

We have a bunch of drafts floating around that are motivated by compression
- and none of them discuss if they actually provide any compression or
follow up with any results to show if they work one way or anther. This is a
silly way to design compression schemes.

Messages I used are attached. (and compressed in exactly the wrong way)











--B_3187000744_9345401
Content-type: application/octet-stream; name="msg.tar"
Content-disposition: attachment;
	filename="msg.tar"
Content-Transfer-Encoding: base64

YWxsLmd6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADAxMDA2NDQA
MDAwMDc2NQAwMDAwMDI0ADAwMDAwMDAxMDI2ADEwMTYzMDYyMzIzADAxMTM0MgAgMAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB1c3RhciAgAGZsdWZm
eQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAc3RhZmYAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAfiwgAs2TMQQID7VNNc5swEL3nV+wP4FNQG5OS
iU1xyySxGUM8k6MsZCADiILipP31FcJm2mndS3tpUp2k1b7dt09PABCutmESQFc0LmH1Xt1j
wq/pC66akmqEVRCHkY404wIAtgV2T2c98SMgZUFrrpG8IDhj2newPr1fl7sW1yT3vs7yj/bu
Jn/MOwd3nWP1CXf4RV2y9hm3aefCVPZImAu+IAJLQYS1X+D9WWpXff6yZZVA4JaVx9R+e/0L
SleXHGeehSzL7IE+Lks1/OBCaltojx17Z5PphE4mU1MS8WP62QXzKJCMsJoLCu4Pfc4qINnN
y5I9u8caCsz9GwX8+coPbhVYR0m4XsUKLB7E1SZYBhvlJBvE94vY34QLcbNaJ+HyYaymBgfR
UeiVFrhkmYwTQhvBCzdNKXjwgtV6lzYKVLTrcEZ1wXff4kw5TSEKqLe0znjugm2iiz5+8OTY
zJODAXJmhmPb79DkuEWOMRWDQBjZcObBOy8YAhA/7R4p4X2QeEeQORO20ZAm1eeeAbJf5eGn
tGCADLFgk0T6fBsNV9hreVPhxjUg8u/udUdkDJBDkdIBgkbI8KojxjLhE5qY+qyvKweUCo9G
N5F1zuYbuqet2htRPvSuKMufbPcXv4L9j3wFNCj4en+C8ScueWR0zGRt9lZNYv03yW9Mwmk6
ZtaUv1WT2K/fJN8ACZ6ZploJAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaW52Lmd6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAADAxMDA2NDQAMDAwMDc2NQAwMDAwMDI0ADAwMDAwMDAwNzEyADEw
MTYzMDYyNDExADAxMTM2NQAgMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAB1c3RhciAgAGZsdWZmeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAc3Rh
ZmYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAfiwgA
KWPMQQIDdVJdc5swEHz3r7gfwKegGCslE5tCyySxGUM8k0dZyEAGEAXipP31FQJ72plaT2Jv
925vBQBE20OUBtCXLaa8OaknQocH9knqtmIa5TUkUawjzVgAwKEk+PKtp34MtCpZM2i0KCnJ
ufaXbKSP5+7YkYYW3u9V8d0+PhZvRe+SvnetkfBMPtWQdx+ky3oMSzkj5Rh8YQRCYYR3v+Dr
TWv3Iz/seC0UpOPVTB2vD/+xdH83kNyzkGWZo9AnVaVG3zBktoVOxLWPNl06zHGWpjTiJ+wn
BnMOSCK8GYQF/M+cmwlId+uq4h947qHA2n9UwF9v/eBJgV2cRrttosDmVZT2QRjslUtskLxs
En8fbURlu0uj8PXaTQ3OYqLIKytJxXOJU8pa4Yu0bSV8DCVv9D5rFahZ35Oc6cLvqSO5ctlC
NFCfWJMPBQbbRIsRP3tybe7JxQC5K8O17S/Ima/INZZiEYhiG248eO8FEwDJ+/GN0WEEqTeL
zJX4bTSkyfQHzwA5r/bIe1ZyQIY4sE9jfX2IpxLxuqGtSYsNiP3nF90VjElyLjM2SdBVMr3q
VWOZ8AM5pr4a+y4WfwAN48IJ6gIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAG1peC5negAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAwMTAwNjQ0ADAwMDA3NjUAMDAwMDAyNAAwMDAwMDAwMTIzMAAxMDE2
MzA2MjMxNAAwMTEzNjQAIDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAdXN0YXIgIABmbHVmZnkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHN0YWZm
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH4sIAC5e
zEECA5VT23LaMBB9z1fs+LX4TsA4mIQ40HqSEAacTPMoZGErY1uuJC7p11c2l5BM6Uz1JO+e
s3t0vAsA0eQlikcgaOVjVi71JcLyhmxRUeXEwKyAeTQ1HcO6AIAXivzDtxmHU8A5JaU0cEYx
SplxQqvh9blacFTiLPjdy763F/fZWyY8JITn1oBHtNXHjG8QT4QP3aZHzHwIlRAYKyGMv0P/
rLRBjR9zVigG4izfQ+vrzV8kDa4kSgPXcV27JoYoz/Xozoek7TpL5LUXbdztkE6nazdCwjn5
5YO9N6iJsFIqCf6nPmcdaNQN85xt/H2NFgzD+xaEw0k4emjB0zSOnibzFty+qtRsNB7NWgfb
YP58Ow9n0a3KTJ7iaPx6rKaP1qqj8iuhKGdpE8eYVEoXqqpc6ZCUlaZIqhYURAiUElPpXXKU
tg6vIKUev1fEh2KVS1ohLs2CbklytWCrMkH8PdAON1v7IEn9gZSpzHzouJcXdVzXj7hT2K74
FzkNYR005rKgsQ8cr2d57fal09lfHc/qKrsgmrbhzFiJYLQLwHy1eCNY1kEc7El2Tw2n4RiN
HhlY0PQrArRKKAPHUgdm8dQcvkx3KRRwWRWo8i2Yho/PpqcQO8qaJmRHcY6U3ewcOa4NP5yO
bfbquv/nCCeCrTgmek6FFN+2RX6Kv6OiYoLWSB9WnDaopkH/WkFhTbhQuUCzDUsDUmKW0DIN
tOd4rHvadTN8/c8tQPFK4W8FDbRMyso3zc1mY2xcg/HUVM+0zZ+PD3OckQLptBRSLS7RBruR
7NclBofx7CuJajWVrkCrd2FB8/x0MzUwz2LfGDlCVeN/QSVJjtCSyA9o3zzK6X8xcvDlJ+j6
xR8hyGbr5gQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJlZjEuZ3oA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwMTAwNjQ0ADAwMDA3NjUA
MDAwMDAyNAAwMDAwMDAwMDU0NgAxMDE2MzA2MjMzNAAwMTE0MzcAIDAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAdXN0YXIgIABmbHVmZnkAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAHN0YWZmAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAH4sIAJRkzEECA3WQXW+CMBSG7/0V5wfwoUDU1WlUBgvRoRFm
4mUp5WOplFEy3X79WpyLy7ZeNec8p+fpCwA7z/d2IMoaEV5lA8ue0zM+1owahB8hCramZfR7
IEGa0UaPOYJ7RSclY7foTDH7EqPrjBm7WyCspFVrkKIkOOfGDa9wdSZJgytSTD/uikcnWRUv
hRhjIcaOAp7wWfd5c8JNKhCMOg9l4EpV8DFpefN+0VHyeiYrv5z8hh/lBG44+0LVdf6H0mzS
4nxqW7Y9UIMuZkwPHhCkjm1leOwkDhkN6XA4GnQibkRfEViXBLsCr1ppgH6s+TeATm7BGD8h
CMJ9EHsaLNyVBu4idL21BpttHGzCSIPlQba6Ldo1NYiel5G7C5ayE27iwD98v6Z7b3KjjCst
MeN5VyeE1tIL1zWTHm3JK1OktQZHKgTOqSl9swbn2vUX8gF9Tau8LRD0e59aIREmJgIAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAByZWYyLmd6AAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMDEwMDY0NAAwMDAwNzY1ADAw
MDAwMjQAMDAwMDAwMDA1NTEAMTAxNjMwNjIzNDEAMDExNDMyACAwAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHVzdGFyICAAZmx1ZmZ5AAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAABzdGFmZgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAB+LCACIZMxBAgN1kF1vgjAUhu/9FecH8KFA1NVpVAYLcUMjzMTL
WsqHKZQVMt1+/VqcxiVbr5rT55zz9AWAred7W2iKGhFepQPLntMzLmtGDcJLiIKNaRn9HkiQ
plToMUfwqOgjpzeSi2ymkF2B0bXFjN0NEFbQqjVIXhCcceNussLVmRwErkg+/XrIn53DKj/m
zRg3zdhRwCs+6z4XJyySBsGo01ACrjQFH5OWi8+LjXLXU1m5t++cfMFL2YEFZz+ous7/UJpN
WpxNbcu2B6rRxYzpwROCxLGtFI+dg0NGQzocjgadiBvRdwT2JcCuwKtWGqBfa/4NoJNbMMZP
CIJwF8SeBgt3pYG7CF3vRYP1Jg7WYaTBci+fui3aNTWI3paRuw2W8iVcx4G/v03TvQ+5UcaV
FJjxrKsTQmvpheuaSY+24JXZJLUGJW0anFFT+qYCZ9r1F3KA/kKrrM0R9HvfGT+jhyUCAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcmVmMy5negAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADAxMDA2NDQAMDAwMDc2NQAwMDAw
MDI0ADAwMDAwMDAwNTUxADEwMTYzMDYyMzQ2ADAxMTQ0MAAgMAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB1c3RhciAgAGZsdWZmeQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAc3RhZmYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAfiwgAjmTMQQIDdZBdb4IwFIbv/RXnB/ChQNTVaVQGC9GhEWbiZS3l
YymUQTPdfv1anMYlW6+a0+ec8/QFgJ3neztoixoRXqUDy57TMy5rRg3CS4iCrWkZ/R5IkKa0
0WOO4FHRgiY3sqJippB9gdG1xYzdLRBW0EoYJC8IzrhxN1nh6kyODa5IPv16yJ+d4yp/y9sx
btuxo4AXfNZ93pxwk7QIRp2GEnClKfiYCN58XmyUu57Kyr195+Q3vJQduOHsB1XX+R9Ks4nA
2dS2bHugGl3MmB48IUgc20rx2Dk6ZDSkw+Fo0Im4EX1H4FwC7Aq8EtIA/VrzbwCd3IIxfkIQ
hPsg9jRYuCsN3EXoemsNNts42ISRBsuDfOq2aNfUIHpdRu4uWMqXcBMH/uE2Tfc+5EYZV1Jg
xrOuTgitpReuayY9RMErs01qDUratjijpvRNG5xp11/IAfqaVpnIEfR7380HD3clAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

--B_3187000744_9345401
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
--B_3187000744_9345401--




From sipping-bounces@ietf.org  Mon Dec 27 17:08: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 RAA09108
	for <sipping-web-archive@ietf.org>; Mon, 27 Dec 2004 17:08:17 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cj3D6-00044r-4S
	for sipping-web-archive@ietf.org; Mon, 27 Dec 2004 17:19:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cj2lZ-0000C6-OV; Mon, 27 Dec 2004 16:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cj1yc-0004sY-FQ
	for sipping@megatron.ietf.org; Mon, 27 Dec 2004 16:00: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 QAA22671
	for <sipping@ietf.org>; Mon, 27 Dec 2004 16:00:24 -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 1Cj29M-00073p-Kg
	for sipping@ietf.org; Mon, 27 Dec 2004 16:11:35 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 27 Dec 2004 14:09:00 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBRKxmdP008429;
	Mon, 27 Dec 2004 12:59:49 -0800 (PST)
Received: from [192.168.1.102] (sjc-vpn4-798.cisco.com [10.21.83.29])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id AVA58866;
	Mon, 27 Dec 2004 12:59:49 -0800 (PST)
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Mon, 27 Dec 2004 13:59:48 -0700
Subject: Re: [Sipping] Comments on event-throttle 01
From: Cullen Jennings <fluffy@cisco.com>
To: Adam Roach <adam@nostrum.com>
Message-ID: <BDF5C5D4.20D63%fluffy@cisco.com>
In-Reply-To: <41CC1D8E.4030001@nostrum.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
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: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

On 12/24/04 6:45 AM, "Adam Roach" <adam@nostrum.com> wrote:

> Cullen Jennings wrote:
> 
>> On 12/15/04 1:18 PM, "Adam Roach" <adam@nostrum.com> wrote:
>> 
>>  
>> 
>>> ...[A]s far as I can tell,
>>> 
>>> the intention isn't to merge several partial states into a full state as
>>> much as it is to merge several partial states into a single partial state.
>>> 
>> I hadn't realized that was the idea - that sounds pretty hard to implement
>> in a way that does not use insane amounts of state.
>> 
> 
> I'm not sure I'd say "insane amounts of state," but it's certainly a
> memory/bandwidth tradeoff.
> 
>> My question still stands, is the goal to reduce bandwidth or number of
>> packets?
>>  
>> 
> 
> I suspect that the answer is bandwidth. At least, it would be for any
> application I'd be inclined to deploy this with.
> 
>>> Concretely: consider the SIP overhead of sending a NOTIFY and getting a
>>> 200 response to it to be X bytes.
>>> 
>>> Now, consider that Client A has subscribed to Client C, with a throttle.
>>> Client B has also subscribed, but without a throttle.
>>> 
>>> Now, client C publishes three notifications, of sizes N, M, and P,
>>> respectively.
>>> 
>>> Client B gets these in separate messages, for a total of 3X + N + M + P
>>> bytes.
>>> 
>>> Client A gets these in a single message, for a total of X + N + M + P bytes.
>>> 
>>> The total savings is 2X bytes.
>>> 
>> What would the saving have been if I was running these messages over a
>> compressed TLS connection?
>>  
>> 
> 
> I'm assuming you're using deflate. Let's assume about 800 bytes of
> headers, and 4000 bytes of body. (I'm just trying to get my sizes right
> for the "offset" and "length" fields). Replicating the headers would
> take three length/distance codes, with the lengths being (2 * 8 bits +
> 13 bits), and the distances being (3 * 16 bits)... or about 10 bytes per
> message, for 20 bytes total. There might also be some incidental savings
> effected because your distance code sizes won't increase as rapidly with
> the headers being absent. So, 10 to 12 bytes is not really a
> *significant* savings (probably only on the order of 2%), but it's still
> not the *expansion* you feared might happen.
> 
> And I'll reiterate that this is the worst case scenario. If more than
> one update for the same piece of state arrived during this period, you
> could completely elide all but the final one, which could well result
> savings of several hundred percent, regardless of whether compression is
> employed.
> 
> (As an aside, have you actually seen clients running TLS-negotiated
> compression in favor of SigComp? Could you point me to an example?)
> 

No - I have not seen anything using compress with TLS - or for that matter
even heard of anyone thinking of using it - and mixing compression with
security is pretty weird too :-)



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 28 10:26: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 KAA04303
	for <sipping-web-archive@ietf.org>; Tue, 28 Dec 2004 10:26:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjJQ7-00058G-Bk
	for sipping-web-archive@ietf.org; Tue, 28 Dec 2004 10:37:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjJBd-0006LA-EV; Tue, 28 Dec 2004 10:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjJ2k-0002VL-2n
	for sipping@megatron.ietf.org; Tue, 28 Dec 2004 10:13: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 KAA02678
	for <sipping@ietf.org>; Tue, 28 Dec 2004 10:13:47 -0500 (EST)
From: Laurent.Thiebaut@alcatel.fr
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjJDf-0004nz-Oo
	for sipping@ietf.org; Tue, 28 Dec 2004 10:25:08 -0500
Received: from frmail14.netfr.alcatel.fr (frmail14.netfr.alcatel.fr
	[155.132.251.14])
	by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id iBSFDipx010753;
	Tue, 28 Dec 2004 16:13:44 +0100
To: adam@estacado.net
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF494DDC6A.28598EFF-ONC1256F78.00504406@netfr.alcatel.fr>
Date: Tue, 28 Dec 2004 16:13:42 +0100
X-MIMETrack: Serialize by Router on FRMAIL14/FR/ALCATEL(Release 5.0.12HF788 |
	September 23, 2004) at 12/28/2004 16:13:44
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
Subject: [Sipping] question on draft-ietf-simple-event-list-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.3 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable

Hello all
I have a small question for my clarification on
draft-ietf-simple-event-list-06 / section 6: example / flow F9.
In the flow F9:  The Local RLS subscribes to the state of the other
non-local
        resource. Local RLS -> RLS in example.org
My question is on how RLS in example.org can apply policies such as
allowing / forbidding some users (watcher adam@example.com in this exam=
ple)
to get presence information when the back-end subscription (i.e. flow F=
9)
does not contain the name of the target UAC (i.e. sip:adam@example.com =
in
this example). Shouldn't - considering that example.org is a trusted do=
main
- a P-Asserted-Id=3D"adam Roach" <sip:adam@example.com> be added in fol=
lowing
sip message layout of flow F9?

   SUBSCRIBE sip:adam-friends@example.org SIP/2.0
   Via: SIP/2.0/TCP pres.example.com;branch=3Dz9hG4bKFSrAF8CZFL
   Max-Forwards: 70
   To: <sip:adam-friends@example.org>
   From: <sip:pres.example.com>;tag=3Da12eztNf
   Call-ID: kBq5XhtZLN@pres.example.com
   CSeq: 980774491 SUBSCRIBE
   Contact: <sip:pres.example.com>
P-Asserted-Id=3D"adam Roach" <sip:adam@example.com>
   Event: presence
   Expires: 3600
   Supported: eventlist
   Accept: application/cpim-pidf+xml
   Accept: application/rlmi+xml
   Accept: multipart/related
   Accept: multipart/signed
   Accept: application/pkcs7-mime
   Content-Length: 0

Best regards
L. Thi=E9baut
=



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 28 12:33: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 MAA11901
	for <sipping-web-archive@ietf.org>; Tue, 28 Dec 2004 12:33:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjLOm-0008Kp-Qj
	for sipping-web-archive@ietf.org; Tue, 28 Dec 2004 12:44:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjL1q-0006jt-Hr; Tue, 28 Dec 2004 12:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjKpc-0001Cw-SX
	for sipping@megatron.ietf.org; Tue, 28 Dec 2004 12:08: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 MAA10355
	for <sipping@ietf.org>; Tue, 28 Dec 2004 12:08:21 -0500 (EST)
Received: from bayc1-pasmtp04.bayc1.hotmail.com ([65.54.191.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjL0Z-0007i1-N3
	for sipping@ietf.org; Tue, 28 Dec 2004 12:19:44 -0500
Message-ID: <BAYC1-PASMTP040A545B270EFD4E6085A5ED9A0@cez.ice>
X-Originating-IP: [64.228.41.127]
X-Originating-Email: [peter.ridler@sympatico.ca]
Received: from jedi ([64.228.41.127]) by bayc1-pasmtp04.bayc1.hotmail.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 28 Dec 2004 09:07:46 -0800
From: "Peter Ridler" <ridler@softrac.ca>
To: "IETF Sipping" <sipping@ietf.org>
Date: Tue, 28 Dec 2004 12:07:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTs/5mrHUkSgoTrSIe6rfkntR9mRA==
Message-ID: <BAYC1-PASMTP04XiuHg00004daf@bayc1-pasmtp04.bayc1.hotmail.com>
X-OriginalArrivalTime: 28 Dec 2004 17:07:47.0685 (UTC)
	FILETIME=[C1497950:01C4ECFF]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
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.0 (+)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

Hi,

In section 8.4 of this draft states::

--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--

Text capability SHOULD be announced in SDP by a declaration in 
line with this example: 
          
      m=text 11000 RTP/AVP 98 100 
      a=rtpmap:98 t140/1000 
      a=rtpmap:100 red/1000 
      a=fmtp:100 98/98/98 
          
Characters SHOULD BE buffered for transmission and transmitted 
every 300 ms. 

--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--

On SDP line 2 (a=rtpmap:98 t140/1000) what does the 1000 stand for?

Nominally it is the clock rate.  If just a filler, could it be the
Timeout value i.e. 1000 = 1000ms or better yet (a=rtpmap:98 t140/300)
300 = 300ms timeout value?

Thanks
Peter
     


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 28 16:45: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 QAA04937
	for <sipping-web-archive@ietf.org>; Tue, 28 Dec 2004 16:45:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjPKM-0008IP-CX
	for sipping-web-archive@ietf.org; Tue, 28 Dec 2004 16:56:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjOzk-0003pR-4R; Tue, 28 Dec 2004 16:35:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjOOM-0005BR-Oa
	for sipping@megatron.ietf.org; Tue, 28 Dec 2004 15:56: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 PAA26075
	for <sipping@ietf.org>; Tue, 28 Dec 2004 15:56:28 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjOZL-00055u-FT
	for sipping@ietf.org; Tue, 28 Dec 2004 16:07:52 -0500
Received: from [192.168.0.108] (adsl-209-30-64-8.dsl.rcsntx.swbell.net
	[209.30.64.8]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBSKuFjB009311
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 28 Dec 2004 14:56:17 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41D1C86E.7040802@nostrum.com>
Date: Tue, 28 Dec 2004 14:56:14 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Laurent.Thiebaut@alcatel.fr
Subject: Re: [Sipping] question on draft-ietf-simple-event-list-06
References: <OF494DDC6A.28598EFF-ONC1256F78.00504406@netfr.alcatel.fr>
In-Reply-To: <OF494DDC6A.28598EFF-ONC1256F78.00504406@netfr.alcatel.fr>
X-Enigmail-Version: 0.89.5.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.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: adam@estacado.net, 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.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit

Laurent.Thiebaut@alcatel.fr wrote:

>Hello all
>I have a small question for my clarification on
>draft-ietf-simple-event-list-06 / section 6: example / flow F9.
>In the flow F9:  The Local RLS subscribes to the state of the other
>non-local
>        resource. Local RLS -> RLS in example.org
>My question is on how RLS in example.org can apply policies such as
>allowing / forbidding some users (watcher adam@example.com in this example)
>to get presence information when the back-end subscription (i.e. flow F9)
>does not contain the name of the target UAC (i.e. sip:adam@example.com in
>this example). Shouldn't - considering that example.org is a trusted domain
>- a P-Asserted-Id="adam Roach" <sip:adam@example.com> be added in following
>sip message layout of flow F9?
>  
>

P-Asserted-Id is only applicable in very limited circumstances, and 
certainly not the internet at large. It has no place in the discussion 
of a general purpose mechanism such as event lists.

Draft-ietf-simple-event-list-06 actually does define a mechanism to 
allow policy decisions, but I'm not going to describe it here, since 
that approach has been abandoned.

At the recent meeting in Washington, D.C., the working group reached 
consensus on a different approach for subscriber identity, using the 
mechanism defined by draft-ietf-sip-identity-03. I submitted a new 
version of the document on the 15th, but it has yet to appear in the 
document repository; see:

http://www.nostrum.com/~adam/ids/draft-ietf-simple-event-list-07.txt

In particular, section 7.1 and its subsections describe 
inter-presence-server authentication issues.

/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  Wed Dec 29 03:52: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 DAA20230
	for <sipping-web-archive@ietf.org>; Wed, 29 Dec 2004 03:52:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjZkP-0008M6-0g
	for sipping-web-archive@ietf.org; Wed, 29 Dec 2004 04:04:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjZY8-0002Dz-CU; Wed, 29 Dec 2004 03:51:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjZVJ-0001cA-7l
	for sipping@megatron.ietf.org; Wed, 29 Dec 2004 03:48: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 DAA19704
	for <sipping@ietf.org>; Wed, 29 Dec 2004 03:48:23 -0500 (EST)
Received: from mail3.pi.se ([195.7.64.137] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjZgO-00086r-5x
	for sipping@ietf.org; Wed, 29 Dec 2004 03:59:52 -0500
Received: from vit (136.240.13.217.in-addr.dgcsystems.net [217.13.240.136])
	(authenticated (0 bits))
	by mail3.pi.se (8.12.10/8.11.2) with ESMTP id iBT8m95p025933;
	Wed, 29 Dec 2004 09:48:10 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "IETF Sipping" <sipping@ietf.org>, "Peter Ridler" <ridler@softrac.ca>
Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
Date: Wed, 29 Dec 2004 09:48:20 +0100
Message-ID: <GHEPIJKACEKDGLKODIGJEELDDMAA.gunnar.hellstrom@omnitor.se>
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.6604 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <BAYC1-PASMTP040A545B270EFD4E6085A5ED9A0@cez.ice>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: 7bit
Cc: Toip list <toip@snowshore.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: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit

Peter,
I am glad you are looking at details of sipping-toip.

The figure 1000 in the sdp line
>      a=rtpmap:98 t140/1000
is indeed a clock rate.

You can read more about it in:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-09.txt
Where some requirements are stated for handling the timestamps.

Even if it has little meaning for a text packet where text characters are stored at the
moment they are created rather than by being sampled, we did not want to deviate from
normal RTP usage of that parameter.

The clock is used for setting the timestamp of the text packets, and for calculation of
time offset for redundant text, and can thus be used if there is a desire to time the
display of characters.

------

Do you see a need for negotiation of the transmission interval?

Regards

Gunnar

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


>-----Original Message-----
>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
>Behalf Of Peter Ridler
>Sent: Tuesday, December 28, 2004 6:08 PM
>To: IETF Sipping
>Subject: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
>
>
>Hi,
>
>In section 8.4 of this draft states::
>
>--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>
>Text capability SHOULD be announced in SDP by a declaration in
>line with this example:
>
>      m=text 11000 RTP/AVP 98 100
>      a=rtpmap:98 t140/1000
>      a=rtpmap:100 red/1000
>      a=fmtp:100 98/98/98
>
>Characters SHOULD BE buffered for transmission and transmitted
>every 300 ms.
>
>--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>
>On SDP line 2 (a=rtpmap:98 t140/1000) what does the 1000 stand for?
>
>Nominally it is the clock rate.  If just a filler, could it be the
>Timeout value i.e. 1000 = 1000ms or better yet (a=rtpmap:98 t140/300)
>300 = 300ms timeout value?
>
>Thanks
>Peter
>
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 Dec 29 14:45:46 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 OAA04504
	for <sipping-web-archive@ietf.org>; Wed, 29 Dec 2004 14:45:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjjwe-00077M-QC
	for sipping-web-archive@ietf.org; Wed, 29 Dec 2004 14:57:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjji7-0003sH-HD; Wed, 29 Dec 2004 14:42:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjjcT-0002eU-Fh
	for sipping@megatron.ietf.org; Wed, 29 Dec 2004 14:36: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 OAA04184
	for <sipping@ietf.org>; Wed, 29 Dec 2004 14:36:27 -0500 (EST)
Received: from bayc1-pasmtp04.bayc1.hotmail.com ([65.54.191.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjjnT-0006vh-MO
	for sipping@ietf.org; Wed, 29 Dec 2004 14:48:02 -0500
Message-ID: <BAYC1-PASMTP0459775758A8CB6756C17DED9B0@cez.ice>
X-Originating-IP: [64.228.35.141]
X-Originating-Email: [peter.ridler@sympatico.ca]
Received: from jedi ([64.228.35.141]) by bayc1-pasmtp04.bayc1.hotmail.com over
	TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 29 Dec 2004 11:35:39 -0800
From: "Peter Ridler" <ridler@softrac.ca>
To: "'Gunnar Hellstrom'" <gunnar.hellstrom@omnitor.se>,
        "'IETF Sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
Date: Wed, 29 Dec 2004 14:35:31 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTtgzIVEYBiJ9EHRCC05zTZsmLdFwATduEg
In-Reply-To: <GHEPIJKACEKDGLKODIGJEELDDMAA.gunnar.hellstrom@omnitor.se>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <BAYC1-PASMTP04u59Vv00005121@bayc1-pasmtp04.bayc1.hotmail.com>
X-OriginalArrivalTime: 29 Dec 2004 19:35:42.0983 (UTC)
	FILETIME=[95CA3970:01C4EDDD]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Content-Transfer-Encoding: 7bit
Cc: "'Toip list'" <toip@snowshore.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.0 (+)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: 7bit

Gunnar,

Thanks for the reply.

If indeed the 1000 is the clock rate, how is this value derived at?

The negotiation of the transmission interval is where I was thinking that
each end MAY suggest a timeout value that it is willing to accept (default
would be the 300ms).  The application I have in mind is the case a TDD
device is communicating via a PSTN gateway to a SIP IVR/ITR where it can
handle a longer delay of text packets (say 500 - 1000ms range).  This would
reduce the number of RTP packets going across the network.  BUT, I am quite
happy with the fixed 300ms interval.

Regards

Peter


 

> -----Original Message-----
> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se] 
> Sent: Wednesday, December 29, 2004 3:48 AM
> To: IETF Sipping; Peter Ridler
> Cc: Toip list
> Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
> 
> Peter,
> I am glad you are looking at details of sipping-toip.
> 
> The figure 1000 in the sdp line
> >      a=rtpmap:98 t140/1000
> is indeed a clock rate.
> 
> You can read more about it in:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-09.txt
> Where some requirements are stated for handling the timestamps.
> 
> Even if it has little meaning for a text packet where text 
> characters are stored at the moment they are created rather 
> than by being sampled, we did not want to deviate from normal 
> RTP usage of that parameter.
> 
> The clock is used for setting the timestamp of the text 
> packets, and for calculation of time offset for redundant 
> text, and can thus be used if there is a desire to time the 
> display of characters.
> 
> ------
> 
> Do you see a need for negotiation of the transmission interval?
> 
> Regards
> 
> Gunnar
> 
> -------------------------------------------
> Gunnar Hellstrom
> Omnitor AB
> Renathvagen 2
> SE 121 37 Johanneshov
> SWEDEN
> +46 8 556 002 03
> Mob: +46 708 204 288
> www.omnitor.se
> Gunnar.Hellstrom@Omnitor.se
> --------------------------------------------
> 
> 
> >-----Original Message-----
> >From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> >Behalf Of Peter Ridler
> >Sent: Tuesday, December 28, 2004 6:08 PM
> >To: IETF Sipping
> >Subject: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
> >
> >
> >Hi,
> >
> >In section 8.4 of this draft states::
> >
> >--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
> >
> >Text capability SHOULD be announced in SDP by a declaration in line 
> >with this example:
> >
> >      m=text 11000 RTP/AVP 98 100
> >      a=rtpmap:98 t140/1000
> >      a=rtpmap:100 red/1000
> >      a=fmtp:100 98/98/98
> >
> >Characters SHOULD BE buffered for transmission and transmitted every 
> >300 ms.
> >
> >--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
> >
> >On SDP line 2 (a=rtpmap:98 t140/1000) what does the 1000 stand for?
> >
> >Nominally it is the clock rate.  If just a filler, could it be the 
> >Timeout value i.e. 1000 = 1000ms or better yet (a=rtpmap:98 
> t140/300) 
> >300 = 300ms timeout value?
> >
> >Thanks
> >Peter
> >
> >
> >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the 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 Dec 29 16:36: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 QAA21263
	for <sipping-web-archive@ietf.org>; Wed, 29 Dec 2004 16:36:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjlfh-0003xK-BX
	for sipping-web-archive@ietf.org; Wed, 29 Dec 2004 16:47:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjkjo-0006GO-Jh; Wed, 29 Dec 2004 15:48:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjked-00035e-K2; Wed, 29 Dec 2004 15:42:47 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09525;
	Wed, 29 Dec 2004 15:42:45 -0500 (EST)
Message-Id: <200412292042.PAA09525@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 29 Dec 2004 15:42:45 -0500
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-kpml-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: 944ecb6e61f753561f559a497458fb4f

--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 
			  Key Press Stimulus (KPML)
	Author(s)	: E. Burger, M. Dolly
	Filename	: draft-ietf-sipping-kpml-07.txt
	Pages		: 55
	Date		: 2004-12-29
	
This document describes a SIP Event Package "kpml" that enables
   monitoring of DTMF signals and uses XML documents referred to as Key
   Press Markup Language (KPML).  The kpml Event Package may be used to
   support applications consistent with the principles defined in the
   document titled "A Framework for Application Interaction in the
   Session Initiation Protocol (SIP)".  The event package uses SUBSCRIBE
   messages and allows for XML scripts that define and describe filter
   specifications for capturing key presses (DTMF Tones) entered at a
   presentation-free User Interface SIP User Agent (UA).  The event
   package uses NOTIFY messages and allows for XML scripts to report the
   captured key presses (DTMF tones), consistent with the filter
   specifications, to an Application Server.  The scope of this package
   is for collecting supplemental key presses or mid-call key presses
   (triggers).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-kpml-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-kpml-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-kpml-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-12-29154115.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-kpml-07.txt

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

Content-Type: text/plain
Content-ID: <2004-12-29154115.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  Thu Dec 30 07:25: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 HAA06458
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 07:25:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjzYL-0006d9-4J
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 07: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 1CjzIi-0007iz-Cc; Thu, 30 Dec 2004 07:21:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjzHD-0007KC-DL
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 07:19: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 HAA06149
	for <sipping@ietf.org>; Thu, 30 Dec 2004 07:19:34 -0500 (EST)
Received: from cmailg3.svr.pol.co.uk ([195.92.195.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjzSN-0006UM-H9
	for sipping@ietf.org; Thu, 30 Dec 2004 07:31:17 -0500
Received: from user-2308.l2.c1.dsl.pol.co.uk ([81.77.169.4] helo=RW)
	by cmailg3.svr.pol.co.uk with smtp (Exim 4.41)
	id 1CjzH0-0005XD-UO; Thu, 30 Dec 2004 12:19:23 +0000
Message-ID: <02f601c4ee69$cc7f2d40$8f00a8c0@RW>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
References: <418E935A.4030800@ericsson.com>
Subject: Re: [Sipping] Announcement: Ad-hoc meeting on SBCs
Date: Thu, 30 Dec 2004 12:19:21 -0000
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.9 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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.9 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

Dear Gonzalo,

Apologies if I have missed the e-mail, but were there any conclusions from 
the SBC
IETF Ad-Hoc meeting?

Thanks,

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware
http://www.tech-know-ware.com/lmx
for LMX XML to C++ binding
(or http://www.xml2cpp.com)
=============================================

----- Original Message ----- 
From: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>
To: "sipping" <sipping@ietf.org>
Cc: "rohan Mahy" <rohan@ekabal.com>; "Allison Mankin" <mankin@psg.com>; "Jon
Peterson" <Jon.Peterson@neustar.biz>; "Dean Willis"
<dean.willis@softarmor.com>
Sent: Sunday, November 07, 2004 9:27 PM
Subject: [Sipping] Announcement: Ad-hoc meeting on SBCs


> 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


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 30 11:47: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 LAA26519
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 11:47:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ck3eC-0004lD-4h
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 11:59:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck3Mz-0006hu-3C; Thu, 30 Dec 2004 11:41:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck3Kd-00063U-6E
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 11: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 LAA25989
	for <sipping@ietf.org>; Thu, 30 Dec 2004 11:39:20 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck3Vz-0004YT-09
	for sipping@ietf.org; Thu, 30 Dec 2004 11:51:07 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com
	[135.86.145.57])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id iBUGcnBK009102
	for <sipping@ietf.org>; Thu, 30 Dec 2004 10:38:49 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service
	(5.5.2657.72) id <YSX8KYPW>; Thu, 30 Dec 2004 16:38:48 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00C2902B2@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Thu, 30 Dec 2004 16:38:46 -0000
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: d8ae4fd88fcaf47c1a71c804d04f413d
Subject: [Sipping] conferencing framework and policy
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: d185fa790257f526fedfd5d01ed9c976

I had a look through the latest version of the conferencing framework document in http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-framework-03.txt and had the following comments on it in relation to the description of policy:

1)	Given the existence of the XCON framework document, I don't think there is any need any more to distinguish between different types of policy. In many instances this is simple, the document talks in the same line about "conference policy and media policy"; as media policy is part of conference policy, in these instances we obviously only need to talk about conference policy. In other cases it is more complex, but I have come to the conclusion that either the sentence or passage making the distinction is no longer relevant, or that the more general reference to comference policy is sufficient and better because we are interested in talking about the SIP reaction, rather than what specifically caused it. Sometimes the references are no longer accurate in current thinking, e.g. references to media policy control protocol. Any text proposed for deletion however shopuld probably be carried into the XCON framework document.

2)	In a couple of places we refer to the conference notification service. Obviously this SIPPING framework document does need to talk about the event package currently under development by the SIPPING group in http://www.ietf.org/internet-drafts/draft-ietf-sipping-conference-package-08.txt. However decisions in the XCON/SIPPING group have identified that this package will be limited to fundamental conference description, and XCON will define an extension that will carry more complex information, e.g. changes in conference policy. http://www.ietf.org/internet-drafts/draft-barnes-xcon-framework-01.txt is already setting out to describe the framework for these extensions. My question is therefore whether any discussions of information carried in the XCON package should be deleted from the SIPPING framework, or whether we should describe the entire conference notification service in the SIPPING framework document, and delete any mention from the XCON framework. If the latter, we!
  should still generalise any mention of policy in accordance with 1) above.

I believe the above comments need addressing at the following points in the document, taking the main body of the document first, and leaving the terminology until later:

-	Section 3, 2nd paragraph (top of page 7). Text: "The focus uses the media policy to determine the proper configuration of the mixers." should be deleted as it is irrelevant to the operation of any of the SIP aspects of the conference.

-	Section 3, 3rd paragraph, change "conference and media policies" to "conference policy" twice. Media policy is a subset of conference policy.

-	Section 3, figure 2, delete "Membership & Media Policy" from figure as in the context of the figure "Conference Policy" is sufficient. I suspect also we should be attempting to generalise the label "Conference Policy Control Protocol" as this is the specific XCON solution here (and in current thinking only part of it), and there may be other solutions that may be completely appropriate for use in conjunction with the SIP aspects. Can we just label it "Policy control"?

-	Section 3, paragraph following figure 2 (9th paragraph - top of page 9), text: "Through this mechanism, it can learn about changes in participants (effectively, the state of the dialogs), the media policy, and the membership policy.". See point 2) above; we can either delete "the media policy, and the membership policy", or just replace it with "and the conference policy".

-	Section 3, 10th paragraph (top of page 9). Sentence "The participant can communicate with the conference policy server using a conference policy control protocol." As in comment on figure 2, should not mention specific XCON protocol name. 

-	Section 3.1, 5th paragraph (top of page 10). Text: "A conference URI can be obtained from a conference policy control protocol, which can be used to create conferences and the policies associated with them." I believe we can delete this sentence as the issue relevant to SIP is already covered in the earlier parts of the paragraph.

-	Section 4.1, 1st paragraph, change "membership policy" to "conference policy" (1 instance).

-	Section 4.1, 2nd paragraph, change "membership policy" to "conference policy" (3 instances).

-	Section 4.1, 3rd paragraph, change "membership policy" to "conference policy" (1 instance).

-	Section 4.1, 4th paragraph, change "membership policy" to "conference policy" (1 instance).

-	Section 4.1, 5th (last) paragraph (top of page 12). Delete sentences: "A similar model exists for media policy." and "Alternatively, if the video is being centrally mixed, it could inform the mixer to send a black screen to that participant.  The means by which the policy is implemented are not subject to specification." Change "media policy" to "conference policy" in remaining text.

-	Section 4.3, 1st paragraph, change "media policy" to "conference policy".

-	Section 4.4, 3rd (last) paragraph, change "media policy" to "conference policy".

-	Section 4.4, See point 2) above; and depending on decision may need to delete all references to conference policy.

-	Section 4.6, 2nd (last) paragraph; delete reference to "conference policy control protocol" (2 instances) and refer to [16] only for conference policy.

-	Section 5.1, 2nd paragraph, text: "When a media and conference policy are created, they are established with default rules that are implementation dependent.  If the creator of the conference wishes to change those rules, they would do so using a non-SIP mechanism." I can see no reason relating to the SIP aspects for retaining this paragraph, and therefore propose that it is deleted.

-	Section 5.5, 2nd paragraph. Change "the conference and media policies" to "the conference policy". Delete sentence: "Any attempts to read or write those policies results in a protocol error." as it is not relevant to the SIP aspects of discussion.

-	Section 5.8, 4th paragraph (penultimate), change "media policy" to "conference policy". 

-	Section 6.3, 1st paragraph (following figure 6). Change "the membership and media policies" to "the conference policy".

-	Section 6.3, 2nd paragraph (top of page 23), Change instances of "membership policy" and "media policy" to "conference policy".

-	Section 6.3, 3rd (last paragraph), change "is unaware of any conference or media policies" to "is unaware of any conference policy".

-	Section 6.4, 1st paragraph, change "which implements the focus, conference policy server, and media policy server" to "which implements the focus, and conference policy server"


Assuming these changes are accepted, then the following changes need to be made to the terminology in section 2.

-	Delete terms "media policy" and "membership policy" as they will no longer be used in the document.

-	Term: "Conference Notification Service". See point 2) above, and at minimum delete reference to "media policy" as covered in "conference policy".

-	Term: "Conference policy server". Delete "and include membership policy and media policy".

-	Term: "Conference policy". Delete "The policy includes membership and media policies.  The conference policy is used to specify and control the operation of a conference instance.", which in any case says the same thing twice.

-	Term: Conference-Aware Participant. Needs modification in regard to protocol support statements, as decisions have moved on from this in XCON. Possibly reuse text from paragraph immediately following figure 2.

regards

Keith


Keith Drage
Lucent Technologies
drage@lucent.com
tel: +44 1793 776249

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 30 15:09:57 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 PAA11986
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 15:09:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ck6np-0001qY-9O
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 15:21:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck6ao-0007BB-6M; Thu, 30 Dec 2004 15: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 1Ck6Rg-0006In-Ko
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 14:58: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 OAA10865
	for <sipping@ietf.org>; Thu, 30 Dec 2004 14:58:50 -0500 (EST)
Received: from av1-1-sn3.vrr.skanova.net ([81.228.9.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck6cu-0001Xb-6r
	for sipping@ietf.org; Thu, 30 Dec 2004 15:10:38 -0500
Received: by av1-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 7910037F18; Thu, 30 Dec 2004 20:58:09 +0100 (CET)
Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net
	[81.228.9.177]) by av1-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 4BE0637F3C; Thu, 30 Dec 2004 20:58:09 +0100 (CET)
Received: from vit (h79n2fls31o265.telia.com [217.208.189.79])
	by smtp1-1-sn3.vrr.skanova.net (Postfix) with SMTP id 235B638007;
	Thu, 30 Dec 2004 20:58:09 +0100 (CET)
From: "Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se>
To: "Peter Ridler" <ridler@softrac.ca>, "'IETF Sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
Date: Thu, 30 Dec 2004 20:57:56 +0100
Message-ID: <GHEPIJKACEKDGLKODIGJOEMPDMAA.gunnar.hellstrom@omnitor.se>
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.6604 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <BAYC1-PASMTP0459775758A8CB6756C17DED9B0@cez.ice>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Content-Transfer-Encoding: 7bit
Cc: "'Toip list'" <toip@snowshore.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: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: 7bit

The time synchronization requirements on text is low.
I suggest that you read a clock every time you copmpose a packet for transmission, and
convert it to a 1 ms base.

If you have a need to synch it to the audio channel, you can follow the general habits for
timing source synchronization of RTP streams.

For your IVR/ITR application, I realize that you could survive with longer transmission
intervals while collecting input from the user, but when the user is ready, she wants a
rapid response. If you really feel a need for increasing the transmission interval during
data collection, it needs to be combined with special action on the character marking the
end of the transaction. That starts to carry too far with application intelligence on the
transport level in my view, so I hope you are happy with the 300 ms default, and knowing
that during input pauses, nothing is transmitted. (except feeding out the redundancy ).

In rfc2793bis there is a section on expected bandwidth loads that you can read to get a
feeling of if the load is acceptable.

Gunnar


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


>-----Original Message-----
>From: Peter Ridler [mailto:ridler@softrac.ca]
>Sent: Wednesday, December 29, 2004 8:36 PM
>To: 'Gunnar Hellstrom'; 'IETF Sipping'
>Cc: 'Toip list'
>Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
>
>
>Gunnar,
>
>Thanks for the reply.
>
>If indeed the 1000 is the clock rate, how is this value derived at?
>
>The negotiation of the transmission interval is where I was thinking that
>each end MAY suggest a timeout value that it is willing to accept (default
>would be the 300ms).  The application I have in mind is the case a TDD
>device is communicating via a PSTN gateway to a SIP IVR/ITR where it can
>handle a longer delay of text packets (say 500 - 1000ms range).  This would
>reduce the number of RTP packets going across the network.  BUT, I am quite
>happy with the fixed 300ms interval.
>
>Regards
>
>Peter
>
>
>
>
>> -----Original Message-----
>> From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se]
>> Sent: Wednesday, December 29, 2004 3:48 AM
>> To: IETF Sipping; Peter Ridler
>> Cc: Toip list
>> Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
>>
>> Peter,
>> I am glad you are looking at details of sipping-toip.
>>
>> The figure 1000 in the sdp line
>> >      a=rtpmap:98 t140/1000
>> is indeed a clock rate.
>>
>> You can read more about it in:
>> http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-09.txt
>> Where some requirements are stated for handling the timestamps.
>>
>> Even if it has little meaning for a text packet where text
>> characters are stored at the moment they are created rather
>> than by being sampled, we did not want to deviate from normal
>> RTP usage of that parameter.
>>
>> The clock is used for setting the timestamp of the text
>> packets, and for calculation of time offset for redundant
>> text, and can thus be used if there is a desire to time the
>> display of characters.
>>
>> ------
>>
>> Do you see a need for negotiation of the transmission interval?
>>
>> Regards
>>
>> Gunnar
>>
>> -------------------------------------------
>> Gunnar Hellstrom
>> Omnitor AB
>> Renathvagen 2
>> SE 121 37 Johanneshov
>> SWEDEN
>> +46 8 556 002 03
>> Mob: +46 708 204 288
>> www.omnitor.se
>> Gunnar.Hellstrom@Omnitor.se
>> --------------------------------------------
>>
>>
>> >-----Original Message-----
>> >From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
>> >Behalf Of Peter Ridler
>> >Sent: Tuesday, December 28, 2004 6:08 PM
>> >To: IETF Sipping
>> >Subject: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
>> >
>> >
>> >Hi,
>> >
>> >In section 8.4 of this draft states::
>> >
>> >--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>> >
>> >Text capability SHOULD be announced in SDP by a declaration in line
>> >with this example:
>> >
>> >      m=text 11000 RTP/AVP 98 100
>> >      a=rtpmap:98 t140/1000
>> >      a=rtpmap:100 red/1000
>> >      a=fmtp:100 98/98/98
>> >
>> >Characters SHOULD BE buffered for transmission and transmitted every
>> >300 ms.
>> >
>> >--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>> >
>> >On SDP line 2 (a=rtpmap:98 t140/1000) what does the 1000 stand for?
>> >
>> >Nominally it is the clock rate.  If just a filler, could it be the
>> >Timeout value i.e. 1000 = 1000ms or better yet (a=rtpmap:98
>> t140/300)
>> >300 = 300ms timeout value?
>> >
>> >Thanks
>> >Peter
>> >
>> >
>> >
>> >_______________________________________________
>> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> >This list is for NEW development of the 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 Dec 30 16:07: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 QAA17630
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 16:07:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ck7hB-0003uE-Da
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 16:18:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck79o-00048w-P4; Thu, 30 Dec 2004 15:44:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChMfp-0007gp-9I
	for sipping@megatron.ietf.org; Thu, 23 Dec 2004 01:42: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 BAA26828
	for <sipping@ietf.org>; Thu, 23 Dec 2004 01:42:07 -0500 (EST)
Received: from c243-111.rim.net ([216.9.243.111] helo=MHS02YKF.rim.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChMpd-0001Ed-S2
	for sipping@ietf.org; Thu, 23 Dec 2004 01:52:18 -0500
Received: from ngw01ykf.rim.net ([10.102.108.30]) by MHS02YKF.rim.net with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Dec 2004 01:42:04 -0500
Importance: normal
Priority: normal
Received: from XCH20YKF.rim.net ([10.102.100.35]) by ngw01ykf.rim.net (SAVSMTP
	3.1.6.45) with SMTP id M2004122301420420460 ;
	Thu, 23 Dec 2004 01:42:04 -0500
Received: from XCH30YKF.rim.net ([10.102.100.42]) by XCH20YKF.rim.net with
	Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Dec 2004 01:42:04 -0500
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Dec 2004 01:42:03 -0500
Message-ID: <AABA1AE6F5565C4E9979704419B3B899037F5FF4@XCH30YKF.rim.net>
Thread-Topic: Discussion of the Allen PoC P-headers draft
thread-index: AcTohYXHvzSGXT8HRXWbJYTjDPJrrAANQIqP
From: "Andrew Allen" <aallen@rim.com>
To: <dean.willis@softarmor.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 23 Dec 2004 06:42:04.0612 (UTC)
	FILETIME=[83CE6840:01C4E8BA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 30 Dec 2004 15:44:27 -0500
Cc: rohan@ekabal.com, thallin@MOTOROLA.COM, jan.holm@ericsson.com,
        Gonzalo.Camarillo@ericsson.com, Ileana.Leuca@cingular.com
Subject: [Sipping] Re: Discussion of the Allen PoC P-headers 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: 995b2e24d23b953c94bac5288c432399
Content-Transfer-Encoding: quoted-printable


Just to summarise what changes are intended in the 01 version from 00:

1. Addition of a section on Requirements for this functionality.

2. Addition of a section discussing the alternate approaches to defining =
new headers that were considered.

3. Addition of support for a server in the Proxy Role to optionallly =
support the P-Alerting-Mode and P-Answer-State headers.

We hope to have the 01 version submitted in mid January after the OMA =
PoC working group has had a chance to review and comment on the proposed =
revision.

Merry Christmas
Andrew
--------------------------
Andrew Allen
Manager Standards
Research In Motion Ltd
BlackBerry Mobile  +1 847 809 8636
http://www.rim.com/

Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Dean Willis <dean.willis@softarmor.com>
To: sipping@ietf.org <sipping@ietf.org>; Andrew Allen <aallen@rim.com>
CC: Rohan Mahy <rohan@ekabal.com>; Gonzalo Camarillo =
<Gonzalo.Camarillo@ericsson.com>; Ileana Leuca =
<Ileana.Leuca@cingular.com>
Sent: Wed Dec 22 19:19:38 2004
Subject: Discussion of the Allen PoC P-headers draft


Sometime soon, OMA is going to ask us to perform expert review and =20
publish (as informational) a draft based on:

http://www.ietf.org/internet-drafts/draft-allen-sipping-poc-p-headers=20
-00.txt


This draft defines two P-headers (limited function headers with strong =20
caveats) used by OMA in their push-to-talk specification, PoC =20
(push-to-talk over cellular).

Please review this draft, and if you have guidance, get it to Andrew =20
ASAP, as I believe he's working on a revision with more justification =20
and other cleanups suggested by people who have responded privately.

A few comments on the draft here:


1) The P-Alerting-Mode header field is used in INVITE and seems to =20
indicate a preference, on the part of the caller or his supporting =20
applications, that the called party provide either automatic or manual =20
answer modes as indicated by the header field's value.

Why is a "caller preferences" approach not usable here?

2) The P-Answer-State header field is used in 1xx or in a 200OK to =20
indicate that a B2BUA generated the response on behalf of a UAS that it  =

expects (but cannot be certain) will eventually answer, and that the =20
media stream may be buffered "in network" pending a final answer. If =20
the answer contains SDP, then the generating node is accepting the =20
responsibility of buffering the transmitted media until the final =20
answer is received, and will deal with the cleanup should the expected =20
final answer not arrive.

I alternate between thinking this is clever, and thinking it is evil.

In the case where the response-generating node is also assuming =20
responsibility for the buffering, I can't see from this draft how the =20
user experience is affected by the presence of the P-Answer-State =20
header. They call, get connected, and start talking. MAYBE (if the =20
final leg fails) they get some kind of failure notification, after =20
they've been talking awhile. Perhaps the response is used to give a =20
different confirmation tone to the user, alerting them to a =20
higher-than-usual probability of post-answer failure? This usage needs =20
to be explained in the draft. I also don't understand the use case here  =

with a non-SDP 200OK, although it makes sense with a 183.

In the case where the response-generating node is NOT buffering and we =20
insert no SDP, we appear to be using this header field to indicate that  =

an upstream node should take responsibility for the buffering, and =20
should consequently insert SDP into the response and act as a B2BUA for  =

the call. It seems if this occurred, that the response sent back =20
upstream from the now-buffering node would need to be a 200 OK, and not  =

an intermediate 18x type message. But there's a problem -- since nobody  =

with knowledge of the terminating client's capabilities inserted SDP, =20
we can't use the "answer" model to determine the client's actual =20
capabilities, so we could end up with an unresolvable codec mismatch.

Here's the scenario: UA-A places a PoC call through S-1 and S-2 to UA-B.

UA-A and S-1 only understand AMR, and UA-B only understands the EVRC =20
encoding.

S-2 knows that UA-B supports auto-answer, is registered, is not busy, =20
and is expected to be able to receive the call (we don't go into HOW it  =

knows this). So S-2 returns a 183 with a P-Answer-State=3Dunconfirmed =
and =20
no media, and S-1 decides to buffer the call, returning a 200OK with =20
media indicating that it is prepared to receive AMR. UA-A starts =20
talking, and S-1 starts buffering. Eventually, UA-B answers, and sends =20
a 200 OK containing EVRC SDP back to S-2 and thence to S-1. Rather than  =

playing the buffered media on toward UA-B, S-1 is now stuck -- it has =20
buffered AMR media, UA-B only understands EVRC, and S-1 doesn't know =20
how to convert. This is precisely the reason we have end-to-end =20
offer-answer.

Perhaps I read the draft wrong, but if so it could use some clarity on =20
this matter, and if not, the mechanism for preventing this error =20
condition needs to be better explained. I think that if the usage of =20
the header in provisional versus final responses were more clearly =20
specified, that this error condition would be either precluded (or =20
discovered to be unavoidable, indicating a clear flaw in the design).


3)  The draft has normative text in 4.2.2.1 saying:

"A UAC that receives a 1XX or 2XX response without a P-Answer-State =20
Header or containing a P-Answer-State header field containing the =20
parameter "Confirmed" SHALL treat it as a "confirmed response"."

I don't believe that it is reasonable for a P-draft to make normative =20
statements about how the absence of a a P-header impacts a UAC in =20
general. In the general case, a 200 OK is a confirmed response. Perhaps  =

something along the lines of:

"A UAC conformant to this specification that receives a response not =20
containing a P-Answer-State header field proceeds as if that response =20
contained a P-Answer-State header field with the value "confirmed"."



4) Somebody who understands early media much better than I do needs to =20
review this draft carefully. Note that we have new RFCs on the topic, =20
RFC 3959 and 3960.


--
Dean Willis




---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential =
information, privileged material (including material protected by the =
solicitor-client or other applicable privileges), or constitute =
non-public information. Any use of this information by anyone other than =
the intended recipient is prohibited. If you have received this =
transmission in error, please immediately reply to the sender and delete =
this information from your system. Use, dissemination, distribution, or =
reproduction of this transmission by unintended recipients is not =
authorized and may be unlawful.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 30 18:37: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 SAA28291
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 18:37:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkA2e-0007Sy-Ng
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 18:49:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck9lC-0003uN-3z; Thu, 30 Dec 2004 18:31:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck9kS-0003e3-9b
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 18:30:28 -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 SAA28002
	for <sipping@ietf.org>; Thu, 30 Dec 2004 18:30:25 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck9vs-0007LP-8t
	for sipping@ietf.org; Thu, 30 Dec 2004 18:42:16 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iBUNR1rw021110; Thu, 30 Dec 2004 18:27:01 -0500 (EST)
Received: by nhmail2.brooktrout.com with Internet Mail Service (5.5.2653.19)
	id <ZR3VMRCN>; Thu, 30 Dec 2004 18:23:40 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: Cullen Jennings <fluffy@cisco.com>, sipping <sipping@ietf.org>
Subject: RE: [Sipping] compression problems
Date: Thu, 30 Dec 2004 18:23:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
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: 36c793b20164cfe75332aa66ddb21196

This is exactly WHY lemonade is currently favoring the TLS w/ null cipher
(or, you can have your security, too :) approach.  We were looking at a ton
of ugly application-layer compression schemes, until we realized that we
could get the same or better results with TLS.

It is not a panacea for lemonade for exactly the reason TLS *is* a panacea
for SIP: in lemonade, one may be transmitting a LOT of pre-compressed data.
In that case, TLS gets you zero compression at the expense of CPU.  The
lemonade environment is a limited CPU environment, so that hurts.

In the SIP environment, virtually EVERYTHING is 7-bit ASCII text.  Yes, we
made a big effort to get people to realize that SIP is 8-bit binary, but the
reality is that MOST of the stuff people are shipping around is and will
remain a very small subset of the octet space.  TLS would get you a big
compression savings off the bat.

> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy@cisco.com]
> Sent: Monday, December 27, 2004 3:59 PM
> To: sipping
> Subject: [Sipping] compression problems
> 
> 
> 
> We seem to be doing a ton of weird things to SIP such as the recent
> even-throttle, events lists etc. all in the name of compression.
> 
> The issue is basically this, people want to put several SIP 
> messages that
> have a lot in common into one sip message for compression 
> reasons. Let's say
> all these messages have most of the header and body about the 
> same then a
> few parts change - it seems clear that they should not take much more
> bandwidth than one message plus the list of things that are 
> different in
> each message. 
> 
> I think we should go and solve this compression problem as a 
> root issue and
> then there would be less need for all kinds of weird things 
> that are being
> done in the name of compression. I think the end result would 
> work better
> and be easier to implement. One possible approach is just to run some
> approximation of arithmetic coding on the stream between and 
> edge proxy and
> UA - for example, TLS with compression negotiated would do 
> this. There are
> no doubt better approaches that take into account that SIP 
> can have encoding
> that is not bitwise exact and take into account structural 
> information and
> advanced context pool switches.
> 
> Let me make a clear example our of all this - I took the 
> example out of the
> lists URI draft with an INVITE with a list to invite three other
> participants - I call this message "mix" for when the list 
> plus the original
> requests were mixed together. Another way to do with would be 
> to send an
> INVITE to create the focus, then send 3 refers to the focus 
> to invite the
> other participants. I called these messages "inv", "ref1", 
> "ref2", "ref3",
> respectively. 
> 
> I don't have a sigcomp engine I can experiment with, but just 
> using gzip as
> something that will give a representative compression 
> approximation I get
> the compressed size of various messages as :
> 
> "mix"  644
> 
> independent compression of "inv+3ref" = 458 + 358 + 361 + 361 = 1538
> 
> compress of "all" 534
> 
> Note the key  factor here - putting what was simple for SIP INV plus 3
> refers though a standard compression scheme actually resulted 
> in better
> compression that the same compression scheme on list approach.
> 
> And both of these was way better than the in depended 
> compression approach
> which I think is more representative of how sigcomp works.
> 
> We have a bunch of drafts floating around that are motivated 
> by compression
> - and none of them discuss if they actually provide any compression or
> follow up with any results to show if they work one way or 
> anther. This is a
> silly way to design compression schemes.
> 
> Messages I used are attached. (and compressed in exactly the 
> wrong way)
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

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


From sipping-bounces@ietf.org  Thu Dec 30 18:39: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 SAA28410
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 18:39:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkA4V-0007WQ-CL
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 18:51:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck9lC-0003us-Uq; Thu, 30 Dec 2004 18:31:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck9kS-0003e5-Og
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 18:30:28 -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 SAA28005
	for <sipping@ietf.org>; Thu, 30 Dec 2004 18:30:26 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck9vs-0007LP-UY
	for sipping@ietf.org; Thu, 30 Dec 2004 18:42:17 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iBUNR1rw021109; Thu, 30 Dec 2004 18:27:01 -0500 (EST)
Received: by nhmail2.brooktrout.com with Internet Mail Service (5.5.2653.19)
	id <ZR3VMRCM>; Thu, 30 Dec 2004 18:23:40 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331EC9EEE@nhmail2.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: Adam Roach <adam@nostrum.com>
Subject: RE: [Sipping] comments on throttle-01
Date: Thu, 30 Dec 2004 18:23:37 -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: 244a2fd369eaf00ce6820a760a3de2e8
Cc: SIPPING WG <sipping@ietf.org>, Aki Niemi <aki.niemi@nokia.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

My point is that for there to be any meaningful throttling, it has to be on
a per-package basis.  Always.

The things that sound like they make sense, like rate of messages, {average,
peak} bandwidth, etc., all have counter-examples that don't make sense for a
given package.

I could see this as a "template extension" for 3265.  In particular, as one
describes subscriber and notifier behavior, one MUST describe throttling.

Then again, doesn't 3265 say that already?

> -----Original Message-----
> From: Adam Roach [mailto:adam@nostrum.com]
> Sent: Wednesday, December 15, 2004 4:03 PM
> To: Eric Burger
> Cc: Aki Niemi; SIPPING WG
> Subject: Re: [Sipping] comments on throttle-01
> 
> 
> Eric Burger wrote:
> 
> >...I still don't get the value of a (future) RFC on the topic.  Why
> >not just refer people to a Buffer Theory textbook and be 
> done with it?
> >There is no protocol stuff going on in here, really.
> >  
> >
> 
> I would argue that the protocol element to this -- and it is an 
> important one -- is the ability for a subscriber to request 
> throttling. 
> The draft also needs to precisely describe what these 
> throttle requests 
> mean, which is where a bulk of the current text comes from -- 
> but there 
> is a distinct protocol element to it.
> 
> During the creation of the document that is now RFC3265, there was a 
> distinct belief that, in certain circumstances, the subscriber should 
> have the ability to request throttling of notification (see section 
> 4.4.3, for example). Back in Vienna, by accepting the throttling 
> requirements, the working group made a decision to define a 
> cross-package throttling mechanism.
> 
> I think Aki's draft is a really good basis for moving this 
> work forward. 
> Given the text in the current document, I have a clear 
> picture of how I 
> would sit down and implement a server that supports this extension.
> 
> As to the open issue, I think this draft should leave out 
> suggestions of 
> recommended throttle intervals, as they will vary not just 
> from package 
> to package, but from application to application.
> 
> As this document necessarily extends RFC3265, I would 
> personally like to 
> see this work handed off to the SIP working group for 
> completion there.
> 
> /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 Dec 30 18:46: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 SAA28925
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 18:46:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkAB5-0007gF-15
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 18:57:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck9yP-0006Ql-Na; Thu, 30 Dec 2004 18:44:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck9tT-0005eH-A1
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 18:39: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 SAA28510
	for <sipping@ietf.org>; Thu, 30 Dec 2004 18:39:44 -0500 (EST)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkA4t-0007XO-Gb
	for sipping@ietf.org; Thu, 30 Dec 2004 18:51:35 -0500
Received: from nhmail2.needham.brooktrout.com (nhmail2.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	iBUNR1rx021110; Thu, 30 Dec 2004 18:27:01 -0500 (EST)
Received: by nhmail2.brooktrout.com with Internet Mail Service (5.5.2653.19)
	id <ZR3VMRCL>; Thu, 30 Dec 2004 18:23:40 -0500
Message-ID: <EDD694D47377D7119C8400D0B77FD331EC9EED@nhmail2.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: Cullen Jennings <fluffy@cisco.com>, Adam Roach <adam@nostrum.com>
Subject: Compress w/ TLS (was RE: [Sipping] Comments on event-throttle 01)
Date: Thu, 30 Dec 2004 18:23:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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: 7655788c23eb79e336f5f8ba8bce7906

Lemonade is considering using TLS, possibly even with NULL cipher, for
on-the-fly compression.

> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy@cisco.com]
> Sent: Monday, December 27, 2004 4:00 PM
> To: Adam Roach
> Cc: sipping
> Subject: Re: [Sipping] Comments on event-throttle 01
> 
[snip]
> No - I have not seen anything using compress with TLS - or 
> for that matter
> even heard of anyone thinking of using it - and mixing 
> compression with
> security is pretty weird too :-)
[snip]

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 30 19:05: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 TAA29999
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 19:05:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkAUI-00085V-AS
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 19:17:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkADK-0001MG-R5; Thu, 30 Dec 2004 19:00:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkA9k-0008U4-Tx
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 18:56: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 SAA29391
	for <sipping@ietf.org>; Thu, 30 Dec 2004 18:56:33 -0500 (EST)
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkALB-0007t2-7f
	for sipping@ietf.org; Thu, 30 Dec 2004 19:08:25 -0500
Received: from dfnjgl21 (c-24-1-97-29.client.comcast.net[24.1.97.29])
	by comcast.net (sccrmhc13) with SMTP
	id <2004123023551501600ps61ve>; Thu, 30 Dec 2004 23:55:16 +0000
Message-ID: <109f01c4eecb$3d579be0$0200a8c0@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "sipping" <sipping@ietf.org>
References: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
Subject: Re: [Sipping] compression problems
Date: Thu, 30 Dec 2004 17:56:53 -0600
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.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
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: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

Hi, Eric,

I happen to like the idea of compression using a 
lower-than-application-level compression mechanism, but doesn't 
relying on TLS-based compression overlook SIP-over-UDP (since TLS 
requires TCP, or something pretty close)?

Spencer


> This is exactly WHY lemonade is currently favoring the TLS w/ null 
> cipher
> (or, you can have your security, too :) approach.  We were looking 
> at a ton
> of ugly application-layer compression schemes, until we realized 
> that we
> could get the same or better results with TLS.
>
> It is not a panacea for lemonade for exactly the reason TLS *is* a 
> panacea
> for SIP: in lemonade, one may be transmitting a LOT of 
> pre-compressed data.
> In that case, TLS gets you zero compression at the expense of CPU. 
> The
> lemonade environment is a limited CPU environment, so that hurts.
>
> In the SIP environment, virtually EVERYTHING is 7-bit ASCII text. 
> Yes, we
> made a big effort to get people to realize that SIP is 8-bit binary, 
> but the
> reality is that MOST of the stuff people are shipping around is and 
> will
> remain a very small subset of the octet space.  TLS would get you a 
> big
> compression savings off the bat. 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Dec 30 23:34:46 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 XAA14507
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 23:34:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkEgQ-0005Wv-Fk
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 23: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 1CkETU-0007Im-7a; Thu, 30 Dec 2004 23:33:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkESQ-0006xW-LP
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 23:32: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 XAA14250
	for <sipping@ietf.org>; Thu, 30 Dec 2004 23:32:08 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkEdt-0005Si-C7
	for sipping@ietf.org; Thu, 30 Dec 2004 23:44:01 -0500
Received: from [192.168.0.108] (adsl-209-30-64-8.dsl.rcsntx.swbell.net
	[209.30.64.8]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBV4W6Oi054038
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 30 Dec 2004 22:32:08 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41D4D644.7010707@nostrum.com>
Date: Thu, 30 Dec 2004 22:32:04 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [Sipping] compression problems
References: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
	<109f01c4eecb$3d579be0$0200a8c0@DFNJGL21>
In-Reply-To: <109f01c4eecb$3d579be0$0200a8c0@DFNJGL21>
X-Enigmail-Version: 0.89.5.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.1 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
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.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

Spencer Dawkins wrote:

> I happen to like the idea of compression using a 
> lower-than-application-level compression mechanism, but doesn't 
> relying on TLS-based compression overlook SIP-over-UDP (since TLS 
> requires TCP, or something pretty close)?


Well, there's DTLS, which runs over UDP...

/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 Dec 30 23:45: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 XAA15110
	for <sipping-web-archive@ietf.org>; Thu, 30 Dec 2004 23:45:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkEqe-0005lm-Rq
	for sipping-web-archive@ietf.org; Thu, 30 Dec 2004 23:57:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkEdz-0000dc-IS; Thu, 30 Dec 2004 23:44:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkEZM-00082r-FE
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 23:39: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 XAA14712
	for <sipping@ietf.org>; Thu, 30 Dec 2004 23:39:17 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkEkp-0005dW-9e
	for sipping@ietf.org; Thu, 30 Dec 2004 23:51:11 -0500
Received: from [192.168.0.108] (adsl-209-30-64-8.dsl.rcsntx.swbell.net
	[209.30.64.8]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iBV4cBgB054420
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 30 Dec 2004 22:38:13 -0600 (CST)
	(envelope-from adam@nostrum.com)
Message-ID: <41D4D7B1.1030201@nostrum.com>
Date: Thu, 30 Dec 2004 22:38:09 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@brooktrout.com>
Subject: Re: [Sipping] compression problems
References: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
In-Reply-To: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
X-Enigmail-Version: 0.89.5.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.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.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.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

Eric Burger wrote:

>This is exactly WHY lemonade is currently favoring the TLS w/ null cipher
>(or, you can have your security, too :) approach.  We were looking at a ton
>of ugly application-layer compression schemes, until we realized that we
>could get the same or better results with TLS.
>
>It is not a panacea for lemonade for exactly the reason TLS *is* a panacea
>for SIP...
>

Well, actually, it isn't. The place that compression is most needed is 
over wireless (i.e. cellular) data links. Unfortunately, the terminals 
involved aren't necessarily up to the task of running a compression 
algorithm as heavy as deflate (which, IIRC, is the only one currently 
registered for use with TLS). I've had real-world experience with such 
handsets running SIP. There are many much cheaper algorithms (I'll cite 
LZJH as an example -- compression takes about 1/6th the time as deflate, 
albeit with slightly larger messages as a result) that are perfectly 
appropriate for such low-end terminals.

So, for the time being, the approach that makes the most sense is the 
one that SigComp has taken: allow each implementation to determine what 
an appropriate level of complexity is for their operating environment.

/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  Fri Dec 31 00:07: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 AAA16268
	for <sipping-web-archive@ietf.org>; Fri, 31 Dec 2004 00:07:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CkFCK-0006Oa-KJ
	for sipping-web-archive@ietf.org; Fri, 31 Dec 2004 00: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 1CkEwO-00064j-8H; Fri, 31 Dec 2004 00:03:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CkEr1-0004w6-IS
	for sipping@megatron.ietf.org; Thu, 30 Dec 2004 23:57: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 XAA15805
	for <sipping@ietf.org>; Thu, 30 Dec 2004 23:57:32 -0500 (EST)
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CkF2T-0006B9-Pw
	for sipping@ietf.org; Fri, 31 Dec 2004 00:09:27 -0500
Received: from dfnjgl21 (c-24-1-97-29.client.comcast.net[24.1.97.29])
	by comcast.net (sccrmhc11) with SMTP
	id <2004123104570001100g64k6e>; Fri, 31 Dec 2004 04:57:00 +0000
Message-ID: <111c01c4eef5$645f6c70$0200a8c0@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "Adam Roach" <adam@nostrum.com>
References: <EDD694D47377D7119C8400D0B77FD331EC9EEF@nhmail2.brooktrout.com>
	<109f01c4eecb$3d579be0$0200a8c0@DFNJGL21>
	<41D4D644.7010707@nostrum.com>
Subject: Re: [Sipping] compression problems
Date: Thu, 30 Dec 2004 22:58:31 -0600
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.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
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: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

From: "Adam Roach" <adam@nostrum.com>
> Spencer Dawkins wrote:
>
>> I happen to like the idea of compression using a 
>> lower-than-application-level compression mechanism, but doesn't 
>> relying on TLS-based compression overlook SIP-over-UDP (since TLS 
>> requires TCP, or something pretty close)?
>
>
> Well, there's DTLS, which runs over UDP...

Adam,

Thanks for the pointer.

The ID tracker for draft-rescorla-dtls-02.txt shows it as Publication 
Requested with no IESG evaluation yet - have we heard anything else 
about its status?

Like I said - I like transport-level compression - so am trying not to 
read too much into an individual draft...

Spencer




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


