From sipping-bounces@ietf.org  Fri Oct  1 03:51: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 DAA03083
	for <sipping-web-archive@ietf.org>; Fri, 1 Oct 2004 03:51:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CDIKZ-0000FB-32
	for sipping-web-archive@ietf.org; Fri, 01 Oct 2004 03:59:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDHsg-0002zd-JY; Fri, 01 Oct 2004 03:31:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CDHlN-0000tV-Kv
	for sipping@megatron.ietf.org; Fri, 01 Oct 2004 03:23:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01597
	for <sipping@ietf.org>; Fri, 1 Oct 2004 03:23:32 -0400 (EDT)
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDHtl-000891-SL
	for sipping@ietf.org; Fri, 01 Oct 2004 03:32:15 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i917KY600512; Fri, 1 Oct 2004 10:20:39 +0300 (EET DST)
X-Scanned: Fri, 1 Oct 2004 10:18:31 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i917IVRa021293;
	Fri, 1 Oct 2004 10:18:31 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 005NmPJI; Fri, 01 Oct 2004 10:18:29 EEST
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i917IOS22605; Fri, 1 Oct 2004 10:18:24 +0300 (EET DST)
Received: from esebe009.NOE.Nokia.com ([172.21.138.41]) by
	esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 1 Oct 2004 10:18:22 +0300
Received: from esebe054.NOE.Nokia.com ([172.21.143.44]) by
	esebe009.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 1 Oct 2004 10:18:22 +0300
Received: ESEBE054.NOE.Nokia.com 172.21.143.44 from 172.21.39.131
	172.21.39.131 via HTTP with MS-WebStorage 6.0.6249
Received: from localhost by ESEBE054.NOE.Nokia.com; 01 Oct 2004 10:18:21 +0300
Subject: Re: [Sipping] Use of PUBLISH in rtcp-summary-03
From: Aki Niemi <aki.niemi@nokia.com>
To: ext Huybrighs Joseph <Joseph.Huybrighs@siemens.com>
In-Reply-To: <6B546A602AD2D211BFF00008C7A428890A941139@hrtades2.atea.be>
References: <6B546A602AD2D211BFF00008C7A428890A941139@hrtades2.atea.be>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1096615101.20916.44.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Fri, 01 Oct 2004 10:18:21 +0300
X-OriginalArrivalTime: 01 Oct 2004 07:18:22.0719 (UTC)
	FILETIME=[D5C5E8F0:01C4A786]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit

Inline.

On Wed, 2004-09-29 at 19:11, ext Huybrighs Joseph wrote:
..snip..
> If the choice is between PUBLISH and NOTIFY then, because PUBLISH
> clearly is about sending "events", PUBLISH would be OK for me. But
> then I would suggest to add additional usage schemes in
> draft-ietf-sip-publish-04 and allow besides "initial", "refresh",
> "modify", and "remove" also a "single" (one-shot if you like) type of
> operation for PUBLISH that doesn't establishes a soft state in the
> Event State Compositor (ESC).

Well, that's just it, the PUBLISH method was designed to carry soft
state. There was some extensive discussion that took place on the SIMPLE
list where it was debated whether PUBLISH should also handle hard-state
publications.

And I must admit I was under the impression that SUBSCRIBE/NOTIFY was
being used to get this perfrpt events from the UA. The draft isn't
really clear on which entity subscribes to this event, and why is
PUBLISH needed vs. the UA itself servicing the subscription(s).

For simply sending stateless, periodic reports to an entity that isn't
an ESC using PUBLISH seems a bit of a misuse of the method. Something
like MESSAGE (or perhaps a REPORT method ;) would fit the description
better.

However, setting the PUBLISH expiration to a reasonably large value
accomplishes something close to hard-state publication. But the draft
probably needs to be strengthened a bit in this respect to include
proper considerations for using PUBLISH, as is stated in
draft-ietf-sip-publish-04 (soon-to-be RFC 3903).

Cheers,
Aki

> Any other thoughts about this?
> 
> Jos
> 
> System Engineering,
> Siemens Subscriber Networks, Brussels
> 
> 
> 
> ______________________________________________________________________
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 mailman-bounces@ietf.org  Fri Oct  1 05:54:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12067
	for <sipping-web-archive@ietf.org>; Fri, 1 Oct 2004 05:54:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CDKFb-00038T-TF
	for sipping-web-archive@ietf.org; Fri, 01 Oct 2004 06:02:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDJWA-0005ll-Ui
	for sipping-web-archive@ietf.org; Fri, 01 Oct 2004 05:15:59 -0400
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.3709.1096621392.3166.mailman@lists.ietf.org>
Date: Fri, 01 Oct 2004 05:03:12 -0400
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  Fri Oct  1 13:21:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27664
	for <sipping-web-archive@ietf.org>; Fri, 1 Oct 2004 13:21:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CDREW-0004Wy-BU
	for sipping-web-archive@ietf.org; Fri, 01 Oct 2004 13:30:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDQdV-0007Tq-By; Fri, 01 Oct 2004 12:52:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CDPja-0002nT-Du
	for sipping@megatron.ietf.org; Fri, 01 Oct 2004 11:54:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15535
	for <sipping@ietf.org>; Fri, 1 Oct 2004 11:54:12 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDPrt-0001id-6T
	for sipping@ietf.org; Fri, 01 Oct 2004 12:02:59 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I4W00A02X37GU@dns2.cselt.it> for sipping@ietf.org; Fri,
	01 Oct 2004 17:45:07 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Fri, 01 Oct 2004 17:50:44 +0200
Date: Fri, 01 Oct 2004 17:53:30 +0200
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
To: sipping@ietf.org
Message-id: <E5880434292FCB448F00BDAEE44A60D0096680@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: profile data for SIP policies
Thread-Index: AcSnzswvWR67l0b1Qr2DKTPQA55ylA==
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 01 Oct 2004 15:50:44.0734 (UTC)
	FILETIME=[697121E0:01C4A7CE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] profile data for SIP policies
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: quoted-printable

Hi,
Some questions on draft-ietf-sipping-session-indep-policy-00:
- Has the XML schema already been defined for the =
application/session-policy+xml type (section 4.2 of the draft)?
- How does the policy document relate to the Profile Delivery Framework: =
how should it be included in the device configuration data? Should it be =
part of the Local Profile, of the User Profile? Or should it be an =
independent document?
- How does the policy document relate to the general configuration =
parameters?
- Actually, are the Local Profile data and User Profile data being =
standardized? Will a draft come out with schemas for this data?
Regards,
Gabrielle Simonetti
Telecom Italia


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

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

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


From sipping-bounces@ietf.org  Fri Oct  1 18:48: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 SAA04751
	for <sipping-web-archive@ietf.org>; Fri, 1 Oct 2004 18:48:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CDWKg-0005Ac-AZ
	for sipping-web-archive@ietf.org; Fri, 01 Oct 2004 18:56:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDVtK-0000xr-MC; Fri, 01 Oct 2004 18:28:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CDVRI-0001z2-W6
	for sipping@megatron.ietf.org; Fri, 01 Oct 2004 17:59:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28983
	for <sipping@ietf.org>; Fri, 1 Oct 2004 17:59:42 -0400 (EDT)
Received: from dirty.research.bell-labs.com ([204.178.16.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDVZq-0007A3-5S
	for sipping@ietf.org; Fri, 01 Oct 2004 18:08:34 -0400
Received: from scummy.research.bell-labs.com
	(H-135-104-2-10.research.bell-labs.com [135.104.2.10])
	by dirty.research.bell-labs.com (8.12.10/8.12.10) with ESMTP id
	i91LxhXJ048619; Fri, 1 Oct 2004 17:59:43 -0400 (EDT)
Received: from bronx.dnrc.bell-labs.com (bronx.dnrc.bell-labs.com
	[135.180.160.8])
	by scummy.research.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	i91LxcU1034974; Fri, 1 Oct 2004 17:59:38 -0400 (EDT)
Received: from [135.180.240.186] (volker-hopc [135.180.240.186])
	by bronx.dnrc.bell-labs.com (8.12.9/8.12.9) with ESMTP id
	i91LxbMJ025091; Fri, 1 Oct 2004 17:59:37 -0400 (EDT)
Message-ID: <415DD287.9000503@bell-labs.com>
Date: Fri, 01 Oct 2004 17:56:23 -0400
From: Volker Hilt <volkerh@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Simonetti Gabrielle <Gabrielle.Simonetti@tilab.com>
Subject: Re: [Sipping] profile data for SIP policies
References: <E5880434292FCB448F00BDAEE44A60D0096680@EXC01C.cselt.it>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D0096680@EXC01C.cselt.it>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

Simonetti Gabrielle wrote:
> Hi,
> Some questions on draft-ietf-sipping-session-indep-policy-00:
> - Has the XML schema already been defined for the
>   application/session-policy+xml type (section 4.2 of the draft)?

We are currently revising the draft (including the schema) and plan to 
submit a new version for the upcoming meeting. Please let me know if you 
have any requirements or items you would like to see in the draft.

> - How does the policy document relate to the Profile Delivery
>   Framework: how should it be included in the device configuration data?
>   Should it be part of the Local Profile, of the User Profile? Or should
>   it be an independent document?

The two drafts clearly need to be aligned (which is what we are 
currently doing). The goal is that policies and device configuration can 
co-exist in the same document.

The separation of the profile types (user, device, local, application) 
enables multiple entities to manage profile data. It does not determine 
the profile content or the XML schema used. Thus, an XML schema could be 
used for local profiles and for user profiles.

> - How does the policy document relate to the general configuration
>   parameters?

Policies are part of the configuration information.

> - Actually, are the Local Profile data and User Profile data being
>   standardized? Will a draft come out with schemas for this data?
> 
Again, I don't think there will be a schema for local or user profile 
data. There will be schemas for different aspects of profile information 
(e.g. media, SIP protocol, address books) which can be used in local, 
user, device, etc. profile types. Of course, not all schemas will make 
sense for every profile type.

-- Volker


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


From sipping-bounces@ietf.org  Mon Oct  4 03:31: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 DAA07024
	for <sipping-web-archive@ietf.org>; Mon, 4 Oct 2004 03:31:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CENSl-0007by-Oz
	for sipping-web-archive@ietf.org; Mon, 04 Oct 2004 03:40:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CENHP-0000IU-Pz; Mon, 04 Oct 2004 03:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CENBp-00087g-T6
	for sipping@megatron.ietf.org; Mon, 04 Oct 2004 03:23:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06732
	for <sipping@ietf.org>; Mon, 4 Oct 2004 03:23:19 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CENKp-00076J-32
	for sipping@ietf.org; Mon, 04 Oct 2004 03:32:42 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLLNDJA>; Mon, 4 Oct 2004 03:22:37 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 4 Oct 2004 03:22:26 -0400 
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: 7655788c23eb79e336f5f8ba8bce7906
Subject: [Sipping] New internet draft on media loopback
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

I would like to bring the attention of the group to a new internet draft on
media loopback capability in SIP sessions. The draft can be found at
http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt

Regards,
Kaynam

-----------------------------------------
Kaynam Hedayat
Chief Technology Officer
Brix Networks
285 Mill Road
Chelmsford, MA 01824

tel.   978.367.5611
fax.   978.367.5700
khedayat@brixnet.com
www.brixnet.com

See it before they hear it: Test the performance and quality of your VoIP at
www.TestYourVoip.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 Oct  4 04:08:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09640
	for <sipping-web-archive@ietf.org>; Mon, 4 Oct 2004 04:08:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CEO2k-00032u-FG
	for sipping-web-archive@ietf.org; Mon, 04 Oct 2004 04:18:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CENsL-0005ZU-MT; Mon, 04 Oct 2004 04:07:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CENlG-000481-8b
	for sipping@megatron.ietf.org; Mon, 04 Oct 2004 03:59:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09163
	for <sipping@ietf.org>; Mon, 4 Oct 2004 03:59:55 -0400 (EDT)
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 1CENuI-0001kT-Mc
	for sipping@ietf.org; Mon, 04 Oct 2004 04:09:19 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 04 Oct 2004 01:06:43 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i947xMEE008166;
	Mon, 4 Oct 2004 00:59:22 -0700 (PDT)
Received: from [127.0.0.1] (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id AXR46776;
	Mon, 4 Oct 2004 01:01:25 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v619)
To: sipping (E-mail) <sipping@ietf.org>
Message-Id: <64FC3298-15DB-11D9-A60F-0003938AF740@cisco.com>
From: Rohan Mahy <rohan@cisco.com>
Date: Mon, 4 Oct 2004 16:00:02 +0800
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 1.1 (+)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Rohan Mahy <rohan@ekabal.com>
Subject: [Sipping] New contact and availability info for Rohan Mahy
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="===============1186582363=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024


--===============1186582363==
Content-Type: multipart/alternative; boundary=Apple-Mail-33-458001456


--Apple-Mail-33-458001456
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

Hello Everyone,

My last day at Cisco is October 8th.  I will be starting a new position 
at Airespace on November 1st. In the interim, you can contact me at the 
following email address:

	r o h a n ( a t ) e k a b a l ( d o t ) c o m

Please also be aware that I will be traveling in Guatemala from October 
12 till October 27 (Note that this period includes both draft 
deadlines).  I will be only checking email irregularly during this 
time.

See you all in Washington, DC.

many thanks,
-rohan


--Apple-Mail-33-458001456
Content-Type: text/enriched;
	charset=US-ASCII
Content-Transfer-Encoding: 7bit

<fontfamily><param>Helvetica</param>Hello Everyone,


My last day at Cisco is October 8th.  I will be starting a new
position at Airespace on November 1st. In the interim, you can contact
me at the following email address:


	r o h a n ( a t ) e k a b a l ( d o t ) c o m


Please also be aware that I will be traveling in Guatemala from
October 12 till October 27 (Note that this period includes both draft
deadlines).  I will be only checking email irregularly during this
time.


See you all in Washington, DC.


many thanks,

-rohan

</fontfamily>


--Apple-Mail-33-458001456--



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




From sipping-bounces@ietf.org  Tue Oct  5 11:29: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 LAA07785
	for <sipping-web-archive@ietf.org>; Tue, 5 Oct 2004 11:29:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CErPd-0005q6-EE
	for sipping-web-archive@ietf.org; Tue, 05 Oct 2004 11:39:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CErEZ-0000PO-Jl; Tue, 05 Oct 2004 11:28:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEr8p-00087z-AE
	for sipping@megatron.ietf.org; Tue, 05 Oct 2004 11:22:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07301
	for <sipping@ietf.org>; Tue, 5 Oct 2004 11:22:13 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CErI5-0004fy-Ur
	for sipping@ietf.org; Tue, 05 Oct 2004 11:31:53 -0400
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 i95FLYR12952; Tue, 5 Oct 2004 11:21:34 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <TS1DXD6C>; Tue, 5 Oct 2004 11:21:31 -0400
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB022C4369@zrc2hxm1.corp.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] Continuation of discussion on draft-elwell-sipping-
	redirection-re	ason
Date: Tue, 5 Oct 2004 11:21:24 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 4d9ae72af46718088458d214998cc683
Cc: "'Elwell, John'" <john.elwell@siemens.com>,
        Francois Audet <audet@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0596918361=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: f460acdc4aacf7fc5e6f9bd32f8fd8c6

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.

--===============0596918361==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4AAEE.F99AC703"

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_01C4AAEE.F99AC703
Content-Type: text/plain

Hi all,
 
It's been awhile and there's been no further discussion on this thread, so
it appears that there is general consensus for the approach to define a new
"protocol" in the Reason Header with a new set of codes for redirection
scenarios.   This would require the Reason header in responses to be
captured in the History-Info.  
 
This does impact the current version of the History-Info draft as it
currently does not look at the Reason header when adding the Reason to its
entry, but rather uses only the SIP response codes to create a new reason
header.  I'll follow-up on the SIP list with the impact on the draft to
support the general concept of using the Reason header.
 
Regards,
Mary 

-----Original Message-----
From: Audet, Francois [SC100:9T51:EXCH] 
Sent: Friday, August 20, 2004 1:55 PM
To: 'Elwell, John'; 'sipping@ietf.org'
Subject: RE: [Sipping] Continuation of discussion on draft-elwell-sipping-
redirection-re ason



That's fine with me. Makes sense from a backward compatibility perspective 
too. 

> -----Original Message----- 
> From: Elwell, John [mailto:john.elwell@siemens.com
<mailto:john.elwell@siemens.com> ] 
> Sent: Friday, August 20, 2004 03:10 
> To: Audet, Francois [SC100:9T51:EXCH]; 'sipping@ietf.org' 
> Subject: RE: [Sipping] Continuation of discussion on 
> draft-elwell-sipping- redirection-re ason 
> 
> 
> Francois, 
> 
> I agree that is a problem that needs to be solved. The 
> relationship to my redirection-reason proposal is that a 
> redirection reason could be inserted somehow into the 3xx 
> response to indicate that it is a redirection in support of a 
> retarget (according the usage of this term in History-Info) 
> and therefore should result in the addition of a History-Info 
> entry (subject to other considerations such as privacy) in 
> the redirected INVITE request. Absence of this indication in 
> the 3xx response (or an explicit value) would imply normal 
> routing (case 2 in your example). 
> 
> Regards, 
> 
> John 
> 
> ________________________________ 
> 
> From: Francois Audet [mailto:audet@nortelnetworks.com
<mailto:audet@nortelnetworks.com> ] 
> Sent: 19 August 2004 02:38 
> To: 'sipping@ietf.org' 
> Cc: 'Elwell, John' 
> Subject: RE: [Sipping] Continuation of discussion on 
> draft-elwell-sipping- redirection-re ason 
> 
> 
> 
> At the San Diego meeting, I promised to described on the list the 
> 302 ambiguity issue. 
> 
> 1st scenario: 
> 
> In this scenario, Alice calls Victor Mann who is absent, and 
> his phones 
> forwards the call to his voicemail system at +1-408-555-1212. 
> 
> A Proxy server is used for routing. Call is routed to 
> sip:vm@blabla.com. 
> Victor has programmed Call forwarding on his phone 
> to forward it to his voicemail at sip:+14085551212@example.com. 
> Victor's phone responds to the INVITE with a 302 Moved temporarily, 
> with Contact: <sip:+14085551212@example.com>. I.e., Victor's phone 
> retargets the call to sip:+14085551212@example.com. Alice's 
> phone then 
> sends an INVITE to Victor's voicemail which will be received 
> interpreted by 
> the voicemail system. The INVITE will look like this: 
> 
> INVITE sip:+14085551212@example.com 
> From: Alice <sip:alice@example.com> 
> To: <sip:vm@blabla.com> 
> History-Info: <sip:vm@blabla.com?Reason=SIP;cause=302>;index=1, 
>               <sip:+14085551212@example.com>;index=2 
> ... 
> 
> 
> 2nd scenario: 
> 
> In this scenario, Alice calls directly her voicemail system. 
> 
> A Redirect server is used for routing. In this case, the voicemail 
> system's address of record is sip:vm@blabla.com. This address is 
> currently routed to a PSTN address +1-408-555-1212 where the 
> legacy voicemail system resides. 
> 
> The redirect server responds with a 302 Moved temporarily, 
> with Contact: 
> <sip:+14085551212@example.com>. This is NOT a retarget in a 
> call forwarding 
> sense, but simple routing with a redirect server. Alice's 
> phone then sends 
> an INVITE to the voicemail system. The INVITE will look like this: 
> 
> INVITE sip:+14085551212@example.com 
> From: Alice <sip:alice@example.com> 
> To: <sip:vm@blabla.com> 
> History-Info: <sip:vm@blabla.com?Reason=SIP;cause=302>;index=1, 
>               <sip:+14085551212@example.com>;index=2 
>                    
>            
> In the two cases, the INVITEs are exaclty the same (including 
> History-Info). 
> 
> 
> However, in the first example, the voicemail system is supposed to 
> let Alice LEAVE a message in Victor Mann's mailbox and in the 
> second case, 
> it is supposed to let Alice RETRIEVE her messages. 
> 
> The 302 Reason is ambiguous in this case because it doesn't 
> distinguish 
> between routing (with a redirect server) and retargeting. 
> 
> Note that the problem does NOT occur with a proxy server: 
> only with a redirect 
> server. It will result in inconsistent behavior between 
> networks where a proxy is 
> used and networks where a redirect server is used for call routing. 
> 
> Of course, this is just an example. Similar issues will occur if one 
> is trying to carryover retargetting/redirection information 
> into the PSTN. 
> Similar issues will also occur for any type of service which 
> have different 
> behaviors depending if the call was retargeted or not (e.g., 
> IVR systems). 
> 
> 
> > -----Original Message----- 
> > From: Elwell, John [mailto:john.elwell@siemens.com
<mailto:john.elwell@siemens.com> ] 
> > Sent: Tuesday, August 17, 2004 09:51 
> > To: 'sipping@ietf.org' 
> > Subject: [Sipping] Continuation of discussion on 
> > draft-elwell-sipping-redirection-re ason 
> > 
> > 
> > At the IETF60 SIPPING meeting different opinions were 
> > expressed about the value of enhancing the repertoire of 
> > reasons for retargeting/redirection, as proposed in the 
> > draft. I would like to solicit more opinions on the following 
> > questions: 
> 
> 
> _______________________________________________ 
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
<https://www1.ietf.org/mailman/listinfo/sipping>  
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current sip 
> Use sip@ietf.org for new developments of core SIP 
> 


------_=_NextPart_001_01C4AAEE.F99AC703
Content-Type: text/html

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

<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>Hi 
all,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>It's 
been awhile and there's been no further discussion on this thread, so it appears 
that there is general consensus for the approach to define a <FONT size=2>new 
"protocol" in the Reason Header with a new set of codes</FONT> for redirection 
scenarios. &nbsp; This would require the Reason header in responses to be 
captured in the History-Info.&nbsp; </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>This 
does impact the current version of the History-Info draft as it currently does 
not look at the Reason header when adding the Reason to its entry, but rather 
uses only the SIP response codes to create a new reason header.&nbsp; I'll 
follow-up on the SIP list with the impact on the draft to support the general 
concept of using the Reason header.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT><FONT face=Arial color=#0000ff 
size=2><SPAN class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN lang=en-us><FONT face=Arial><FONT color=#0000ff size=2><SPAN 
class=496282518-28092004>Regards,</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN lang=en-us><FONT face=Arial><FONT size=2><SPAN 
class=496282518-28092004></SPAN><FONT 
color=#0000ff>Mary</FONT></FONT></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Audet, Francois 
  [SC100:9T51:EXCH] <BR><B>Sent:</B> Friday, August 20, 2004 1:55 
  PM<BR><B>To:</B> 'Elwell, John'; 'sipping@ietf.org'<BR><B>Subject:</B> RE: 
  [Sipping] Continuation of discussion on draft-elwell-sipping- redirection-re 
  ason<BR><BR></FONT></DIV>
  <P><FONT size=2>That's fine with me. Makes sense from a backward compatibility 
  perspective</FONT> <BR><FONT size=2>too.</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Elwell, John [<A 
  href="mailto:john.elwell@siemens.com">mailto:john.elwell@siemens.com</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: Friday, August 20, 2004 03:10</FONT> 
  <BR><FONT size=2>&gt; To: Audet, Francois [SC100:9T51:EXCH]; 
  'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] 
  Continuation of discussion on </FONT><BR><FONT size=2>&gt; 
  draft-elwell-sipping- redirection-re ason</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Francois,</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I agree that is a problem 
  that needs to be solved. The </FONT><BR><FONT size=2>&gt; relationship to my 
  redirection-reason proposal is that a </FONT><BR><FONT size=2>&gt; redirection 
  reason could be inserted somehow into the 3xx </FONT><BR><FONT size=2>&gt; 
  response to indicate that it is a redirection in support of a </FONT><BR><FONT 
  size=2>&gt; retarget (according the usage of this term in History-Info) 
  </FONT><BR><FONT size=2>&gt; and therefore should result in the addition of a 
  History-Info </FONT><BR><FONT size=2>&gt; entry (subject to other 
  considerations such as privacy) in </FONT><BR><FONT size=2>&gt; the redirected 
  INVITE request. Absence of this indication in </FONT><BR><FONT size=2>&gt; the 
  3xx response (or an explicit value) would imply normal </FONT><BR><FONT 
  size=2>&gt; routing (case 2 in your example).</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Regards,</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; John</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; ________________________________</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; From: Francois Audet [<A 
  href="mailto:audet@nortelnetworks.com">mailto:audet@nortelnetworks.com</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: 19 August 2004 02:38</FONT> <BR><FONT 
  size=2>&gt; To: 'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; Cc: 'Elwell, 
  John'</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] Continuation of 
  discussion on </FONT><BR><FONT size=2>&gt; draft-elwell-sipping- 
  redirection-re ason</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; At the San Diego 
  meeting, I promised to described on the list the </FONT><BR><FONT size=2>&gt; 
  302 ambiguity issue. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  1st scenario: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; In 
  this scenario, Alice calls Victor Mann who is absent, and </FONT><BR><FONT 
  size=2>&gt; his phones </FONT><BR><FONT size=2>&gt; forwards the call to his 
  voicemail system at +1-408-555-1212. </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; A Proxy server is used for routing. Call is 
  routed to </FONT><BR><FONT size=2>&gt; sip:vm@blabla.com. </FONT><BR><FONT 
  size=2>&gt; Victor has programmed Call forwarding on his phone 
  </FONT><BR><FONT size=2>&gt; to forward it to his voicemail at 
  sip:+14085551212@example.com. </FONT><BR><FONT size=2>&gt; Victor's phone 
  responds to the INVITE with a 302 Moved temporarily, </FONT><BR><FONT 
  size=2>&gt; with Contact: &lt;sip:+14085551212@example.com&gt;. I.e., Victor's 
  phone </FONT><BR><FONT size=2>&gt; retargets the call to 
  sip:+14085551212@example.com. Alice's </FONT><BR><FONT size=2>&gt; phone then 
  </FONT><BR><FONT size=2>&gt; sends an INVITE to Victor's voicemail which will 
  be received </FONT><BR><FONT size=2>&gt; interpreted by </FONT><BR><FONT 
  size=2>&gt; the voicemail system. The INVITE will look like this: 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; INVITE 
  sip:+14085551212@example.com </FONT><BR><FONT size=2>&gt; From: Alice 
  &lt;sip:alice@example.com&gt; </FONT><BR><FONT size=2>&gt; To: 
  &lt;sip:vm@blabla.com&gt; </FONT><BR><FONT size=2>&gt; History-Info: 
  &lt;sip:vm@blabla.com?Reason=SIP;cause=302&gt;;index=1, </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;sip:+14085551212@example.com&gt;;index=2 </FONT><BR><FONT size=2>&gt; ... 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; 2nd scenario: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; In this scenario, Alice calls directly her voicemail system. 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; A Redirect server is 
  used for routing. In this case, the voicemail </FONT><BR><FONT size=2>&gt; 
  system's address of record is sip:vm@blabla.com. This address is 
  </FONT><BR><FONT size=2>&gt; currently routed to a PSTN address 
  +1-408-555-1212 where the </FONT><BR><FONT size=2>&gt; legacy voicemail system 
  resides. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; The 
  redirect server responds with a 302 Moved temporarily, </FONT><BR><FONT 
  size=2>&gt; with Contact: </FONT><BR><FONT size=2>&gt; 
  &lt;sip:+14085551212@example.com&gt;. This is NOT a retarget in a 
  </FONT><BR><FONT size=2>&gt; call forwarding </FONT><BR><FONT size=2>&gt; 
  sense, but simple routing with a redirect server. Alice's </FONT><BR><FONT 
  size=2>&gt; phone then sends </FONT><BR><FONT size=2>&gt; an INVITE to the 
  voicemail system. The INVITE will look like this: </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; INVITE sip:+14085551212@example.com 
  </FONT><BR><FONT size=2>&gt; From: Alice &lt;sip:alice@example.com&gt; 
  </FONT><BR><FONT size=2>&gt; To: &lt;sip:vm@blabla.com&gt; </FONT><BR><FONT 
  size=2>&gt; History-Info: 
  &lt;sip:vm@blabla.com?Reason=SIP;cause=302&gt;;index=1, </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;sip:+14085551212@example.com&gt;;index=2 </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </FONT><BR><FONT size=2>&gt; In the two cases, the INVITEs are exaclty the 
  same (including </FONT><BR><FONT size=2>&gt; History-Info).</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; However, 
  in the first example, the voicemail system is supposed to </FONT><BR><FONT 
  size=2>&gt; let Alice LEAVE a message in Victor Mann's mailbox and in the 
  </FONT><BR><FONT size=2>&gt; second case, </FONT><BR><FONT size=2>&gt; it is 
  supposed to let Alice RETRIEVE her messages. </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; The 302 Reason is ambiguous in this case because 
  it doesn't </FONT><BR><FONT size=2>&gt; distinguish </FONT><BR><FONT 
  size=2>&gt; between routing (with a redirect server) and retargeting. 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Note that the 
  problem does NOT occur with a proxy server: </FONT><BR><FONT size=2>&gt; only 
  with a redirect </FONT><BR><FONT size=2>&gt; server. It will result in 
  inconsistent behavior between </FONT><BR><FONT size=2>&gt; networks where a 
  proxy is </FONT><BR><FONT size=2>&gt; used and networks where a redirect 
  server is used for call routing. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Of course, this is just an example. Similar issues will occur if 
  one </FONT><BR><FONT size=2>&gt; is trying to carryover 
  retargetting/redirection information </FONT><BR><FONT size=2>&gt; into the 
  PSTN. </FONT><BR><FONT size=2>&gt; Similar issues will also occur for any type 
  of service which </FONT><BR><FONT size=2>&gt; have different </FONT><BR><FONT 
  size=2>&gt; behaviors depending if the call was retargeted or not (e.g., 
  </FONT><BR><FONT size=2>&gt; IVR systems). </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Elwell, John [<A 
  href="mailto:john.elwell@siemens.com">mailto:john.elwell@siemens.com</A>] 
  </FONT><BR><FONT size=2>&gt; &gt; Sent: Tuesday, August 17, 2004 09:51 
  </FONT><BR><FONT size=2>&gt; &gt; To: 'sipping@ietf.org' </FONT><BR><FONT 
  size=2>&gt; &gt; Subject: [Sipping] Continuation of discussion on 
  </FONT><BR><FONT size=2>&gt; &gt; draft-elwell-sipping-redirection-re ason 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; At the IETF60 SIPPING meeting different 
  opinions were</FONT> <BR><FONT size=2>&gt; &gt; expressed about the value of 
  enhancing the repertoire of </FONT><BR><FONT size=2>&gt; &gt; reasons for 
  retargeting/redirection, as proposed in the </FONT><BR><FONT size=2>&gt; &gt; 
  draft. I would like to solicit more opinions on the following </FONT><BR><FONT 
  size=2>&gt; &gt; questions: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  Sipping mailing list&nbsp; <A 
  href="https://www1.ietf.org/mailman/listinfo/sipping" 
  target=_blank>https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; This list is for NEW development of the application of 
  SIP</FONT> <BR><FONT size=2>&gt; Use sip-implementors@cs.columbia.edu for 
  questions on current sip</FONT> <BR><FONT size=2>&gt; Use sip@ietf.org for new 
  developments of core SIP</FONT> <BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4AAEE.F99AC703--


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



From sipping-bounces@ietf.org  Tue Oct  5 16:27: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 QAA07534
	for <sipping-web-archive@ietf.org>; Tue, 5 Oct 2004 16:27:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CEw44-0008Qk-LM
	for sipping-web-archive@ietf.org; Tue, 05 Oct 2004 16:37:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEvjJ-00077V-9S; Tue, 05 Oct 2004 16:16:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEvKM-00009j-7u
	for sipping@megatron.ietf.org; Tue, 05 Oct 2004 15:50:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01653
	for <sipping@ietf.org>; Tue, 5 Oct 2004 15:50:24 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEvTg-0001ME-MM
	for sipping@ietf.org; Tue, 05 Oct 2004 16:00:06 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 05 Oct 2004 15:49:54 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i95Jnpr5007792; 
	Tue, 5 Oct 2004 15:49:51 -0400 (EDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMB48641; Tue, 5 Oct 2004 15:49:50 -0400 (EDT)
Message-ID: <4162FADE.40208@cisco.com>
Date: Tue, 05 Oct 2004 15:49:50 -0400
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: "Hedayat, Kaynam" <khedayat@brixnet.com>
Subject: Re: [Sipping] New internet draft on media loopback
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

I support the functionality represented by this draft. A few comments:

- this seems to be structured for consideration as a draft in the
   SIP WG. But the content is all about SDP and offer/answer. As such,
   I think it makes more sense to target this to the MMUSIC WG. This
   would mean removing anything specific to SIP - which should be easy
   because there is little or nothing here that needs to be specific
   to SIP.

   A companion draft in the SIP (or SIPPING) WG could be developed to
   specify sip specific usage rules and guidelines.

- Section 6.3 says "The loopback-source attribute can only appear in an
   offer", and 6.4 says "The loopback-mirror attribute can only appear in
   an answer". There seems no reason for this restriction. All that is
   required is that a loopback-source offer be answered by a
   loopback-mirror and visa versa. Perhaps it is more likely that the
   source be offered and the mirror answered, but the opposite clearly
   has meaning. (I.e. please test me.) Of course it may be harder for a
   testee to find a tester than the converse, but that is a usage issue.

   Note also that section 6.5 mentions "In cases where the offer contains
   the loopback-mirror attribute", implying that support for this has
   been considered.

- section 6.5 (typo): "one code" should be "one codec".

- section 9.4: is there a way to indicate support for both loopback
   types, and/or for both loopback-source and loopback-mirror? It would
   be a good thing to do. I think it should be possible to tweak things
   so it is.

- section 11 says: "...given that it is recommended that the user is not
   alerted for calls that only have loopback media modes..." but I can
   find no such recommendation. I think this would relate back to the
   partitioning of mmusic and sip aspects into separate drafts. Alerting
   is a sip consideration.

	Paul


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


From sipping-bounces@ietf.org  Tue Oct  5 17:09: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 RAA12400
	for <sipping-web-archive@ietf.org>; Tue, 5 Oct 2004 17:09:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CEwi4-0005dk-Ii
	for sipping-web-archive@ietf.org; Tue, 05 Oct 2004 17:19:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEwSm-0000V6-7R; Tue, 05 Oct 2004 17:03:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEwRg-0000Jz-Hh
	for sipping@megatron.ietf.org; Tue, 05 Oct 2004 17:02:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12140
	for <sipping@ietf.org>; Tue, 5 Oct 2004 17:02:01 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEwb1-0004Xt-Dc
	for sipping@ietf.org; Tue, 05 Oct 2004 17:11:44 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 05 Oct 2004 17:01:32 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i95K1PEF016408; 
	Tue, 5 Oct 2004 16:01:27 -0400 (EDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMB55565; Tue, 5 Oct 2004 17:01:27 -0400 (EDT)
Message-ID: <41630BA7.6010306@cisco.com>
Date: Tue, 05 Oct 2004 17:01:27 -0400
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: hisham.khartabil@nokia.com
Subject: Re: [Sipping] GRUU support in reg event package
References: <2038BCC78B1AD641891A0D1AE133DBB7023EEB6A@esebe019.ntc.nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
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: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit

Hisham,

I realized I never responded to your points here.

	Paul

hisham.khartabil@nokia.com wrote:
> 
>>Jonathan has expressed interest in including info on any Path header 
>>that might be associated with a Contact.
>>
>>- Do you think info on the Path header should be returned
>>   in reg event notifications?
> 
> Well, the Path header contents are useless to the client. I don't know what advantages this will gather.

There is potential use for this by a client, although unnecessary when 
gruus are available.

If one uses the reg event package to learn about registrations, and if 
this provided Path header info, then that could be used to format a 
request so it traverses the same path that a request addressed to the 
AOR would, but supplying the contact address rather than having the home 
proxy pick it. This would permit reaching a contacts that isn't directly 
reachable from the sender.

Suppose the AOR is sip:alice@atlanta.com,
and the contact is sip:alice@alice-pc.private.atlanta.com,
and there is an associated Path with sip:sbc.atlanta.com;lr

Then a subscriber could use this information to format a request like:

	INVITE sip:alice@alice-pc.private.atlanta.com
	Route: sip:atlanta.com;lr
	Route: sip:sbc.atlanta.com;lr
	...

This would have a decent chance of actually making it to Alice's pc.
(Admittedly this is a stretch, and there are other ways to achieve the 
same thing.)

>>At them moment I am not aware of any other registrar state to be 
>>reported, but feel free to point out something I have forgotten.
>>
>>- Are there other extensions to the reg event package that you would 
>>like to see?
> 
> Maybe service-route header? More useful to the client that the Path headers anyway.

The service-route is only useful to the register client, and is provided 
to it via the register. This client doesn't need to subscribe to the reg 
event package to get this information. And the information isn't useful 
to any other client.

So I find reporting on Path at least potentially useful, while reporting 
on Service-Route doesn't seem to be.

> I have a further comment about this draft:
> 
> I think it is a good idea for the draft stress that this is an extension and how a client should behave when it receives the notifications with XML elements it does not understand (ignore them, for example). A section on registrar behaviour is beneficial as well.

OK, that seems reasonable.

	Thanks,
	Paul


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


From sipping-bounces@ietf.org  Tue Oct  5 20:06: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 UAA28012
	for <sipping-web-archive@ietf.org>; Tue, 5 Oct 2004 20:06:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CEzTD-0005x4-2c
	for sipping-web-archive@ietf.org; Tue, 05 Oct 2004 20:15:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEzCo-0005XA-Ph; Tue, 05 Oct 2004 19:58:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEyz1-0000tf-Vg
	for sipping@megatron.ietf.org; Tue, 05 Oct 2004 19:44:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24764
	for <sipping@ietf.org>; Tue, 5 Oct 2004 19:44:36 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.200] helo=mproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEz8P-0002Ex-Mx
	for sipping@ietf.org; Tue, 05 Oct 2004 19:54:22 -0400
Received: by mproxy.gmail.com with SMTP id 79so356030rnl
	for <sipping@ietf.org>; Tue, 05 Oct 2004 16:44:33 -0700 (PDT)
Received: by 10.38.1.71 with SMTP id 71mr808072rna;
	Tue, 05 Oct 2004 16:44:32 -0700 (PDT)
Received: by 10.38.164.71 with HTTP; Tue, 5 Oct 2004 16:44:32 -0700 (PDT)
Message-ID: <a9994e9404100516442edbe5ba@mail.gmail.com>
Date: Tue, 5 Oct 2004 19:44:32 -0400
From: Arjun Roychowdhury <arjunrc@gmail.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] New internet draft on media loopback
In-Reply-To: <4162FADE.40208@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>
	<4162FADE.40208@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
Cc: "sipping@ietf.org" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Arjun Roychowdhury <arjunrc@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.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit

On Tue, 05 Oct 2004 15:49:50 -0400, Paul Kyzivat <pkyzivat@cisco.com> wrote:
> I support the functionality represented by this draft. A few comments:
> 
> - this seems to be structured for consideration as a draft in the
>   SIP WG. But the content is all about SDP and offer/answer. As such,
>   I think it makes more sense to target this to the MMUSIC WG. This
>   would mean removing anything specific to SIP - which should be easy
>   because there is little or nothing here that needs to be specific
>   to SIP.

I like the partitioning idea. One of the ideas that we discussed was
to _possibly_ later develop another draft that would be related to
identification of "test" calls in general and have this media draft
refer the "test" draft, since media-loopback is essentially a
specialized test scenario.
Speaking for myself, I like the idea of completely disassociating the
current draft from SIP and developing the additional SIP draft with
guidelines and possibly the other ideas described above.

I think Kaynam has already posted this across to mmusic in the
meantime. Do we need to remove all references to SIP for this draft to
be considered in mmusic ?

> - Section 6.3 says "The loopback-source attribute can only appear in an
>   offer", and 6.4 says "The loopback-mirror attribute can only appear in
>   an answer". There seems no reason for this restriction. All that is
>   required is that a loopback-source offer be answered by a
>   loopback-mirror and visa versa. Perhaps it is more likely that the
>   source be offered and the mirror answered, but the opposite clearly
>   has meaning. (I.e. please test me.) Of course it may be harder for a
>   testee to find a tester than the converse, but that is a usage issue.

> 
>   Note also that section 6.5 mentions "In cases where the offer contains
>   the loopback-mirror attribute", implying that support for this has
>   been considered.

Oops - I think was a remnant of an earlier internal debate we had
where one of the older versions of the draft had the ability to switch
source and mirror only in cases of reINVITEs coming from the reverse
side (example A invites B, then B decides to re-INVITE to extend the
session, the B sends mirror in the offer to keep the flow of testing
intact - anyway we discarded that idea as leading to complexity).

Specific to your note on allowing mirror in the offer, I don't beleive
there is any technical reason not to allow it, but just that I am not
sure how common a 'please test me' requirement is.

> 
> - section 6.5 (typo): "one code" should be "one codec".
> 
> - section 9.4: is there a way to indicate support for both loopback
>   types, and/or for both loopback-source and loopback-mirror? It would
>   be a good thing to do. I think it should be possible to tweak things
>   so it is.

Yes - I think it should be possible for a UA to return both back. I
would think this makes sense especially if the other authors also
believe allowing a 'mirror' in the offer is a good idea.

> 
> - section 11 says: "...given that it is recommended that the user is not
>   alerted for calls that only have loopback media modes..." but I can
>   find no such recommendation. I think this would relate back to the
>   partitioning of mmusic and sip aspects into separate drafts. Alerting
>   is a sip consideration.

The reccomendation is part of 10.2 UAS guidelines

regds
arjun
-- 
Arjun Roychowdhury

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct  5 20:06:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28274
	for <sipping-web-archive@ietf.org>; Tue, 5 Oct 2004 20:06:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CEzTu-00060j-O3
	for sipping-web-archive@ietf.org; Tue, 05 Oct 2004 20:16:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CEzCu-0005dv-Hq; Tue, 05 Oct 2004 19:59:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CEyze-0001Dv-TB
	for sipping@megatron.ietf.org; Tue, 05 Oct 2004 19:45:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24879
	for <sipping@ietf.org>; Tue, 5 Oct 2004 19:45:15 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEz92-0002Iu-GZ
	for sipping@ietf.org; Tue, 05 Oct 2004 19:55:01 -0400
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i95NjFW17051; Wed, 6 Oct 2004 02:45:15 +0300 (EET DST)
X-Scanned: Wed, 6 Oct 2004 02:45:02 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i95Nj2d2014884;
	Wed, 6 Oct 2004 02:45:02 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00nNcR5Z; Wed, 06 Oct 2004 02:44:10 EEST
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
	i95Ni9Y17505; Wed, 6 Oct 2004 02:44:09 +0300 (EET DST)
Received: from esebe003.NOE.Nokia.com ([172.21.138.39]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Oct 2004 02:44:06 +0300
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by
	esebe003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Oct 2004 02:44:05 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] GRUU support in reg event package
Date: Wed, 6 Oct 2004 02:44:06 +0300
Message-ID: <5816828233DEFA41807A6CFDFDF2343C08B6A5@esebe056.ntc.nokia.com>
Thread-Topic: [Sipping] GRUU support in reg event package
Thread-Index: AcSrHpSDoj2/3HB5QoOmr+2rv8RH9gAFaShw
To: <pkyzivat@cisco.com>
X-OriginalArrivalTime: 05 Oct 2004 23:44:05.0724 (UTC)
	FILETIME=[336749C0:01C4AB35]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: quoted-printable



> -----Original Message-----
> From: ext Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: 06.October.2004 00:01
> To: Khartabil Hisham (Nokia-TP-MSW/Helsinki)
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] GRUU support in reg event package
>=20
>=20
> Hisham,
>=20
> I realized I never responded to your points here.
>=20
> 	Paul
>=20
> hisham.khartabil@nokia.com wrote:
> >=20
> >>Jonathan has expressed interest in including info on any=20
> Path header=20
> >>that might be associated with a Contact.
> >>
> >>- Do you think info on the Path header should be returned
> >>   in reg event notifications?
> >=20
> > Well, the Path header contents are useless to the client. I=20
> don't know what advantages this will gather.
>=20
> There is potential use for this by a client, although=20
> unnecessary when=20
> gruus are available.
>=20
> If one uses the reg event package to learn about=20
> registrations, and if=20
> this provided Path header info, then that could be used to format a=20
> request so it traverses the same path that a request addressed to the=20
> AOR would, but supplying the contact address rather than=20
> having the home=20
> proxy pick it. This would permit reaching a contacts that=20
> isn't directly=20
> reachable from the sender.
>=20
> Suppose the AOR is sip:alice@atlanta.com,
> and the contact is sip:alice@alice-pc.private.atlanta.com,
> and there is an associated Path with sip:sbc.atlanta.com;lr
>=20
> Then a subscriber could use this information to format a request like:
>=20
> 	INVITE sip:alice@alice-pc.private.atlanta.com
> 	Route: sip:atlanta.com;lr
> 	Route: sip:sbc.atlanta.com;lr
> 	...

This is a stretch, since I doubt that anyone besides the owner would =
subscribe or should be allowed to such event package. Path headers =
reveal information about the network architecture. That may be a =
security problem.

/Hisham

>=20
> This would have a decent chance of actually making it to Alice's pc.
> (Admittedly this is a stretch, and there are other ways to=20
> achieve the=20
> same thing.)
>=20
> >>At them moment I am not aware of any other registrar state to be=20
> >>reported, but feel free to point out something I have forgotten.
> >>
> >>- Are there other extensions to the reg event package that=20
> you would=20
> >>like to see?
> >=20
> > Maybe service-route header? More useful to the client that=20
> the Path headers anyway.
>=20
> The service-route is only useful to the register client, and=20
> is provided=20
> to it via the register. This client doesn't need to subscribe=20
> to the reg=20
> event package to get this information. And the information=20
> isn't useful=20
> to any other client.
>=20
> So I find reporting on Path at least potentially useful,=20
> while reporting=20
> on Service-Route doesn't seem to be.
>=20
> > I have a further comment about this draft:
> >=20
> > I think it is a good idea for the draft stress that this is=20
> an extension and how a client should behave when it receives=20
> the notifications with XML elements it does not understand=20
> (ignore them, for example). A section on registrar behaviour=20
> is beneficial as well.
>=20
> OK, that seems reasonable.
>=20
> 	Thanks,
> 	Paul
>=20
>=20

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


From sipping-bounces@ietf.org  Wed Oct  6 09:30:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24317
	for <sipping-web-archive@ietf.org>; Wed, 6 Oct 2004 09:30:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFC1j-0002Le-J2
	for sipping-web-archive@ietf.org; Wed, 06 Oct 2004 09:40:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFBqP-0006UN-HX; Wed, 06 Oct 2004 09:28:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFBmE-0005fD-2I
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 09:24:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23665
	for <sipping@ietf.org>; Wed, 6 Oct 2004 09:24:16 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFBvh-0001t6-BS
	for sipping@ietf.org; Wed, 06 Oct 2004 09:34:07 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0I5500D8IZSFIF@dns1.cselt.it> for sipping@ietf.org; Wed,
	06 Oct 2004 15:21:51 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Wed, 06 Oct 2004 15:25:32 +0200
Date: Wed, 06 Oct 2004 15:23:41 +0200
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] profile data for SIP policies
To: Volker Hilt <volkerh@bell-labs.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D00966A0@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] profile data for SIP policies
Thread-Index: AcSrp6ZH0rhOcgEtTfOaZG9Km5TrIw==
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 06 Oct 2004 13:25:32.0578 (UTC)
	FILETIME=[F4A86020:01C4ABA7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: quoted-printable

Volker,
In response to your mail, here are some items that I think should be =
considered in the I-D:

1. Concerning the policies:

- It should be specified how to solve the "superposition" of the same =
piece of profile information. For example, if both the local profile and =
the user profile specify the transport protocol to be used, the UA =
should know which information to set in priority. In most cases, the =
policy applied to a specific user might restrict the policy applied to =
the whole domain.

- It could be useful to combine some configuration settings to form a =
specific configuration set. The UA could thus be provided with several =
configuration sets, each with different values, with the configuration =
sets ordered by priority. Then, depending on which configuration set the =
UA was able to apply, the UA would be provided with a specific behavior. =
This involves the specification of conditions within the profile data =
policies, for example to force some codec to be used in concordance to =
an outbound proxy (acting as RTP proxy/transcoder), or when trying to =
set a codec from a list, some codecs may require the device to point =
toward such a proxy while others may use a different one.

- In the case where the UA, for some reason, is not able to set any of =
the settings provided, the profile data should include a default =
behaviour, for example to perform some UI alert or send a network alert.


2. Concerning the different aspects of profile information:

- The following data sets would be useful:

  . An "outbound_proxy" data set, for both the local profile and the =
user profile

  . A "NAT_address" data set, for the local profile (in the case calls =
are made through a NAT)

  . A "credential" data set including the user's realm/userID/passToken, =
for the user profile=20

- Extensibility for new features within each piece of profile =
information should be provided, e.g. the "media" element could be =
extended with a child element to specify the number of voice frame =
packets to be transmitted.

Thanks,
Gabrielle

> -----Original Message-----
> From: Volker Hilt [mailto:volkerh@bell-labs.com]
> Sent: venerd=EC 1 ottobre 2004 23.56
> To: Simonetti Gabrielle
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] profile data for SIP policies
>=20
>=20
> Simonetti Gabrielle wrote:
> > Hi,
> > Some questions on draft-ietf-sipping-session-indep-policy-00:
> > - Has the XML schema already been defined for the
> >   application/session-policy+xml type (section 4.2 of the draft)?
>=20
> We are currently revising the draft (including the schema)=20
> and plan to=20
> submit a new version for the upcoming meeting. Please let me=20
> know if you=20
> have any requirements or items you would like to see in the draft.
>=20
> > - How does the policy document relate to the Profile Delivery
> >   Framework: how should it be included in the device=20
> configuration data?
> >   Should it be part of the Local Profile, of the User=20
> Profile? Or should
> >   it be an independent document?
>=20
> The two drafts clearly need to be aligned (which is what we are=20
> currently doing). The goal is that policies and device=20
> configuration can=20
> co-exist in the same document.
>=20
> The separation of the profile types (user, device, local,=20
> application)=20
> enables multiple entities to manage profile data. It does not=20
> determine=20
> the profile content or the XML schema used. Thus, an XML=20
> schema could be=20
> used for local profiles and for user profiles.
>=20
> > - How does the policy document relate to the general configuration
> >   parameters?
>=20
> Policies are part of the configuration information.
>=20
> > - Actually, are the Local Profile data and User Profile data being
> >   standardized? Will a draft come out with schemas for this data?
> >=20
> Again, I don't think there will be a schema for local or user profile=20
> data. There will be schemas for different aspects of profile=20
> information=20
> (e.g. media, SIP protocol, address books) which can be used in local,=20
> user, device, etc. profile types. Of course, not all schemas=20
> will make=20
> sense for every profile type.
>=20
> -- Volker
>=20
>=20




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

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

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


From sipping-bounces@ietf.org  Wed Oct  6 09:34: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 JAA24718
	for <sipping-web-archive@ietf.org>; Wed, 6 Oct 2004 09:34:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFC5Y-0002Zt-D8
	for sipping-web-archive@ietf.org; Wed, 06 Oct 2004 09:44:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFBqw-0006cm-J9; Wed, 06 Oct 2004 09:29:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFBnQ-0005z2-7P
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 09:25:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23788
	for <sipping@ietf.org>; Wed, 6 Oct 2004 09:25:30 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFBwv-0001vD-CP
	for sipping@ietf.org; Wed, 06 Oct 2004 09:35:21 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 06 Oct 2004 06:25:27 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i96DOwbV020039;
	Wed, 6 Oct 2004 06:24:58 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMB90165; Wed, 6 Oct 2004 09:24:57 -0400 (EDT)
Message-ID: <4163F229.6020101@cisco.com>
Date: Wed, 06 Oct 2004 09:24:57 -0400
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: hisham.khartabil@nokia.com
Subject: Re: [Sipping] GRUU support in reg event package
References: <5816828233DEFA41807A6CFDFDF2343C08B6A5@esebe056.ntc.nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
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: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit



hisham.khartabil@nokia.com wrote:
> 
>>>Well, the Path header contents are useless to the client. I 
>>don't know what advantages this will gather.
>>
>>There is potential use for this by a client, although 
>>unnecessary when gruus are available.
>>
>>If one uses the reg event package to learn about 
>>registrations, and if 
>>this provided Path header info, then that could be used to format a 
>>request so it traverses the same path that a request addressed to the 
>>AOR would, but supplying the contact address rather than 
>>having the home 
>>proxy pick it. This would permit reaching a contacts that 
>>isn't directly 
>>reachable from the sender.
>>
>>Suppose the AOR is sip:alice@atlanta.com,
>>and the contact is sip:alice@alice-pc.private.atlanta.com,
>>and there is an associated Path with sip:sbc.atlanta.com;lr
>>
>>Then a subscriber could use this information to format a request like:
>>
>>	INVITE sip:alice@alice-pc.private.atlanta.com
>>	Route: sip:atlanta.com;lr
>>	Route: sip:sbc.atlanta.com;lr
>>	...
> 
> 
> This is a stretch, since I doubt that anyone besides the owner would subscribe or should be allowed to such event package. Path headers reveal information about the network architecture. That may be a security problem.

Yes, it is true that not everybody is likely to be permitted to 
subscribe to this package. But the "owner" also includes agents working 
on behalf of the owner, and there may be several of these.

For instance, *all* the devices that register are agents of the owner. 
These act as "multiple line appearances" where the AOR is the "line". To 
provide the kind of user experience that is normally expected for 
multiple line appearances, each device needs to be aware of all the 
others and subscribe to the dialog event package at each of its peers. 
The 'reg' package is the most reliable way keep current about which 
peers exist.

And once a peer is discovered, a subscribe must be directed to that 
peer. The above is one way to achieve that.

Of course GRUU provides another way, and that is the counter-argument.

Another possible use case is when the "home proxy" is not collocated 
with the registrar. It may be that the proxy itself wants to use the reg 
event package to maintain its routing tables.

	Paul


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


From sipping-bounces@ietf.org  Wed Oct  6 10:57: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 KAA04295
	for <sipping-web-archive@ietf.org>; Wed, 6 Oct 2004 10:57:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFDNr-0008Ib-EL
	for sipping-web-archive@ietf.org; Wed, 06 Oct 2004 11:07:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFDAy-0003C7-NG; Wed, 06 Oct 2004 10:53:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFD8s-0002Uc-Vt
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 10:51:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03831
	for <sipping@ietf.org>; Wed, 6 Oct 2004 10:51:44 -0400 (EDT)
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 1CFDIO-0007tA-Kh
	for sipping@ietf.org; Wed, 06 Oct 2004 11:01:37 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 06 Oct 2004 07:58:55 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i96Ep4EG024575
	for <sipping@ietf.org>; Wed, 6 Oct 2004 07:51:12 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMB98339; Wed, 6 Oct 2004 10:51:03 -0400 (EDT)
Message-ID: <41640657.8010401@cisco.com>
Date: Wed, 06 Oct 2004 10:51:03 -0400
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
CC: "sipping@ietf.org" <sipping@ietf.org>
Subject: Re: [Sipping] New internet draft on media loopback
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>	
	<4162FADE.40208@cisco.com>
	<a9994e9404100516442edbe5ba@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
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: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: 7bit



Arjun Roychowdhury wrote:
 > On Tue, 05 Oct 2004 15:49:50 -0400, Paul Kyzivat <pkyzivat@cisco.com> 
wrote:
 >
 >>I support the functionality represented by this draft. A few comments:
 >>
 >>- this seems to be structured for consideration as a draft in the
 >>  SIP WG. But the content is all about SDP and offer/answer. As such,
 >>  I think it makes more sense to target this to the MMUSIC WG. This
 >>  would mean removing anything specific to SIP - which should be easy
 >>  because there is little or nothing here that needs to be specific
 >>  to SIP.
 >
 >
 > I like the partitioning idea. One of the ideas that we discussed was
 > to _possibly_ later develop another draft that would be related to
 > identification of "test" calls in general and have this media draft
 > refer the "test" draft, since media-loopback is essentially a
 > specialized test scenario.
 > Speaking for myself, I like the idea of completely disassociating the
 > current draft from SIP and developing the additional SIP draft with
 > guidelines and possibly the other ideas described above.
 >
 > I think Kaynam has already posted this across to mmusic in the
 > meantime. Do we need to remove all references to SIP for this draft to
 > be considered in mmusic ?

I defer to those more familiar with procedures in mmusic. But I think
they don't all have to be removed, but should be relegated to examples,
while leaving open the possibility that some other protocol might use
this. Essentially this is just an extension to RFC3264, so that would
probably be a good guideline to follow.

 >>- Section 6.3 says "The loopback-source attribute can only appear in an
 >>  offer", and 6.4 says "The loopback-mirror attribute can only appear in
 >>  an answer". There seems no reason for this restriction. All that is
 >>  required is that a loopback-source offer be answered by a
 >>  loopback-mirror and visa versa. Perhaps it is more likely that the
 >>  source be offered and the mirror answered, but the opposite clearly
 >>  has meaning. (I.e. please test me.) Of course it may be harder for a
 >>  testee to find a tester than the converse, but that is a usage issue.
 >
 >
 >>  Note also that section 6.5 mentions "In cases where the offer contains
 >>  the loopback-mirror attribute", implying that support for this has
 >>  been considered.
 >
 > Oops - I think was a remnant of an earlier internal debate we had
 > where one of the older versions of the draft had the ability to switch
 > source and mirror only in cases of reINVITEs coming from the reverse
 > side (example A invites B, then B decides to re-INVITE to extend the
 > session, the B sends mirror in the offer to keep the flow of testing
 > intact - anyway we discarded that idea as leading to complexity).
 >
 > Specific to your note on allowing mirror in the offer, I don't beleive
 > there is any technical reason not to allow it, but just that I am not
 > sure how common a 'please test me' requirement is.

It seems less likely. But why gratuitously exclude it when there is no
technical reason to do so?

 >>- section 6.5 (typo): "one code" should be "one codec".
 >>
 >>- section 9.4: is there a way to indicate support for both loopback
 >>  types, and/or for both loopback-source and loopback-mirror? It would
 >>  be a good thing to do. I think it should be possible to tweak things
 >>  so it is.
 >
 > Yes - I think it should be possible for a UA to return both back. I
 > would think this makes sense especially if the other authors also
 > believe allowing a 'mirror' in the offer is a good idea.

The trick here is that as things are currently structured, it would not
make sense to include both in an offer or answer. Yet the SDP returned
in response to an OPTIONS is supposed to be like what the UA would offer.

To fix this it may be necessary to actually allow the offering of both.
We can find current examples of how to do this that can be followed:

- for the loopback attribute, the strategy used for codecs in the m-line
    could be used - offer all that are supported, with the answerer
    picking. E.g.:

	offer:  a=loopback:rtp-pkt-loopback rtp-media-loopback
	answer: a=loopback:rtp-media-loopback

- for loopback-source/loopback-mirror, the strategy used for
    send/recv/sendrecv - add another value that means 'both', such
    as source-or-mirror. E.g.

	offer:  a=loopback-source-or-mirror
	answer: a=loopback-source

    This is a little ugly, but it needs to be understood as added
    alternatives to
               send/recv/sendrecv/inactive

    An alternative might be to divorce it from that family of
    directionality attributes. Make it a separate attribute to be
    used in conjunction with sendrecv. Something like:

	Offer:  a=sendrecv
	        a=loopback-role: source mirror

	answer: a=sendrecv
	        a=loopback-role: mirror

 >>- section 11 says: "...given that it is recommended that the user is not
 >>  alerted for calls that only have loopback media modes..." but I can
 >>  find no such recommendation. I think this would relate back to the
 >>  partitioning of mmusic and sip aspects into separate drafts. Alerting
 >>  is a sip consideration.
 >
 > The reccomendation is part of 10.2 UAS guidelines

Sorry - I looked but still missed it.

	Paul



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


From sipping-bounces@ietf.org  Wed Oct  6 12:27: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 MAA10432
	for <sipping-web-archive@ietf.org>; Wed, 6 Oct 2004 12:27:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFEmn-0005W8-Be
	for sipping-web-archive@ietf.org; Wed, 06 Oct 2004 12:37:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFEZ2-0006ms-CD; Wed, 06 Oct 2004 12:22:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFEGT-0001p5-3s
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 12:03:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09099
	for <sipping@ietf.org>; Wed, 6 Oct 2004 12:03:38 -0400 (EDT)
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 1CFEPy-0003zV-Pc
	for sipping@ietf.org; Wed, 06 Oct 2004 12:13:32 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-1.cisco.com with ESMTP; 06 Oct 2004 09:10:50 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i96G33EE016094;
	Wed, 6 Oct 2004 09:03:04 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMC04939; Wed, 6 Oct 2004 12:03:02 -0400 (EDT)
Message-ID: <41641736.7040604@cisco.com>
Date: Wed, 06 Oct 2004 12:03:02 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] GRUU support in reg event package
References: <2038BCC78B1AD641891A0D1AE133DBB7023EEB6A@esebe019.ntc.nokia.com>
	<41630BA7.6010306@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
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



Paul Kyzivat wrote:
> 
>> I have a further comment about this draft:
>>
>> I think it is a good idea for the draft stress that this is an 
>> extension and how a client should behave when it receives the 
>> notifications with XML elements it does not understand (ignore them, 
>> for example). A section on registrar behaviour is beneficial as well.
> 
> OK, that seems reasonable.

I thought further about this, and have questions:

It does no good for an extension to provide special instructions for how 
the extension should be supported by something that doesn't support the 
extension. In fact RFC 3680 already gives very clear instruction that 
unknown values in the extension entities MUST be ignored. So that is 
already covered.

What probably does make sense is just to point out that fact - that this 
extension is indeed backward compatible because of the rules in 3680.

Regarding registrar behavior - nominally the registrar isn't involved at 
all. The NOTIFIER is presumably in some close relationship with the 
registrar. It may make sense to have the kind of sections that typically 
appear in event packages:

- Notifier Processing of SUBSCRIBE Requests
- Notifier Generation of NOTIFY Requests
- Subscriber Processing of NOTIFY Requests

Would that cover your concerns?

	Paul


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


From sipping-bounces@ietf.org  Wed Oct  6 13:25:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14890
	for <sipping-web-archive@ietf.org>; Wed, 6 Oct 2004 13:25:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFFhO-0000WA-FO
	for sipping-web-archive@ietf.org; Wed, 06 Oct 2004 13:35:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFFW7-0007zl-TE; Wed, 06 Oct 2004 13:23:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFFUn-0007ep-KZ
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 13:22:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14624
	for <sipping@ietf.org>; Wed, 6 Oct 2004 13:22:30 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFFeH-0000Hf-TF
	for sipping@ietf.org; Wed, 06 Oct 2004 13:32:25 -0400
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
	i96HMMO24527; Wed, 6 Oct 2004 20:22:22 +0300 (EET DST)
X-Scanned: Wed, 6 Oct 2004 20:21:56 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i96HLuGp016368;
	Wed, 6 Oct 2004 20:21:56 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00NcrsE3; Wed, 06 Oct 2004 20:21:54 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i96HLmY24344; Wed, 6 Oct 2004 20:21:48 +0300 (EET DST)
Received: from esebe001.NOE.Nokia.com ([172.21.138.30]) by
	esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Oct 2004 20:21:47 +0300
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by
	esebe001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 6 Oct 2004 20:21:47 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] GRUU support in reg event package
Date: Wed, 6 Oct 2004 20:21:47 +0300
Message-ID: <5816828233DEFA41807A6CFDFDF2343C08B6A9@esebe056.ntc.nokia.com>
Thread-Topic: [Sipping] GRUU support in reg event package
Thread-Index: AcSrvmxDA7T4AlqtRga67oQjeZaC9AACnfSg
To: <pkyzivat@cisco.com>
X-OriginalArrivalTime: 06 Oct 2004 17:21:47.0390 (UTC)
	FILETIME=[F58109E0:01C4ABC8]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable



> -----Original Message-----
> From: ext Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: 06.October.2004 19:03
> To: Paul Kyzivat
> Cc: Khartabil Hisham (Nokia-TP-MSW/Helsinki); sipping@ietf.org
> Subject: Re: [Sipping] GRUU support in reg event package
>=20
>=20
>=20
>=20
> Paul Kyzivat wrote:
> >=20
> >> I have a further comment about this draft:
> >>
> >> I think it is a good idea for the draft stress that this is an=20
> >> extension and how a client should behave when it receives the=20
> >> notifications with XML elements it does not understand=20
> (ignore them,=20
> >> for example). A section on registrar behaviour is=20
> beneficial as well.
> >=20
> > OK, that seems reasonable.
>=20
> I thought further about this, and have questions:
>=20
> It does no good for an extension to provide special=20
> instructions for how=20
> the extension should be supported by something that doesn't=20
> support the=20
> extension. In fact RFC 3680 already gives very clear instruction that=20
> unknown values in the extension entities MUST be ignored. So that is=20
> already covered.
>=20
> What probably does make sense is just to point out that fact=20
> - that this=20
> extension is indeed backward compatible because of the rules in 3680.
>=20
> Regarding registrar behavior - nominally the registrar isn't=20
> involved at=20
> all. The NOTIFIER is presumably in some close relationship with the=20
> registrar. It may make sense to have the kind of sections=20
> that typically=20
> appear in event packages:
>=20
> - Notifier Processing of SUBSCRIBE Requests
> - Notifier Generation of NOTIFY Requests
> - Subscriber Processing of NOTIFY Requests
>=20
> Would that cover your concerns?

Yes, thanks.

Hisham
>=20
> 	Paul
>=20
>=20

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


From sipping-bounces@ietf.org  Thu Oct  7 03:24: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 DAA17983
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 03:24:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFSn3-00078r-3f
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 03:34:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFSW1-0007O1-W2; Thu, 07 Oct 2004 03:16:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFSMC-0005GI-6A
	for sipping@megatron.ietf.org; Thu, 07 Oct 2004 03:06:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16466
	for <sipping@ietf.org>; Thu, 7 Oct 2004 03:06:30 -0400 (EDT)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFSVd-00060p-Kf
	for sipping@ietf.org; Thu, 07 Oct 2004 03:16:31 -0400
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	i9776HRU006860 for <sipping@ietf.org>; Thu, 7 Oct 2004 09:06:17 +0200
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	Thu, 7 Oct 2004 09:06:17 +0200
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id 4J5FVZ76; Thu, 7 Oct 2004 09:06:17 +0200
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.31.224])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id DAA8B18AA9; Thu,  7 Oct 2004 10:06:16 +0300 (EEST)
Message-ID: <4164EAE8.1090105@ericsson.com>
Date: Thu, 07 Oct 2004 10:06:16 +0300
X-Sybari-Trust: fba8e0da 74898554 21fb9c7e 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>, Dean Willis <dean.willis@softarmor.com>,
        Rohan Mahy <rohan@ekabal.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Oct 2004 07:06:17.0422 (UTC)
	FILETIME=[23F0DEE0:01C4AC3C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Agenda requests for DC
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: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit

Folks,

we will be gathering agenda requests for the SIPPING meeting in 
Washington DC under the following link:

http://www.softarmor.com/sipping/meets/ietf61/requests.html

As usual, if you use the template provided at the end of this email to
submit your agenda request, it will make this task easier. Agenda
requests are submitted in an email addressed to the chairs.

Regarding the requests we will be accepting and rejecting, we intend to 
use a large part of the meeting to discuss issues related to WG items, 
as we did in the last meeting. We will only discuss individual 
contributions that have received considerable attention since the last 
meeting.


     <tr>
       <td><a href="mailto:Gonzalo.Camarillo@ericsson.com">
Gonzalo Camarillo</a></td>
       <td>Exploders</td>
       <td><center>5</center></td>
       <td>
<a
href="http://www.ietf.org/internet-drafts/draft-camarillo-sipping-exploders-02.txt">
draft-camarillo-sipping-exploders-02.txt</a></td>
     </tr>


Thanks,

Gonzalo
SIPPING co-chair



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


From sipping-bounces@ietf.org  Thu Oct  7 16:48: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 QAA24884
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 16:48:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFfL1-0002nH-2o
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 16:58:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFeJg-0007Ks-A5; Thu, 07 Oct 2004 15:52:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFe2g-0008UD-Nx; Thu, 07 Oct 2004 15:35:10 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15886;
	Thu, 7 Oct 2004 15:35:08 -0400 (EDT)
Message-Id: <200410071935.PAA15886@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, 07 Oct 2004 15:35:08 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D
	ACTION:draft-ietf-sipping-conferencing-requirements-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: 2.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		: High Level Requirements for  Tightly Coupled SIP Conferencing
	Author(s)	: O. Levin, R. Even
	Filename	: draft-ietf-sipping-conferencing-requirements-01.txt
	Pages		: 13
	Date		: 2004-10-7
	
This document examines a wide range of conferencing requirements for
tightly coupled SIP conferences. Separate documents will map the
requirements to existing protocol primitives, define new protocol
extensions, and introduce new protocols as needed. Together, these
documents will provide a guide for building interoperable SIP
conferencing applications.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-conferencing-requirements-01.txt

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

Content-Type: text/plain
Content-ID: <2004-10-7155517.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 Oct  7 17:23: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 RAA28664
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 17:23:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFftM-0005ZY-Qf
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 17:33:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFfYp-0001zz-LG; Thu, 07 Oct 2004 17:12:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFfO7-0006fd-KF
	for sipping@megatron.ietf.org; Thu, 07 Oct 2004 17:01:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26733
	for <sipping@ietf.org>; Thu, 7 Oct 2004 17:01:20 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFfXt-0003xw-QR
	for sipping@ietf.org; Thu, 07 Oct 2004 17:11:30 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL3BZ8>; Thu, 7 Oct 2004 17:00:52 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A69B@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>,
        "Hedayat, Kaynam"
	<khedayat@brixnet.com>
Subject: RE: [Sipping] New internet draft on media loopback
Date: Thu, 7 Oct 2004 17:00:50 -0400 
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
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976

Paul,

Thank you for your comments. Please see my reply below.

Regards,
Kaynam

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Tuesday, October 05, 2004 3:50 PM
To: Hedayat, Kaynam
Cc: 'sipping@ietf.org'
Subject: Re: [Sipping] New internet draft on media loopback


I support the functionality represented by this draft. A few comments:

- this seems to be structured for consideration as a draft in the
   SIP WG. But the content is all about SDP and offer/answer. As such,
   I think it makes more sense to target this to the MMUSIC WG. This
   would mean removing anything specific to SIP - which should be easy
   because there is little or nothing here that needs to be specific
   to SIP.

   A companion draft in the SIP (or SIPPING) WG could be developed to
   specify sip specific usage rules and guidelines.

[KH] I agree with your comments. We will separate the draft into two drafts,
one addressing sdp issues and one sip usage issues.

- Section 6.3 says "The loopback-source attribute can only appear in an
   offer", and 6.4 says "The loopback-mirror attribute can only appear in
   an answer". There seems no reason for this restriction. All that is
   required is that a loopback-source offer be answered by a
   loopback-mirror and visa versa. Perhaps it is more likely that the
   source be offered and the mirror answered, but the opposite clearly
   has meaning. (I.e. please test me.) Of course it may be harder for a
   testee to find a tester than the converse, but that is a usage issue.

   Note also that section 6.5 mentions "In cases where the offer contains
   the loopback-mirror attribute", implying that support for this has
   been considered.

[KH] Per Arjun's comments we didn't see any reason for this restriction
and will remove it from the draft. The only restriction will be that
the answer should be the opposite of the offer.

- section 6.5 (typo): "one code" should be "one codec".
[KH] Corrected.

- section 9.4: is there a way to indicate support for both loopback
   types, and/or for both loopback-source and loopback-mirror? It would
   be a good thing to do. I think it should be possible to tweak things
   so it is.

[KH] I don't see any reason for specifying loopback-source in the
answer in this case. The point is to query a device to mirror a
stream. The case for querying a device to source a loopback stream
should be addressed at a higher level.

- section 11 says: "...given that it is recommended that the user is not
   alerted for calls that only have loopback media modes..." but I can
   find no such recommendation. I think this would relate back to the
   partitioning of mmusic and sip aspects into separate drafts. Alerting
   is a sip consideration.

[KH]Section 10.2 specifies,
"Furthermore, it is RECOMMENDED that the user is not alerted for 
    calls that only have loopback media modes and when such calls are 
    answered automatically."



	Paul


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


From sipping-bounces@ietf.org  Thu Oct  7 18:14:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04222
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 18:14:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFggu-0000AT-0a
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 18:24:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFgOD-0004W7-12; Thu, 07 Oct 2004 18:05:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFgCq-000875-NC
	for sipping@megatron.ietf.org; Thu, 07 Oct 2004 17:53:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01927
	for <sipping@ietf.org>; Thu, 7 Oct 2004 17:53:45 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFgMa-00071r-4V
	for sipping@ietf.org; Thu, 07 Oct 2004 18:03:55 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 07 Oct 2004 17:53:15 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i97Lr9EF023158; 
	Thu, 7 Oct 2004 17:53:12 -0400 (EDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMD20179; Thu, 7 Oct 2004 17:53:08 -0400 (EDT)
Message-ID: <4165BAC4.5000106@cisco.com>
Date: Thu, 07 Oct 2004 17:53:08 -0400
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: "Hedayat, Kaynam" <khedayat@brixnet.com>
Subject: Re: [Sipping] New internet draft on media loopback
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A69B@mail.brixnet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit



Hedayat, Kaynam wrote:
> Paul,
> 
> Thank you for your comments. Please see my reply below.
>

Just one further response:

> - section 9.4: is there a way to indicate support for both loopback
>    types, and/or for both loopback-source and loopback-mirror? It would
>    be a good thing to do. I think it should be possible to tweak things
>    so it is.
> 
> [KH] I don't see any reason for specifying loopback-source in the
> answer in this case. The point is to query a device to mirror a
> stream. The case for querying a device to source a loopback stream
> should be addressed at a higher level.

I don't follow you. This is just a continuation of the symetry of the 
two modes. If I can send an offer with loopback-mirror and get a 
response of loopback-source, then it would be good to support an OPTIONS 
query where I can determine that a device actually supports that mode of 
operation.

Of course there will be higher level functions for deciding which nodes 
to query, but that doesn't negate the value of this basic level.

I just see this as a small effort of structuring the notation so that it 
MAY be used in this way. I can imagine that there could be testing nodes 
that would be capable of operating in either mode. It would be good for 
them to be able to indicate this capability.

	Paul


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


From sipping-bounces@ietf.org  Thu Oct  7 19:15: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 TAA08853
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 19:15:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFhdm-0003xY-RF
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 19:25:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFhPw-00056B-8b; Thu, 07 Oct 2004 19:11:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFhIe-0003dW-3d
	for sipping@megatron.ietf.org; Thu, 07 Oct 2004 19:03:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07923
	for <sipping@ietf.org>; Thu, 7 Oct 2004 19:03:48 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFhSH-00039S-Bm
	for sipping@ietf.org; Thu, 07 Oct 2004 19:13:59 -0400
Received: from dynamicsoft.com ([63.113.46.31])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i97N3Mpl027562; 
	Thu, 7 Oct 2004 19:03:23 -0400 (EDT)
Message-ID: <4165CB22.5070308@dynamicsoft.com>
Date: Thu, 07 Oct 2004 19:02:58 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Hedayat, Kaynam" <khedayat@brixnet.com>
Subject: Re: [Sipping] New internet draft on media loopback
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>
In-Reply-To: <07B0D4912B83D31188F300A0C9F62EBB03E7A66D@mail.brixnet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit

Thanks for writing this up.

I like the general idea of adding mechanisms in sip to facilitate 
testing and monitoring of an active network, but there are a lot of 
higher level questions about this specific proposal.

Firstly, I think you need to step back and really understand the problem 
that is being solved. Is the problem that you want a way to have network 
operator that deploys sip figure out the quality of calls made in the 
network? Is the problem that someone in the field wants to test if the 
system is "working"? That is, if a call can be made?

I'm assuming it's probably the latter. Do you need the phone that is 
acting as the mirror to also automatically answer the sip invite, or is 
another human going to do that? If its the former, then you need more 
things than just SDP mirroring. You would need a way for an automated 
answering of the call. That has all kinds of interesting security 
issues; being able to send someone a message that causes them to 
automatically answer calls can be troubling and used as a source of dos 
attacks (consider a phone with a single line).

If you assume that there is a human that will answer the phone acting as 
the mirror, what is the need for actually mirroring the media? Isn't it 
enough to merely receive some kind of media, and you can collect 
statistics from the RTCP? Why isn't someone saying 
"testing-1-2-3-testing" sufficient?

So, at a high level, I still don't understand the specific diagnostic 
problem which this is attempting to solve. I think you need to 
articulate that as a problem statement and requirements in order for the 
group to evaluate it better.

Thanks,
Jonathan R.

Hedayat, Kaynam wrote:
> I would like to bring the attention of the group to a new internet draft on
> media loopback capability in SIP sessions. The draft can be found at
> http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt
> 
> Regards,
> Kaynam
> 
> -----------------------------------------
> Kaynam Hedayat
> Chief Technology Officer
> Brix Networks
> 285 Mill Road
> Chelmsford, MA 01824
> 
> tel.   978.367.5611
> fax.   978.367.5700
> khedayat@brixnet.com
> www.brixnet.com
> 
> See it before they hear it: Test the performance and quality of your VoIP at
> www.TestYourVoip.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
> 

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

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


From sipping-bounces@ietf.org  Thu Oct  7 19:21: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 TAA09403
	for <sipping-web-archive@ietf.org>; Thu, 7 Oct 2004 19:21:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFhjB-0004MI-DK
	for sipping-web-archive@ietf.org; Thu, 07 Oct 2004 19:31:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFhR6-0005I0-4C; Thu, 07 Oct 2004 19:12:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFhMi-0004GO-Am
	for sipping@megatron.ietf.org; Thu, 07 Oct 2004 19:08:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08304
	for <sipping@ietf.org>; Thu, 7 Oct 2004 19:08:01 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFhWU-0003Ne-K4
	for sipping@ietf.org; Thu, 07 Oct 2004 19:18:12 -0400
Received: from dynamicsoft.com ([63.113.46.31])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i97N7mpl027577; 
	Thu, 7 Oct 2004 19:07:51 -0400 (EDT)
Message-ID: <4165CC2C.109@dynamicsoft.com>
Date: Thu, 07 Oct 2004 19:07:24 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: Re: [Sipping] profile data for SIP policies
References: <E5880434292FCB448F00BDAEE44A60D00966A0@EXC01C.cselt.it>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D00966A0@EXC01C.cselt.it>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: Volker Hilt <volkerh@bell-labs.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit



Simonetti Gabrielle wrote:

> Volker, In response to your mail, here are some items that I think
> should be considered in the I-D:
> 
> 1. Concerning the policies:
> 
> - It should be specified how to solve the "superposition" of the same
> piece of profile information. For example, if both the local profile
> and the user profile specify the transport protocol to be used, the
> UA should know which information to set in priority. In most cases,
> the policy applied to a specific user might restrict the policy
> applied to the whole domain.

I really think this is a second order problem. Right now, we have no 
means to configure a phone in any kind of standard way. I don't see a 
need for our first stab at this to allow reconciliation of conflicting 
configuration data across multiple providers.

> 
> 2. Concerning the different aspects of profile information:
> 
> - The following data sets would be useful:
> 
> . An "outbound_proxy" data set, for both the local profile and the
> user profile
> 
> . A "NAT_address" data set, for the local profile (in the case calls
> are made through a NAT)

How does the provider know this? THis is a very brittle configuration 
assumption. ICE makes the determination of connectivity dynamic, and 
thus there is no need for this to be included as configuration data.

-Jonathan R.



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

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


From sipping-bounces@ietf.org  Fri Oct  8 10:07:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25799
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 10:07:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFvZR-0007Ir-Mf
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 10:18:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFvLm-0000fe-2W; Fri, 08 Oct 2004 10:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFvDK-0005MO-Eh
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 09:55:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24346
	for <sipping@ietf.org>; Fri, 8 Oct 2004 09:55:17 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFvND-000716-54
	for sipping@ietf.org; Fri, 08 Oct 2004 10:05:34 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL32SN>; Fri, 8 Oct 2004 09:54:44 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A69F@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "Hedayat, Kaynam"
	<khedayat@brixnet.com>
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 09:54:41 -0400 
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: 825e642946eda55cd9bc654a36dab8c2
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2

Jonathan,

Thank you for your comments. My reply is in-line below.

Regards,
Kaynam

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
Sent: Thursday, October 07, 2004 7:03 PM
To: Hedayat, Kaynam
Cc: 'sipping@ietf.org'
Subject: Re: [Sipping] New internet draft on media loopback


Thanks for writing this up.

I like the general idea of adding mechanisms in sip to facilitate 
testing and monitoring of an active network, but there are a lot of 
higher level questions about this specific proposal.

Firstly, I think you need to step back and really understand the problem 
that is being solved. Is the problem that you want a way to have network 
operator that deploys sip figure out the quality of calls made in the 
network? Is the problem that someone in the field wants to test if the 
system is "working"? That is, if a call can be made?

[KH] The problem is pro-active monitoring of a VoIP service to make sure
that it is working per quality standards set by the provider. The
proposed solution is making "test" calls to endpoints and collecting
performance statistics for such calls.

I'm assuming it's probably the latter. Do you need the phone that is 
acting as the mirror to also automatically answer the sip invite, or is 
another human going to do that? If its the former, then you need more 
things than just SDP mirroring. You would need a way for an automated 
answering of the call. That has all kinds of interesting security 
issues; being able to send someone a message that causes them to 
automatically answer calls can be troubling and used as a source of dos 
attacks (consider a phone with a single line).

[KH] The intervention of a human being is not going to be scalable and
manageable solution. Therefore the calls should be answered
automatically. Furthermore, some of the Voice Quality measurements
will not be possible without the loopback of the original media. However,
our goal is not to mandate the loopback of media and/or automatic
answer for "test" calls. Our goal is to introduce a loopback media 
attribute and the notion of the "test" call. The caller decides
how media should be handled (loopback, someone talking, etc). The callee
decides how to handle a "test" call. As you suggested there is more than 
SDP mirroring that needs to be done. We are currently working on changing 
this draft to address SDP issues only (e.g. new attributes) and a new draft 
for establishing "test" calls that will address your concerns.

If you assume that there is a human that will answer the phone acting as 
the mirror, what is the need for actually mirroring the media? Isn't it 
enough to merely receive some kind of media, and you can collect 
statistics from the RTCP? Why isn't someone saying 
"testing-1-2-3-testing" sufficient?

[KH] The need for mirroring the media is the reception of the sent media
for voice quality measurement and voice recording (for offline quality
assessment). That said in some situations someone saying "testing-1-2-3"
is sufficient. Our goal is to leave this as an option.

So, at a high level, I still don't understand the specific diagnostic 
problem which this is attempting to solve. I think you need to 
articulate that as a problem statement and requirements in order for the 
group to evaluate it better.

[KH] We will do what you have suggested. As far as the IETF process, should
we post a new draft based on comments on the list prior to the IETF meeting?

Thanks,
Jonathan R.

Hedayat, Kaynam wrote:
> I would like to bring the attention of the group to a new internet draft
on
> media loopback capability in SIP sessions. The draft can be found at
> http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt
> 
> Regards,
> Kaynam
> 
> -----------------------------------------
> Kaynam Hedayat
> Chief Technology Officer
> Brix Networks
> 285 Mill Road
> Chelmsford, MA 01824
> 
> tel.   978.367.5611
> fax.   978.367.5700
> khedayat@brixnet.com
> www.brixnet.com
> 
> See it before they hear it: Test the performance and quality of your VoIP
at
> www.TestYourVoip.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
> 

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

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


From sipping-bounces@ietf.org  Fri Oct  8 10:46: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 KAA00829
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 10:46:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFwAl-0008Pr-6b
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 10:56:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFvid-00031J-Ls; Fri, 08 Oct 2004 10:27:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFvcK-0000Rx-KX
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:21:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27816
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:21:07 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFvmG-0007hT-2K
	for sipping@ietf.org; Fri, 08 Oct 2004 10:31:25 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL32YZ>; Fri, 8 Oct 2004 10:20:37 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A6A0@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Christian Jansson'" <christian.jansson@hotsip.com>,
        Jonathan Rosenberg
	<jdrosen@dynamicsoft.com>,
        "Hedayat, Kaynam" <khedayat@brixnet.com>
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:20:30 -0400 
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: 9182cfff02fae4f1b6e9349e01d62f32
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: e5ba305d0e64821bf3d8bc5d3bb07228

The service will provide loopback points in specific locations of the
network. The goal is to provide loopback points in all locations of the
network. As stated in the draft what you suggested has been implemented in
some networks and has proven to be not scalable and unmanageable.

Regards,
Kaynam

-----Original Message-----
From: Christian Jansson [mailto:christian.jansson@hotsip.com]
Sent: Friday, October 08, 2004 4:03 AM
To: Jonathan Rosenberg; Hedayat, Kaynam
Cc: sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback




Why not build a service and give it a SIP-URI like
sip:audiotest@domain.com that answers all calls and loops back the
audio? There is no need for any new SDP attributes to be able to build
such a service. 

/ Christian Jansson, Hotsip


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct  8 10:49: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 KAA01105
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 10:49:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFwDd-0008V3-2e
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 10:59:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFvjh-0003CG-D3; Fri, 08 Oct 2004 10:28:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFvgE-0002AF-0a
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:25:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28403
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:25:08 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFvqA-0007sl-5v
	for sipping@ietf.org; Fri, 08 Oct 2004 10:35:26 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL325L>; Fri, 8 Oct 2004 10:24:39 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A6A2@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Jain, Rajnish'" <rjain@excelswitching.com>,
        "Hedayat, Kaynam"
	<khedayat@brixnet.com>, sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:24:32 -0400 
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: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d

Rajnish,

This is a very good point. What are the requirements for the responder of
the 102, 105, 108 tests? Is looping back the media sufficient?

Regards,
Kaynam

-----Original Message-----
From: Jain, Rajnish [mailto:rjain@excelswitching.com]
Sent: Friday, October 08, 2004 10:18 AM
To: Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback


Kaynam,

In many ways, this draft is analogous to continuity test (COT) and test
calls 102, 105, 108 of traditional telephony. While there are some
fundamental differences between a TDM continuity test and an RTP media
loopback test, there are many similar goals. 

While the draft at this time seems to emphasize user end-points, the
idea can also be extended to SIP-enabled media gateways. Currently, in a
SIP bridging scenario (RFC 3372, RFC 3398), a continuity test between an
SSP and a media gateway tests only the local TDM path (not the
end-to-end TDM-RTP-TDM path). If SIP bridging were to be truly
transparent to the two SSPs with respect to the continuity test, the
media gateways could possibly receive a continuity test request on the
TDM side and propagate to the SIP side (and vice-versa). 
 
Rajnish

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Hedayat, Kaynam
Sent: Monday, October 04, 2004 3:22 AM
To: 'sipping@ietf.org'
Subject: [Sipping] New internet draft on media loopback

I would like to bring the attention of the group to a new internet draft
on media loopback capability in SIP sessions. The draft can be found at
http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt

Regards,
Kaynam

-----------------------------------------
Kaynam Hedayat
Chief Technology Officer
Brix Networks
285 Mill Road
Chelmsford, MA 01824

tel.   978.367.5611
fax.   978.367.5700
khedayat@brixnet.com
www.brixnet.com

See it before they hear it: Test the performance and quality of your
VoIP at www.TestYourVoip.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 Oct  8 10:54: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 KAA01496
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 10:54:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFwIT-0000D4-PF
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 11:04:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFw66-0000Q8-Ss; Fri, 08 Oct 2004 10:51:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFvsA-00053r-7h
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:37:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00041
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:37:29 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFw25-0008Ap-L6
	for sipping@ietf.org; Fri, 08 Oct 2004 10:47:47 -0400
Received: from dynamicsoft.com ([63.113.46.18])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i98Eb7pl000821; 
	Fri, 8 Oct 2004 10:37:08 -0400 (EDT)
Message-ID: <41668877.5010400@dynamicsoft.com>
Date: Fri, 08 Oct 2004 08:30:47 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christian Jansson <christian.jansson@hotsip.com>
Subject: Re: [Sipping] New internet draft on media loopback
References: <B7192C0D8D60754DADA9E22294C573694527A5@mailserver.hotsip.com>
In-Reply-To: <B7192C0D8D60754DADA9E22294C573694527A5@mailserver.hotsip.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

Before jumping into solutions, I think it is important to understand the 
specific diagnostic and testing requirements. What is it that you wish 
to discover with the test?

-Jonathan R.

Christian Jansson wrote:
> 
> Why not build a service and give it a SIP-URI like
> sip:audiotest@domain.com that answers all calls and loops back the
> audio? There is no need for any new SDP attributes to be able to build
> such a service. 
> 
> / Christian Jansson, Hotsip
> 

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


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


From sipping-bounces@ietf.org  Fri Oct  8 11:02:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02210
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 11:02:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFwQe-0000RO-Bx
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 11:13:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFw6d-0000jp-Sq; Fri, 08 Oct 2004 10:52:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFvyM-0006N3-EA
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:43:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00559
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:43:53 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFw8G-0008Ja-6O
	for sipping@ietf.org; Fri, 08 Oct 2004 10:54:11 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL3298>; Fri, 8 Oct 2004 10:43:21 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A6A4@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        Christian Jansson
	<christian.jansson@hotsip.com>
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:43:18 -0400 
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: 9ed51c9d1356100bce94f1ae4ec616a9
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: 50a516d93fd399dc60588708fd9a3002

The goal is to:

- Measure availability of an endpoint (at the SIP level)
- Measure Call Signaling performance (PDD, etc.)
- Measure Media performance (voice quality)
- Identify causes of poor Call Signaling & Media performance (packet loss,
jitter, etc.)

Regards,
Kaynam

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
Sent: Friday, October 08, 2004 8:31 AM
To: Christian Jansson
Cc: Hedayat, Kaynam; sipping@ietf.org
Subject: Re: [Sipping] New internet draft on media loopback


Before jumping into solutions, I think it is important to understand the 
specific diagnostic and testing requirements. What is it that you wish 
to discover with the test?

-Jonathan R.

Christian Jansson wrote:
> 
> Why not build a service and give it a SIP-URI like
> sip:audiotest@domain.com that answers all calls and loops back the
> audio? There is no need for any new SDP attributes to be able to build
> such a service. 
> 
> / Christian Jansson, Hotsip
> 

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


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


From sipping-bounces@ietf.org  Fri Oct  8 11:22: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 LAA03720
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 11:22:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFwk6-0000ui-Cp
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 11:33:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFwT8-0005dj-8w; Fri, 08 Oct 2004 11:15:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFwGg-0003EQ-QS
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 11:02:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02207
	for <sipping@ietf.org>; Fri, 8 Oct 2004 11:02:49 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFwQb-0000QQ-4h
	for sipping@ietf.org; Fri, 08 Oct 2004 11:13:06 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL3JD0>; Fri, 8 Oct 2004 11:02:14 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A6A5@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Jain, Rajnish'" <rjain@excelswitching.com>,
        "Hedayat, Kaynam"
	<khedayat@brixnet.com>, sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 11:02:04 -0400 
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: 32b73d73e8047ed17386f9799119ce43
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

RTP loopback will apply to 108 test. 102 and 105 tests would require
additional signaling at the signaling layer.

Regards,
Kaynam

-----Original Message-----
From: Jain, Rajnish [mailto:rjain@excelswitching.com]
Sent: Friday, October 08, 2004 10:59 AM
To: Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback


108 is a simple loopback test. However, 102 and 105 require responder to
generate special tones.

-----Original Message-----
From: Hedayat, Kaynam [mailto:khedayat@brixnet.com] 
Sent: Friday, October 08, 2004 10:25 AM
To: Jain, Rajnish; Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback

Rajnish,

This is a very good point. What are the requirements for the responder
of the 102, 105, 108 tests? Is looping back the media sufficient?

Regards,
Kaynam

-----Original Message-----
From: Jain, Rajnish [mailto:rjain@excelswitching.com]
Sent: Friday, October 08, 2004 10:18 AM
To: Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback


Kaynam,

In many ways, this draft is analogous to continuity test (COT) and test
calls 102, 105, 108 of traditional telephony. While there are some
fundamental differences between a TDM continuity test and an RTP media
loopback test, there are many similar goals. 

While the draft at this time seems to emphasize user end-points, the
idea can also be extended to SIP-enabled media gateways. Currently, in a
SIP bridging scenario (RFC 3372, RFC 3398), a continuity test between an
SSP and a media gateway tests only the local TDM path (not the
end-to-end TDM-RTP-TDM path). If SIP bridging were to be truly
transparent to the two SSPs with respect to the continuity test, the
media gateways could possibly receive a continuity test request on the
TDM side and propagate to the SIP side (and vice-versa). 
 
Rajnish

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Hedayat, Kaynam
Sent: Monday, October 04, 2004 3:22 AM
To: 'sipping@ietf.org'
Subject: [Sipping] New internet draft on media loopback

I would like to bring the attention of the group to a new internet draft
on media loopback capability in SIP sessions. The draft can be found at
http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt

Regards,
Kaynam

-----------------------------------------
Kaynam Hedayat
Chief Technology Officer
Brix Networks
285 Mill Road
Chelmsford, MA 01824

tel.   978.367.5611
fax.   978.367.5700
khedayat@brixnet.com
www.brixnet.com

See it before they hear it: Test the performance and quality of your
VoIP at www.TestYourVoip.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 Oct  8 12:30: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 MAA08789
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 12:30:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFxnO-0002LP-9B
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 12:40:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFxWD-0007df-76; Fri, 08 Oct 2004 12:22:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFxDw-0006vd-1k
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 12:04:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07413
	for <sipping@ietf.org>; Fri, 8 Oct 2004 12:04:03 -0400 (EDT)
Received: from webmail.brixnet.com ([63.122.27.38] helo=brixcorp2.brixnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFxNs-0001r3-RY
	for sipping@ietf.org; Fri, 08 Oct 2004 12:14:22 -0400
Received: by mail.brixnet.com with Internet Mail Service (5.5.2657.72)
	id <RTLL3JTF>; Fri, 8 Oct 2004 12:03:32 -0400
Message-ID: <07B0D4912B83D31188F300A0C9F62EBB03E7A6AA@mail.brixnet.com>
From: "Hedayat, Kaynam" <khedayat@brixnet.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>,
        "Hedayat, Kaynam"
	<khedayat@brixnet.com>
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 12:03:23 -0400 
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

Paul,

I see your point. The notations allows for response of both loopback modes
(in case of OPTIONS request). One option would be:

a=loopback:rtp-media-loopback rtp-pkt-loopback
a=loopback-mirror loopback-source

The loopback types apply to loopback-mirror only.

Regards,
Kaynam

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Thursday, October 07, 2004 5:53 PM
To: Hedayat, Kaynam
Cc: 'sipping@ietf.org'
Subject: Re: [Sipping] New internet draft on media loopback




Hedayat, Kaynam wrote:
> Paul,
> 
> Thank you for your comments. Please see my reply below.
>

Just one further response:

> - section 9.4: is there a way to indicate support for both loopback
>    types, and/or for both loopback-source and loopback-mirror? It would
>    be a good thing to do. I think it should be possible to tweak things
>    so it is.
> 
> [KH] I don't see any reason for specifying loopback-source in the
> answer in this case. The point is to query a device to mirror a
> stream. The case for querying a device to source a loopback stream
> should be addressed at a higher level.

I don't follow you. This is just a continuation of the symetry of the 
two modes. If I can send an offer with loopback-mirror and get a 
response of loopback-source, then it would be good to support an OPTIONS 
query where I can determine that a device actually supports that mode of 
operation.

Of course there will be higher level functions for deciding which nodes 
to query, but that doesn't negate the value of this basic level.

I just see this as a small effort of structuring the notation so that it 
MAY be used in this way. I can imagine that there could be testing nodes 
that would be capable of operating in either mode. It would be good for 
them to be able to indicate this capability.

	Paul


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


From sipping-bounces@ietf.org  Fri Oct  8 13:11:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11772
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 13:11:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CFyRI-0003KG-39
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 13:21:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CFyBQ-00081S-Su; Fri, 08 Oct 2004 13:05:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFy1V-0005on-21
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 12:55:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10446
	for <sipping@ietf.org>; Fri, 8 Oct 2004 12:55:16 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFyBS-0002pX-CN
	for sipping@ietf.org; Fri, 08 Oct 2004 13:05:35 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 08 Oct 2004 09:55:35 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i98GshbV011799;
	Fri, 8 Oct 2004 09:54:43 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMD69620; Fri, 8 Oct 2004 12:54:42 -0400 (EDT)
Message-ID: <4166C652.7010607@cisco.com>
Date: Fri, 08 Oct 2004 12:54:42 -0400
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: "Hedayat, Kaynam" <khedayat@brixnet.com>
Subject: Re: [Sipping] New internet draft on media loopback
References: <07B0D4912B83D31188F300A0C9F62EBB03E7A6AA@mail.brixnet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit



Hedayat, Kaynam wrote:
> Paul,
> 
> I see your point. The notations allows for response of both loopback modes
> (in case of OPTIONS request). One option would be:
> 
> a=loopback:rtp-media-loopback rtp-pkt-loopback

That works for me - both in OPTIONS and in an offer. (Means the answerer 
mush choose one.)

> a=loopback-mirror loopback-source

Trouble is this is inconsistent with the other "direction" attributes. 
E.g. I can't say:

   a=send recv

If these are to be considered as alternatives to 
send/recv/sendrecv/inactive, then I think consistent conventions should 
apply. Going that way would suggest adding yet another attribute, 
perhaps loopback-source-mirror or loopback-either. That doesn't seem 
very appealing.

Another possibility is to decouple these attributes from the 
directionality, and just mandate that when using them you must also 
negotiate sendrecv. If you did that, then what you suggest above would 
be fine.

> The loopback types apply to loopback-mirror only.

Why? They are equally applicable to loopback-source. If I am a mirror 
looking for a source then I may also be looking for a source that can 
provide the kind of test I am capable of cooperating with, or that I 
would like to have performed.

	Paul

> Regards,
> Kaynam
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Thursday, October 07, 2004 5:53 PM
> To: Hedayat, Kaynam
> Cc: 'sipping@ietf.org'
> Subject: Re: [Sipping] New internet draft on media loopback
> 
> 
> 
> 
> Hedayat, Kaynam wrote:
> 
>>Paul,
>>
>>Thank you for your comments. Please see my reply below.
>>
> 
> 
> Just one further response:
> 
> 
>>- section 9.4: is there a way to indicate support for both loopback
>>   types, and/or for both loopback-source and loopback-mirror? It would
>>   be a good thing to do. I think it should be possible to tweak things
>>   so it is.
>>
>>[KH] I don't see any reason for specifying loopback-source in the
>>answer in this case. The point is to query a device to mirror a
>>stream. The case for querying a device to source a loopback stream
>>should be addressed at a higher level.
> 
> 
> I don't follow you. This is just a continuation of the symetry of the 
> two modes. If I can send an offer with loopback-mirror and get a 
> response of loopback-source, then it would be good to support an OPTIONS 
> query where I can determine that a device actually supports that mode of 
> operation.
> 
> Of course there will be higher level functions for deciding which nodes 
> to query, but that doesn't negate the value of this basic level.
> 
> I just see this as a small effort of structuring the notation so that it 
> MAY be used in this way. I can imagine that there could be testing nodes 
> that would be capable of operating in either mode. It would be good for 
> them to be able to indicate this capability.
> 
> 	Paul
> 
> 


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


From sipping-bounces@ietf.org  Fri Oct  8 17:01:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14781
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 17:01:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CG21u-00040M-9A
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 17:11:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CG0xU-00069s-V3; Fri, 08 Oct 2004 16:03:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CG0cZ-0001DV-Jx; Fri, 08 Oct 2004 15:41:43 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29049;
	Fri, 8 Oct 2004 15:41:41 -0400 (EDT)
Message-Id: <200410081941.PAA29049@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, 08 Oct 2004 15:41:41 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-e2m-sec-reqs-04.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: 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-04.txt
	Pages		: 14
	Date		: 2004-10-8
	
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-04.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-04.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-04.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-10-8160203.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2004-10-8160203.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 Oct  8 23:09:27 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 XAA22790
	for <sipping-web-archive@ietf.org>; Fri, 8 Oct 2004 23:09:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CG7lv-0003YK-EX
	for sipping-web-archive@ietf.org; Fri, 08 Oct 2004 23:19:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CG7Zz-00058Y-P6; Fri, 08 Oct 2004 23:07:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CG7VG-000409-Bm
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 23:02:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22361
	for <sipping@ietf.org>; Fri, 8 Oct 2004 23:02:35 -0400 (EDT)
Received: from filter4.kt.co.kr ([147.6.42.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG7f6-0003QD-Ko
	for sipping@ietf.org; Fri, 08 Oct 2004 23:13:00 -0400
Received: from external ([147.6.9.113]) by filter4 (1.0) id i9931rX00D53;
	Sat, 09 Oct 2004 12:01:53 +0900
X-SMF-UNIQ33B8657C0E4123ECDBACEB8E52847943: i9931rX00D53
Message-ID: <019501c4adac$572a8100$71090693@ROMEO>
From: =?utf-8?B?7Zmp7KeE6rK9?= <jkhwang@kt.co.kr>
To: <sipping@ietf.org>
References: <41062F5D.9040101@eresmas.net>
Date: Sat, 9 Oct 2004 12:01:58 +0900
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 1.1 (+)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Sipping] automatic answer
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="===============0599243135=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

This is a multi-part message in MIME format.

--===============0599243135==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0192_01C4ADF7.C7090140"

This is a multi-part message in MIME format.

------=_NextPart_000_0192_01C4ADF7.C7090140
Content-Type: text/plain;
 charset="utf-8"
Content-Transfer-Encoding: base64

SGksIA0KDQpJcyB0aGVyZSBhbnkgSS1EIHJlZ2FyZGluZyBwYXJhbXMgZm9yIFNJUCBwaG9uZSB0
byBhbnN3ZXIgYXV0b21hdGljYWxseSA/IChmb3IgYW5zd2VyaW5nIG1hY2hpbmUgZnVuY3Rpb25h
bGl0eSkNCg0KSSB3b3VsZCBsaWtlIHRvIGtub3cgd2hlbiB0aGUgY2FsbCBhcnJpdmVzIGEgcGhv
bmUsIGJ5IHdoaWNoIHBhcmFtL2hlYWRlciB2YWx1ZSB0aGUgcGhvbmUgYW5zd2VycyB3aXRob3V0
IHJpbmdpbmcuDQoNCg0KDQpBbnkgcmVwb25zZSB3b3VsZCBiZSBhcHByZWNpYXRlZC4NCg0KDQpK
aW5reXVuZyBId2FuZw0KS1Q=

------=_NextPart_000_0192_01C4ADF7.C7090140
Content-Type: text/html;
 charset="utf-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT48L1RJVExFPg0KPE1FVEEgaHR0cC1lcXVpdj1D
b250ZW50LVR5cGUgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIGNv
bnRlbnQ9Ik1TSFRNTCA2LjAwLjI4MDAuMTQ1OCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9T
VFlMRT4NCjwvSEVBRD4NCjxCT0RZIHRleHQ9IzAwMDAwMCBiZ0NvbG9yPSNmZmZmZmY+DQo8RElW
PjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPkhpLCA8L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPjwvRk9OVD4mbmJz
cDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+SXMg
dGhlcmUgYW55IEktRCByZWdhcmRpbmcgcGFyYW1zIGZvciANClNJUCBwaG9uZSB0byBhbnN3ZXIg
YXV0b21hdGljYWxseSA/IChmb3IgYW5zd2VyaW5nIG1hY2hpbmUgDQpmdW5jdGlvbmFsaXR5KTwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+
PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgw
IHNpemU9Mj5JIHdvdWxkIGxpa2UgdG8ga25vdyB3aGVuIHRoZSBjYWxsIA0KYXJyaXZlcyBhIHBo
b25lLCBieSB3aGljaCBwYXJhbS9oZWFkZXIgdmFsdWUgdGhlIHBob25lIGFuc3dlcnMgd2l0aG91
dCANCnJpbmdpbmcuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0j
MDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U96rW066a8
IGNvbG9yPSMwMDAwODAgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFj
ZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj5BbnkgcmVwb25zZSB3b3VsZCBi
ZSANCmFwcHJlY2lhdGVkLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29s
b3I9IzAwMDA4MCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1
tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05U
IGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPkppbmt5dW5nIEh3YW5nPC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj5LVDwvRk9O
VD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0192_01C4ADF7.C7090140--



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




From sipping-bounces@ietf.org  Mon Oct 11 02:57: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 CAA05928
	for <sipping-web-archive@ietf.org>; Mon, 11 Oct 2004 02:57:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CGuHh-0000RE-9j
	for sipping-web-archive@ietf.org; Mon, 11 Oct 2004 03:07:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CGu4P-0004Mq-7T; Mon, 11 Oct 2004 02:54:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CGu3i-0004Es-Mj
	for sipping@megatron.ietf.org; Mon, 11 Oct 2004 02:53:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05782
	for <sipping@ietf.org>; Mon, 11 Oct 2004 02:53:24 -0400 (EDT)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGuE9-0000NL-CH
	for sipping@ietf.org; Mon, 11 Oct 2004 03:04:16 -0400
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
	(PMDF V6.0-24 #40642) id <0I5E00C01R0YHO@siemenscomms.co.uk> for
	sipping@ietf.org; Mon, 11 Oct 2004 07:50:58 +0100 (BST)
Received: from ntht206e.siemenscomms.co.uk ([137.223.247.52])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0I5E00891R0YC8@siemenscomms.co.uk>; Mon,
	11 Oct 2004 07:50:58 +0100 (BST)
Received: by ntht206e.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <T53C87XX>; Mon, 11 Oct 2004 07:52:44 +0100
Content-return: allowed
Date: Mon, 11 Oct 2004 07:52:38 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] Continuation of discussion on draft-elwell-sipping-
	redirection-re	ason
To: "'Mary Barnes'" <mary.barnes@nortelnetworks.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <50B1CBA96870A34799A506B2313F26670252D437@ntht201e>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 715d0e6950aaebd45af78ef9318d0186
Cc: Francois Audet <audet@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0717460921=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 14278aea5bdd1edf35ec09ffb7b61f9d

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.

--===============0717460921==
Content-return: allowed
Content-type: multipart/alternative;
	boundary="Boundary_(ID_QTmmP2ZPoCApLEk2/y1jlw)"

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

--Boundary_(ID_QTmmP2ZPoCApLEk2/y1jlw)
Content-type: text/plain
Content-Transfer-Encoding: 7BIT

Mary,
 
Sorry for the delay in replying. I am in the final stages of producing a
revised I-D to define a new "protocol" in the Reason header.
 
John

  _____  

From: Mary Barnes [mailto:mary.barnes@nortelnetworks.com] 
Sent: 05 October 2004 16:21
To: 'sipping@ietf.org'
Cc: Francois Audet; 'Elwell, John'
Subject: RE: [Sipping] Continuation of discussion on draft-elwell-sipping-
redirection-re ason


Hi all,
 
It's been awhile and there's been no further discussion on this thread, so
it appears that there is general consensus for the approach to define a new
"protocol" in the Reason Header with a new set of codes for redirection
scenarios.   This would require the Reason header in responses to be
captured in the History-Info.  
 
This does impact the current version of the History-Info draft as it
currently does not look at the Reason header when adding the Reason to its
entry, but rather uses only the SIP response codes to create a new reason
header.  I'll follow-up on the SIP list with the impact on the draft to
support the general concept of using the Reason header.
 
Regards,
Mary 

-----Original Message-----
From: Audet, Francois [SC100:9T51:EXCH] 
Sent: Friday, August 20, 2004 1:55 PM
To: 'Elwell, John'; 'sipping@ietf.org'
Subject: RE: [Sipping] Continuation of discussion on draft-elwell-sipping-
redirection-re ason



That's fine with me. Makes sense from a backward compatibility perspective 
too. 

> -----Original Message----- 
> From: Elwell, John [mailto:john.elwell@siemens.com
<mailto:john.elwell@siemens.com> ] 
> Sent: Friday, August 20, 2004 03:10 
> To: Audet, Francois [SC100:9T51:EXCH]; 'sipping@ietf.org' 
> Subject: RE: [Sipping] Continuation of discussion on 
> draft-elwell-sipping- redirection-re ason 
> 
> 
> Francois, 
> 
> I agree that is a problem that needs to be solved. The 
> relationship to my redirection-reason proposal is that a 
> redirection reason could be inserted somehow into the 3xx 
> response to indicate that it is a redirection in support of a 
> retarget (according the usage of this term in History-Info) 
> and therefore should result in the addition of a History-Info 
> entry (subject to other considerations such as privacy) in 
> the redirected INVITE request. Absence of this indication in 
> the 3xx response (or an explicit value) would imply normal 
> routing (case 2 in your example). 
> 
> Regards, 
> 
> John 
> 
> ________________________________ 
> 
> From: Francois Audet [mailto:audet@nortelnetworks.com
<mailto:audet@nortelnetworks.com> ] 
> Sent: 19 August 2004 02:38 
> To: 'sipping@ietf.org' 
> Cc: 'Elwell, John' 
> Subject: RE: [Sipping] Continuation of discussion on 
> draft-elwell-sipping- redirection-re ason 
> 
> 
> 
> At the San Diego meeting, I promised to described on the list the 
> 302 ambiguity issue. 
> 
> 1st scenario: 
> 
> In this scenario, Alice calls Victor Mann who is absent, and 
> his phones 
> forwards the call to his voicemail system at +1-408-555-1212. 
> 
> A Proxy server is used for routing. Call is routed to 
> sip:vm@blabla.com. 
> Victor has programmed Call forwarding on his phone 
> to forward it to his voicemail at sip:+14085551212@example.com. 
> Victor's phone responds to the INVITE with a 302 Moved temporarily, 
> with Contact: <sip:+14085551212@example.com>. I.e., Victor's phone 
> retargets the call to sip:+14085551212@example.com. Alice's 
> phone then 
> sends an INVITE to Victor's voicemail which will be received 
> interpreted by 
> the voicemail system. The INVITE will look like this: 
> 
> INVITE sip:+14085551212@example.com 
> From: Alice <sip:alice@example.com> 
> To: <sip:vm@blabla.com> 
> History-Info: <sip:vm@blabla.com?Reason=SIP;cause=302>;index=1, 
>               <sip:+14085551212@example.com>;index=2 
> ... 
> 
> 
> 2nd scenario: 
> 
> In this scenario, Alice calls directly her voicemail system. 
> 
> A Redirect server is used for routing. In this case, the voicemail 
> system's address of record is sip:vm@blabla.com. This address is 
> currently routed to a PSTN address +1-408-555-1212 where the 
> legacy voicemail system resides. 
> 
> The redirect server responds with a 302 Moved temporarily, 
> with Contact: 
> <sip:+14085551212@example.com>. This is NOT a retarget in a 
> call forwarding 
> sense, but simple routing with a redirect server. Alice's 
> phone then sends 
> an INVITE to the voicemail system. The INVITE will look like this: 
> 
> INVITE sip:+14085551212@example.com 
> From: Alice <sip:alice@example.com> 
> To: <sip:vm@blabla.com> 
> History-Info: <sip:vm@blabla.com?Reason=SIP;cause=302>;index=1, 
>               <sip:+14085551212@example.com>;index=2 
>                    
>            
> In the two cases, the INVITEs are exaclty the same (including 
> History-Info). 
> 
> 
> However, in the first example, the voicemail system is supposed to 
> let Alice LEAVE a message in Victor Mann's mailbox and in the 
> second case, 
> it is supposed to let Alice RETRIEVE her messages. 
> 
> The 302 Reason is ambiguous in this case because it doesn't 
> distinguish 
> between routing (with a redirect server) and retargeting. 
> 
> Note that the problem does NOT occur with a proxy server: 
> only with a redirect 
> server. It will result in inconsistent behavior between 
> networks where a proxy is 
> used and networks where a redirect server is used for call routing. 
> 
> Of course, this is just an example. Similar issues will occur if one 
> is trying to carryover retargetting/redirection information 
> into the PSTN. 
> Similar issues will also occur for any type of service which 
> have different 
> behaviors depending if the call was retargeted or not (e.g., 
> IVR systems). 
> 
> 
> > -----Original Message----- 
> > From: Elwell, John [mailto:john.elwell@siemens.com
<mailto:john.elwell@siemens.com> ] 
> > Sent: Tuesday, August 17, 2004 09:51 
> > To: 'sipping@ietf.org' 
> > Subject: [Sipping] Continuation of discussion on 
> > draft-elwell-sipping-redirection-re ason 
> > 
> > 
> > At the IETF60 SIPPING meeting different opinions were 
> > expressed about the value of enhancing the repertoire of 
> > reasons for retargeting/redirection, as proposed in the 
> > draft. I would like to solicit more opinions on the following 
> > questions: 
> 
> 
> _______________________________________________ 
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
<https://www1.ietf.org/mailman/listinfo/sipping>  
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current sip 
> Use sip@ietf.org for new developments of core SIP 
> 


--Boundary_(ID_QTmmP2ZPoCApLEk2/y1jlw)
Content-type: text/html
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=262095106-11102004><FONT face=Arial 
color=#0000ff size=2>Mary,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=262095106-11102004><FONT face=Arial 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=262095106-11102004><FONT face=Arial 
color=#0000ff size=2>Sorry for the delay in replying. I am in the final stages 
of producing a revised I-D to define a new "protocol" in the Reason 
header.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=262095106-11102004><FONT face=Arial 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=262095106-11102004><FONT face=Arial 
color=#0000ff size=2>John</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Mary Barnes 
[mailto:mary.barnes@nortelnetworks.com] <BR><B>Sent:</B> 05 October 2004 
16:21<BR><B>To:</B> 'sipping@ietf.org'<BR><B>Cc:</B> Francois Audet; 'Elwell, 
John'<BR><B>Subject:</B> RE: [Sipping] Continuation of discussion on 
draft-elwell-sipping- redirection-re ason<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>Hi 
all,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>It's 
been awhile and there's been no further discussion on this thread, so it appears 
that there is general consensus for the approach to define a <FONT size=2>new 
"protocol" in the Reason Header with a new set of codes</FONT> for redirection 
scenarios. &nbsp; This would require the Reason header in responses to be 
captured in the History-Info.&nbsp; </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=496282518-28092004>This 
does impact the current version of the History-Info draft as it currently does 
not look at the Reason header when adding the Reason to its entry, but rather 
uses only the SIP response codes to create a new reason header.&nbsp; I'll 
follow-up on the SIP list with the impact on the draft to support the general 
concept of using the Reason header.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=496282518-28092004></SPAN></FONT><FONT face=Arial color=#0000ff 
size=2><SPAN class=496282518-28092004></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN lang=en-us><FONT face=Arial><FONT color=#0000ff size=2><SPAN 
class=496282518-28092004>Regards,</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN lang=en-us><FONT face=Arial><FONT size=2><SPAN 
class=496282518-28092004></SPAN><FONT 
color=#0000ff>Mary</FONT></FONT></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Audet, Francois 
  [SC100:9T51:EXCH] <BR><B>Sent:</B> Friday, August 20, 2004 1:55 
  PM<BR><B>To:</B> 'Elwell, John'; 'sipping@ietf.org'<BR><B>Subject:</B> RE: 
  [Sipping] Continuation of discussion on draft-elwell-sipping- redirection-re 
  ason<BR><BR></FONT></DIV>
  <P><FONT size=2>That's fine with me. Makes sense from a backward compatibility 
  perspective</FONT> <BR><FONT size=2>too.</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> <BR><FONT size=2>&gt; 
  From: Elwell, John [<A 
  href="mailto:john.elwell@siemens.com">mailto:john.elwell@siemens.com</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: Friday, August 20, 2004 03:10</FONT> 
  <BR><FONT size=2>&gt; To: Audet, Francois [SC100:9T51:EXCH]; 
  'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] 
  Continuation of discussion on </FONT><BR><FONT size=2>&gt; 
  draft-elwell-sipping- redirection-re ason</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Francois,</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I agree that is a problem 
  that needs to be solved. The </FONT><BR><FONT size=2>&gt; relationship to my 
  redirection-reason proposal is that a </FONT><BR><FONT size=2>&gt; redirection 
  reason could be inserted somehow into the 3xx </FONT><BR><FONT size=2>&gt; 
  response to indicate that it is a redirection in support of a </FONT><BR><FONT 
  size=2>&gt; retarget (according the usage of this term in History-Info) 
  </FONT><BR><FONT size=2>&gt; and therefore should result in the addition of a 
  History-Info </FONT><BR><FONT size=2>&gt; entry (subject to other 
  considerations such as privacy) in </FONT><BR><FONT size=2>&gt; the redirected 
  INVITE request. Absence of this indication in </FONT><BR><FONT size=2>&gt; the 
  3xx response (or an explicit value) would imply normal </FONT><BR><FONT 
  size=2>&gt; routing (case 2 in your example).</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; Regards,</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; John</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; ________________________________</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; From: Francois Audet [<A 
  href="mailto:audet@nortelnetworks.com">mailto:audet@nortelnetworks.com</A>] 
  </FONT><BR><FONT size=2>&gt; Sent: 19 August 2004 02:38</FONT> <BR><FONT 
  size=2>&gt; To: 'sipping@ietf.org'</FONT> <BR><FONT size=2>&gt; Cc: 'Elwell, 
  John'</FONT> <BR><FONT size=2>&gt; Subject: RE: [Sipping] Continuation of 
  discussion on </FONT><BR><FONT size=2>&gt; draft-elwell-sipping- 
  redirection-re ason</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; At the San Diego 
  meeting, I promised to described on the list the </FONT><BR><FONT size=2>&gt; 
  302 ambiguity issue. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  1st scenario: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; In 
  this scenario, Alice calls Victor Mann who is absent, and </FONT><BR><FONT 
  size=2>&gt; his phones </FONT><BR><FONT size=2>&gt; forwards the call to his 
  voicemail system at +1-408-555-1212. </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; A Proxy server is used for routing. Call is 
  routed to </FONT><BR><FONT size=2>&gt; sip:vm@blabla.com. </FONT><BR><FONT 
  size=2>&gt; Victor has programmed Call forwarding on his phone 
  </FONT><BR><FONT size=2>&gt; to forward it to his voicemail at 
  sip:+14085551212@example.com. </FONT><BR><FONT size=2>&gt; Victor's phone 
  responds to the INVITE with a 302 Moved temporarily, </FONT><BR><FONT 
  size=2>&gt; with Contact: &lt;sip:+14085551212@example.com&gt;. I.e., Victor's 
  phone </FONT><BR><FONT size=2>&gt; retargets the call to 
  sip:+14085551212@example.com. Alice's </FONT><BR><FONT size=2>&gt; phone then 
  </FONT><BR><FONT size=2>&gt; sends an INVITE to Victor's voicemail which will 
  be received </FONT><BR><FONT size=2>&gt; interpreted by </FONT><BR><FONT 
  size=2>&gt; the voicemail system. The INVITE will look like this: 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; INVITE 
  sip:+14085551212@example.com </FONT><BR><FONT size=2>&gt; From: Alice 
  &lt;sip:alice@example.com&gt; </FONT><BR><FONT size=2>&gt; To: 
  &lt;sip:vm@blabla.com&gt; </FONT><BR><FONT size=2>&gt; History-Info: 
  &lt;sip:vm@blabla.com?Reason=SIP;cause=302&gt;;index=1, </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;sip:+14085551212@example.com&gt;;index=2 </FONT><BR><FONT size=2>&gt; ... 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; 2nd scenario: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; In this scenario, Alice calls directly her voicemail system. 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; A Redirect server is 
  used for routing. In this case, the voicemail </FONT><BR><FONT size=2>&gt; 
  system's address of record is sip:vm@blabla.com. This address is 
  </FONT><BR><FONT size=2>&gt; currently routed to a PSTN address 
  +1-408-555-1212 where the </FONT><BR><FONT size=2>&gt; legacy voicemail system 
  resides. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; The 
  redirect server responds with a 302 Moved temporarily, </FONT><BR><FONT 
  size=2>&gt; with Contact: </FONT><BR><FONT size=2>&gt; 
  &lt;sip:+14085551212@example.com&gt;. This is NOT a retarget in a 
  </FONT><BR><FONT size=2>&gt; call forwarding </FONT><BR><FONT size=2>&gt; 
  sense, but simple routing with a redirect server. Alice's </FONT><BR><FONT 
  size=2>&gt; phone then sends </FONT><BR><FONT size=2>&gt; an INVITE to the 
  voicemail system. The INVITE will look like this: </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; INVITE sip:+14085551212@example.com 
  </FONT><BR><FONT size=2>&gt; From: Alice &lt;sip:alice@example.com&gt; 
  </FONT><BR><FONT size=2>&gt; To: &lt;sip:vm@blabla.com&gt; </FONT><BR><FONT 
  size=2>&gt; History-Info: 
  &lt;sip:vm@blabla.com?Reason=SIP;cause=302&gt;;index=1, </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;sip:+14085551212@example.com&gt;;index=2 </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </FONT><BR><FONT 
  size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </FONT><BR><FONT size=2>&gt; In the two cases, the INVITEs are exaclty the 
  same (including </FONT><BR><FONT size=2>&gt; History-Info).</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; However, 
  in the first example, the voicemail system is supposed to </FONT><BR><FONT 
  size=2>&gt; let Alice LEAVE a message in Victor Mann's mailbox and in the 
  </FONT><BR><FONT size=2>&gt; second case, </FONT><BR><FONT size=2>&gt; it is 
  supposed to let Alice RETRIEVE her messages. </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; The 302 Reason is ambiguous in this case because 
  it doesn't </FONT><BR><FONT size=2>&gt; distinguish </FONT><BR><FONT 
  size=2>&gt; between routing (with a redirect server) and retargeting. 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Note that the 
  problem does NOT occur with a proxy server: </FONT><BR><FONT size=2>&gt; only 
  with a redirect </FONT><BR><FONT size=2>&gt; server. It will result in 
  inconsistent behavior between </FONT><BR><FONT size=2>&gt; networks where a 
  proxy is </FONT><BR><FONT size=2>&gt; used and networks where a redirect 
  server is used for call routing. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Of course, this is just an example. Similar issues will occur if 
  one </FONT><BR><FONT size=2>&gt; is trying to carryover 
  retargetting/redirection information </FONT><BR><FONT size=2>&gt; into the 
  PSTN. </FONT><BR><FONT size=2>&gt; Similar issues will also occur for any type 
  of service which </FONT><BR><FONT size=2>&gt; have different </FONT><BR><FONT 
  size=2>&gt; behaviors depending if the call was retargeted or not (e.g., 
  </FONT><BR><FONT size=2>&gt; IVR systems). </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; &gt; -----Original 
  Message-----</FONT> <BR><FONT size=2>&gt; &gt; From: Elwell, John [<A 
  href="mailto:john.elwell@siemens.com">mailto:john.elwell@siemens.com</A>] 
  </FONT><BR><FONT size=2>&gt; &gt; Sent: Tuesday, August 17, 2004 09:51 
  </FONT><BR><FONT size=2>&gt; &gt; To: 'sipping@ietf.org' </FONT><BR><FONT 
  size=2>&gt; &gt; Subject: [Sipping] Continuation of discussion on 
  </FONT><BR><FONT size=2>&gt; &gt; draft-elwell-sipping-redirection-re ason 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; At the IETF60 SIPPING meeting different 
  opinions were</FONT> <BR><FONT size=2>&gt; &gt; expressed about the value of 
  enhancing the repertoire of </FONT><BR><FONT size=2>&gt; &gt; reasons for 
  retargeting/redirection, as proposed in the </FONT><BR><FONT size=2>&gt; &gt; 
  draft. I would like to solicit more opinions on the following </FONT><BR><FONT 
  size=2>&gt; &gt; questions: </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  _______________________________________________</FONT> <BR><FONT size=2>&gt; 
  Sipping mailing list&nbsp; <A 
  href="https://www1.ietf.org/mailman/listinfo/sipping" 
  target=_blank>https://www1.ietf.org/mailman/listinfo/sipping</A></FONT> 
  <BR><FONT size=2>&gt; This list is for NEW development of the application of 
  SIP</FONT> <BR><FONT size=2>&gt; Use sip-implementors@cs.columbia.edu for 
  questions on current sip</FONT> <BR><FONT size=2>&gt; Use sip@ietf.org for new 
  developments of core SIP</FONT> <BR><FONT size=2>&gt; 
</FONT></P></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_QTmmP2ZPoCApLEk2/y1jlw)--


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



From sipping-bounces@ietf.org  Mon Oct 11 15:05: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 PAA04719
	for <sipping-web-archive@ietf.org>; Mon, 11 Oct 2004 15:05:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CH5eo-0006mm-95
	for sipping-web-archive@ietf.org; Mon, 11 Oct 2004 15:16:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CH5Qt-0006xJ-Ne; Mon, 11 Oct 2004 15:02:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CH5KK-0002MC-JP
	for sipping@megatron.ietf.org; Mon, 11 Oct 2004 14:55:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03433
	for <sipping@ietf.org>; Mon, 11 Oct 2004 14:55:18 -0400 (EDT)
Received: from mail.lumenvox.com ([206.169.193.45] helo=lv-svr.lumenvox.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH5Uu-0006Q7-Lo
	for sipping@ietf.org; Mon, 11 Oct 2004 15:06:17 -0400
Received: from PROGTHOMAS ([10.0.0.141]) by lv-svr.lumenvox.com with Microsoft
	SMTPSVC(5.0.2195.6713); Mon, 11 Oct 2004 11:46:39 -0700
From: "Thomas Gal" <ThomasGal@LumenVox.com>
To: "'???'" <jkhwang@kt.co.kr>, <sipping@ietf.org>
Subject: RE: [Sipping] automatic answer
Date: Mon, 11 Oct 2004 11:54:47 -0700
Organization: LumenVox LLC
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <2D0CA64CDC33E14DA7AB043B8CC4D2BB0258C7A4@svr-exc.domain.com>
Thread-Index: AcStrPuU0xePy/MhQIaUINQ2ahqUpQCFMylg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <LV-SVRBZgQkM0V987y700000cc0@lv-svr.lumenvox.com>
X-OriginalArrivalTime: 11 Oct 2004 18:46:39.0375 (UTC)
	FILETIME=[A4A109F0:01C4AFC2]
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ThomasGal@LumenVox.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>
Content-Type: multipart/mixed; boundary="===============0176350325=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.7 (+)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9

This is a multi-part message in MIME format.

--===============0176350325==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_011A_01C4AF89.1B3476E0"

This is a multi-part message in MIME format.

------=_NextPart_000_011A_01C4AF89.1B3476E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

    Have you read the spec? You will probably get slammed with some
responses as there's several ways to do this.
    If you support presence, then it should be automatic. The SIP Proxy
would route the request to vmail and it would be automatic. Or:
 
21.4.24 486 Busy Here

   The callee's end system was contacted successfully, but the callee is
   currently not willing or able to take additional calls at this end
   system.  The response MAY indicate a better time to call in the
   Retry-After header field.  The user could also be available
   elsewhere, such as through a voice mail service.  Status 600 (Busy
   Everywhere) SHOULD be used if the client knows that no other end
   system will be able to accept this call.
 
Would be indicative of the need to contact another location, probably to
leave a voicemail. Typically this could be done with a redirection server.
If it was stateful it would know to try another location (ie voicemail). 
 
    Plus your question is kinda ambiguous, so I hope this helps. Really this
is a system implementation question it seems, and up to the implementor.
 
Tom



  _____  

From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of ???
Sent: Friday, October 08, 2004 8:02 PM
To: sipping@ietf.org
Subject: [Sipping] automatic answer


Hi, 
 
Is there any I-D regarding params for SIP phone to answer automatically ?
(for answering machine functionality)
 
I would like to know when the call arrives a phone, by which param/header
value the phone answers without ringing.
 
 
 
Any reponse would be appreciated.
 
 
Jinkyung Hwang
KT


------=_NextPart_000_011A_01C4AF89.1B3476E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D610294018-11102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp;&nbsp; Have you read the spec? You =
will=20
probably get slammed with some responses as there's several ways to do=20
this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D610294018-11102004>&nbsp;&nbsp;&nbsp; <FONT=20
face=3DArial color=3D#0000ff size=3D2>If you support presence, then it =
should be=20
automatic. The SIP Proxy would route the request to vmail and it would =
be=20
automatic. Or:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D610294018-11102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D610294018-11102004>21.4.24 486 =
Busy=20
Here<BR><BR>&nbsp;&nbsp; The callee's end system was contacted =
successfully, but=20
the callee is<BR>&nbsp;&nbsp; currently not willing or able to take =
additional=20
calls at this end<BR>&nbsp;&nbsp; system.&nbsp; The response MAY =
indicate a=20
better time to call in the<BR>&nbsp;&nbsp; Retry-After header =
field.&nbsp; The=20
user could also be available<BR>&nbsp;&nbsp; elsewhere, such as through =
a voice=20
mail service.&nbsp; Status 600 (Busy<BR>&nbsp;&nbsp; Everywhere) SHOULD =
be used=20
if the client knows that no other end<BR>&nbsp;&nbsp; system will be =
able to=20
accept this call.</SPAN></DIV>
<DIV><SPAN class=3D610294018-11102004></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D610294018-11102004><FONT face=3DArial color=3D#0000ff =
size=3D2>Would=20
be indicative of the need to contact another location, probably to leave =
a=20
voicemail. Typically this could be done with a redirection server. If it =
was=20
stateful it would know to try another location (ie voicemail).=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D610294018-11102004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D610294018-11102004>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Plus your question is kinda ambiguous, so I =
hope this=20
helps. Really this is a system implementation question it seems, and up =
to the=20
implementor.</FONT></SPAN></DIV>
<DIV><SPAN class=3D610294018-11102004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D610294018-11102004><FONT face=3DArial color=3D#0000ff =

size=3D2>Tom</FONT></DIV>
<DIV dir=3Dltr align=3Dleft><BR></DIV></SPAN><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> sipping-bounces@ietf.org=20
  [mailto:sipping-bounces@ietf.org] <B>On Behalf Of =
</B>???<BR><B>Sent:</B>=20
  Friday, October 08, 2004 8:02 PM<BR><B>To:</B>=20
  sipping@ietf.org<BR><B>Subject:</B> [Sipping] automatic=20
  answer<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 size=3D2>Hi, =
</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 size=3D2>Is there =
any I-D regarding params for=20
  SIP phone to answer automatically ? (for answering machine=20
  functionality)</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 size=3D2>I would =
like to know when the call=20
  arrives a phone, by which param/header value the phone answers without =

  ringing.</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 size=3D2>Any =
reponse would be=20
  appreciated.</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080 size=3D2>Jinkyung =
Hwang</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; color=3D#000080=20
size=3D2>KT</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_011A_01C4AF89.1B3476E0--



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




From sipping-bounces@ietf.org  Tue Oct 12 09:30:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19563
	for <sipping-web-archive@ietf.org>; Tue, 12 Oct 2004 09:30:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CHMud-0005BO-5h
	for sipping-web-archive@ietf.org; Tue, 12 Oct 2004 09:42:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHMbT-0006Xh-FF; Tue, 12 Oct 2004 09:22:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHMVj-0004Jj-31
	for sipping@megatron.ietf.org; Tue, 12 Oct 2004 09:16:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18425
	for <sipping@ietf.org>; Tue, 12 Oct 2004 09:16:13 -0400 (EDT)
From: concita@aethra.com
Received: from fe-mail04.albacom.net ([213.217.149.84]
	helo=FE-mail04.sfg.albacom.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHMgP-0004uo-F9
	for sipping@ietf.org; Tue, 12 Oct 2004 09:27:21 -0400
Received: from sirmail.vnet.aethra.it (217.220.54.50) by
	FE-mail04.sfg.albacom.net (7.0.009)
	id 40F9D5C70063D3D3; Tue, 12 Oct 2004 15:04:24 +0200
Received: from alderaan ([192.168.110.167])
	by sirmail.vnet.aethra.it (Lotus Domino Release 5.0.11)
	with ESMTP id 2004101215045400:47830 ;
	Tue, 12 Oct 2004 15:04:54 +0200 
To: jdrosen@dynamicsoft.com
Subject: [Sipping] Nat scenarios: examples
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF779AD9AD.DB586169-ONC1256F2A.004A2E7E@vnet.aethra.it>
Date: Tue, 12 Oct 2004 15:05:04 +0200
X-MIMETrack: Serialize by Router on SIRCOMPAQ2/AETHRA(Release 5.0.11 |July 24,
	2002) at 12.10.2004 15:05:09,
	Serialize complete at 12.10.2004 15:05:09,
	Itemize by SMTP Server on SIRMAIL/AETHRA(Release 5.0.11  |July 24,
	2002) at 10/12/2004 03:04:54 PM,
	Serialize by Router on SIRMAIL/AETHRA(Release 5.0.11  |July 24,
	2002) at 10/12/2004 03:05:08 PM,
	Serialize complete at 10/12/2004 03:05:08 PM
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0123585071=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

Questo 
 un messaggio multiparte in formato MIME.
--===============0123585071==
Content-Type: multipart/alternative;
	boundary="=_alternative 0047B98FC1256F2B_="

Questo 
 un messaggio multiparte in formato MIME.
--=_alternative 0047B98FC1256F2B_=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit

Hi,
I'd like to have some clarification about 
draft-rosenberg-sipping-nat-scenarios-03, in particular about session 5.1 
"Intra-Enterprise Call".
I'd like to understand better the ICE methodology and reading the examples 
in this draft I have some doubts. 
Please would you like to help me? below some questions of mine:

in Figure 25 (A's unilateral allocations) in messages 6-7 there are TURN 
Alloc & TURN Resp with s=192.0.2.1:9989, d= 192.0.2.10:5556 and M= 
192.0.2.10:8076.......and in Figure 28 in messages 5-6 the STUN Bind 
(to/from STUN+TURN server) use d=192.0.2:9988 instead of 192.0.2.1:9989 
... Does the TURN server lock down the binding allocated to A in messages 
5-6 of Figure 28? 
in Figure 30, messages 4-5: the corporate NAT uses a mapping 
s=10.0.1.1:1010, d=192.0.2.10:8078 --> s=192.0.2.1:9992................... while in Figure 28, messages 4-5 , in the same 
Corporate NAT there is a mapping s=10.0.1.2:23766, d=192.0.2.10:8076--> s=192.0.2.1:9992. Is it correct ? Is it possible to bind the same address/port pair to two 
different source-destination pairs?
in Figure 30, message 14: why is d=192.0.2.1:9991 instead of 
d=192.0.2.1:9992? This question just thinking of binding locked down to A 
(compering messages 13-14 in figure 30 with messages 9-10 in figure 28). 
Furthermore, in figure 30 the message 15 uses a NAT's binding 
s=192.0.2.10:8076, d=192.0.2.1:9991 --> d=10.0.1.2:23766 (-->is it in 
contrast with the NAT's binding used in figure 28 for messages 4-5?)

Thanks in advance for your support.
Concita 
--=_alternative 0047B98FC1256F2B_=
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7Bit


<br><font size=2 face="sans-serif">Hi,</font>
<br><font size=2 face="sans-serif">I'd like to have some clarification about draft-rosenberg-sipping-nat-scenarios-03, in particular about session 5.1 &quot;Intra-Enterprise Call&quot;.</font>
<br><font size=2 face="sans-serif">I'd like to understand better the ICE methodology and reading the examples in this draft I have some doubts. </font>
<br><font size=2 face="sans-serif">Please would you like to help me? below some questions of mine:</font>
<br>
<ul>
<li><font size=2 face="sans-serif">in Figure 25 (A's unilateral allocations) in messages 6-7 there are TURN Alloc &amp; TURN Resp with s=192.0.2.1:9989, d= 192.0.2.10:5556 and M= 192.0.2.10:8076.......and in Figure 28 in messages 5-6 the STUN Bind (to/from STUN+TURN server) use d=192.0.2:9988 instead of 192.0.2.1:9989 &nbsp;... Does the TURN server lock down the binding allocated to A in messages 5-6 of Figure 28? </font>
<li><font size=2 face="sans-serif">in Figure 30, messages 4-5: the corporate NAT uses a mapping s=10.0.1.1:1010, d=192.0.2.10:8078 --&gt; s=<b>192.0.2.1:9992</b>................... while in Figure 28, messages 4-5 , in the same Corporate NAT there is a mapping s=10.0.1.2:23766, d=192.0.2.10:8076--&gt; s=<b>192.0.2.1:9992</b>. Is it correct ? Is it possible to bind the same address/port pair to two different source-destination pairs?</font>
<li><font size=2 face="sans-serif">in Figure 30, message 14: why is d=192.0.2.1:9991 instead of d=192.0.2.1:9992? This question just thinking of binding locked down to A (compering messages 13-14 in figure 30 with messages 9-10 in figure 28). Furthermore, in figure 30 the message 15 uses a NAT's binding s=192.0.2.10:8076, d=192.0.2.1:9991 --&gt; d=10.0.1.2:23766 (--&gt;is it in contrast with the NAT's binding used in figure 28 for messages 4-5?)</font>
<br>
<br><font size=2 face="sans-serif">Thanks in advance for your support.</font>
<br><font size=2 face="sans-serif">Concita &nbsp;</font></ul>
--=_alternative 0047B98FC1256F2B_=--


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



From sipping-bounces@ietf.org  Tue Oct 12 14:04: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 OAA14959
	for <sipping-web-archive@ietf.org>; Tue, 12 Oct 2004 14:04:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CHRBP-0003fz-VL
	for sipping-web-archive@ietf.org; Tue, 12 Oct 2004 14:15:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHQss-0005tl-2u; Tue, 12 Oct 2004 13:56:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHQju-0003Z5-RT
	for sipping@megatron.ietf.org; Tue, 12 Oct 2004 13:47:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13380
	for <sipping@ietf.org>; Tue, 12 Oct 2004 13:47:10 -0400 (EDT)
Received: from qfe1.july.broomfield1.level3.net ([209.245.18.72]
	helo=f4bb49-05.idc1.level3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHQue-0003Dx-V2
	for sipping@ietf.org; Tue, 12 Oct 2004 13:58:20 -0400
Received: from scanner5.level3.com (qfe0.f10212-07.adc1.oss.level3.com
	[10.2.1.102])
	by f4bb49-05.idc1.level3.com (8.12.10/8.12.10) with ESMTP id
	i9CHkktO027755; Tue, 12 Oct 2004 17:46:46 GMT
Received: from scanner5.level3.com (localhost [127.0.0.1])
	by localhost.level3.com (Postfix) with ESMTP
	id 14BE6124803; Tue, 12 Oct 2004 17:46:39 +0000 (GMT)
Received: from idc1exc0001.corp.global.level3.com
	(idc1exc0001.corp.global.level3.com [10.1.7.194])
	by scanner5.level3.com (Postfix) with SMTP
	id AE63F124802; Tue, 12 Oct 2004 17:46:38 +0000 (GMT)
Received: from idc1exc0004.corp.global.level3.com ([10.1.8.20]) by
	idc1exc0001.corp.global.level3.com with Microsoft
	SMTPSVC(6.0.3790.0); Tue, 12 Oct 2004 11:46:38 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 12 Oct 2004 11:46:37 -0600
Message-ID: <3F75233A2E57CC468B35F3B1FAF71EC01299E7@idc1exc0004.corp.global.level3.com>
Thread-Topic: Status of dialog event package?
Thread-Index: AcSwg2xNThuKL3IYSvqdc3NbFlG8bw==
From: "Hearty, John" <John.Hearty@Level3.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 12 Oct 2004 17:46:38.0417 (UTC)
	FILETIME=[6CB43410:01C4B083]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: rohan@ekabal.com, jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu
Subject: [Sipping] Status of dialog 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>
Content-Type: multipart/mixed; boundary="===============1011562528=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0

This is a multi-part message in MIME format.

--===============1011562528==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4B083.6C631094"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4B083.6C631094
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Can anyone tell me what the status of this draft is?  The 04 version
expired 8/13/2004.  I found nothing in the archives.  Rohan appeared to
be the main editor and I see he is traveling to Guatemala from October
12 till October 27.

=20

John Hearty

Level3


------_=_NextPart_001_01C4B083.6C631094
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3D"#606420">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can anyone tell me what the status of this draft is? =
&nbsp;The
04 version expired 8/13/2004.&nbsp; I found nothing in the =
archives.&nbsp;
Rohan appeared to be the main editor and I see he is traveling to =
Guatemala from October 12 till October 27.</span></font></p>

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C4B083.6C631094--


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



From sipping-bounces@ietf.org  Tue Oct 12 15:47: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 PAA24942
	for <sipping-web-archive@ietf.org>; Tue, 12 Oct 2004 15:47:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CHSn5-0005wW-6M
	for sipping-web-archive@ietf.org; Tue, 12 Oct 2004 15:58:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHSXu-0005UU-RE; Tue, 12 Oct 2004 15:42:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSRG-0002Sv-B9
	for sipping@megatron.ietf.org; Tue, 12 Oct 2004 15:36:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23253
	for <sipping@ietf.org>; Tue, 12 Oct 2004 15:36:01 -0400 (EDT)
Received: from figas.ekabal.com ([157.22.13.42])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHSc1-0005a7-4L
	for sipping@ietf.org; Tue, 12 Oct 2004 15:47:12 -0400
Received: (from apache@localhost)
	by figas.ekabal.com (8.11.6/8.11.6) id i9CJZZJ10331;
	Tue, 12 Oct 2004 12:35:35 -0700
From: Rohan Mahy <rohan@ekabal.com>
X-Authentication-Warning: figas.ekabal.com: apache set sender to
	rohan@localhost using -f
Received: from 131.161.248.67 (SquirrelMail authenticated user rohan);
	by figas.ekabal.com with HTTP; Tue, 12 Oct 2004 12:35:35 -0700 (PDT)
Message-ID: <1274.131.161.248.67.1097609735.squirrel@131.161.248.67>
In-Reply-To: <3F75233A2E57CC468B35F3B1FAF71EC01299E7@idc1exc0004.corp.global.level3
	.com>
References: <3F75233A2E57CC468B35F3B1FAF71EC01299E7@idc1exc0004.corp.global.level3.com>
Date: Tue, 12 Oct 2004 12:35:35 -0700 (PDT)
To: "Hearty, John" <John.Hearty@Level3.com>
User-Agent: SquirrelMail/1.4.3a-1
X-Mailer: SquirrelMail/1.4.3a-1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 8bit
Cc: rohan@ekabal.com, jdrosen@dynamicsoft.com, sipping@ietf.org,
        schulzrinne@cs.columbia.edu
Subject: [Sipping] Re: Status of dialog 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: 8bit

This draft will be updated to reflect the consensus reached in San Diego
(add two new media feature parameters).

thanks,
-rohan

> Can anyone tell me what the status of this draft is?  The 04 version
> expired 8/13/2004.  I found nothing in the archives.  Rohan appeared to
> be the main editor and I see he is traveling to Guatemala from October
> 12 till October 27.
>
>
>
> John Hearty
>
> Level3
>
>


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 02:48: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 CAA28860
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 02:48:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIM4x-0007Oh-2P
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 03:00:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CILs6-0005yY-CO; Fri, 15 Oct 2004 02:47:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CILlZ-0004Ts-VY
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 02:40:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28398
	for <sipping@ietf.org>; Fri, 15 Oct 2004 02:40:40 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CILwt-0007Ff-J2
	for sipping@ietf.org; Fri, 15 Oct 2004 02:52:23 -0400
Received: from dynamicsoft.com ([63.113.46.23])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i9F6eXdj013703
	for <sipping@ietf.org>; Fri, 15 Oct 2004 02:40:33 -0400 (EDT)
Message-ID: <416F538A.1050508@dynamicsoft.com>
Date: Fri, 15 Oct 2004 00:35:22 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Subject: [Sipping] What problems are SBCs addressing?
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

Folks,

As many of you know, there are a large number of products on the market 
these days under the general moniker "Session Border Controller"; 
generally these are B2BUas that play some kind of policy enforcement and 
control function, typically at trust boundaries.

Our specifications don't define how B2BUas should operate, and they say 
nothing at all about an SBC (although they do address many problems that 
relate to inter-domain operations and trust boundaries). However, the 
preponderence of these devices in the market and in VoIP networks seems 
to indicate that there are real problems that providers believe they 
have, which they feel these products are solving for them.

This begs the important question - what are those problems, and are 
those problems for which the IETF has produced specifications to 
address? If not, is there a need to do so? If yes, are these products 
using those specifications, and if not, why have those solutions not 
seen implementation and/or deployment?

Put in another way, sipping is all about requirements and problems, and 
it is clear that there are one or more problems here somewhere. Do we 
understand those requirements, and do we need to produce specifications 
to address them?

This is a fairly meaty topic, one for which I expect to see lots of 
emails in reply to this note suggesting answers ;) Furthermore, we are 
planning an informal get together at IETF 61 to continue the dialog, 
focusing squarely on understanding requirements and specification gaps. 
Details TBA shortly. Whether one likes the solutions that are out there 
or not, the first step in doing anything is to understand the 
requirements. I really want to do that.

I think it's important to have this discussion now, while there is still 
time to address these issues with standards-based solutions. To 
paraphrase Spencer Dawkins' recent note - I don't want to have a BoF 
session three years hence called "son-of-behave", where we discuss what 
an SBC should do, wishing that we had written specifications three years 
earlier and thus avoided the interop mess that had resulted. Given the 
recent concerns about GRUU and SIP identity operation through SBC, this 
is even more telling.

Inputs from people who work for vendors of such devices, your input is 
most welcome..

Thanks,
Jonathan R.

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



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


From sipping-bounces@ietf.org  Fri Oct 15 04:32:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04891
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 04:32:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CINhA-0000pa-DP
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 04:44:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CINTj-0006uE-Vs; Fri, 15 Oct 2004 04:30:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CINRP-0006Uo-MZ
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 04:27:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04713
	for <sipping@ietf.org>; Fri, 15 Oct 2004 04:27:56 -0400 (EDT)
From: stredicke@snom.de
Received: from www.strato-webmail.de ([81.169.148.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CINcj-0000lP-8m
	for sipping@ietf.org; Fri, 15 Oct 2004 04:39:41 -0400
Received: from localhost ([127.0.0.1] helo=snom.de)
	by www.strato-webmail.de with smtp (Exim 4.10)
	id 1CINRG-0007Mk-00; Fri, 15 Oct 2004 10:27:50 +0200
To: Jonathan@ietf.org, Rosenberg@ietf.org,
        [jdrosen@dynamicsoft.com].cnri.reston.va.us
Subject: Re: [Sipping] What problems are SBCs addressing?
X-Mailer: STRATO-Webmail.de, powered by PHlyMail OEM, http://phlymail.com
X-Sender-IP: 217.224.213.53
Message-Id: <E1CINRG-0007Mk-00@www.strato-webmail.de>
Date: Fri, 15 Oct 2004 10:27:50 +0200
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
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.3 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

I think there are three things a SBC is adressing:

1. Converter from "lean" SIP to "full" SIP:

Most of the devices out there are not really SIP compliant (missing TCP
support, UDP fragmentation, sloppy routing support, REFER, DNS NAPTR/SRV,
MoH, etc etc). Most of the SBC address this problem by making these
devices a little bit smarter so that from the outside world they look like
"real" SIP user agents.

2. Things that a UA can't do

Here we are essentially talking about NAT. Especially in the Symmetrical
NAT case, even the smartest UA can not esablish two-way audio. A TURN
server would be an alternative, but the SBC approach (combined with other
features) seems to be easier. ICE can be nicely combiled with that.

3. Security and Billing

Hide information to the UA! For example, the UA should not see the routing
information (if the packet goes through a PSTN gateway or directly!). If
you want to record calls (caleia), the media must flow through a device
that can do the recording.


Christian

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Friday, October 15, 2004 9:01 AM
> To: sipping
> Subject: [Sipping] What problems are SBCs addressing?
> 
> Folks,
> 
> As many of you know, there are a large number of products on 
> the market these days under the general moniker "Session 
> Border Controller"; generally these are B2BUas that play some 
> kind of policy enforcement and control function, typically at 
> trust boundaries.
> 
> Our specifications don't define how B2BUas should operate, 
> and they say nothing at all about an SBC (although they do 
> address many problems that relate to inter-domain operations 
> and trust boundaries). However, the preponderence of these 
> devices in the market and in VoIP networks seems to indicate 
> that there are real problems that providers believe they 
> have, which they feel these products are solving for them.
> 
> This begs the important question - what are those problems, 
> and are those problems for which the IETF has produced 
> specifications to address? If not, is there a need to do so? 
> If yes, are these products using those specifications, and if 
> not, why have those solutions not seen implementation and/or 
> deployment?
> 
> Put in another way, sipping is all about requirements and 
> problems, and it is clear that there are one or more problems 
> here somewhere. Do we understand those requirements, and do 
> we need to produce specifications to address them?
> 
> This is a fairly meaty topic, one for which I expect to see 
> lots of emails in reply to this note suggesting answers ;) 
> Furthermore, we are planning an informal get together at IETF 
> 61 to continue the dialog, focusing squarely on understanding 
> requirements and specification gaps. 
> Details TBA shortly. Whether one likes the solutions that are 
> out there or not, the first step in doing anything is to 
> understand the requirements. I really want to do that.
> 
> I think it's important to have this discussion now, while 
> there is still time to address these issues with 
> standards-based solutions. To paraphrase Spencer Dawkins' 
> recent note - I don't want to have a BoF session three years 
> hence called "son-of-behave", where we discuss what an SBC 
> should do, wishing that we had written specifications three 
> years earlier and thus avoided the interop mess that had 
> resulted. Given the recent concerns about GRUU and SIP 
> identity operation through SBC, this is even more telling.
> 
> Inputs from people who work for vendors of such devices, your 
> input is most welcome..
> 
> Thanks,
> Jonathan R.
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> 
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 04:51:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06325
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 04:51:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CINzJ-0001E0-8e
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 05:03:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CINkJ-0000fM-Se; Fri, 15 Oct 2004 04:47:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CINga-0000FC-Hc
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 04:43:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05788
	for <sipping@ietf.org>; Fri, 15 Oct 2004 04:43:38 -0400 (EDT)
From: stredicke@snom.de
Received: from natnoddy.rzone.de ([81.169.145.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CINru-000140-SA
	for sipping@ietf.org; Fri, 15 Oct 2004 04:55:23 -0400
Received: from snom.de (pD9E0D535.dip.t-dialin.net [217.224.213.53])
	by post.webmailer.de (8.13.1/8.13.1) with ESMTP id i9F8hVuh029027
	for <sipping@ietf.org>; Fri, 15 Oct 2004 10:43:32 +0200 (MEST)
Received: from mail pickup service by snom.de with Microsoft SMTPSVC;
	Fri, 15 Oct 2004 10:46:25 +0200
Thread-Index: AcSyk3PAsnjnsUfTQwevBb31y4+cTQ==
X-Envelope-From: <stredicke@snom.de>
X-Envelope-To: <stredicke@snom.de>
X-Delivery-Time: 1097828873
Message-ID: <001001c4b293$73c08530$3a00a8c0@intern.snom.de>
To: <Jonathan@post.webmailer.de>, <Rosenberg@post.webmailer.de>,
        "\"[jdr\"@dynamicsoft.com]" <"[jdr"@dynamicsoft.com].cnri.reston.va.us>,
        "IMB Recipient 1" <mspop3connector.Christian.Stredicke@snom.de>
Subject: Re: [Sipping] What problems are SBCs addressing?
X-Mailer: STRATO-Webmail.de, powered by PHlyMail OEM, http://phlymail.com
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
X-Sender-IP: 217.224.213.53
Importance: normal
Date: Fri, 15 Oct 2004 10:46:24 +0200
Priority: normal
X-OriginalArrivalTime: 15 Oct 2004 08:46:25.0515 (UTC)
	FILETIME=[74591BB0:01C4B293]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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.6 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027

I think there are three things a SBC is adressing:

1. Converter from "lean" SIP to "full" SIP:

Most of the devices out there are not really SIP compliant (missing TCP
support, UDP fragmentation, sloppy routing support, REFER, DNS NAPTR/SRV,
MoH, etc etc). Most of the SBC address this problem by making these
devices a little bit smarter so that from the outside world they look like
"real" SIP user agents.

2. Things that a UA can't do

Here we are essentially talking about NAT. Especially in the Symmetrical
NAT case, even the smartest UA can not esablish two-way audio. A TURN
server would be an alternative, but the SBC approach (combined with other
features) seems to be easier. ICE can be nicely combiled with that.

3. Security and Billing

Hide information to the UA! For example, the UA should not see the routing
information (if the packet goes through a PSTN gateway or directly!). If
you want to record calls (caleia), the media must flow through a device
that can do the recording.


Christian

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Friday, October 15, 2004 9:01 AM
> To: sipping
> Subject: [Sipping] What problems are SBCs addressing?
> 
> Folks,
> 
> As many of you know, there are a large number of products on 
> the market these days under the general moniker "Session 
> Border Controller"; generally these are B2BUas that play some 
> kind of policy enforcement and control function, typically at 
> trust boundaries.
> 
> Our specifications don't define how B2BUas should operate, 
> and they say nothing at all about an SBC (although they do 
> address many problems that relate to inter-domain operations 
> and trust boundaries). However, the preponderence of these 
> devices in the market and in VoIP networks seems to indicate 
> that there are real problems that providers believe they 
> have, which they feel these products are solving for them.
> 
> This begs the important question - what are those problems, 
> and are those problems for which the IETF has produced 
> specifications to address? If not, is there a need to do so? 
> If yes, are these products using those specifications, and if 
> not, why have those solutions not seen implementation and/or 
> deployment?
> 
> Put in another way, sipping is all about requirements and 
> problems, and it is clear that there are one or more problems 
> here somewhere. Do we understand those requirements, and do 
> we need to produce specifications to address them?
> 
> This is a fairly meaty topic, one for which I expect to see 
> lots of emails in reply to this note suggesting answers ;) 
> Furthermore, we are planning an informal get together at IETF 
> 61 to continue the dialog, focusing squarely on understanding 
> requirements and specification gaps. 
> Details TBA shortly. Whether one likes the solutions that are 
> out there or not, the first step in doing anything is to 
> understand the requirements. I really want to do that.
> 
> I think it's important to have this discussion now, while 
> there is still time to address these issues with 
> standards-based solutions. To paraphrase Spencer Dawkins' 
> recent note - I don't want to have a BoF session three years 
> hence called "son-of-behave", where we discuss what an SBC 
> should do, wishing that we had written specifications three 
> years earlier and thus avoided the interop mess that had 
> resulted. Given the recent concerns about GRUU and SIP 
> identity operation through SBC, this is even more telling.
> 
> Inputs from people who work for vendors of such devices, your 
> input is most welcome..
> 
> Thanks,
> Jonathan R.
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP 
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> 
> 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 06:38: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 GAA15294
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 06:38:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIPfK-0003Xz-Cd
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 06:50:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIPKh-0008Rk-Jj; Fri, 15 Oct 2004 06:29:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CBviu-0000n2-To
	for sipping@megatron.ietf.org; Mon, 27 Sep 2004 09:39:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29132
	for <sipping@ietf.org>; Mon, 27 Sep 2004 09:39:22 -0400 (EDT)
Received: from mail.xmedius.net ([207.35.87.240] helo=PEGASUS.interstarinc.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBvqT-00067t-0k
	for sipping@ietf.org; Mon, 27 Sep 2004 09:47:17 -0400
Received: by pegasus.interstarinc.com with Internet Mail Service (5.5.2657.72)
	id <TRJL9Q61>; Mon, 27 Sep 2004 09:45:49 -0400
Message-ID: <3EEA4EEB3CA1304A9D8E3F8D2344856C02AB3497@pegasus.interstarinc.com>
From: Laurent Sabourin <lsabourin@interstarinc.com>
To: msharmin@comcast.net, sipping@ietf.org
Subject: RE: [Sipping] sip & T38 fax
Date: Mon, 27 Sep 2004 09:45:48 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4A498.4B955A80"
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 27926f06e907bbf9243f0c64922be55f
X-Mailman-Approved-At: Fri, 15 Oct 2004 06:29:10 -0400
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.5 (+++)
X-Scan-Signature: 33707bc67e3caa2a3a3b1a445f23984a

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_01C4A498.4B955A80
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4A498.4B955A80"


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

Attached to the message :
=20
draft-ietf-sipping-realtimefax-00.txt by Jean-Fran=E7ois Mule.

-----Original Message-----
From: msharmin@comcast.net [mailto:msharmin@comcast.net]
Sent: September 26, 2004 22:30
To: sipping@ietf.org
Subject: [Sipping] sip & T38 fax


What is the status of sip based T38 fax? There was a draft by Jean Mule
sometime back, I cant seem to be able to locate it anymore.=20


------_=_NextPart_001_01C4A498.4B955A80
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.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D535513713-27092004>Attached to the message =
:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D535513713-27092004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D535513713-27092004>draft-ietf-sipping-realtimefax-00.txt by =
Jean-Fran=E7ois=20
Mule.</SPAN></FONT></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
msharmin@comcast.net=20
  [mailto:msharmin@comcast.net]<BR><B>Sent:</B> September 26, 2004=20
  22:30<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> [Sipping] sip =
&amp;=20
  T38 fax<BR><BR></FONT></DIV>What is the status of sip based T38 fax? =
There was=20
  a draft by Jean Mule sometime back, I cant seem to be able to locate =
it=20
  anymore. </BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4A498.4B955A80--

------_=_NextPart_000_01C4A498.4B955A80
Content-Type: text/plain;
	name="draft-ietf-sipping-realtimefax-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-sipping-realtimefax-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable



Internet Engineering Task Force                      Jean-Francois Mule =

Internet Draft                                                CableLabs =

Document: <draft-ietf-sipping-realtimefax-00.txt>            Jieying Li =

Category: Informational                                   iVox Networks =

Expires: February 2002                                      August 2002 =

=20
                      SIP Support for Real-time Fax:=20
                            Call Flow Examples=20
                                    And=20
                          Best Current Practices=20
=20
Status of this Memo=20
=20
   This document is an Internet-Draft and is in full conformance with=20
   all provisions of Section 10 of RFC2026 [1]. =20
   =20
   Internet-Drafts are working documents of the Internet Engineering=20
   Task Force (IETF), its areas, and its working groups.  Note that=20
   other groups may also distribute working documents as Internet-
   Drafts. =20
   =20
   Internet-Drafts are draft documents valid for a maximum of six=20
   months and may be updated, replaced, or obsoleted by other documents =

   at any time.  It is inappropriate to use Internet- Drafts as=20
   reference material or to cite them other than as "work in progress." =
=20
   =20
   The list of current Internet-Drafts can be accessed at=20
   http://www.ietf.org/ietf/1id-abstracts.txt =20
   The list of Internet-Draft Shadow Directories can be accessed at=20
   http://www.ietf.org/shadow.html.=20
   =20
   =20
1. Abstract=20
   =20
   The Session Initiation Protocol (SIP) allows the establishment of=20
   real-time Internet fax communications.  Real-time facsimile=20
   communications over IP may follow 2 modes of operation: T.38 fax=20
   relay as defined by the ITU-T T.38 recommendation or fax pass-
   through. =20
   This document clarifies the options available to Internet telephony=20
   gateway vendors to handle real-time fax calls using SIP.  While our=20
   primary focus is to address the more reliable real-time T.38 Group 3 =

   fax mode, we briefly cover the fax pass-through mode to enable=20
   fallback operations and super G3 fax communications using SIP.  We=20
   also give examples of SIP call flows for real-time Internet fax=20
   gateways or SIP proxy redirect servers.  Elements in these call=20
   flows include SIP User Agents, SIP Proxy Servers, and Gateways to=20
   the PSTN (Public Switch Telephone Network).=20
   This document introduces best current practices for SIP T.38 fax and =

   SIP fax pass-through sessions.  A session starts with audio=20
   capabilities, and, upon fax tone detection, T.38 fax capabilities=20
   are negotiated; upon successful negotiation, the session continues=20
   with fax capabilities and the media termination hosts exchange T.38=20
   Internet fax packets.  The T.38 fax call scenarios include various=20
 =20
J-F. Mule/J. Li               SIPPING WG                             1=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   aspects of the call sequence: the detection of fax transmission, the =

   usage of the T.38 session description attributes, the optional=20
   fallback into fax pass-through mode and the session termination. The =

   fax pass-through call scenarios involve some specific SDP media=20
   attributes to enable proper fax transmission.=20
   Fax transmission can be detected by the receiving side, the emitting =

   side or both (in the latter case, a 'glare' effect may appear). =20
   This document only covers the case when the fax transmission is=20
   detected by the receiving side: it is the most common practice and=20
   the other cases do not represent any particular challenges and are=20
   therefore left for future discussions).  Call flow diagrams and=20
   message details are shown.  A list of IANA defined SDP attribute=20
   names for T.38 is summarized in section 7.=20
   =20
   =20
                             Table of Contents=20
   =20
Status of this =
Memo.......................................................1=20
1. =
Abstract...............................................................1=
=20
2. Conventions used in this =
document......................................3=20
3. =
Overview...............................................................3=
=20
3.1.  General =
Assumptions.................................................3=20
3.2 Legend for Message =
Flows..............................................3=20
3.3 Changes to previous =
drafts............................................4=20
4 Handling of real-time fax communication using =
SIP.......................4=20
4.1 Internet telephony gateways and fax =
detection.........................5=20
4.2 Internet telephony gateways and T.38 fax media =
connections............5=20
4.3 SIP session and fax =
termination.......................................6=20
4.4 Internet telephony gateways and fax pass-through =
mode.................6=20
4.5 Responses to SIP OPTIONS =
request......................................7=20
4.6 Beyond Internet telephony =
gateways....................................7=20
5 Successful SIP T.38 fax Call =
Scenarios..................................7=20
5.1 Internet fax device =96 fax only =
support................................7=20
5.1.1 Sequence =
Diagram....................................................7=20
5.1.2 Message =
Details.....................................................8=20
5.2 SIP T.38 fax call =96 fax stream replaces voice =
stream.................13=20
5.2.1 Sequence =
Diagram...................................................13=20
5.2.2 Message =
Details....................................................15=20
5.3 SIP T.38 fax call =96 fax stream added to voice =
stream.................25=20
5.3.1 Sequence =
Diagram...................................................26=20
5.3.2 Message =
Details....................................................27=20
5.4 SIP T.38 fax call =96 fax stream forced to replace voice =
stream........37=20
5.4.1 Sequence =
Diagram...................................................37=20
5.4.2 Message =
Details....................................................37=20
6. Unsuccessful =
Scenarios................................................41=20
6.1. Unsuccessful T.38 fax scenario =96 no support for =
T.38................41=20
6.1.1. Sequence =
Diagram..................................................41=20
6.1.2. Message =
Details...................................................42=20
6.2. Unsuccessful T.38 fax scenario =96 488/606 response & G.711 =
fallback..43=20
6.2.1. Sequence =
Diagram..................................................44=20
6.2.2. Message =
Details...................................................45=20
7. SDP Attribute Table for T.38 =
sessions.................................50=20
8. =
Considerations........................................................51=
=20
8.1. Level of requirements for Internet =
gateways.........................51=20
8.2. Negotiation of UDP ports for T.38 =
transmission......................51=20
 =20
J-F. Mule/J. Li                                                      2=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
8.3. Adding a fax stream to SIP session vs. Replacing audio =
stream.......51=20
8.4. Adding text to make use of SIP OPTIONS: in progress in =
draft-02.....51=20
8.5. Use of IP addresses in SDP connection =
information...................52=20
8.6. Unsuccessful scenario: 606 or =
488...................................52=20
9. Security =
Considerations...............................................52=20
10. =
References...........................................................52 =

11. =
Acknowledgments......................................................53 =

12. Author's =
Addresses...................................................53=20
Full Copyright =
Statement.................................................53=20
   =20
   =20
2. Conventions used in this document=20
   =20
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=20
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in=20
   this document are to be interpreted as described in RFC-2119 [2].=20
   =20
   =20
3. Overview=20
   =20
   The Session Initiation Protocol (SIP) is defined by RFC2543 [3] and=20
   T.38 is the ITU-T Recommendation defining the procedures for real-
   time Group 3 facsimile communications over IP networks [4].  This=20
   document deals with the handling of real-time fax communications=20
   using the SIP protocol for T.38 fax and fax pass-through modes.  =20
   For T.38, this document deals primarily with one transport protocol=20
   for the media: T.38 over UDP/UDPTL; T.38 fax packet transport over=20
   TCP using SIP session establishment can easily be extrapolated.=20
   These T.38 call flows were developed in the design of carrier-class=20
   SIP Telephony products supporting voice and real-time fax traffic.=20
   It is the hope of the authors that this document will be useful for=20
   the SIP community, SIP implementors of T.38 fax products, designers. =

   Call flows shown in this document complement the main SIP call flow=20
   Internet-Draft [5].  These call flows are based on the current=20
   version 2.0 of SIP in RFC2543[3], the ITU-T T.38 Amendment 2 [6] and =

   an ITU-T SG8 liaison to IANA.  Note: IANA registration of the T.38=20
   SDP attributes is currently a work in progress.=20
   =20
   =20
3.1.  General Assumptions=20
   =20
   Internet telephony gateways with T.38 support MAY pass various fax=20
   tones (T.30 CNG, CED, etc.) or flag sequence (like V.21 Preamble) in =

   the RTP audio streams before those tones or flag sequence are=20
   detected.  Once detected by the DSP resources, T.38 fax-capable=20
   devices switch from audio to fax mode and initiate a T.38 fax packet =

   transmission.=20
   These best current practices MAY apply to "Network Gateway",=20
   "Enterprise Gateway" and Internet-aware fax devices or terminals.=20
   =20
   =20
3.2 Legend for Message Flows=20
   =20
 =20
J-F. Mule/J. Li                                                      3=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   The legend defined [5] also applies in this document. =20
   Dashed lines (---) represent control messages that are mandatory to  =
=20
   the call scenario.  These control messages can be SIP or PSTN=20
   signaling. Double dashed lines (=3D=3D=3D) represent media paths =
between=20
   network elements. Messages with parenthesis around name represent=20
   optional control messages.  Messages are identified in the Figures=20
   as F1, F2, etc.  This references the message details in the table=20
   that follows the Figure.  Comments in the message details are shown=20
   in the following form:    /* Comments. */=20
   =20
   =20
3.3 Changes to previous drafts=20
   =20
   o  Changes to draft-01=20
   The changes between the current draft and draft-01 are:=20
      - Major updates: =20
            + additions based on SIPit fax testing event 8/2001: added=20
              text regarding the negotiation of T38MaxBitRate in 4.2,=20
            + added more general text for the handling of real-time=20
              fax pass-through,=20
            + added of echo cancellation & silence suppression SDP=20
              attributes and usage recommendations in 6.2,=20
            + correction of the session version number in SDP when=20
              issuing re-INVITE with updated SDP information as per=20
              draft-ietf-sip-rfc2543bis-05,=20
            + started a section on the use of the OPTIONS method to =20
              determine the support of T.38 capabilities (work-in-=20
              progress),=20
      - Minor editorial updates (added tag fields in To and From header =

   lines as well as Contact header lines as per draft-ietf-sip-
   rfc2543bis-05, added proper reference to T.38 Amendment 2 pre-
   published version, exact case matching for T38MaxBitRate, etc.)=20
   =20
   o  Changes to draft-00=20
   The major changes between draft-01 and draft-00 are listed below:=20
      - Major updates: =20
            + new text in fax handling section 4.2 based on sip list: =20
              clarified text for fax detection, capability negotiation  =

              and termination=20
            + additions of new successful call flows in section 5=20
            + additions of unsuccessful call flows in section 6         =
   =20
      - Added Record-Route header, modified Cseq numbers, =20
      - Added T38FaxMaxDatagram attribute in SDP and corrected =20
        the sample value for T38FaxMaxBuffer,=20
      - Minor editorial changes (e.g. removed references in Abstract).=20
4 Handling of real-time fax communication using SIP=20
   =20
   The handling of real-time fax sessions using SIP involves the=20
   initial session establishment, the modification or negotiation of=20
   session capabilities upon fax detection, the optional fallback into=20
   fax pass-through mode and the session termination.=20
   =20

 =20
J-F. Mule/J. Li                                                      4=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   Some variants of these best current practices MAY apply depending on =

   the nature or the configuration of Internet telephony gateways.  Two =

   distinct cases are considered in this document:=20
         o The Internet telephony gateway only supports T.38 real-time=20
   fax communications (by design or by configuration).  In this case,=20
   the Internet fax gateway SHOULD initiate the SIP session with T.38=20
   SDP capabilities (this is typically the case of Internet fax=20
   terminals, also called Internet-aware fax devices or the case of=20
   gateways statically configured to support T.38 fax calls only);=20
         o The Internet telephony gateway supports voice and real-time=20
   fax communications.  In this case, the Internet telephony gateway=20
   initiates the SIP session with audio capabilities, and, upon fax=20
   detection, the switchover to T.38 fax capabilities is triggered. =20
   The fax media connection may replace or be added to the audio=20
   connection depending on the target applications.=20
   =20
=20
4.1 Internet telephony gateways and fax detection=20
   =20
   Two possible ways exist for an Internet telephony gateway to detect=20
   a facsimile communication:=20
   =20
   1. On the emitting gateway (the one sending the facsimile document), =

   the T.30 calling tone (CNG) is detected.  The CNG tone is however an =

   optional signal [7];=20
   2. On the receiving gateway, the V.21 Preamble flag sequence is=20
   detected.  The Preamble is always present and follows the called=20
   station identification tone (CED) when CED is present.=20
   Note that even though the CED tone may be detected on the receiving=20
   gateway, since the fax CED tone is similar to V.25 ANS modem tones,=20
   it SHOULD NOT be used to trigger the fax switchover.=20
   =20
   In conclusion, several conditions can trigger fax detection.=20
   Internet telephony gateways supporting T.38 real-time facsimile MUST =

   support the detection of fax transmission on the V.21 Preamble flag=20
   sequence; Internet telephony gateways MAY support the detection of=20
   fax on CNG tone.  The authors recommend that a facsimile=20
   transmission SHOULD be detected on the receiving Internet telephony=20
   gateway.  =20
   =20
   =20
4.2 Internet telephony gateways and T.38 fax media connections=20
   =20
   Upon successful fax detection, the description of the media=20
   connection(s) is modified using the SDP protocol [8] as described in =

   SIP (see sections in chapter 5).=20
   =20
   Several cases should be considered:=20
   - In the case of Internet fax devices (supporting T.38 fax only=20
   communications), the SIP session is established with SDP description =

   containing the T.38 media attributes; refer to section 5.1 for a=20
   sample call flow for Internet fax devices.=20

 =20
J-F. Mule/J. Li                                                      5=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   - In the case of Internet telephony gateways, the SIP/SDP session is =

   modified and the T.38 fax media connection SHOULD replace the=20
   existing audio media connection.  The SIP UAC triggering the=20
   modification of the session description MUST indicate all of its=20
   T.38 media attributes in SDP.  This is the recommended behavior for=20
   gateways; refer to section 5.2 for a sample call flow illustrating=20
   this scenario. =20
   Some implementations MAY choose to add the fax media connection to=20
   the existing audio connection and in that case, they SHOULD mute the =

   audio connection while fax is transmitted.  Refer to section 5.3 for =

   a sample call flow illustrating this optional scenario.=20
   =20
   Note:=20
   Among the SDP T.38 media attributes being exchanged after fax=20
   detection, implementors should particularly pay attention to=20
   T38MaxBitRate, the maximum T.38 bit rate for the media connection. =20
   It is recommended to implement the following rule when responding to =

   a maximum bit rate proposal.  If the remote peer's SDP description=20
   contains a maximum fax bit rate of X and the local host is set to a=20
   maximum bit rate of Y (either by fax protocol detection or=20
   configuration), the local host MUST propose a maximum fax rate of=20
   min (X,Y) in the SIP response to the re-INVITE in order to=20
   facilitate the negotiation.  This note is exemplified in section=20
   5.2.1. in messages F11-F14.  Failures to implement this rule MAY=20
   imply call teardown in some cases.=20
   =20
   =20
4.3 SIP session and fax termination=20
   =20
   Upon completion of the fax transmission, any audio connection=20
   successfully established prior to fax detection SHOULD be restored=20
   or the session MUST be terminated.=20
   =20
   =20
4.4 Internet telephony gateways and fax pass-through mode=20
   =20
   This section deals real-time facsimile communications over IP using=20
   fax pass-through instead of T.38 fax relay.  In this mode, the=20
   facsimile communication is handled as a PCM audio call (PCMA/PCMU as =

   specified in ITU-T recommendation G.711). =20
   =20
   The fax pass-through mode is important to prevent call failures, for =

   example in cases when one of the SIP communication peers does not=20
   support T.38.  For Internet telephony gateways with support for=20
   PCM/G.711 audio but no support for T.38 real-time fax, it is=20
   recommended to switch the session to fax pass-through mode. =20
   Internet telephony gateways SHOULD handle the fall back mode to fax=20
   pass-through by recognizing the SDP T.38 connection and proposing to =

   switch to a new audio connection.  The new audio connection SHOULD=20
   have the following characteristics: at a minimum, specify PCM G.711=20
   codec, silence suppression OFF, echo cancellation ON.  The telephony =

   gateway that originated the failed T.38 re-INVITE SHOULD initiate=20
   the subsequent re-INVITE to fax pass-through mode. =20
 =20
J-F. Mule/J. Li                                                      6=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   Refer to section 6.2 for a sample call flow illustrating this=20
   scenario.=20
   =20
   =20
4.5 Responses to SIP OPTIONS request=20
   Suggestion currently logged in section 8.4, just a placeholder for=20
   now; <<work in progress >>=20
   =20
   =20
4.6 Beyond Internet telephony gateways=20
   =20
   This document may also serve to vendors of SIP redirect servers or=20
   other SIP UA types like SIP phones.  Such SIP entities may recognize =

   the fax nature of the sessions and redirect the flows to the proper=20
   real-time fax-capable devices or to other fax service providers.=20
   =20
   =20
5 Successful SIP T.38 fax Call Scenarios=20
   =20
   =20
5.1 Internet fax device =96 fax only support=20
=20
   This section represents a SIP call flow for a T.38 fax session=20
   between 2 Internet fax terminals.  It is also applicable to Internet =

   telephony gateways when telephony ports are statically configured to =

   support fax only (case of analog IP telephony gateways where a=20
   specific port is connected to a fax terminal).=20
   A session starts with fax capabilities (t.38/udptl).  The mechanism=20
   for supporting T.38 in SIP & SDP is detailed in T.38 Annex D [9], a=20
   temporary document that proposes an amendment to T.38 describing SIP =

   call establishment procedures. =20
   =20
   =20
5.1.1 Sequence Diagram=20
   =20
     Internet Fax UA           Proxy               IFTGW UA=20
   =20
      Fax  |                    |                    |=20
   ------->|   F1 INVITE        |                    |=20
   emitted |------------------->|                    |=20
           |                    |   F2 INVITE        |=20
           |                    |------------------->|=20
           |   F3  100 Trying   |                    |=20
           |<-------------------|   F4  100 Trying   |=20
           |                    |<-------------------|=20
           |                    |                    |=20
           |                    |   F5  180 Ringing  |=20
           |   F6  180 Ringing  |<-------------------|=20
           |<-------------------|                    |=20
           |                    |   F7  200 OK       |=20
           |   F8  200 OK       |<-------------------|=20
           |<-------------------|                    |=20

 =20
J-F. Mule/J. Li                                                      7=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
           |   F9  ACK          |                    |=20
           |------------------->|   F10 ACK          |=20
           |                    |------------------->|=20
           |                                         |=20
           |         T.38/UDPTL Fax Flow Established |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   End of  |                                         |=20
   fax     |                    |                    |=20
   detected|                    |                    |=20
   ------->|                    |                    |=20
           |   F11 BYE          |                    |=20
           |------------------->|                    |=20
           |                    |   F12 BYE          |=20
           |                    |------------------->|=20
           |                    |   F13  200 OK      |=20
           |                    |<-------------------|=20
           |   F14  200 OK      |                    |=20
           |<-------------------|                    |=20
=20
=20
5.1.2 Message Details=20
   =20
   F1 INVITE  I.FAX UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab111=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ifax.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Difaxgw1 2890846527 2890846527 IN IP4 ifax.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 ifaxmg.here.com=20
      t=3D0 0=20
      m=3Dimage 15002 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
 =20
J-F. Mule/J. Li                                                      8=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   F2 INVITE  PROXY -> IFTGW UA=20
   =20
      INVITE sip:+1-650-555-2222@iftgw.there.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab111=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ifax.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Difaxgw1 2890846527 2890846527 IN IP4 ifax.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 ifaxmg.here.com=20
      t=3D0 0=20
      m=3Dimage 15002 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F3 (100 Trying) PROXY -> I.FAX UA=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab111=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Content-Length: 0=20
   =20
   =20
   =20
   =20
   =20
   F4 (100 Trying) IFTGW UA -> PROXY=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
 =20
J-F. Mule/J. Li                                                      9=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
   =20
   =20
   F5 180 Ringing IFTGW UA -> PROXY=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
    =20
   =20
   F6 180 Ringing PROXY -> I.FAX UA=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
   =20
   =20
   F7 200 OK   IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844527 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Dimage 49172 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
 =20
J-F. Mule/J. Li                                                     10=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F8 200 OK   PROXY -> I.FAX UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844527 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Dimage 49172 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F9 ACK I.FAX UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Route: <sip:+1-650-555-2222@iftgw.there.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   =20
 =20
J-F. Mule/J. Li                                                     11=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   F10 ACK PROXY -> IFTGW UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   =20
   /* T.38 fax streams are established. */=20
    =20
   =20
   F11 BYE I.FAX UA -> PROXY=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 18 BYE=20
      Content-Length: 0=20
   =20
   =20
   F12 BYE PROXY -> IFTGW UA=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 18 BYE=20
      Content-Length: 0=20
   =20
   =20
   =20
   =20
   =20
   F13 200 OK IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab22=20
 =20
J-F. Mule/J. Li                                                     12=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 18 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   F14 200 OK  PROXY -> I.FAX UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ifax.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ifax.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ifax.here.com=20
      CSeq: 18 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
5.2 SIP T.38 fax call =96 fax stream replaces voice stream=20
=20
   This section represents the SIP call flow for a T.38 fax session=20
   between 2 Internet telephony gateways (fax detection on terminating=20
   side). =20
   A session starts with audio capabilities, and then the session is=20
   modified to switch to t38 fax mode (t.38/udptl).=20
   =20
   Scenario:=20
   1. A SIP INVITE is sent to the called party requesting a voice=20
   connection per RFC2543; our scenario involves 1 SIP proxy.  An audio =

   connection is established,=20
   2. Upon detection of Preamble by the terminating gateway, a SIP re-
   INVITE request is sent to the emitting gateway to modify the=20
   parameters of the session to allow a T.38 fax media connection. =20
   This INVITE request contains new SDP information detailing T.38=20
   capabilities,=20
   3. Upon successful acknowledgments, T.38 IFP fax packets are=20
   sent/received on UDP ports, which may be the same UDP ports used for =

   audio RTP,=20
   4. Once the fax transmission is terminated, audio capabilities are=20
   =93restored=94 or the call is terminated.=20
   =20
   =20
   =20
   =20
5.2.1 Sequence Diagram=20
   In our example, we illustrate the fact that Internet telephony=20
   gateways may use multiple network interfaces for signaling and/or=20
   media streaming or one network interface with multiple IP addresses. =
 =20
   Typically, our example shows:=20

 =20
J-F. Mule/J. Li                                                     13=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      - one interface for SIP signaling =20
   (ingress gateway =3D ift.here.com, egress gateway =3D =
iftgw.there.com)=20
      - one or multiple interface(s) for media transport:=20
   (ingress gateway =3D iftmg.here.com, egress gateway =3D =
iftmg.there.com)=20
   A proxy is acting as a pure SIP signaling proxy (obelix.wcom.com).=20
   =20
         IFT UA                 Proxy              IFTGW UA=20
           |                    |                    |=20
           |   F1 INVITE        |                    |=20
           |------------------->|                    |=20
           |                    |   F2 INVITE        |=20
           |                    |------------------->|=20
           |   F3  100 Trying   |                    |=20
           |<-------------------|   F4  100 Trying   |=20
           |                    |<-------------------|=20
           |                    |                    |=20
           |                    |   F5  180 Ringing  |=20
           |   F6  180 Ringing  |<-------------------|=20
           |<-------------------|                    |=20
           |                    |   F7  200 OK       |=20
           |   F8  200 OK       |<-------------------|=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F9  ACK          |                    |=20
           |------------------->|   F10 ACK          |=20
           |                     ------------------->|=20
           |                                         |=20
           |      Both Way RTP Media Established     |=20
      Fax  =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   ------->|                                         |=20
   emitted |                    |                    | =20
           |                    |                    | Preamble=20
           |                    |                    |<---------=20
           |                    |   F11 INVITE       | detected=20
           |                    |<-------------------|=20
           |   F12 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F13 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F14 200 OK       |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F15  ACK         |=20
           |                    |<-------------------|=20
           |   F16  ACK         |                    |=20
           |<-------------------|                    |=20
           |                                         |=20
           |          T.38/UDPT Fax Flow Established |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   End of  |                                         |=20
   fax     |                    |                    |=20

 =20
J-F. Mule/J. Li                                                     14=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   detected|                    |                    |=20
   ------->|                    |                    |=20
           |                    |                    | End of fax=20
           |                    |                    |<----------=20
           |                    |                    |   detected=20
   =20
           |                    |   F17 INVITE       |   =20
           |                    |<-------------------|=20
           |   F18 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F19 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F20 200 OK       |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F21  ACK         |=20
           |                    |<-------------------|=20
           |   F22  ACK         |                    |=20
           |<-------------------|                    |=20
   =20
           |      Both Way RTP Media Re-Established  |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
           |   F23 BYE          |                    |=20
           |------------------->|                    |=20
           |                    |   F24 BYE          |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F25  200 OK      |=20
           |                    |<-------------------|=20
           |   F26  200 OK      |                    |=20
           |<-------------------|                    |=20
   =20
   =20
5.2.2 Message Details=20
   =20
   F1 INVITE  IFT UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 146=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 2890844527 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
 =20
J-F. Mule/J. Li                                                     15=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F2 INVITE  PROXY -> IFTGW UA=20
   =20
      INVITE sip:+1-650-555-2222@iftgw.there.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 146=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 2890844527 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F3 (100 Trying) PROXY -> IFT UA=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Content-Length: 0=20
   =20
   =20
   F4 100 Trying IFTGW UA -> PROXY=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
   =20
   =20
 =20
J-F. Mule/J. Li                                                     16=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   F5 180 Ringing IFTGW UA -> PROXY=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
    =20
   =20
   F6 180 Ringing PROXY -> IFT UA=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
   =20
   =20
   F7 200 OK   IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 171089 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   =20
   F8 200 OK   PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
 =20
J-F. Mule/J. Li                                                     17=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 171089 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F9 ACK IFT UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Route: <sip:+1-650-555-2222@iftgw.there.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   =20
   F10 ACK PROXY -> IFTGW UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   =20
   =20
   =20
   =20
   /* RTP streams are established.  The CNG fax tone is sent in-band if =

   it is present.  The receiving side IFT gateway DSP detects the=20
   Preamble sequence.  A new UDP port is open on IFTGW for T.38 IFP=20
   packets and the IFTGW signals the switch over to fax mode by send a=20
   re-INVITE with the new UDP port in the SDP.=20
 =20
J-F. Mule/J. Li                                                     18=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   Note: the IFTGW has a T38MaxBitRate configured to 9600 */=20
    =20
   =20
   F11 INVITE  IFTGW UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Dimage 49172 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:9600=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F12 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
 =20
J-F. Mule/J. Li                                                     19=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Dimage 49172 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:9600=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   /* Note: the IFT has a T38MaxBitRate configured to 14400 but since=20
   it received a T38MaxBitRate proposal of 9600, it replies with=20
   T38MaxBitRate =3D min (9600,14400) */=20
   =20
   F13 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Dimage 15002 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:9600=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F14 200 OK  PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
 =20
J-F. Mule/J. Li                                                     20=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Dimage 15002 udptl t38=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:9600=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F15 ACK IFTGW UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 ACK=20
      Content-Length: 0=20
   =20
   =20
   F16 ACK  PROXY -> IFT UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 ACK=20
      Content-Length: 0=20
   =20
   =20
 =20
J-F. Mule/J. Li                                                     21=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   /* T.38 fax transmission established both ways */=20
   =20
   /* Then, the end of the fax transmission is detected on ingress side =

   and sent to the egress side (IFTGW).  IFTGW initiates the switch=20
   back to voice communication */=20
   =20
   =20
   F17 INVITE  IFTGW UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F18 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
 =20
J-F. Mule/J. Li                                                     22=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   =20
   F19 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844529 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F20 200 OK  PROXY -> IFTGW UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844529 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   =20
   =20
   F21 ACK IFTGW UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
 =20
J-F. Mule/J. Li                                                     23=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   F22 ACK  PROXY -> IFT UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   /* Voice streams re-established both ways */=20
   =20
   =20
   F23 BYE IFT UA -> PROXY=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Length: 0=20
   =20
   =20
   F24 BYE PROXY -> IFTGW UA=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Length: 0=20
   =20
   =20
   F25 200 OK IFTGW UA -> PROXY=20
 =20
J-F. Mule/J. Li                                                     24=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde24=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   F26 200 OK  PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde24=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
5.3 SIP T.38 fax call =96 fax stream added to voice stream=20
   =20
   This section represents the SIP call flow for a T.38 fax session=20
   between 2 Internet telephony gateways.  It shows the detection of=20
   the fax communication on terminating or receiving side. =20
   A session starts with one audio stream in SDP, and, upon detection=20
   of fax, an additional fax stream is added to the session while the=20
   voice stream is muted.  After the fax communication is terminated,=20
   the fax stream is terminated and the voice stream is restored.=20
   =20
   Scenario:=20
   1. A SIP INVITE is sent to the called party requesting a voice=20
   connection per RFC2543; our scenario involves 1 SIP proxy.  An audio =

   connection is established,=20
   2. Upon detection of Preamble by the terminating gateway, a SIP=20
   re=ADINVITE request is sent to the emitting gateway to modify the=20
   parameters of the session to add a T.38 fax connection.  The=20
   connection data is specified per media description and not at the=20
   session-level.  This allows the audio stream and t.38 fax stream to=20
   be controlled independently (i.e., placing the audio on hold while=20
   the t.38 fax transmission is active).  Also note that the t.38 fax=20
   media stream has been added to the session.  This re-INVITE request=20
   contains SDP information detailing the additional T.38 capabilities, =

   3. It is suggested that the voice pipe be muted while the fax=20
   session is in progress.  Upon successful acknowledgments, T.38 IFP=20
   fax packets are sent/received on different UDP ports than the one=20
   used for audio RTP,=20
 =20
J-F. Mule/J. Li                                                     25=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   4. Once the fax transmission is terminated, audio capabilities are=20
   =93restored=94 or the call is terminated.=20
   =20
=20
5.3.1 Sequence Diagram=20
   =20
         IFT UA                 Proxy              IFTGW UA=20
           |                    |                    |=20
           |   F1 INVITE        |                    |=20
           |------------------->|                    |=20
           |                    |   F2 INVITE        |=20
           |                    |------------------->|=20
           |   F3  100 Trying   |                    |=20
           |<-------------------|   F4  100 Trying   |=20
           |                    |<-------------------|=20
           |                    |                    |=20
           |                    |   F5  180 Ringing  |=20
           |   F6  180 Ringing  |<-------------------|=20
           |<-------------------|                    |=20
           |                    |   F7  200 OK       |=20
           |   F8  200 OK       |<-------------------|=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F9  ACK          |                    |=20
           |------------------->|   F10 ACK          |=20
           |                     ------------------->|=20
           |                                         |=20
           |      Both Way RTP Media Established     |=20
      Fax  =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   ------->|                                         |=20
   emitted |                    |                    | =20
           |                    |                    | Preamble=20
           |                    |                    |<---------=20
           |                    |   F11 INVITE       | detected=20
           |                    |<-------------------|=20
           |   F12 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F13 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F14 200 OK       |=20
           |                    |------------------->|=20
           |                    |   F15  ACK         |=20
           |                    |<-------------------|=20
           |   F16  ACK         |                    |=20
           |<-------------------|                    |=20
           |                                         |=20
           |     T.38/UDPT Fax Flow Established      |=20
           |     Voice connection muted              |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   End of  |                                         |=20
   fax     |                    |                    |=20

 =20
J-F. Mule/J. Li                                                     26=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   detected|                    |                    |=20
   ------->|                    |                    |=20
           |                                         |=20
           |                    |                    | End of fax=20
           |                    |                    |<----------=20
           |                    |                    |   detected=20
           |                    |   F17 INVITE       |   =20
           |                    |<-------------------|=20
           |   F18 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F19 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F20 200 OK       |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F21  ACK         |=20
           |                    |<-------------------|=20
           |   F22  ACK         |                    |=20
           |<-------------------|                    |=20
           |                                         |=20
           |     Both way RTP Flow restored          |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
           |                                         |=20
           |   F23 BYE          |                    |=20
           |------------------->|                    |=20
           |                    |   F24 BYE          |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F25  200 OK      |=20
           |                    |<-------------------|=20
           |   F26  200 OK      |                    |=20
           |<-------------------|                    |=20
=20
   =20
5.3.2 Message Details=20
=20
   F1 INVITE  IFT UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 146=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 2890844527 IN IP4 ift.here.com=20
      s=3DSession SDP=20
 =20
J-F. Mule/J. Li                                                     27=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   =20
   F2 INVITE  PROXY -> IFTGW UA=20
   =20
      INVITE sip:+1-650-555-2222@iftgw.there.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 146=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 2890844527 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F3 (100 Trying) PROXY -> IFT UA=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Content-Length: 0=20
   =20
   =20
   F4 100 Trying IFTGW UA -> PROXY=20
   =20
      SIP/2.0 100 Trying=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
 =20
J-F. Mule/J. Li                                                     28=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   =20
   =20
   F5 180 Ringing IFTGW UA -> PROXY=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
    =20
   =20
   F6 180 Ringing PROXY -> IFT UA=20
   =20
      SIP/2.0 180 Ringing=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Length: 0=20
   =20
   =20
   F7 200 OK   IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 171089 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F8 200 OK   PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
 =20
J-F. Mule/J. Li                                                     29=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3DIFAXTERMINAL01 2890844527 171089 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   =20
   F9 ACK IFT UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Route: <sip:+1-650-555-2222@iftgw.there.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   =20
   F10 ACK PROXY -> IFTGW UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@iftgw.there.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 17 ACK=20
      Content-Length: 0=20
   =20
   /* RTP streams are established.  The CNG fax tone is sent in-band if =

   it is present.  The receiving side IFT gateway DSP detects the=20
   Preamble.  A new UDP port is open on IFTGW for T.38 IFP packets and=20
   the IFTGW signals the switch over to fax mode by send a re-INVITE=20
   with the new UDP port in the SDP */=20
   =20
   =20
 =20
J-F. Mule/J. Li                                                     30=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   F11 INVITE  IFTGW UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 49172 udptl t38=20
      c=3DIN IP4 iftmg.there.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F12 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      t=3D0 0=20
 =20
J-F. Mule/J. Li                                                     31=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      m=3Daudio 12322 RTP/AVP 0=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 49172 udptl t38=20
      c=3DIN IP4 iftmg.there.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F13 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 15002 udptl t38=20
      c=3DIN IP4 iftmg.here.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F14 200 OK  PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
 =20
J-F. Mule/J. Li                                                     32=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 15002 udptl t38=20
      c=3DIN IP4 iftmg.here.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F15 ACK IFTGW UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 ACK=20
      Content-Length: 0=20
   =20
   =20
   F16 ACK  PROXY -> IFT UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 ACK=20
      Content-Length: 0=20
 =20
J-F. Mule/J. Li                                                     33=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   =20
   =20
   /* T.38 fax transmission established both ways and the voice stream=20
   is muted */=20
   /* Then, the end of the fax transmission is detected on ingress side =

   and sent to the egress side (IFTGW). IFTGW initiates the switch back =

   to voice communication */=20
   =20
   =20
   F17 INVITE  IFTGW UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F18 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
 =20
J-F. Mule/J. Li                                                     34=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F19 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844529 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   =20
   F20 200 OK  PROXY -> IFTGW UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844529 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
   =20
   F21 ACK IFTGW UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
 =20
J-F. Mule/J. Li                                                     35=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   F22 ACK  PROXY -> IFT UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   F23 BYE IFT UA -> PROXY=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Length: 0=20
   =20
   =20
   F24 BYE PROXY -> IFTGW UA=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Length: 0=20
   =20
   F25 200 OK IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
 =20
J-F. Mule/J. Li                                                     36=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde24=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   F26 200 OK  PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde24=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
=20
   =20
5.4 SIP T.38 fax call =96 fax stream forced to replace voice stream=20
   =20
   This section illustrates the following scenario:=20
   1. A SIP INVITE is sent to the called party requesting a voice=20
   connection per RFC2543; our scenario involves 1 SIP proxy.  An audio =

   connection is established,=20
   2. Upon detection of Preamble by the terminating gateway, a SIP=20
   re=ADINVITE request is sent to the emitting gateway to modify the=20
   parameters of the session to add a T.38 fax connection.  This re-
   INVITE request contains SDP information detailing the additional=20
   T.38 capabilities.  It is also suggested that the voice pipe be=20
   muted while the fax session is in progress.  =20
   3. The emitting gateway does not have the resources to maintain both =

   the audio & fax streams and replies by allowing the fax media=20
   stream.  Upon successful acknowledgments, the audio stream is=20
   terminated and T.38 IFP fax packets are exchanged,=20
   4. Once the fax transmission is terminated, audio capabilities are=20
   =93re-negotiated=94 and the call is terminated.=20
   =20
5.4.1 Sequence Diagram=20
   Refer to section 5.3.1; sequence diagram is unchanged.=20
   =20
   =20
   =20
   =20
5.4.2 Message Details=20
   See section 5.3.2 for the complete set of messages.  We only=20
   indicate the changed messages based on the emitting gateway=92s=20
   decline to support both voice and fax streams.=20
   =20
   ...=20
   F11 INVITE  IFTGW UA -> PROXY=20
 =20
J-F. Mule/J. Li                                                     37=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 49172 udptl t38=20
      c=3DIN IP4 iftmg.there.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   F12 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com; =20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 320=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171090 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
 =20
J-F. Mule/J. Li                                                     38=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      c=3DIN IP4 0.0.0.0=20
      m=3Dimage 49172 udptl t38=20
      c=3DIN IP4 iftmg.there.com=20
      a=3DT38FaxVersion:0=20
      a=3DT38MaxBitRate:14400=20
      a=3DT38FaxFillBitRemoval:0=20
      a=3DT38FaxTranscodingMMR:0=20
      a=3DT38FaxTranscodingJBIG:0=20
      a=3DT38FaxRateManagement:transferredTCF=20
      a=3DT38FaxMaxBuffer:72=20
      a=3DT38FaxMaxDatagram:316=20
      a=3DT38FaxUdpEC:t38UDPFEC=20
      a=3DT38FaxUdpEC:t38UDPRedundancy=20
   =20
   =20
   =20
      F13 200 OK IFT UA -> PROXY =20
       =20
         SIP/2.0 200 OK =20
         Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1 =20
         Via: SIP/2.0/UDP iftgw.there.com:5060 =20
         From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11 =

         To: =
sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
         Call-ID: 1717@ift.here.com =20
         CSeq: 18 INVITE=20
         Contact: <sip:+1-303-555-1111@ift.here.com>=20
         Content-Type: application/sdp =20
         Content-Length: 320 =20
       =20
         v=3D0 =20
         o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com =20
         s=3DSession SDP =20
         t=3D0 0 =20
         m=3Daudio 0 RTP/AVP 0=20
         c=3DIN IP4 0.0.0.0 =20
         m=3Dimage 15002 udptl t38 =20
         c=3DIN IP4 iftmg.here.com =20
         a=3DT38FaxVersion:0 =20
         a=3DT38MaxBitRate:14400 =20
         a=3DT38FaxFillBitRemoval:0 =20
         a=3DT38FaxTranscodingMMR:0 =20
         a=3DT38FaxTranscodingJBIG:0 =20
         a=3DT38FaxRateManagement:transferredTCF =20
         a=3DT38FaxMaxBuffer:72 =20
         a=3DT38FaxMaxDatagram:316 =20
         a=3DT38FaxUdpEC:t38UDPRedundancy =20
       =20
       =20
      F14 200 OK  PROXY -> IFT UA =20
       =20
         SIP/2.0 200 OK =20
         Via: SIP/2.0/UDP iftgw.there.com:5060 =20
         Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;  =20
 =20
J-F. Mule/J. Li                                                     39=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
                       maddr=3Dobelix.wcom.com> =20
         From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11 =

         To: =
sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
         Call-ID: 1717@ift.here.com =20
         CSeq: 18 INVITE =20
         Contact: <sip:+1-303-555-1111@ift.here.com>=20
         Content-Type: application/sdp =20
         Content-Length: 320 =20
       =20
         v=3D0 =20
         o=3Dfaxgw1 2890846527 2890846528 IN IP4 ift.here.com =20
         s=3DSession SDP =20
         t=3D0 0 =20
         m=3Daudio 0 RTP/AVP 0=20
         c=3DIN IP4 0.0.0.0 =20
         m=3Dimage 15002 udptl t38 =20
         c=3DIN IP4 iftmg.here.com =20
         a=3DT38FaxVersion:0 =20
         a=3DT38MaxBitRate:14400 =20
         a=3DT38FaxFillBitRemoval:0 =20
         a=3DT38FaxTranscodingMMR:0 =20
         a=3DT38FaxTranscodingJBIG:0 =20
         a=3DT38FaxRateManagement:transferredTCF =20
         a=3DT38FaxMaxBuffer:72 =20
         a=3DT38FaxMaxDatagram:316 =20
         a=3DT38FaxUdpEC:t38UDPRedundancy =20
       =20
       =20
      F15 ACK IFTGW UA -> PROXY =20
       =20
         ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0 =20
         Via: SIP/2.0/UDP iftgw.there.com:5060 =20
         Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                 maddr=3Dobelix.wcom.com> =20
         From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11 =

         To: =
sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
         Call-ID: 1717@ift.here.com =20
         CSeq: 18 ACK =20
         Content-Length: 0 =20
           =20
       =20
      F16 ACK  PROXY -> IFT UA =20
       =20
         ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0 =20
         Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1 =20
         Via: SIP/2.0/UDP iftgw.there.com:5060 =20
         Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;  =20
                        maddr=3Dobelix.wcom.com> =20
         From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11 =

         To: =
sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
         Call-ID: 1717@ift.here.com =20
         CSeq: 18 ACK =20
         Content-Length: 0 =20
 =20
J-F. Mule/J. Li                                                     40=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
=20
=20
6. Unsuccessful Scenarios=20
   =20
6.1. Unsuccessful T.38 fax scenario =96 no support for T.38=20
   This section represents a SIP T.38 call failure because the emitting =

   gateway does not support T.38.=20
   =20
   Scenario:=20
   1. A SIP INVITE is sent to the called party requesting a voice=20
   connection per RFC2543; our scenario involves 1 SIP proxy.  An audio =

   connection is established,=20
   2. Upon detection of Preamble by the terminating gateway, a SIP=20
   re=ADINVITE request is sent to the emitting gateway to modify the=20
   parameters of the session to allow a T.38 fax connection.  This re-
   INVITE request contains SDP information detailing T.38 capabilities, =

   3. The emitting gateway rejects the re=ADINVITE with a 415 =
Unsupported=20
   Media Type response.    =20
   4. Upon reception of the reject, the call is terminated.=20
   =20
6.1.1. Sequence Diagram=20
   =20
   The messages F1 to F12 are identical to section 5.2.=20
   =20
   =20
         IFT UA                 Proxy              IFTGW UA=20
           |                    |                    |=20
           |   F1 INVITE        |                    |=20
           |------------------->|                    |=20
           |                    |   F2 INVITE        |=20
           |                    |------------------->|=20
           |   F3  100 Trying   |                    |=20
           |<-------------------|   F4  100 Trying   |=20
           |                    |<-------------------|=20
           |                    |                    |=20
           |                    |   F5  180 Ringing  |=20
           |   F6  180 Ringing  |<-------------------|=20
           |<-------------------|                    |=20
           |                    |   F7  200 OK       |=20
           |   F8  200 OK       |<-------------------|=20
           |<-------------------|                    |=20
           |   F9  ACK          |                    |=20
           |------------------->|   F10 ACK          |=20
           |                     ------------------->|=20
           |                                         |=20
           |      Both Way RTP Media Established     |=20
      Fax  =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   ------->|                                         |=20
   emitted |                    |                    | =20
           |                    |                    | Preamble=20
           |                    |                    |<---------=20
           |                    |   F11 INVITE       | detected=20

 =20
J-F. Mule/J. Li                                                     41=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
           |                    |<-------------------|=20
           |   F12 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F13 415          |                    |=20
           |------------------->|                    |=20
           |                    |   F14 415          |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F15  BYE         |=20
           |                    |<-------------------|=20
           |   F16  BYE         |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F17 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F18 200 OK       |=20
           |                    |------------------->|=20
   =20
   =20
6.1.2. Message Details=20
   =20
   Messages F1 to F12 are identical to section 5.2; refer to 5.2.=20
   =20
   F13 415 Unsupported Media Type  IFT UA -> PROXY=20
   =20
      SIP/2.0 415 Unsupported Media Type=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Length: 0=20
   =20
   =20
   F14 415 Unsupported Media Type  PROXY -> IFTGW UA=20
   =20
      SIP/2.0 415 Unsupported Media Type=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d010.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Length: 0=20
   =20
   =20
   F15 BYE IFTGW UA -> PROXY=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
 =20
J-F. Mule/J. Li                                                     42=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 BYE=20
      Content-Length: 0=20
   =20
   =20
   F16 BYE PROXY -> IFT UA=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d010.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 BYE=20
      Content-Length: 0=20
   =20
   =20
   F17 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   F18 200 OK  PROXY -> IFTGW UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
6.2. Unsuccessful T.38 fax scenario =96 488/606 response & G.711 =
fallback=20
=20
 =20
J-F. Mule/J. Li                                                     43=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   This section represents an unsuccessful SIP T.38 fax call:  when the =

   emitting gateway does not support T.38 fax relay, it SHOULD respond=20
   with either a =93488 Not Acceptable Here=94 response or a =93606 Not =

   Acceptable=94 response to indicate that some aspects of the session=20
   description are not acceptable.  The terminating gateway SHOULD=20
   react by proposing a fallback to G.711 fax pass-through with special =

   codec characteristics =96 echo cancellation ON, silence suppression=20
   OFF.  The message details in this section make use of the generic=20
   SDP attributes ecan and silenceSupp, defined in RFC3108 [10]. =20
   =20
   Scenario:=20
   1. A SIP INVITE is sent to the called party requesting a voice=20
   connection per RFC2543; our scenario involves 1 SIP proxy.  An audio =

   connection is established,=20
   2. Upon detection of Preamble by the terminating gateway, a SIP=20
   re=ADINVITE request is sent to the emitting gateway to modify the=20
   parameters of the session to allow a T.38 fax connection.  This re-
   INVITE request contains SDP information detailing T.38 capabilities, =

   3. The emitting gateway rejects the re-INVITE with a 488 or 606=20
   response.  Upon reception of the reject, the terminating gateway=20
   proposes to use plain G.711 to carry the fax stream.  =20
   4. The call is terminated.=20
   =20
6.2.1. Sequence Diagram=20
   The messages F1 to F12 are identical to section 5.2.=20
   =20
         IFT UA                 Proxy              IFTGW UA=20
           |                    |                    |=20
           |   F1 INVITE        |                    |=20
           |------------------->|                    |=20
           |                    |   F2 INVITE        |=20
           |                    |------------------->|=20
           |   F3  100 Trying   |                    |=20
           |<-------------------|   F4  100 Trying   |=20
           |                    |<-------------------|=20
           |                    |                    |=20
           |                    |   F5  180 Ringing  |=20
           |   F6  180 Ringing  |<-------------------|=20
           |<-------------------|                    |=20
           |                    |   F7  200 OK       |=20
           |   F8  200 OK       |<-------------------|=20
           |<-------------------|                    |=20
           |   F9  ACK          |                    |=20
           |------------------->|   F10 ACK          |=20
           |                     ------------------->|=20
           |                                         |=20
           |      Both Way RTP Media Established     |=20
      Fax  =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
   ------->|                                         |=20
   emitted |                    |                    | =20
           |                    |                    | Preamble=20
           |                    |                    |<---------=20

 =20
J-F. Mule/J. Li                                                     44=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
           |                    |   F11 INVITE       | detected=20
           |                    |<-------------------|=20
           |   F12 INVITE       |                    |=20
           |<-------------------|                    |=20
           |                    |                    |=20
           |   F13 606          |                    |=20
           |------------------->|                    |=20
           |                    |   F14 606 (or 488) |=20
           |                    |------------------->|=20
           |                    |   F15 INVITE       |=20
           |                    |<-------------------|=20
           |   F16 INVITE       |                    |=20
           |<-------------------|                    |=20
           |   F17 200 OK       |                    |=20
           |------------------->|                    |=20
           |                    |   F18 200 OK       |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F19  ACK         |=20
           |                    |<-------------------|=20
           |   F20  ACK         |                    |=20
           |<-------------------|                    |=20
           |                                         |=20
           | G.711 RTP Flow Established              |=20
           =
|<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>|=20
           |          for fax pass-through           |=20
           |                                         |=20
           |   F21 BYE          |                    |=20
           |------------------->|                    |=20
           |                    |   F22 BYE          |=20
           |                    |------------------->|=20
           |                    |                    |=20
           |                    |   F23  200 OK      |=20
           |                    |<-------------------|=20
           |   F24  200 OK      |                    |=20
           |<-------------------|                    |=20
   =20
   =20
6.2.2. Message Details=20
   =20
   Messages F1 to F12 are identical to section 5.2; refer to 5.2.=20
   =20
   F13 606 Not Acceptable    IFT UA -> PROXY=20
   =20
      SIP/2.0 606 Not Acceptable=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Warning: 304 Media type not available: One or more media types=20
               contained in the session description are not available.=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
 =20
J-F. Mule/J. Li                                                     45=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Content-Length: 0=20
   =20
   =20
   F14 606 Not Acceptable    PROXY -> IFTGW UA=20
   =20
      SIP/2.0 606 Not Acceptable=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d010.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Warning: 304 Media type not available: One or more media types=20
               contained in the session description are not available.=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 18 INVITE=20
      Content-Length: 0=20
   =20
   =20
   F15 INVITE  IFTGW UA -> PROXY=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
      a=3Decan:fb on -=20
      a=3DsilenceSupp:off - - - -=20
   =20
   =20
   =20
   =20
   F16 INVITE  PROXY -> IFT UA=20
   =20
      INVITE sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
 =20
J-F. Mule/J. Li                                                     46=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-650-555-2222@iftgw.there.com>=20
      Content-Type: application/sdp=20
      Content-Length: 181=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 171091 IN IP4 iftgw.there.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.there.com=20
      t=3D0 0=20
      m=3Daudio 12322 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
      a=3Decan:fb on -=20
      a=3DsilenceSupp:off - - - -=20
   =20
   =20
   F17 200 OK IFT UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d008.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
      a=3Decan:fb on -=20
      a=3DsilenceSupp:off - - - -=20
   =20
   =20
   F18 200 OK  PROXY -> IFTGW UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 INVITE=20
      Contact: <sip:+1-303-555-1111@ift.here.com>=20
      Content-Type: application/sdp=20
 =20
J-F. Mule/J. Li                                                     47=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Content-Length: 150=20
   =20
      v=3D0=20
      o=3Dfaxgw1 2890844527 2890844528 IN IP4 ift.here.com=20
      s=3DSession SDP=20
      c=3DIN IP4 iftmg.here.com=20
      t=3D0 0=20
      m=3Daudio 3456 RTP/AVP 0=20
      a=3Drtpmap:0 PCMU/8000=20
      a=3Decan:fb on -=20
      a=3DsilenceSupp:off - - - -=20
   =20
   =20
   F19 ACK IFTGW UA -> PROXY=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   F20 ACK  PROXY -> IFT UA=20
   =20
      ACK sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP iftgw.there.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                     maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab11=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde17=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 19 ACK=20
      Content-Length: 0=20
   =20
   =20
   /* G.711 audio streams established both ways for fax pass through */ =

   =20
   =20
   F21 BYE IFT UA -> PROXY=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
              maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
 =20
J-F. Mule/J. Li                                                     48=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
      Content-Length: 0=20
   =20
   =20
   F22 BYE PROXY -> IFTGW UA=20
   =20
      BYE sip:+1-650-555-2222@obelix.wcom.com SIP/2.0=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d009.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Length: 0=20
   =20
   =20
   F23 200 OK IFTGW UA -> PROXY=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP obelix.wcom.com:5060; branch=3D2d007.1=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   F24 200 OK  PROXY -> IFT UA=20
   =20
      SIP/2.0 200 OK=20
      Via: SIP/2.0/UDP ift.here.com:5060=20
      Record-Route: <sip:+1-650-555-2222@obelix.wcom.com;=20
                    maddr=3Dobelix.wcom.com>=20
      From: sip:+1-303-555-1111@ift.here.com;user=3Dphone;tag=3Dab22=20
      To: sip:+1-650-555-2222@obelix.wcom.com;user=3Dphone;tag=3Dcde34=20
      Call-ID: 1717@ift.here.com=20
      CSeq: 20 BYE=20
      Content-Type: application/sdp=20
      Content-Length: 0=20
   =20
   =20
   =20
   =20
   =20






 =20
J-F. Mule/J. Li                                                     49=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
7. SDP Attribute Table for T.38 sessions=20
   For a detailed description of these attributes, refer to IANA.  The=20
   tables below are replicated here for reference only. =20
   =20
   +-----------------------+---------------------+--------------+=20
   |  SDP Attribute Name   | Appropriate values  |   Example    |=20
   |     ("att-field")     |                     |              |=20
   +-----------------------+---------------------+--------------+=20
   |                       |                     |              |=20
   |     T38FaxVersion     |       1*DIGIT       |      0       |=20
   |                       |                     |              |=20
   |     T38MaxBitRate     |      1*(DIGIT)      |    14400     |=20
   |                       |                     |              |=20
   | T38FaxFillBitRemoval  |       boolean       |      0       |=20
   |                       |                     |              |=20
   | T38FaxTranscodingMMR  |       boolean       |      0       |=20
   |                       |                     |              |=20
   | T38FaxTranscodingJBIG |       boolean       |      0       |=20
   |                       |                     |              |=20
   | T38FaxRateManagement  |     localTCF |      |transferredTCF|=20
   |                       |   transferredTCF    |              |=20
   |                       |                     |              |=20
   |    T38FaxMaxBuffer    | 1*(DIGIT); optional |     72       |=20
   |                       |                     |   (bytes)    |=20
   |                       |                     |              |=20
   |   T38FaxMaxDatagram   |     1*(DIGIT);      |  Depends on  |=20
   |                       |     optional        |  redundancy; |=20
   |                       |                     |   316 (bytes)|=20
   |                       |                     |              |=20
   |      T38FaxUdpEC      |     t38UDPFEC |     | T38UDPRedund |=20
   |                       |  t38UDPRedundancy   |     ancy     |=20
   +-----------------------+---------------------+--------------+=20
   =20
   Registered SDP Protocol =93proto=94 for T.38:=20
   =20
   +-----------------+=20
   |      Name       |=20
   |                 |=20
   +-----------------+=20
   |                 |=20
   |     UDPTL       |=20
   |                 |=20
   |     TCP         |=20
   |                 |=20
   +-----------------+=20
   =20
   Registered SDP Protocol =93fmt=94, MIME media type image/t38:=20
      MIME media type name: image=20
      MIME subtype name: t38=20
   =20
   =20
   =20
   =20
 =20
J-F. Mule/J. Li                                                     50=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
8. Considerations=20
   =20
   In this temporary section, we log the open items for discussion as=20
   well as issues that have been solved on the mailing list:=20
   =20
8.1. Level of requirements for Internet gateways=20
   --- Status: closed, solved by old draft01 text in section 4.2=20
   Based on the comments received on old draft-00, the authors=20
   recommend that:  T.38 Internet fax gateways MUST trigger a SIP re-
   INVITE upon detection of the V.21 Preamble flag sequence on the=20
   receiving side.   Emitting gateways MAY trigger session modification =

   upon CNG.=20
   =20
8.2. Negotiation of UDP ports for T.38 transmission=20
   --- Status: not an issue, just logged here=20
   When switching to T.38 mode, Internet fax gateways specify a new set =

   of parameters for the media connection in SDP.  Some gateways may=20
   choose the UDP/RTP port used in audio mode for UDP/UDPTL/T.38=20
   traffic.  Some gateways may choose to open a new UDP port for=20
   UDPTL/T.38 fax (and keep the previous UDP/RTP port open for the=20
   switch back to audio).=20
   SDP provides the mechanism to precisely define in SIP all cases:=20
   - if an Internet Fax gateway desires to re-use the UDP/RTP port for=20
   UDP/UDPTL/T.38, put 1 =93m=3D=94 line in the re-INVITE.=20
          m=3Dimage <original_RTP_port> udptl t38=20
   - if an Internet Fax gateway desires to release the RTP port and=20
   open a new UDP port for T.38: =20
          m=3Dimage <new_UDP_port> udptl t38=20
   - if an Internet Fax gateway desires to keep the RTP port for future =

   use in the session and open a new UDP port for T.38, we need to=20
   repeat the RTP/AVP port: =20
          m=3Daudio <original_RTP_port> RTP/AVP 0=20
          m=3Dimage <new_UDP_port> udptl t38=20
=20
8.3. Adding a fax stream to SIP session vs. Replacing audio stream=20
   --- Status: closed, see flows 5.2 and 5.3=20
   Based on the mailing list discussion, it is recommended in section=20
   5.2 to replace an existing audio media connection with a fax one.  =20
   We however kept section 5.3 to illustrate what adding a fax stream=20
   would entail.=20
   =20
8.4. Adding text to make use of SIP OPTIONS: in progress in draft-02=20
   --- Status: Open for discussion=20
   As discussed with Bill Sulzen, the SIP OPTIONS response could be=20
   used to assert that real-time fax communications using either T.38=20
   or fax-passthrough are supported.  This could certainly improve the=20
   negotiation phases and reduce the number of SIP messages.  It is=20
   also key to get the capabilities of the Internet-aware fax device or =

   gateway other than on a per call basis.=20
   What needs to be added:=20
       - add text in sub-section in section 4.5=20
       - specify how the Accept header line should be populated (do we=20
   want to specify t.38 and/or fax pass-through (meaning ability to=20
 =20
J-F. Mule/J. Li                                                     51=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
   support ecan and silencesuppression), and within t.38, do we want to =

   specify whether it is t.38 over tcp, udptl, both, etc.=20
   =20
8.5. Use of IP addresses in SDP connection information=20
   --- Status: Open for discussion=20
   Comment from Christer Holmberg: SDP connection information should=20
   use IP addresses instead of domain names (as per draft-ietf-mmusic-
   sdp-new-03)=20
   =20
8.6. Unsuccessful scenario: 606 or 488=20
   --- Status: closed=20
   Comment from Bill Sulzen: it is acceptable or even preferable to=20
   reject with a 488 Not Acceptable Media?=20
   Resolution: treat 606 and 488 as equally appropriate.=20
   =20
   =20
9. Security Considerations=20
=20
   The security mechanisms provided in RFC2543 apply: message=20
   authentication can be performed on SIP INVITEs and also BYE.=20
   =20
   =20
10. References=20
=20
   1  S. Bradner, "The Internet Standards Process -- Revision 3", BCP=20
      9, RFC 2026, October 1996.=20
   =20
   2  S. Bradner, "Key words for use in RFCs to Indicate Requirement=20
      Levels", BCP 14, RFC 2119, March 1997.=20
   =20
   3  M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP:=20
          Session Initiation Protocol", RFC 2543, March 1999.=20
   =20
   4  ITU-T Recommendation T.38, =93Procedures for real-time Group 3=20
      facsimile communication over IP networks=94, June 1998.=20
   =20
   5  Johnston, et al, =93SIP Telephony Call Flow Examples=94, =
Internet-
      Draft draft-ietf-sip-call-flows-05.txt, June 2001.=20
   =20
   6  ITU-T Recommendation T.38 Amendment 2, =93Procedures for =
real-time=20
      Group 3 facsimile communication over IP networks=94, February =
2000.=20
   =20
   7  ITU-T Recommendation T.30, =93Procedures for document facsimile=20
      transmission in the general switched telephone network=94, March=20
      1993.=20
   =20
   8  M. Handley, V. Jacobson, "SDP: session description protocol",=20
      RFC 2327, April 1998.=20
                         =20
   9  ITU-T Recommendation T.38 Amendment 2 Annex D, =93SIP/SDP Call=20
      Establishment Procedures=94, February 2000.=20
   =20
=20
 =20
J-F. Mule/J. Li                                                     52=20
=0C
                         SIP T.38 Call Flows            February 2002=20
=20
=20
=20
   10 R. Kumar, M. Mostafa, =93Conventions for the use of the Session=20
      Description Protocol (SDP) for ATM Bearer Connections=94, =
RFC3108,=20
      May 2001.=20
=20
11. Acknowledgments=20
   =20
   This document would not have been possible without the help of the=20
   following development engineers and fax experts, in particular=20
   Stanley Khouw, Bill Michalek, and George Maphis of Clarent=20
   Corporation.=20
   =20
   The authors would like to thank Bill Sulzen of Cisco Systems for his =

   continued support and critical comments.  We also acknowledge the=20
   valuable contributions from Flemming Andreasen of Cisco Systems,=20
   Christer Holmberg of Ericsson, and Bert Culpepper of InterVoice-
   Brite.=20
   Many thanks to the reviewers of the previous document for their=20
   comments: Jim Renkel of 3COM, Sudipto Mukherjee of Cisco Systems,=20
   Arjun Roychowdhury of Hughes Software Systems.=20
   =20
   =20
12. Author's Addresses=20
   =20
   Jieying Li=20
   iVox Networks=20
   26701 West Agoura Road=20
   Calabasa, CA 91302=20
   email:jieying.li@ivoxnetworks.com=20
   =20
   Jean-Francois Mule=92=20
   CableLabs=20
   400 Centennial Parkway=20
   Louisville, CO 80027=20
   USA=20
   email: jf.mule@cablelabs.com=20
   =20
Full Copyright Statement=20
=20
   "Copyright (C) The Internet Society (2002). All Rights Reserved.=20
   This document and translations of it may be copied and furnished to=20
   others, and derivative works that comment on or otherwise explain it =

   or assist in its implementation may be prepared, copied, published=20
   and distributed, in whole or in part, without restriction of any=20
   kind, provided that the above copyright notice and this paragraph=20
   are included on all such copies and derivative works. However, this=20
   document itself may not be modified in any way, such as by removing=20
   the copyright notice or references to the Internet Society or other=20
   Internet organizations, except as needed for the purpose of=20
   developing Internet standards in which case the procedures for=20
   copyrights defined in the Internet Standards process must be=20
   followed, or as required to translate it into=20
 =20
J-F. Mule/J. Li                                                     53=20
=0C

------_=_NextPart_000_01C4A498.4B955A80
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_01C4A498.4B955A80--



From sipping-bounces@ietf.org  Fri Oct 15 06:43:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15598
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 06:43:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIPja-0003cv-Nr
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 06:55:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIPKi-0008Rq-LK; Fri, 15 Oct 2004 06:29:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CF4DD-0003QM-0M
	for sipping@megatron.ietf.org; Wed, 06 Oct 2004 01:19:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20627
	for <sipping@ietf.org>; Wed, 6 Oct 2004 01:19:37 -0400 (EDT)
From: anagarajan@hssworld.com
Received: from [61.16.168.135] (helo=hssworld.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF4MS-0005Qm-5f
	for sipping@ietf.org; Wed, 06 Oct 2004 01:29:23 -0400
Received: from pragati.blr.hss.hns.com (pragati.hss.hns.com [172.17.33.22])
	by hssworld.com (8.11.6/8.11.6) with ESMTP id i965D5C16420;
	Wed, 6 Oct 2004 10:43:08 +0530
To: sipping@ietf.org, sip-implementors@cs.columbia.edu, fluffy@cisco.com,
        Jon.Peterson@NeuStar.biz, mwatson@nortelnetworks.com,
        mary.barnes@nortelnetworks.com
X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004
Message-ID: <OF446B854D.2666A354-ON65256F25.0019CB0C-65256F25.001D87A5@hssworld.com>
Date: Wed, 6 Oct 2004 10:47:37 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5|September 18,
	2003) at 10/06/2004 10:48:05 AM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-Mailman-Approved-At: Fri, 15 Oct 2004 06:29:10 -0400
Subject: [Sipping] Doubt in ANBF defined in
	draft-ietf-sip-history-info-02.txt 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.5 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793





Hi All,

            I have a doubt on the ABNF of "history-info" header as defined
in "draft-ietf-sip-history-info-02.txt" :-


    History-Info = "History-Info" HCOLON   hist-info *(COMMA hist-info)
    hist-info = hi-targeted-to-uri *( SEMI hi-param )
    hi-targeted-to-uri= name-addr

Please note that grammar for name-addr is defined in RFC 3261.

However in an example of History-Info header defined in the draft (in
section 4.2) :-
History-Info:<sip:UserA@ims.nortelnetworks.com?Reason=SIP;cause=302;text=
"Moved Temporarily">; index=1; foo=bar

note that quoted string occurs in uri-parameters of SIP URI

But as per the SIP-URI grammar defined in Rfc3261, quoted string cannot
occur .

Please confirm on this..


Regards
Anil N

Hughes Software Systems (HSS)-  B'lore India
Office Number: +91-80-51067074

***********************  HSS-Unclassified   ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 06:45:27 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 GAA15742
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 06:45:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIPlT-0003g0-Dl
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 06:57:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIPKj-0008Rw-Es; Fri, 15 Oct 2004 06:29:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFpkQ-0000yP-ME
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 04:05:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02394
	for <sipping@ietf.org>; Fri, 8 Oct 2004 04:05:04 -0400 (EDT)
Received: from [62.119.82.41] (helo=mailserver.hotsip.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFpuI-0000ql-D0
	for sipping@ietf.org; Fri, 08 Oct 2004 04:15:19 -0400
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] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:02:31 +0200
Message-ID: <B7192C0D8D60754DADA9E22294C573694527A5@mailserver.hotsip.com>
Thread-Topic: [Sipping] New internet draft on media loopback
Thread-Index: AcSsw5JmDW//IOK4RwiQ7At91xYBWgASJ1KA
From: "Christian Jansson" <christian.jansson@hotsip.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        "Hedayat, Kaynam" <khedayat@brixnet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 15 Oct 2004 06:29:10 -0400
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: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: quoted-printable



Why not build a service and give it a SIP-URI like
sip:audiotest@domain.com that answers all calls and loops back the
audio? There is no need for any new SDP attributes to be able to build
such a service.=20

/ Christian Jansson, Hotsip


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 06:47:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15956
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 06:47:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIPnt-0003kG-QU
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 06:59:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIPKk-0008S2-51; Fri, 15 Oct 2004 06:29:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFva1-0007ky-FM
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:18:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27285
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:18:44 -0400 (EDT)
Received: from mailout.excelswitching.com ([208.236.123.107])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFvju-0007Zj-Ef
	for sipping@ietf.org; Fri, 08 Oct 2004 10:29:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:17:36 -0400
Message-ID: <656BE56E7D48F6419054CC1C81114927014CD667@exch01.corp.xl.com>
Thread-Topic: [Sipping] New internet draft on media loopback
thread-index: AcSp5DVCgR74EkRzRI+JyGJjtJ6RCADXPxYA
From: "Jain, Rajnish" <rjain@excelswitching.com>
To: "Hedayat, Kaynam" <khedayat@brixnet.com>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 15 Oct 2004 06:29:10 -0400
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable

Kaynam,

In many ways, this draft is analogous to continuity test (COT) and test
calls 102, 105, 108 of traditional telephony. While there are some
fundamental differences between a TDM continuity test and an RTP media
loopback test, there are many similar goals.=20

While the draft at this time seems to emphasize user end-points, the
idea can also be extended to SIP-enabled media gateways. Currently, in a
SIP bridging scenario (RFC 3372, RFC 3398), a continuity test between an
SSP and a media gateway tests only the local TDM path (not the
end-to-end TDM-RTP-TDM path). If SIP bridging were to be truly
transparent to the two SSPs with respect to the continuity test, the
media gateways could possibly receive a continuity test request on the
TDM side and propagate to the SIP side (and vice-versa).=20
=20
Rajnish

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Hedayat, Kaynam
Sent: Monday, October 04, 2004 3:22 AM
To: 'sipping@ietf.org'
Subject: [Sipping] New internet draft on media loopback

I would like to bring the attention of the group to a new internet draft
on media loopback capability in SIP sessions. The draft can be found at
http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt

Regards,
Kaynam

-----------------------------------------
Kaynam Hedayat
Chief Technology Officer
Brix Networks
285 Mill Road
Chelmsford, MA 01824

tel.   978.367.5611
fax.   978.367.5700
khedayat@brixnet.com
www.brixnet.com

See it before they hear it: Test the performance and quality of your
VoIP at www.TestYourVoip.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 Oct 15 06:47: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 GAA15992
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 06:47:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIPoG-0003ks-Ar
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 06:59:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIPKk-0008S8-RD; Fri, 15 Oct 2004 06:29:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CFwDI-0002ZU-Dx
	for sipping@megatron.ietf.org; Fri, 08 Oct 2004 10:59:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01927
	for <sipping@ietf.org>; Fri, 8 Oct 2004 10:59:19 -0400 (EDT)
Received: from mailout.excelswitching.com ([208.236.123.107])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFwNF-0000KZ-9s
	for sipping@ietf.org; Fri, 08 Oct 2004 11:09:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] New internet draft on media loopback
Date: Fri, 8 Oct 2004 10:58:49 -0400
Message-ID: <656BE56E7D48F6419054CC1C811149270239F9F3@exch01.corp.xl.com>
Thread-Topic: [Sipping] New internet draft on media loopback
thread-index: AcStQo6hfXUBgC38QDqKByt8pbBWwQAAYXTw
From: "Jain, Rajnish" <rjain@excelswitching.com>
To: "Hedayat, Kaynam" <khedayat@brixnet.com>, <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 15 Oct 2004 06:29:10 -0400
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: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable

108 is a simple loopback test. However, 102 and 105 require responder to
generate special tones.

-----Original Message-----
From: Hedayat, Kaynam [mailto:khedayat@brixnet.com]=20
Sent: Friday, October 08, 2004 10:25 AM
To: Jain, Rajnish; Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback

Rajnish,

This is a very good point. What are the requirements for the responder
of the 102, 105, 108 tests? Is looping back the media sufficient?

Regards,
Kaynam

-----Original Message-----
From: Jain, Rajnish [mailto:rjain@excelswitching.com]
Sent: Friday, October 08, 2004 10:18 AM
To: Hedayat, Kaynam; sipping@ietf.org
Subject: RE: [Sipping] New internet draft on media loopback


Kaynam,

In many ways, this draft is analogous to continuity test (COT) and test
calls 102, 105, 108 of traditional telephony. While there are some
fundamental differences between a TDM continuity test and an RTP media
loopback test, there are many similar goals.=20

While the draft at this time seems to emphasize user end-points, the
idea can also be extended to SIP-enabled media gateways. Currently, in a
SIP bridging scenario (RFC 3372, RFC 3398), a continuity test between an
SSP and a media gateway tests only the local TDM path (not the
end-to-end TDM-RTP-TDM path). If SIP bridging were to be truly
transparent to the two SSPs with respect to the continuity test, the
media gateways could possibly receive a continuity test request on the
TDM side and propagate to the SIP side (and vice-versa).=20
=20
Rajnish

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Hedayat, Kaynam
Sent: Monday, October 04, 2004 3:22 AM
To: 'sipping@ietf.org'
Subject: [Sipping] New internet draft on media loopback

I would like to bring the attention of the group to a new internet draft
on media loopback capability in SIP sessions. The draft can be found at
http://www.ietf.org/internet-drafts/draft-hedayat-media-loopback-00.txt

Regards,
Kaynam

-----------------------------------------
Kaynam Hedayat
Chief Technology Officer
Brix Networks
285 Mill Road
Chelmsford, MA 01824

tel.   978.367.5611
fax.   978.367.5700
khedayat@brixnet.com
www.brixnet.com

See it before they hear it: Test the performance and quality of your
VoIP at www.TestYourVoip.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 Oct 15 12:57: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 MAA20265
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 12:57:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIVaD-0004FG-Br
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 13:09:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIVHS-0006rN-KR; Fri, 15 Oct 2004 12:50:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIVFL-0005zt-N7
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 12:48:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19481
	for <sipping@ietf.org>; Fri, 15 Oct 2004 12:48:00 -0400 (EDT)
Received: from broadsoft.com ([204.200.197.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIVQk-0003yz-82
	for sipping@ietf.org; Fri, 15 Oct 2004 12:59:50 -0400
Received: from brett1 (host4.brodsoft.com [66.160.10.4]) (authenticated bits=0)
	by broadsoft.com (8.13.1/8.12.11) with ESMTP id i9FGlOR1087106;
	Fri, 15 Oct 2004 12:47:29 -0400 (EDT)
From: "Brett Tate" <brett@broadsoft.com>
To: <anagarajan@hssworld.com>
Subject: RE: [Sipping] Doubt in ANBF defined
	indraft-ietf-sip-history-info-02.txt draft
Date: Fri, 15 Oct 2004 12:47:30 -0400
Message-ID: <001401c4b2d6$aa184800$a601a8c0@brett1>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
In-Reply-To: <OF446B854D.2666A354-ON65256F25.0019CB0C-65256F25.001D87A5@hssworld.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org, mary.barnes@nortelnetworks.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

> However in an example of History-Info 
> header defined in the draft (in section 4.2) :- 
> History-Info:<sip:UserA@ims.nortelnetworks.com
>  ?Reason=SIP;cause=302;text=
>  "Moved Temporarily">; index=1; foo=bar
> 
> note that quoted string occurs in uri-parameters 
> of SIP URI
> 
> But as per the SIP-URI grammar defined in 
> Rfc3261, quoted string cannot occur .
> 
> Please confirm on this..

A quoted string can occur; however the 
example does not reflect the escaping 
across the sip-uri which must occur.

However I continue to have doubts with the
escaping/unescaping process concerning 
quoted strings containing UTF8-NONASCII 
characters.  This can occur in a sip-uri
when embedding a header containing a 
name-addr with a UTF8-NONASCII display-name.



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 14:22: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 OAA26592
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 14:22:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIWts-00066S-IT
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 14:34:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIWZP-0005fl-Eg; Fri, 15 Oct 2004 14:12:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIWTM-0004DC-Nx
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 14:06:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25227
	for <sipping@ietf.org>; Fri, 15 Oct 2004 14:06:35 -0400 (EDT)
Received: from cmailm4.svr.pol.co.uk ([195.92.193.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIWei-0005jM-Nf
	for sipping@ietf.org; Fri, 15 Oct 2004 14:18:21 -0400
Received: from user-5202.l1.c5.dsl.pol.co.uk ([81.76.20.82] helo=RW)
	by cmailm4.svr.pol.co.uk with smtp (Exim 4.14)
	id 1CIWTF-000148-De; Fri, 15 Oct 2004 19:06:29 +0100
Message-ID: <002101c4b2e1$b09e3300$c700a8c0@RW>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        "sipping" <sipping@ietf.org>
References: <416F538A.1050508@dynamicsoft.com>
Subject: Re: [Sipping] What problems are SBCs addressing?
Date: Fri, 15 Oct 2004 19:06:22 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
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.1 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: 7bit

I'm not actually working for any vendors at the moment, so feel free to
dismiss my input!!!

If you've got this far, I think that SBC's in the broadest sense offer:

1)
Perimeter defence - not sure if that's the right term, but much like a mail
server in the DMZ provides protection at the SMTP level, an SBC in (or
around) the DMZ can provide protection at the SIP/RTP level.  My feeling
that it is unreasonable to expect a standard firewall (what ever that is) to
be best of class in all protocols, so proxies can help.  The firewall makes
sure packets go to/from the relevant proxy, and the firewall trusts that the
proxy will do its job (because the administrator told it to!).

This 'bump' in the path is a problem for end-to-end security, but my feeling
that most organisations forced to choose between perimeter defence vs.
encryption and authentication would (at the moment - spam is an issue!) go
for perimeter defence.

A number of SBCs are outside the DMZ.  This makes it harder for the firewall
to trust, but this is motivated by outsourcing, much as SMTP proxies are
outsourced.  Basically its a question of how much expertise is around to
manage the devices.  The latter seems to be a practicality of the real
world.  (This is really something I observe rather than strongly defend.
Mind you, the customer's always right!)

2)
There's a hope that SBC's can play some part in the QoS management puzzle
primarily in the relatively bandwidth limited access link.  I think it's
only a piece in the puzzle, and there may be other ways to do it.

That's my two cents!!!

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware
http://www.tech-know-ware.com
For LMX XML to C++ binding see http://www.xml2cpp.com
=============================================

----- Original Message ----- 
From: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
To: "sipping" <sipping@ietf.org>
Sent: Friday, October 15, 2004 5:35 AM
Subject: [Sipping] What problems are SBCs addressing?


> Folks,
>
> As many of you know, there are a large number of products on the market
> these days under the general moniker "Session Border Controller";
> generally these are B2BUas that play some kind of policy enforcement and
> control function, typically at trust boundaries.
>
> Our specifications don't define how B2BUas should operate, and they say
> nothing at all about an SBC (although they do address many problems that
> relate to inter-domain operations and trust boundaries). However, the
> preponderence of these devices in the market and in VoIP networks seems
> to indicate that there are real problems that providers believe they
> have, which they feel these products are solving for them.
>
> This begs the important question - what are those problems, and are
> those problems for which the IETF has produced specifications to
> address? If not, is there a need to do so? If yes, are these products
> using those specifications, and if not, why have those solutions not
> seen implementation and/or deployment?
>
> Put in another way, sipping is all about requirements and problems, and
> it is clear that there are one or more problems here somewhere. Do we
> understand those requirements, and do we need to produce specifications
> to address them?
>
> This is a fairly meaty topic, one for which I expect to see lots of
> emails in reply to this note suggesting answers ;) Furthermore, we are
> planning an informal get together at IETF 61 to continue the dialog,
> focusing squarely on understanding requirements and specification gaps.
> Details TBA shortly. Whether one likes the solutions that are out there
> or not, the first step in doing anything is to understand the
> requirements. I really want to do that.
>
> I think it's important to have this discussion now, while there is still
> time to address these issues with standards-based solutions. To
> paraphrase Spencer Dawkins' recent note - I don't want to have a BoF
> session three years hence called "son-of-behave", where we discuss what
> an SBC should do, wishing that we had written specifications three years
> earlier and thus avoided the interop mess that had resulted. Given the
> recent concerns about GRUU and SIP identity operation through SBC, this
> is even more telling.
>
> Inputs from people who work for vendors of such devices, your input is
> most welcome..
>
> Thanks,
> Jonathan R.
>
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 15 15:36: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 PAA02680
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 15:36:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIY3Q-0007em-Ss
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 15:47:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIXkA-0005PD-FK; Fri, 15 Oct 2004 15:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIXer-0001oH-4L
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 15:22:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01306
	for <sipping@ietf.org>; Fri, 15 Oct 2004 15:22:30 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIXqF-0007L7-VS
	for sipping@ietf.org; Fri, 15 Oct 2004 15:34:21 -0400
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 i9FJLp706116; Fri, 15 Oct 2004 15:21:51 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <49CZ9L80>; Fri, 15 Oct 2004 15:21:52 -0400
Message-ID: <1ECE0EB50388174790F9694F77522CCFCF5416@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'sipping'"
	<sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Fri, 15 Oct 2004 15:21:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 40161b1d86420e0807d771943d981d25
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="===============0460228570=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4515df9441674711565101d9d5c4f63f

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.

--===============0460228570==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4B2EC.30A57BF4"

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_01C4B2EC.30A57BF4
Content-Type: text/plain

I assume that you are only planning to focus on the SIP aspects.

One thing they do is bridging between two different domain, in particular
for security.

While this is not terribly difficult for SIP/TLS, it is considerably more
awkward/nasty for sRTP.

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Thursday, October 14, 2004 21:35
> To: sipping
> Subject: [Sipping] What problems are SBCs addressing?
> 
> 
> Folks,
> 
> As many of you know, there are a large number of products on 
> the market 
> these days under the general moniker "Session Border Controller"; 
> generally these are B2BUas that play some kind of policy 
> enforcement and 
> control function, typically at trust boundaries.
> 
> Our specifications don't define how B2BUas should operate, 
> and they say 
> nothing at all about an SBC (although they do address many 
> problems that 
> relate to inter-domain operations and trust boundaries). However, the 
> preponderence of these devices in the market and in VoIP 
> networks seems 
> to indicate that there are real problems that providers believe they 
> have, which they feel these products are solving for them.
> 
> This begs the important question - what are those problems, and are 
> those problems for which the IETF has produced specifications to 
> address? If not, is there a need to do so? If yes, are these products 
> using those specifications, and if not, why have those solutions not 
> seen implementation and/or deployment?
> 
> Put in another way, sipping is all about requirements and 
> problems, and 
> it is clear that there are one or more problems here somewhere. Do we 
> understand those requirements, and do we need to produce 
> specifications 
> to address them?
> 
> This is a fairly meaty topic, one for which I expect to see lots of 
> emails in reply to this note suggesting answers ;) 
> Furthermore, we are 
> planning an informal get together at IETF 61 to continue the dialog, 
> focusing squarely on understanding requirements and 
> specification gaps. 
> Details TBA shortly. Whether one likes the solutions that are 
> out there 
> or not, the first step in doing anything is to understand the 
> requirements. I really want to do that.
> 
> I think it's important to have this discussion now, while 
> there is still 
> time to address these issues with standards-based solutions. To 
> paraphrase Spencer Dawkins' recent note - I don't want to have a BoF 
> session three years hence called "son-of-behave", where we 
> discuss what 
> an SBC should do, wishing that we had written specifications 
> three years 
> earlier and thus avoided the interop mess that had resulted. 
> Given the 
> recent concerns about GRUU and SIP identity operation through 
> SBC, this 
> is even more telling.
> 
> Inputs from people who work for vendors of such devices, your 
> input is 
> most welcome..
> 
> Thanks,
> Jonathan R.
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 
> 

------_=_NextPart_001_01C4B2EC.30A57BF4
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Sipping] What problems are SBCs addressing?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I assume that you are only planning to focus on the =
SIP aspects.</FONT>
</P>

<P><FONT SIZE=3D2>One thing they do is bridging between two different =
domain, in particular</FONT>
<BR><FONT SIZE=3D2>for security.</FONT>
</P>

<P><FONT SIZE=3D2>While this is not terribly difficult for SIP/TLS, it =
is considerably more</FONT>
<BR><FONT SIZE=3D2>awkward/nasty for sRTP.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: sipping-bounces@ietf.org </FONT>
<BR><FONT SIZE=3D2>&gt; [<A =
HREF=3D"mailto:sipping-bounces@ietf.org">mailto:sipping-bounces@ietf.org=
</A>] On Behalf Of Jonathan Rosenberg</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, October 14, 2004 21:35</FONT>
<BR><FONT SIZE=3D2>&gt; To: sipping</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sipping] What problems are SBCs =
addressing?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As many of you know, there are a large number =
of products on </FONT>
<BR><FONT SIZE=3D2>&gt; the market </FONT>
<BR><FONT SIZE=3D2>&gt; these days under the general moniker =
&quot;Session Border Controller&quot;; </FONT>
<BR><FONT SIZE=3D2>&gt; generally these are B2BUas that play some kind =
of policy </FONT>
<BR><FONT SIZE=3D2>&gt; enforcement and </FONT>
<BR><FONT SIZE=3D2>&gt; control function, typically at trust =
boundaries.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Our specifications don't define how B2BUas =
should operate, </FONT>
<BR><FONT SIZE=3D2>&gt; and they say </FONT>
<BR><FONT SIZE=3D2>&gt; nothing at all about an SBC (although they do =
address many </FONT>
<BR><FONT SIZE=3D2>&gt; problems that </FONT>
<BR><FONT SIZE=3D2>&gt; relate to inter-domain operations and trust =
boundaries). However, the </FONT>
<BR><FONT SIZE=3D2>&gt; preponderence of these devices in the market =
and in VoIP </FONT>
<BR><FONT SIZE=3D2>&gt; networks seems </FONT>
<BR><FONT SIZE=3D2>&gt; to indicate that there are real problems that =
providers believe they </FONT>
<BR><FONT SIZE=3D2>&gt; have, which they feel these products are =
solving for them.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This begs the important question - what are =
those problems, and are </FONT>
<BR><FONT SIZE=3D2>&gt; those problems for which the IETF has produced =
specifications to </FONT>
<BR><FONT SIZE=3D2>&gt; address? If not, is there a need to do so? If =
yes, are these products </FONT>
<BR><FONT SIZE=3D2>&gt; using those specifications, and if not, why =
have those solutions not </FONT>
<BR><FONT SIZE=3D2>&gt; seen implementation and/or deployment?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Put in another way, sipping is all about =
requirements and </FONT>
<BR><FONT SIZE=3D2>&gt; problems, and </FONT>
<BR><FONT SIZE=3D2>&gt; it is clear that there are one or more problems =
here somewhere. Do we </FONT>
<BR><FONT SIZE=3D2>&gt; understand those requirements, and do we need =
to produce </FONT>
<BR><FONT SIZE=3D2>&gt; specifications </FONT>
<BR><FONT SIZE=3D2>&gt; to address them?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This is a fairly meaty topic, one for which I =
expect to see lots of </FONT>
<BR><FONT SIZE=3D2>&gt; emails in reply to this note suggesting answers =
;) </FONT>
<BR><FONT SIZE=3D2>&gt; Furthermore, we are </FONT>
<BR><FONT SIZE=3D2>&gt; planning an informal get together at IETF 61 to =
continue the dialog, </FONT>
<BR><FONT SIZE=3D2>&gt; focusing squarely on understanding requirements =
and </FONT>
<BR><FONT SIZE=3D2>&gt; specification gaps. </FONT>
<BR><FONT SIZE=3D2>&gt; Details TBA shortly. Whether one likes the =
solutions that are </FONT>
<BR><FONT SIZE=3D2>&gt; out there </FONT>
<BR><FONT SIZE=3D2>&gt; or not, the first step in doing anything is to =
understand the </FONT>
<BR><FONT SIZE=3D2>&gt; requirements. I really want to do that.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think it's important to have this discussion =
now, while </FONT>
<BR><FONT SIZE=3D2>&gt; there is still </FONT>
<BR><FONT SIZE=3D2>&gt; time to address these issues with =
standards-based solutions. To </FONT>
<BR><FONT SIZE=3D2>&gt; paraphrase Spencer Dawkins' recent note - I =
don't want to have a BoF </FONT>
<BR><FONT SIZE=3D2>&gt; session three years hence called =
&quot;son-of-behave&quot;, where we </FONT>
<BR><FONT SIZE=3D2>&gt; discuss what </FONT>
<BR><FONT SIZE=3D2>&gt; an SBC should do, wishing that we had written =
specifications </FONT>
<BR><FONT SIZE=3D2>&gt; three years </FONT>
<BR><FONT SIZE=3D2>&gt; earlier and thus avoided the interop mess that =
had resulted. </FONT>
<BR><FONT SIZE=3D2>&gt; Given the </FONT>
<BR><FONT SIZE=3D2>&gt; recent concerns about GRUU and SIP identity =
operation through </FONT>
<BR><FONT SIZE=3D2>&gt; SBC, this </FONT>
<BR><FONT SIZE=3D2>&gt; is even more telling.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Inputs from people who work for vendors of such =
devices, your </FONT>
<BR><FONT SIZE=3D2>&gt; input is </FONT>
<BR><FONT SIZE=3D2>&gt; most welcome..</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; Jonathan R.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Jonathan D. Rosenberg, =
Ph.D.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; 600 Lanidex Plaza</FONT>
<BR><FONT SIZE=3D2>&gt; Chief Technology =
Officer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Parsippany, NJ =
07054-2711</FONT>
<BR><FONT SIZE=3D2>&gt; dynamicsoft</FONT>
<BR><FONT SIZE=3D2>&gt; =
jdrosen@dynamicsoft.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
FAX:&nbsp;&nbsp; (973) 952-5050</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.jdrosen.net" =
TARGET=3D"_blank">http://www.jdrosen.net</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; PHONE: (973) 952-5000</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.dynamicsoft.com" =
TARGET=3D"_blank">http://www.dynamicsoft.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the =
application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current </FONT>
<BR><FONT SIZE=3D2>&gt; sip Use sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4B2EC.30A57BF4--


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



From sipping-bounces@ietf.org  Fri Oct 15 16:02: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 QAA05810
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 16:02:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIYTN-0000Gd-9b
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 16:14:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIY21-0007yl-BS; Fri, 15 Oct 2004 15:46:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIXuI-0003l9-ME
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 15:38:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02919
	for <sipping@ietf.org>; Fri, 15 Oct 2004 15:38:28 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIY5j-0007iy-0o
	for sipping@ietf.org; Fri, 15 Oct 2004 15:50:19 -0400
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 i9FJbu709186; Fri, 15 Oct 2004 15:37:56 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <49CZ9NMM>; Fri, 15 Oct 2004 15:37:56 -0400
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB022C43F4@zrc2hxm1.corp.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: "'Brett Tate'" <brett@broadsoft.com>, anagarajan@hssworld.com
Subject: RE: [Sipping] Doubt in ANBF defined indraft-ietf-sip-history-info
	-02.txt draft
Date: Fri, 15 Oct 2004 15:37:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1652582909=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51

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.

--===============1652582909==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4B2EE.73322826"

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_01C4B2EE.73322826
Content-Type: text/plain

Brett,

Thanks for your response. Yes, I do need to correct that example in terms of
accurately reflecting the escaping across the SIP-URI, although, the text
prior to the example in section 4.2 of  the -03 version (current WG version,
submitted in July) of the draft does suggest that the current format is for
readability purposes, this point has been brought up before.  But, from a
specification perspective, it should be accurate.  I'll fix that in the -04
which I will be submitting soon. 

Mary


-----Original Message-----
From: Brett Tate [mailto:brett@broadsoft.com] 
Sent: Friday, October 15, 2004 11:48 AM
To: anagarajan@hssworld.com
Cc: Barnes, Mary [NGC:B601:EXCH]; sipping@ietf.org
Subject: RE: [Sipping] Doubt in ANBF defined
indraft-ietf-sip-history-info-02.txt draft


> However in an example of History-Info 
> header defined in the draft (in section 4.2) :- 
> History-Info:<sip:UserA@ims.nortelnetworks.com
>  ?Reason=SIP;cause=302;text=
>  "Moved Temporarily">; index=1; foo=bar
> 
> note that quoted string occurs in uri-parameters 
> of SIP URI
> 
> But as per the SIP-URI grammar defined in 
> Rfc3261, quoted string cannot occur .
> 
> Please confirm on this..

A quoted string can occur; however the 
example does not reflect the escaping 
across the sip-uri which must occur.

However I continue to have doubts with the
escaping/unescaping process concerning 
quoted strings containing UTF8-NONASCII 
characters.  This can occur in a sip-uri
when embedding a header containing a 
name-addr with a UTF8-NONASCII display-name.




------_=_NextPart_001_01C4B2EE.73322826
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Sipping] Doubt in ANBF defined =
indraft-ietf-sip-history-info-02.txt draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Brett,</FONT>
</P>

<P><FONT SIZE=3D2>Thanks for your response. Yes, I do need to correct =
that example in terms of accurately reflecting the escaping across the =
SIP-URI, although, the text prior to the example in section 4.2 =
of&nbsp; the -03 version (current WG version, submitted in July) of the =
draft does suggest that the current format is for readability purposes, =
this point has been brought up before.&nbsp; But, from a specification =
perspective, it should be accurate.&nbsp; I'll fix that in the -04 =
which I will be submitting soon. </FONT></P>

<P><FONT SIZE=3D2>Mary</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Brett Tate [<A =
HREF=3D"mailto:brett@broadsoft.com">mailto:brett@broadsoft.com</A>] =
</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, October 15, 2004 11:48 AM</FONT>
<BR><FONT SIZE=3D2>To: anagarajan@hssworld.com</FONT>
<BR><FONT SIZE=3D2>Cc: Barnes, Mary [NGC:B601:EXCH]; =
sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Sipping] Doubt in ANBF defined =
indraft-ietf-sip-history-info-02.txt draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; However in an example of History-Info </FONT>
<BR><FONT SIZE=3D2>&gt; header defined in the draft (in section 4.2) :- =
</FONT>
<BR><FONT SIZE=3D2>&gt; =
History-Info:&lt;sip:UserA@ims.nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; ?Reason=3DSIP;cause=3D302;text=3D</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &quot;Moved Temporarily&quot;&gt;; =
index=3D1; foo=3Dbar</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; note that quoted string occurs in =
uri-parameters </FONT>
<BR><FONT SIZE=3D2>&gt; of SIP URI</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; But as per the SIP-URI grammar defined in =
</FONT>
<BR><FONT SIZE=3D2>&gt; Rfc3261, quoted string cannot occur .</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Please confirm on this..</FONT>
</P>

<P><FONT SIZE=3D2>A quoted string can occur; however the </FONT>
<BR><FONT SIZE=3D2>example does not reflect the escaping </FONT>
<BR><FONT SIZE=3D2>across the sip-uri which must occur.</FONT>
</P>

<P><FONT SIZE=3D2>However I continue to have doubts with the</FONT>
<BR><FONT SIZE=3D2>escaping/unescaping process concerning </FONT>
<BR><FONT SIZE=3D2>quoted strings containing UTF8-NONASCII </FONT>
<BR><FONT SIZE=3D2>characters.&nbsp; This can occur in a sip-uri</FONT>
<BR><FONT SIZE=3D2>when embedding a header containing a </FONT>
<BR><FONT SIZE=3D2>name-addr with a UTF8-NONASCII display-name.</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4B2EE.73322826--


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



From sipping-bounces@ietf.org  Fri Oct 15 17:29:27 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 RAA24322
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 17:29:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIZpA-0005uq-2M
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 17:41:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIZSv-0006je-0c; Fri, 15 Oct 2004 17:18:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIYUU-0001AT-9f
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 16:15:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08390
	for <sipping@ietf.org>; Fri, 15 Oct 2004 16:15:51 -0400 (EDT)
Message-Id: <200410152015.QAA08390@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIYft-000198-67
	for sipping@ietf.org; Fri, 15 Oct 2004 16:27:42 -0400
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.42)
	id 1CIYUK-0003NC-KM; Fri, 15 Oct 2004 15:15:44 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Francois Audet'" <audet@nortelnetworks.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Fri, 15 Oct 2004 16:15:38 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcSy7jaH0aeqMvBlT5aUDrAhLz0flAAAKxJg
In-Reply-To: <1ECE0EB50388174790F9694F77522CCFCF5416@zrc2hxm0.corp.nortel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-Antivirus-Scanner: Clean mail though you should still use an Antivirus
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Content-Transfer-Encoding: quoted-printable

First of all, thanks Jonathan for starting discussion on this very =
important
issue.

Most of the SBC pitches I have seen focus on:
1. NAT traversal (and actual NAT functions)
2. Firewall=20
3. DoS attack mitigation
4. SLA enforcement/measurement/facilitation
5. Service provider infrastructure hiding
6. Routing services
7. Legal Intercept
8. Protocol interwork
7. Packet marking and remarking
9. Bandwidth management/policing
10. Call admission control
11. CDR creation and other billing functions
12. Protocol "repair"

That's a pretty good list.  There is overlap, and every vendor has some
twist on flavors of these things.

Brian
________________________________________
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On =
Behalf
Of Francois Audet
Sent: Friday, October 15, 2004 3:22 PM
To: 'Jonathan Rosenberg'; 'sipping'
Subject: RE: [Sipping] What problems are SBCs addressing?

I assume that you are only planning to focus on the SIP aspects.=20
One thing they do is bridging between two different domain, in =
particular=20
for security.=20
While this is not terribly difficult for SIP/TLS, it is considerably =
more=20
awkward/nasty for sRTP.=20
> -----Original Message-----=20
> From: sipping-bounces@ietf.org=20
> [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg=20
> Sent: Thursday, October 14, 2004 21:35=20
> To: sipping=20
> Subject: [Sipping] What problems are SBCs addressing?=20
>=20
>=20
> Folks,=20
>=20
> As many of you know, there are a large number of products on=20
> the market=20
> these days under the general moniker "Session Border Controller";=20
> generally these are B2BUas that play some kind of policy=20
> enforcement and=20
> control function, typically at trust boundaries.=20
>=20
> Our specifications don't define how B2BUas should operate,=20
> and they say=20
> nothing at all about an SBC (although they do address many=20
> problems that=20
> relate to inter-domain operations and trust boundaries). However, the=20
> preponderence of these devices in the market and in VoIP=20
> networks seems=20
> to indicate that there are real problems that providers believe they=20
> have, which they feel these products are solving for them.=20
>=20
> This begs the important question - what are those problems, and are=20
> those problems for which the IETF has produced specifications to=20
> address? If not, is there a need to do so? If yes, are these products=20
> using those specifications, and if not, why have those solutions not=20
> seen implementation and/or deployment?=20
>=20
> Put in another way, sipping is all about requirements and=20
> problems, and=20
> it is clear that there are one or more problems here somewhere. Do we=20
> understand those requirements, and do we need to produce=20
> specifications=20
> to address them?=20
>=20
> This is a fairly meaty topic, one for which I expect to see lots of=20
> emails in reply to this note suggesting answers ;)=20
> Furthermore, we are=20
> planning an informal get together at IETF 61 to continue the dialog,=20
> focusing squarely on understanding requirements and=20
> specification gaps.=20
> Details TBA shortly. Whether one likes the solutions that are=20
> out there=20
> or not, the first step in doing anything is to understand the=20
> requirements. I really want to do that.=20
>=20
> I think it's important to have this discussion now, while=20
> there is still=20
> time to address these issues with standards-based solutions. To=20
> paraphrase Spencer Dawkins' recent note - I don't want to have a BoF=20
> session three years hence called "son-of-behave", where we=20
> discuss what=20
> an SBC should do, wishing that we had written specifications=20
> three years=20
> earlier and thus avoided the interop mess that had resulted.=20
> Given the=20
> recent concerns about GRUU and SIP identity operation through=20
> SBC, this=20
> is even more telling.=20
>=20
> Inputs from people who work for vendors of such devices, your=20
> input is=20
> most welcome..=20
>=20
> Thanks,=20
> Jonathan R.=20
>=20
> --=20
> Jonathan D. Rosenberg, =
Ph.D.=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 600 Lanidex Plaza=20
> Chief Technology =
Officer=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
Parsippany, NJ 07054-2711=20
> dynamicsoft=20
> =
jdrosen@dynamicsoft.com=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 FAX:=A0=A0 (973) 952-5050=20
> =
http://www.jdrosen.net=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 PHONE: (973) 952-5000=20
> http://www.dynamicsoft.com=20
>=20
>=20
>=20
> _______________________________________________=20
> Sipping mailing list=A0 https://www1.ietf.org/mailman/listinfo/sipping =

> This list is for NEW development of the application of SIP=20
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP=20
>=20
>=20



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


From sipping-bounces@ietf.org  Fri Oct 15 18:11: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 SAA28913
	for <sipping-web-archive@ietf.org>; Fri, 15 Oct 2004 18:11:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIaTW-0007AX-8Q
	for sipping-web-archive@ietf.org; Fri, 15 Oct 2004 18:23:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIaFA-0005xu-VZ; Fri, 15 Oct 2004 18:08:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIaB7-0003CT-Mt
	for sipping@megatron.ietf.org; Fri, 15 Oct 2004 18:04:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28069
	for <sipping@ietf.org>; Fri, 15 Oct 2004 18:03:58 -0400 (EDT)
Received: from mailhost.unt.edu ([129.120.209.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIaMY-00071r-LZ
	for sipping@ietf.org; Fri, 15 Oct 2004 18:15:51 -0400
Received: from iatro (localhost.localdomain [127.0.0.1])
	by mail2 (Postfix) with SMTP id 9C56D73E1C
	for <sipping@ietf.org>; Fri, 15 Oct 2004 17:01:23 -0500 (CDT)
Received: from gwia.unt.edu (gwia.unt.edu [129.120.221.21])
	by mailhost.unt.edu (Postfix) with ESMTP id 1332873E75
	for <sipping@ietf.org>; Fri, 15 Oct 2004 17:01:09 -0500 (CDT)
Received: from SMTP-MTA by gwia.unt.edu
	with Novell_GroupWise; Fri, 15 Oct 2004 17:01:07 -0500
Message-Id: <s1700253.014@gwia.unt.edu>
X-Mailer: Novell GroupWise Internet Agent 6.0.5 Beta
Date: Fri, 15 Oct 2004 17:00:09 -0500
From: "Ram Dantu" <RDANTU@egw.unt.edu>
To: <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
Subject: Re: [Sipping] What problems are SBCs addressing?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable


We are having a workshop on this topic (VoIP Security).
In particular, we would like to work on the issues what
SBCs are not addressing. Let me know if you need
further information

http://www.globecom2004.org/images/W05_CFP.pdf

Ram Dantu


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 16 00:11: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 AAA05149
	for <sipping-web-archive@ietf.org>; Sat, 16 Oct 2004 00:11:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIg6g-0005gN-Ms
	for sipping-web-archive@ietf.org; Sat, 16 Oct 2004 00:23:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIfsa-0002N3-PR; Sat, 16 Oct 2004 00:09:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIfqF-0001Br-Rq
	for sipping@megatron.ietf.org; Sat, 16 Oct 2004 00:06:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04912
	for <sipping@ietf.org>; Sat, 16 Oct 2004 00:06:47 -0400 (EDT)
Received: from tonnant.concentric.net ([207.155.248.72]
	helo=tonnant.cnchost.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIg1j-0005bs-Ko
	for sipping@ietf.org; Sat, 16 Oct 2004 00:18:44 -0400
Received: from MedhaviLT (pool-138-88-3-211.res.east.verizon.net
	[138.88.3.211]) by tonnant.cnchost.com
	id AAA28882; Sat, 16 Oct 2004 00:06:32 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.17]
Message-ID: <200410160406.AAA28882@tonnant.cnchost.com>
From: "Medhavi Bhatia" <mbhatia@nextone.com>
To: "'Brian Rosen'" <br@brianrosen.net>,
        "'Francois Audet'" <audet@nortelnetworks.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Sat, 16 Oct 2004 00:06:27 -0400
Organization: NexTone Communications
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <200410152015.QAA08390@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcSy7jaH0aeqMvBlT5aUDrAhLz0flAAAKxJgAA8ijeA=
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mbhatia@nextone.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.2 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Content-Transfer-Encoding: quoted-printable

This looks like a good list to start with (I'd say this captures a good
50-60% of the use cases at this point). However, I think a better point =
to
start with on this list would be the B2BUA, which applies to about =
30-40% of
the functionality of the SBC (the rest being related to other protocols =
and
supporting functions). B2BUAs are used at network core as well as
application servers.

I see this discussion similar to previous threads on B2BUAs and
interworking. From a standardization perspective, we can standardize the =
two
sides of an intermediate entity. The rest is determined by a higher =
layer
(session/application/policy etc).=20

-Medhavi.

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On =
Behalf
Of Brian
> Rosen
> Sent: Friday, October 15, 2004 4:16 PM
> To: 'Francois Audet'; 'Jonathan Rosenberg'; 'sipping'
> Subject: RE: [Sipping] What problems are SBCs addressing?
>=20
> First of all, thanks Jonathan for starting discussion on this very
important
> issue.
>=20
> Most of the SBC pitches I have seen focus on:
> 1. NAT traversal (and actual NAT functions)
> 2. Firewall
> 3. DoS attack mitigation
> 4. SLA enforcement/measurement/facilitation
> 5. Service provider infrastructure hiding
> 6. Routing services
> 7. Legal Intercept
> 8. Protocol interwork
> 7. Packet marking and remarking
> 9. Bandwidth management/policing
> 10. Call admission control
> 11. CDR creation and other billing functions
> 12. Protocol "repair"
>=20
> That's a pretty good list.  There is overlap, and every vendor has =
some
> twist on flavors of these things.
>=20
> Brian
> ________________________________________
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On =
Behalf
> Of Francois Audet
> Sent: Friday, October 15, 2004 3:22 PM
> To: 'Jonathan Rosenberg'; 'sipping'
> Subject: RE: [Sipping] What problems are SBCs addressing?
>=20
> I assume that you are only planning to focus on the SIP aspects.
> One thing they do is bridging between two different domain, in =
particular
> for security.
> While this is not terribly difficult for SIP/TLS, it is considerably =
more
> awkward/nasty for sRTP.
> > -----Original Message-----
> > From: sipping-bounces@ietf.org
> > [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> > Sent: Thursday, October 14, 2004 21:35
> > To: sipping
> > Subject: [Sipping] What problems are SBCs addressing?
> >
> >
> > Folks,
> >
> > As many of you know, there are a large number of products on
> > the market
> > these days under the general moniker "Session Border Controller";
> > generally these are B2BUas that play some kind of policy
> > enforcement and
> > control function, typically at trust boundaries.
> >
> > Our specifications don't define how B2BUas should operate,
> > and they say
> > nothing at all about an SBC (although they do address many
> > problems that
> > relate to inter-domain operations and trust boundaries). However, =
the
> > preponderence of these devices in the market and in VoIP
> > networks seems
> > to indicate that there are real problems that providers believe they
> > have, which they feel these products are solving for them.
> >
> > This begs the important question - what are those problems, and are
> > those problems for which the IETF has produced specifications to
> > address? If not, is there a need to do so? If yes, are these =
products
> > using those specifications, and if not, why have those solutions not
> > seen implementation and/or deployment?
> >
> > Put in another way, sipping is all about requirements and
> > problems, and
> > it is clear that there are one or more problems here somewhere. Do =
we
> > understand those requirements, and do we need to produce
> > specifications
> > to address them?
> >
> > This is a fairly meaty topic, one for which I expect to see lots of
> > emails in reply to this note suggesting answers ;)
> > Furthermore, we are
> > planning an informal get together at IETF 61 to continue the dialog,
> > focusing squarely on understanding requirements and
> > specification gaps.
> > Details TBA shortly. Whether one likes the solutions that are
> > out there
> > or not, the first step in doing anything is to understand the
> > requirements. I really want to do that.
> >
> > I think it's important to have this discussion now, while
> > there is still
> > time to address these issues with standards-based solutions. To
> > paraphrase Spencer Dawkins' recent note - I don't want to have a BoF
> > session three years hence called "son-of-behave", where we
> > discuss what
> > an SBC should do, wishing that we had written specifications
> > three years
> > earlier and thus avoided the interop mess that had resulted.
> > Given the
> > recent concerns about GRUU and SIP identity operation through
> > SBC, this
> > is even more telling.
> >
> > Inputs from people who work for vendors of such devices, your
> > input is
> > most welcome..
> >
> > Thanks,
> > Jonathan R.
> >
> > --
> > Jonathan D. Rosenberg, =
Ph.D.=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 600 Lanidex Plaza
> > Chief Technology =
Officer=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
Parsippany, NJ 07054-2711
> > dynamicsoft
> > =
jdrosen@dynamicsoft.com=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 FAX:=A0=A0 (973) 952-5050
> > =
http://www.jdrosen.net=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 PHONE: (973) 952-5000
> > http://www.dynamicsoft.com
> >
> >
> >
> > _______________________________________________
> > Sipping mailing list=A0 =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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  Sat Oct 16 00:29:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06356
	for <sipping-web-archive@ietf.org>; Sat, 16 Oct 2004 00:29:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIgNT-00061r-Q1
	for sipping-web-archive@ietf.org; Sat, 16 Oct 2004 00:41:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIg94-0000AE-RW; Sat, 16 Oct 2004 00:26:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIg4x-0007kQ-HG
	for sipping@megatron.ietf.org; Sat, 16 Oct 2004 00:22:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05874
	for <sipping@ietf.org>; Sat, 16 Oct 2004 00:21:59 -0400 (EDT)
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIgGD-0005r9-T1
	for sipping@ietf.org; Sat, 16 Oct 2004 00:33:56 -0400
Received: from huawei08hiby56 (mta1.huawei.com [172.17.1.60])
	by mta1.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
	with ESMTPA id <0I5N006IKSTMZZ@mta1.huawei.com> for sipping@ietf.org;
	Sat, 16 Oct 2004 12:08:12 +0800 (CST)
Date: Sat, 16 Oct 2004 09:57:06 +0530
From: Prasanna <prasanna@huawei.com>
Subject: RE: [Sipping] Doubt in ANBF
	definedindraft-ietf-sip-history-info-02.txt draft
In-reply-to: <E3F9D87C63E2774390FE67C924EC99BB022C43F4@zrc2hxm1.corp.nortel.com>
To: "'Mary Barnes'" <mary.barnes@nortelnetworks.com>,
        "'Brett Tate'" <brett@broadsoft.com>, anagarajan@hssworld.com
Message-id: <013001c4b338$659cc590$e905120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.7 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1722104332=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd

This is a multi-part message in MIME format.

--===============1722104332==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_YTWF3QxSTbfZlAewYPlANw)"

This is a multi-part message in MIME format.

--Boundary_(ID_YTWF3QxSTbfZlAewYPlANw)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

I guess the WSP in the URI also has to be escaped, as that is also not
allowed.
-Prasanna

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of Mary Barnes
Sent: Saturday, October 16, 2004 1:08 AM
To: 'Brett Tate'; anagarajan@hssworld.com
Cc: sipping@ietf.org
Subject: RE: [Sipping] Doubt in ANBF
definedindraft-ietf-sip-history-info-02.txt draft



Brett, 

Thanks for your response. Yes, I do need to correct that example in terms of
accurately reflecting the escaping across the SIP-URI, although, the text
prior to the example in section 4.2 of  the -03 version (current WG version,
submitted in July) of the draft does suggest that the current format is for
readability purposes, this point has been brought up before.  But, from a
specification perspective, it should be accurate.  I'll fix that in the -04
which I will be submitting soon. 

Mary 


-----Original Message----- 
From: Brett Tate [mailto:brett@broadsoft.com] 
Sent: Friday, October 15, 2004 11:48 AM 
To: anagarajan@hssworld.com 
Cc: Barnes, Mary [NGC:B601:EXCH]; sipping@ietf.org 
Subject: RE: [Sipping] Doubt in ANBF defined
indraft-ietf-sip-history-info-02.txt draft 


> However in an example of History-Info 
> header defined in the draft (in section 4.2) :- 
> History-Info:<sip:UserA@ims.nortelnetworks.com 
>  ?Reason=SIP;cause=302;text= 
>  "Moved Temporarily">; index=1; foo=bar 
> 
> note that quoted string occurs in uri-parameters 
> of SIP URI 
> 
> But as per the SIP-URI grammar defined in 
> Rfc3261, quoted string cannot occur . 
> 
> Please confirm on this.. 

A quoted string can occur; however the 
example does not reflect the escaping 
across the sip-uri which must occur. 

However I continue to have doubts with the 
escaping/unescaping process concerning 
quoted strings containing UTF8-NONASCII 
characters.  This can occur in a sip-uri 
when embedding a header containing a 
name-addr with a UTF8-NONASCII display-name. 




--Boundary_(ID_YTWF3QxSTbfZlAewYPlANw)
Content-type: text/html; charset=us-ascii
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1476" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=529092604-16102004><FONT face=Arial color=#0000ff size=2>I 
guess the WSP in the URI also has to be escaped, as that is also not 
allowed.</FONT></SPAN></DIV>
<DIV><SPAN class=529092604-16102004><FONT face=Arial color=#0000ff 
size=2>-Prasanna</FONT></SPAN></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us 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>Mary Barnes<BR><B>Sent:</B> Saturday, October 16, 2004 1:08 
  AM<BR><B>To:</B> 'Brett Tate'; anagarajan@hssworld.com<BR><B>Cc:</B> 
  sipping@ietf.org<BR><B>Subject:</B> RE: [Sipping] Doubt in ANBF 
  definedindraft-ietf-sip-history-info-02.txt draft<BR><BR></FONT></DIV>
  <P><FONT size=2>Brett,</FONT> </P>
  <P><FONT size=2>Thanks for your response. Yes, I do need to correct that 
  example in terms of accurately reflecting the escaping across the SIP-URI, 
  although, the text prior to the example in section 4.2 of&nbsp; the -03 
  version (current WG version, submitted in July) of the draft does suggest that 
  the current format is for readability purposes, this point has been brought up 
  before.&nbsp; But, from a specification perspective, it should be 
  accurate.&nbsp; I'll fix that in the -04 which I will be submitting soon. 
  </FONT></P>
  <P><FONT size=2>Mary</FONT> </P><BR>
  <P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Brett 
  Tate [<A href="mailto:brett@broadsoft.com">mailto:brett@broadsoft.com</A>] 
  </FONT><BR><FONT size=2>Sent: Friday, October 15, 2004 11:48 AM</FONT> 
  <BR><FONT size=2>To: anagarajan@hssworld.com</FONT> <BR><FONT size=2>Cc: 
  Barnes, Mary [NGC:B601:EXCH]; sipping@ietf.org</FONT> <BR><FONT 
  size=2>Subject: RE: [Sipping] Doubt in ANBF defined 
  indraft-ietf-sip-history-info-02.txt draft</FONT> </P><BR>
  <P><FONT size=2>&gt; However in an example of History-Info </FONT><BR><FONT 
  size=2>&gt; header defined in the draft (in section 4.2) :- </FONT><BR><FONT 
  size=2>&gt; History-Info:&lt;sip:UserA@ims.nortelnetworks.com</FONT> <BR><FONT 
  size=2>&gt;&nbsp; ?Reason=SIP;cause=302;text=</FONT> <BR><FONT 
  size=2>&gt;&nbsp; "Moved Temporarily"&gt;; index=1; foo=bar</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; note that quoted string occurs in 
  uri-parameters </FONT><BR><FONT size=2>&gt; of SIP URI</FONT> <BR><FONT 
  size=2>&gt; </FONT><BR><FONT size=2>&gt; But as per the SIP-URI grammar 
  defined in </FONT><BR><FONT size=2>&gt; Rfc3261, quoted string cannot occur 
  .</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; Please confirm on 
  this..</FONT> </P>
  <P><FONT size=2>A quoted string can occur; however the </FONT><BR><FONT 
  size=2>example does not reflect the escaping </FONT><BR><FONT size=2>across 
  the sip-uri which must occur.</FONT> </P>
  <P><FONT size=2>However I continue to have doubts with the</FONT> <BR><FONT 
  size=2>escaping/unescaping process concerning </FONT><BR><FONT size=2>quoted 
  strings containing UTF8-NONASCII </FONT><BR><FONT size=2>characters.&nbsp; 
  This can occur in a sip-uri</FONT> <BR><FONT size=2>when embedding a header 
  containing a </FONT><BR><FONT size=2>name-addr with a UTF8-NONASCII 
  display-name.</FONT> </P><BR><BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_YTWF3QxSTbfZlAewYPlANw)--


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



From sipping-bounces@ietf.org  Sat Oct 16 04:20: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 EAA02197
	for <sipping-web-archive@ietf.org>; Sat, 16 Oct 2004 04:20:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIjz2-00016R-4s
	for sipping-web-archive@ietf.org; Sat, 16 Oct 2004 04:32:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIji7-0000lL-VF; Sat, 16 Oct 2004 04:14:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIjb9-0007U1-5P
	for sipping@megatron.ietf.org; Sat, 16 Oct 2004 04:07:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00722
	for <sipping@ietf.org>; Sat, 16 Oct 2004 04:07:28 -0400 (EDT)
Received: from natsmtp00.rzone.de ([81.169.145.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIjmg-0000t4-6i
	for sipping@ietf.org; Sat, 16 Oct 2004 04:19:26 -0400
Received: from snom.de (pD956AE75.dip.t-dialin.net [217.86.174.117])
	by post.webmailer.de (8.13.1/8.13.1) with ESMTP id i9G87Agi008996;
	Sat, 16 Oct 2004 10:07:11 +0200 (MEST)
Message-ID: <4170D6EB.3010804@snom.de>
Date: Sat, 16 Oct 2004 10:08:11 +0200
From: Harry Behrens <hb@snom.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'sipping'" <sipping@ietf.org>
Subject: Re: [Sipping] What problems are SBCs addressing?
References: <200410160406.AAA28882@tonnant.cnchost.com>
In-Reply-To: <200410160406.AAA28882@tonnant.cnchost.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b
Content-Transfer-Encoding: 7bit
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Francois Audet'" <audet@nortelnetworks.com>, mbhatia@nextone.com
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: harry.behrens@snom.de
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: df9edf1223802dd4cf213867a3af6121
Content-Transfer-Encoding: 7bit

First of all I fully agree with what Medhavi says. One will find that a 
lot of
the functionality of an "SBC" is based on operating a B2BUA.

On a more general note:

I caution from "overloading". Looking at Brian's list, I ask myself:
what is left of the network when you take away all of the functionality
supposedly handled by the "SBC"?
The group will never get anywhere practically valuable if you aim at
"solving the question".
A best practice or description of state-of-the-art seems more modest and 
sensible.

This is after all a moving target.

Just my 2c,

    Harry Behrens

Medhavi Bhatia wrote:

>This looks like a good list to start with (I'd say this captures a good
>50-60% of the use cases at this point). However, I think a better point to
>start with on this list would be the B2BUA, which applies to about 30-40% of
>the functionality of the SBC (the rest being related to other protocols and
>supporting functions). B2BUAs are used at network core as well as
>application servers.
>
>I see this discussion similar to previous threads on B2BUAs and
>interworking. From a standardization perspective, we can standardize the two
>sides of an intermediate entity. The rest is determined by a higher layer
>(session/application/policy etc). 
>
>-Medhavi.
>
>  
>
>>-----Original Message-----
>>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
>>    
>>
>Of Brian
>  
>
>>Rosen
>>Sent: Friday, October 15, 2004 4:16 PM
>>To: 'Francois Audet'; 'Jonathan Rosenberg'; 'sipping'
>>Subject: RE: [Sipping] What problems are SBCs addressing?
>>
>>First of all, thanks Jonathan for starting discussion on this very
>>    
>>
>important
>  
>
>>issue.
>>
>>Most of the SBC pitches I have seen focus on:
>>1. NAT traversal (and actual NAT functions)
>>2. Firewall
>>3. DoS attack mitigation
>>4. SLA enforcement/measurement/facilitation
>>5. Service provider infrastructure hiding
>>6. Routing services
>>7. Legal Intercept
>>8. Protocol interwork
>>7. Packet marking and remarking
>>9. Bandwidth management/policing
>>10. Call admission control
>>11. CDR creation and other billing functions
>>12. Protocol "repair"
>>
>>That's a pretty good list.  There is overlap, and every vendor has some
>>twist on flavors of these things.
>>
>>Brian
>>________________________________________
>>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
>>Of Francois Audet
>>Sent: Friday, October 15, 2004 3:22 PM
>>To: 'Jonathan Rosenberg'; 'sipping'
>>Subject: RE: [Sipping] What problems are SBCs addressing?
>>
>>I assume that you are only planning to focus on the SIP aspects.
>>One thing they do is bridging between two different domain, in particular
>>for security.
>>While this is not terribly difficult for SIP/TLS, it is considerably more
>>awkward/nasty for sRTP.
>>    
>>
>>>-----Original Message-----
>>>From: sipping-bounces@ietf.org
>>>[mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
>>>Sent: Thursday, October 14, 2004 21:35
>>>To: sipping
>>>Subject: [Sipping] What problems are SBCs addressing?
>>>
>>>
>>>Folks,
>>>
>>>As many of you know, there are a large number of products on
>>>the market
>>>these days under the general moniker "Session Border Controller";
>>>generally these are B2BUas that play some kind of policy
>>>enforcement and
>>>control function, typically at trust boundaries.
>>>
>>>Our specifications don't define how B2BUas should operate,
>>>and they say
>>>nothing at all about an SBC (although they do address many
>>>problems that
>>>relate to inter-domain operations and trust boundaries). However, the
>>>preponderence of these devices in the market and in VoIP
>>>networks seems
>>>to indicate that there are real problems that providers believe they
>>>have, which they feel these products are solving for them.
>>>
>>>This begs the important question - what are those problems, and are
>>>those problems for which the IETF has produced specifications to
>>>address? If not, is there a need to do so? If yes, are these products
>>>using those specifications, and if not, why have those solutions not
>>>seen implementation and/or deployment?
>>>
>>>Put in another way, sipping is all about requirements and
>>>problems, and
>>>it is clear that there are one or more problems here somewhere. Do we
>>>understand those requirements, and do we need to produce
>>>specifications
>>>to address them?
>>>
>>>This is a fairly meaty topic, one for which I expect to see lots of
>>>emails in reply to this note suggesting answers ;)
>>>Furthermore, we are
>>>planning an informal get together at IETF 61 to continue the dialog,
>>>focusing squarely on understanding requirements and
>>>specification gaps.
>>>Details TBA shortly. Whether one likes the solutions that are
>>>out there
>>>or not, the first step in doing anything is to understand the
>>>requirements. I really want to do that.
>>>
>>>I think it's important to have this discussion now, while
>>>there is still
>>>time to address these issues with standards-based solutions. To
>>>paraphrase Spencer Dawkins' recent note - I don't want to have a BoF
>>>session three years hence called "son-of-behave", where we
>>>discuss what
>>>an SBC should do, wishing that we had written specifications
>>>three years
>>>earlier and thus avoided the interop mess that had resulted.
>>>Given the
>>>recent concerns about GRUU and SIP identity operation through
>>>SBC, this
>>>is even more telling.
>>>
>>>Inputs from people who work for vendors of such devices, your
>>>input is
>>>most welcome..
>>>
>>>Thanks,
>>>Jonathan R.
>>>
>>>--
>>>Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
>>>Chief Technology Officer                    Parsippany, NJ 07054-2711
>>>dynamicsoft
>>>jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
>>>http://www.jdrosen.net                      PHONE: (973) 952-5000
>>>http://www.dynamicsoft.com
>>>
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current
>>>sip Use sip@ietf.org for new developments of core SIP
>>>
>>>
>>>      
>>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the 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  Sat Oct 16 13:56: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 NAA05392
	for <sipping-web-archive@ietf.org>; Sat, 16 Oct 2004 13:56:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIszE-0002Ug-Ri
	for sipping-web-archive@ietf.org; Sat, 16 Oct 2004 14:09:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIsmS-00085Z-P3; Sat, 16 Oct 2004 13:55:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIslc-0007vD-Li
	for sipping@megatron.ietf.org; Sat, 16 Oct 2004 13:54:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05358
	for <sipping@ietf.org>; Sat, 16 Oct 2004 13:54:54 -0400 (EDT)
Message-Id: <200410161754.NAA05358@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIsxF-0002Tu-0T
	for sipping@ietf.org; Sat, 16 Oct 2004 14:06:57 -0400
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CIslM-000370-8X; Sat, 16 Oct 2004 12:54:40 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: <harry.behrens@snom.de>, "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Sat, 16 Oct 2004 13:54:30 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcSzVySNbfCEOIqBTYWZz77p3Ix/bgAMtAfQ
In-Reply-To: <4170D6EB.3010804@snom.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5fb88b8381f3896aeacc5a021513237b
Content-Transfer-Encoding: 7bit
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, mbhatia@nextone.com,
        "'Francois Audet'" <audet@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Content-Transfer-Encoding: 7bit

The question Jonathan raised was "what problem are SBCs solving?"
While I didn't phrase my response in terms of problems, just stating what
the effect B2BUAs have on a call is pretty far from what was asked.

I don't agree with Medhavi at all.  A B2BUA can be operated in such a way
that it is completely transparent to the signaling, and does not provide any
of the functions I listed.

I'm assuming Jonathan wants to start efforts that lead to STANDARDIZED ways
to solve the problems that SBCs are solving because the way SBCs work is to
break the end to end model of SIP (and the Internet).  I think he believes,
as I do, that it's a BAD THING to break e2e.  An example is that an SBC that
rewrites SDP (to force media to go through the SBC) breaks any S/MIME
security on the body.

We're breaking down the problem.  One of the functions SBCs do that I listed
was to mark (or remark) packets.  If a network offers some form of QoS like
DiffServ, they may mark voice packets belonging to calls admitted to the
network to get "special" treatment by the network.  Some form of priority,
for example.  Network operators want to make sure that only calls they
specifically admit to the network can have media packets marked for special
treatment.  They want to make sure that someone doesn't steal services by
marking packets inappropriately.

So the SBC does call admission control (which may limit the number of calls
admitted so that the total amount of "special treatment" packets in the
network doesn't exceed the capacity of the network to provide the special
treatment.  That part is also "SLA enforcement/facilitation".  It rewrites
the SDP addresses so that media flows through the SBC rather than direct to
the other end.  It then tracks all of the media packets flowing through it
(firewall functions), and makes sure that those for calls which it has
admitted have the correct packet marking.  It either unmarks packets it
doesn't recognize, or may even drop them.

To standardize the problem the SBC is solving is fairly difficult.  We might
provide a way to explicitly route packets through (normally passive) packet
relays that monitor marking that is explicitly signaled.  That would provide
a monitoring point that was explicit rather than require the SBC to rewrite
the SDP.  

Brian

> -----Original Message-----
> From: Harry Behrens [mailto:hb@snom.de]
> Sent: Saturday, October 16, 2004 4:08 AM
> To: 'sipping'
> Cc: mbhatia@nextone.com; 'Brian Rosen'; 'Francois Audet'; 'Jonathan
> Rosenberg'
> Subject: Re: [Sipping] What problems are SBCs addressing?
> 
> First of all I fully agree with what Medhavi says. One will find that a
> lot of
> the functionality of an "SBC" is based on operating a B2BUA.
> 
> On a more general note:
> 
> I caution from "overloading". Looking at Brian's list, I ask myself:
> what is left of the network when you take away all of the functionality
> supposedly handled by the "SBC"?
> The group will never get anywhere practically valuable if you aim at
> "solving the question".
> A best practice or description of state-of-the-art seems more modest and
> sensible.
> 
> This is after all a moving target.
> 
> Just my 2c,
> 
>     Harry Behrens
> 
> Medhavi Bhatia wrote:
> 
> >This looks like a good list to start with (I'd say this captures a good
> >50-60% of the use cases at this point). However, I think a better point
> to
> >start with on this list would be the B2BUA, which applies to about 30-40%
> of
> >the functionality of the SBC (the rest being related to other protocols
> and
> >supporting functions). B2BUAs are used at network core as well as
> >application servers.
> >
> >I see this discussion similar to previous threads on B2BUAs and
> >interworking. From a standardization perspective, we can standardize the
> two
> >sides of an intermediate entity. The rest is determined by a higher layer
> >(session/application/policy etc).
> >
> >-Medhavi.
> >
> >
> >
> >>-----Original Message-----
> >>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> >>
> >>
> >Of Brian
> >
> >
> >>Rosen
> >>Sent: Friday, October 15, 2004 4:16 PM
> >>To: 'Francois Audet'; 'Jonathan Rosenberg'; 'sipping'
> >>Subject: RE: [Sipping] What problems are SBCs addressing?
> >>
> >>First of all, thanks Jonathan for starting discussion on this very
> >>
> >>
> >important
> >
> >
> >>issue.
> >>
> >>Most of the SBC pitches I have seen focus on:
> >>1. NAT traversal (and actual NAT functions)
> >>2. Firewall
> >>3. DoS attack mitigation
> >>4. SLA enforcement/measurement/facilitation
> >>5. Service provider infrastructure hiding
> >>6. Routing services
> >>7. Legal Intercept
> >>8. Protocol interwork
> >>7. Packet marking and remarking
> >>9. Bandwidth management/policing
> >>10. Call admission control
> >>11. CDR creation and other billing functions
> >>12. Protocol "repair"
> >>
> >>That's a pretty good list.  There is overlap, and every vendor has some
> >>twist on flavors of these things.
> >>
> >>Brian
> >>________________________________________
> >>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> >>Of Francois Audet
> >>Sent: Friday, October 15, 2004 3:22 PM
> >>To: 'Jonathan Rosenberg'; 'sipping'
> >>Subject: RE: [Sipping] What problems are SBCs addressing?
> >>
> >>I assume that you are only planning to focus on the SIP aspects.
> >>One thing they do is bridging between two different domain, in
> particular
> >>for security.
> >>While this is not terribly difficult for SIP/TLS, it is considerably
> more
> >>awkward/nasty for sRTP.
> >>
> >>
> >>>-----Original Message-----
> >>>From: sipping-bounces@ietf.org
> >>>[mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> >>>Sent: Thursday, October 14, 2004 21:35
> >>>To: sipping
> >>>Subject: [Sipping] What problems are SBCs addressing?
> >>>
> >>>
> >>>Folks,
> >>>
> >>>As many of you know, there are a large number of products on
> >>>the market
> >>>these days under the general moniker "Session Border Controller";
> >>>generally these are B2BUas that play some kind of policy
> >>>enforcement and
> >>>control function, typically at trust boundaries.
> >>>
> >>>Our specifications don't define how B2BUas should operate,
> >>>and they say
> >>>nothing at all about an SBC (although they do address many
> >>>problems that
> >>>relate to inter-domain operations and trust boundaries). However, the
> >>>preponderence of these devices in the market and in VoIP
> >>>networks seems
> >>>to indicate that there are real problems that providers believe they
> >>>have, which they feel these products are solving for them.
> >>>
> >>>This begs the important question - what are those problems, and are
> >>>those problems for which the IETF has produced specifications to
> >>>address? If not, is there a need to do so? If yes, are these products
> >>>using those specifications, and if not, why have those solutions not
> >>>seen implementation and/or deployment?
> >>>
> >>>Put in another way, sipping is all about requirements and
> >>>problems, and
> >>>it is clear that there are one or more problems here somewhere. Do we
> >>>understand those requirements, and do we need to produce
> >>>specifications
> >>>to address them?
> >>>
> >>>This is a fairly meaty topic, one for which I expect to see lots of
> >>>emails in reply to this note suggesting answers ;)
> >>>Furthermore, we are
> >>>planning an informal get together at IETF 61 to continue the dialog,
> >>>focusing squarely on understanding requirements and
> >>>specification gaps.
> >>>Details TBA shortly. Whether one likes the solutions that are
> >>>out there
> >>>or not, the first step in doing anything is to understand the
> >>>requirements. I really want to do that.
> >>>
> >>>I think it's important to have this discussion now, while
> >>>there is still
> >>>time to address these issues with standards-based solutions. To
> >>>paraphrase Spencer Dawkins' recent note - I don't want to have a BoF
> >>>session three years hence called "son-of-behave", where we
> >>>discuss what
> >>>an SBC should do, wishing that we had written specifications
> >>>three years
> >>>earlier and thus avoided the interop mess that had resulted.
> >>>Given the
> >>>recent concerns about GRUU and SIP identity operation through
> >>>SBC, this
> >>>is even more telling.
> >>>
> >>>Inputs from people who work for vendors of such devices, your
> >>>input is
> >>>most welcome..
> >>>
> >>>Thanks,
> >>>Jonathan R.
> >>>
> >>>--
> >>>Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> >>>Chief Technology Officer                    Parsippany, NJ 07054-2711
> >>>dynamicsoft
> >>>jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> >>>http://www.jdrosen.net                      PHONE: (973) 952-5000
> >>>http://www.dynamicsoft.com
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >>>This list is for NEW development of the application of SIP
> >>>Use sip-implementors@cs.columbia.edu for questions on current
> >>>sip Use sip@ietf.org for new developments of core SIP
> >>>
> >>>
> >>>
> >>>
> >>
> >>_______________________________________________
> >>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >>This list is for NEW development of the 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  Sat Oct 16 14:01: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 OAA05724
	for <sipping-web-archive@ietf.org>; Sat, 16 Oct 2004 14:01:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CIt3W-0002b3-Mt
	for sipping-web-archive@ietf.org; Sat, 16 Oct 2004 14:13:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIsmT-00085f-FM; Sat, 16 Oct 2004 13:55:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIslf-0007vF-1l
	for sipping@megatron.ietf.org; Sat, 16 Oct 2004 13:54:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05361
	for <sipping@ietf.org>; Sat, 16 Oct 2004 13:54:57 -0400 (EDT)
Message-Id: <200410161754.NAA05361@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIsx7-0002To-QA
	for sipping@ietf.org; Sat, 16 Oct 2004 14:07:00 -0400
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CIslN-000370-5P; Sat, 16 Oct 2004 12:54:41 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Ram Dantu'" <RDANTU@egw.unt.edu>, <jdrosen@dynamicsoft.com>,
        <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Sat, 16 Oct 2004 13:54:30 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcSzA95bBgq8tbDrTi+tClwTbEaroQAhVWgA
In-Reply-To: <s1700253.014@gwia.unt.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
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.8 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

The big one is that IETF specifications will REQUIRE TLS security for
emergency calls (1-1-2/9-1-1/...) because location is carried in the
signaling.  When I checked last, there were no SBCs which would maintain a
sips connection.  That may have changed, but it's an issue.

There are a number of other issues with respect to emergency calls that will
require changes in SBCs, but with respect to security its maintaining TLS.

Brian

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
> Of Ram Dantu
> Sent: Friday, October 15, 2004 6:00 PM
> To: jdrosen@dynamicsoft.com; sipping@ietf.org
> Subject: Re: [Sipping] What problems are SBCs addressing?
> 
> 
> We are having a workshop on this topic (VoIP Security).
> In particular, we would like to work on the issues what
> SBCs are not addressing. Let me know if you need
> further information
> 
> http://www.globecom2004.org/images/W05_CFP.pdf
> 
> Ram Dantu
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 17 00:09:27 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 AAA03311
	for <sipping-web-archive@ietf.org>; Sun, 17 Oct 2004 00:09:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJ2Y5-0002rM-4J
	for sipping-web-archive@ietf.org; Sun, 17 Oct 2004 00:21:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJ2Ln-000120-9y; Sun, 17 Oct 2004 00:08:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJ2JO-0000Vf-Dy
	for sipping@megatron.ietf.org; Sun, 17 Oct 2004 00:06:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03132
	for <sipping@ietf.org>; Sun, 17 Oct 2004 00:06:22 -0400 (EDT)
Received: from tonnant.concentric.net ([207.155.248.72]
	helo=tonnant.cnchost.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJ2V5-0002nM-6D
	for sipping@ietf.org; Sun, 17 Oct 2004 00:18:31 -0400
Received: from MedhaviLT (pool-141-156-215-192.res.east.verizon.net
	[141.156.215.192]) by tonnant.cnchost.com
	id AAA00052; Sun, 17 Oct 2004 00:06:04 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.17]
Message-ID: <200410170406.AAA00052@tonnant.cnchost.com>
From: "Medhavi Bhatia" <mbhatia@nextone.com>
To: "'Brian Rosen'" <br@brianrosen.net>, <harry.behrens@snom.de>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Sun, 17 Oct 2004 00:06:03 -0400
Organization: NexTone Communications
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <200410161754.NAA05358@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcSzVySNbfCEOIqBTYWZz77p3Ix/bgAMtAfQABqPwtA=
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5ba9b8496764663b12c333825fbf6b3d
Content-Transfer-Encoding: 7bit
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Francois Audet'" <audet@nortelnetworks.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mbhatia@nextone.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.2 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Content-Transfer-Encoding: 7bit

> I don't agree with Medhavi at all.  A B2BUA can be operated in such a way
> that it is completely transparent to the signaling, and does not provide
any
> of the functions I listed.
> 
[MB] I don't think I hinted at all B2BUAs having to do some kind of SBC
functions (I think I did mention application servers/proxies as other
applications of B2BUA, so varying degrees of transparency are possible).
However I do think there are some misconceptions about SBCs breaking those
transparencies and that an SBC is always a B2BUA underneath rewriting SDP.
These problems are probably solvable without using B2BUAs. However, a
different solution/approach to these problems does not change the role or
specification of the SBC in each of the application/use cases. For example,
when a service provider wants an SBC which solves the lawful interception
problem or implements QoS in the network, they don't care whether it is a
B2BUA or a proxy,  or if SDP is being rewritten and how (the way that these
problems are solved currently is using B2BUAs). In scenarios where e2e
security is important, clearly there must be cooperation between the end
user and the intermediate network as the goals are conflicting. However the
nature of the solution does not change what these elements are called today
by customers/service providers.

> I'm assuming Jonathan wants to start efforts that lead to STANDARDIZED
ways
> to solve the problems that SBCs are solving because the way SBCs work is
to
> break the end to end model of SIP (and the Internet).  I think he
believes,
> as I do, that it's a BAD THING to break e2e.  An example is that an SBC
that
> rewrites SDP (to force media to go through the SBC) breaks any S/MIME
> security on the body.
> 
[MB] Again I think what you are trying to say is that the way SBCs are
implemented today (which is using B2BUAs), e2e security is not supported.
However, there is no reason why it shouldn't and I believe that it will once
the network and the user cooperate, and there are several approaches like
the policy framework/nsis for some of this stuff. Whatever the solution is,
it will be implemented and the net "thing" will still be called an SBC. Each
kind of SBC (and some of which you mention below) is really a set of
requirements.

> We're breaking down the problem.  One of the functions SBCs do that I
listed
> was to mark (or remark) packets.  If a network offers some form of QoS
like
> DiffServ, they may mark voice packets belonging to calls admitted to the
> network to get "special" treatment by the network.  Some form of priority,
> for example.  Network operators want to make sure that only calls they
> specifically admit to the network can have media packets marked for
special
> treatment.  They want to make sure that someone doesn't steal services by
> marking packets inappropriately.
> 
[MB] I think I can add some more requirements to the QoS set. It is both the
policing and facilitation as you mention below. However, I think there are
ways to do this w/o rewriting SDP. QoS measurement is another requirement to
consider. Breaking down each of these problems sounds good, but there are
too many of these (real) problems. Don't we already know the common set ? I
believe it is: any entity in the path of a session may like to know who the
originator is (for SLA purposes, this may be the end user or previous hop),
what resources are being really expected, the provision/detection of the use
of these resources and their policing. All this and e2e transparency.

> So the SBC does call admission control (which may limit the number of
calls
> admitted so that the total amount of "special treatment" packets in the
> network doesn't exceed the capacity of the network to provide the special
> treatment.  That part is also "SLA enforcement/facilitation".  It rewrites
> the SDP addresses so that media flows through the SBC rather than direct
to
> the other end.  It then tracks all of the media packets flowing through it
> (firewall functions), and makes sure that those for calls which it has
> admitted have the correct packet marking.  It either unmarks packets it
> doesn't recognize, or may even drop them.
> 
> To standardize the problem the SBC is solving is fairly difficult.  We
might
> provide a way to explicitly route packets through (normally passive)
packet
> relays that monitor marking that is explicitly signaled.  That would
provide
> a monitoring point that was explicit rather than require the SBC to
rewrite
> the SDP.
> 
[MB] I haven't looked at the nsis work recently. From what I understand that
is the kind of cooperative mechanism SBCs will develop.

-Medhavi.

> Brian
> 
> > -----Original Message-----
> > From: Harry Behrens [mailto:hb@snom.de]
> > Sent: Saturday, October 16, 2004 4:08 AM
> > To: 'sipping'
> > Cc: mbhatia@nextone.com; 'Brian Rosen'; 'Francois Audet'; 'Jonathan
> > Rosenberg'
> > Subject: Re: [Sipping] What problems are SBCs addressing?
> >
> > First of all I fully agree with what Medhavi says. One will find that a
> > lot of
> > the functionality of an "SBC" is based on operating a B2BUA.
> >
> > On a more general note:
> >
> > I caution from "overloading". Looking at Brian's list, I ask myself:
> > what is left of the network when you take away all of the functionality
> > supposedly handled by the "SBC"?
> > The group will never get anywhere practically valuable if you aim at
> > "solving the question".
> > A best practice or description of state-of-the-art seems more modest and
> > sensible.
> >
> > This is after all a moving target.
> >
> > Just my 2c,
> >
> >     Harry Behrens
> >
> > Medhavi Bhatia wrote:
> >
> > >This looks like a good list to start with (I'd say this captures a good
> > >50-60% of the use cases at this point). However, I think a better point
> > to
> > >start with on this list would be the B2BUA, which applies to about
30-40%
> > of
> > >the functionality of the SBC (the rest being related to other protocols
> > and
> > >supporting functions). B2BUAs are used at network core as well as
> > >application servers.
> > >
> > >I see this discussion similar to previous threads on B2BUAs and
> > >interworking. From a standardization perspective, we can standardize
the
> > two
> > >sides of an intermediate entity. The rest is determined by a higher
layer
> > >(session/application/policy etc).
> > >
> > >-Medhavi.
> > >
> > >
> > >
> > >>-----Original Message-----
> > >>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf
> > >>
> > >>
> > >Of Brian
> > >
> > >
> > >>Rosen
> > >>Sent: Friday, October 15, 2004 4:16 PM
> > >>To: 'Francois Audet'; 'Jonathan Rosenberg'; 'sipping'
> > >>Subject: RE: [Sipping] What problems are SBCs addressing?
> > >>
> > >>First of all, thanks Jonathan for starting discussion on this very
> > >>
> > >>
> > >important
> > >
> > >
> > >>issue.
> > >>
> > >>Most of the SBC pitches I have seen focus on:
> > >>1. NAT traversal (and actual NAT functions)
> > >>2. Firewall
> > >>3. DoS attack mitigation
> > >>4. SLA enforcement/measurement/facilitation
> > >>5. Service provider infrastructure hiding
> > >>6. Routing services
> > >>7. Legal Intercept
> > >>8. Protocol interwork
> > >>7. Packet marking and remarking
> > >>9. Bandwidth management/policing
> > >>10. Call admission control
> > >>11. CDR creation and other billing functions
> > >>12. Protocol "repair"
> > >>
> > >>That's a pretty good list.  There is overlap, and every vendor has
some
> > >>twist on flavors of these things.
> > >>
> > >>Brian
> > >>________________________________________
> > >>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf
> > >>Of Francois Audet
> > >>Sent: Friday, October 15, 2004 3:22 PM
> > >>To: 'Jonathan Rosenberg'; 'sipping'
> > >>Subject: RE: [Sipping] What problems are SBCs addressing?
> > >>
> > >>I assume that you are only planning to focus on the SIP aspects.
> > >>One thing they do is bridging between two different domain, in
> > particular
> > >>for security.
> > >>While this is not terribly difficult for SIP/TLS, it is considerably
> > more
> > >>awkward/nasty for sRTP.
> > >>
> > >>
> > >>>-----Original Message-----
> > >>>From: sipping-bounces@ietf.org
> > >>>[mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> > >>>Sent: Thursday, October 14, 2004 21:35
> > >>>To: sipping
> > >>>Subject: [Sipping] What problems are SBCs addressing?
> > >>>
> > >>>
> > >>>Folks,
> > >>>
> > >>>As many of you know, there are a large number of products on
> > >>>the market
> > >>>these days under the general moniker "Session Border Controller";
> > >>>generally these are B2BUas that play some kind of policy
> > >>>enforcement and
> > >>>control function, typically at trust boundaries.
> > >>>
> > >>>Our specifications don't define how B2BUas should operate,
> > >>>and they say
> > >>>nothing at all about an SBC (although they do address many
> > >>>problems that
> > >>>relate to inter-domain operations and trust boundaries). However, the
> > >>>preponderence of these devices in the market and in VoIP
> > >>>networks seems
> > >>>to indicate that there are real problems that providers believe they
> > >>>have, which they feel these products are solving for them.
> > >>>
> > >>>This begs the important question - what are those problems, and are
> > >>>those problems for which the IETF has produced specifications to
> > >>>address? If not, is there a need to do so? If yes, are these products
> > >>>using those specifications, and if not, why have those solutions not
> > >>>seen implementation and/or deployment?
> > >>>
> > >>>Put in another way, sipping is all about requirements and
> > >>>problems, and
> > >>>it is clear that there are one or more problems here somewhere. Do we
> > >>>understand those requirements, and do we need to produce
> > >>>specifications
> > >>>to address them?
> > >>>
> > >>>This is a fairly meaty topic, one for which I expect to see lots of
> > >>>emails in reply to this note suggesting answers ;)
> > >>>Furthermore, we are
> > >>>planning an informal get together at IETF 61 to continue the dialog,
> > >>>focusing squarely on understanding requirements and
> > >>>specification gaps.
> > >>>Details TBA shortly. Whether one likes the solutions that are
> > >>>out there
> > >>>or not, the first step in doing anything is to understand the
> > >>>requirements. I really want to do that.
> > >>>
> > >>>I think it's important to have this discussion now, while
> > >>>there is still
> > >>>time to address these issues with standards-based solutions. To
> > >>>paraphrase Spencer Dawkins' recent note - I don't want to have a BoF
> > >>>session three years hence called "son-of-behave", where we
> > >>>discuss what
> > >>>an SBC should do, wishing that we had written specifications
> > >>>three years
> > >>>earlier and thus avoided the interop mess that had resulted.
> > >>>Given the
> > >>>recent concerns about GRUU and SIP identity operation through
> > >>>SBC, this
> > >>>is even more telling.
> > >>>
> > >>>Inputs from people who work for vendors of such devices, your
> > >>>input is
> > >>>most welcome..
> > >>>
> > >>>Thanks,
> > >>>Jonathan R.
> > >>>
> > >>>--
> > >>>Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> > >>>Chief Technology Officer                    Parsippany, NJ 07054-2711
> > >>>dynamicsoft
> > >>>jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> > >>>http://www.jdrosen.net                      PHONE: (973) 952-5000
> > >>>http://www.dynamicsoft.com
> > >>>
> > >>>
> > >>>
> > >>>_______________________________________________
> > >>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > >>>This list is for NEW development of the application of SIP
> > >>>Use sip-implementors@cs.columbia.edu for questions on current
> > >>>sip Use sip@ietf.org for new developments of core SIP
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>_______________________________________________
> > >>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > >>This list is for NEW development of the application of SIP
> > >>Use sip-implementors@cs.columbia.edu for questions on current sip
> > >>Use sip@ietf.org for new developments of core SIP
> > >>
> > >>
> > >
> > >
> > >_______________________________________________
> > >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > >This list is for NEW development of the application of SIP
> > >Use sip-implementors@cs.columbia.edu for questions on current sip
> > >Use sip@ietf.org for new developments of core SIP
> > >
> > >
> > >
> >
> >
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Sun Oct 17 20:58: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 UAA10122
	for <sipping-web-archive@ietf.org>; Sun, 17 Oct 2004 20:58:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJM2m-0002wP-5R
	for sipping-web-archive@ietf.org; Sun, 17 Oct 2004 21:10:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJLow-0003rr-7G; Sun, 17 Oct 2004 20:56:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJLoK-0002ya-Hw
	for sipping@megatron.ietf.org; Sun, 17 Oct 2004 20:55:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09848
	for <sipping@ietf.org>; Sun, 17 Oct 2004 20:55:39 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJM0C-0002pw-R2
	for sipping@ietf.org; Sun, 17 Oct 2004 21:07:58 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 17 Oct 2004 18:02:18 -0700
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 i9I0swYJ019157
	for <sipping@ietf.org>; Sun, 17 Oct 2004 17:55:01 -0700 (PDT)
Received: from [10.0.2.2] (sjc-vpn1-1106.cisco.com [10.21.100.82])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATF15335;
	Sun, 17 Oct 2004 17:55:01 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Sun, 17 Oct 2004 20:55:09 -0400
From: Cullen Jennings <fluffy@cisco.com>
To: sipping <sipping@ietf.org>
Message-ID: <BD988CAD.1571D%fluffy@cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Subject: [Sipping] New draft on getting certificates to UAs 
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


Jon and I submitted a new version of this draft. Until it shows up in
directory, you can find a copy at

http://scm.sipfoundry.org/rep/ietf-drafts/fluffy/draft-ietf-sipping-certs-00
.html

or

http://scm.sipfoundry.org/rep/ietf-drafts/fluffy/draft-ietf-sipping-certs-00
.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


From sipping-bounces@ietf.org  Mon Oct 18 04:59: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 EAA29095
	for <sipping-web-archive@ietf.org>; Mon, 18 Oct 2004 04:59:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJTYo-0003gq-Kk
	for sipping-web-archive@ietf.org; Mon, 18 Oct 2004 05:12:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJTI2-0003Ur-Jj; Mon, 18 Oct 2004 04:54:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJTGH-0003LR-Kg
	for sipping@megatron.ietf.org; Mon, 18 Oct 2004 04:53:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28408
	for <sipping@ietf.org>; Mon, 18 Oct 2004 04:52:59 -0400 (EDT)
Received: from cmailg1.svr.pol.co.uk ([195.92.195.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJTSD-0003Xb-RK
	for sipping@ietf.org; Mon, 18 Oct 2004 05:05:23 -0400
Received: from user-3685.l1.c1.dsl.pol.co.uk ([81.77.78.101] helo=RW)
	by cmailg1.svr.pol.co.uk with smtp (Exim 4.14)
	id 1CJTG1-00025L-Np; Mon, 18 Oct 2004 09:52:45 +0100
Message-ID: <002a01c4b4ef$d7f83d50$c700a8c0@RW>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Brian Rosen" <br@brianrosen.net>, <jdrosen@dynamicsoft.com>,
        <sipping@ietf.org>
References: <200410161754.NAA05361@ietf.org>
Subject: Re: [Sipping] What problems are SBCs addressing?
Date: Mon, 18 Oct 2004 09:52:40 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
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.1 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit

The apparent incompatibility between proxy based perimeter defence and
things like TLS (e.g. end-to-end encryption/authentication) is something I
want to emphasis.  (Most firewall functions are currently located at the
network perimeter.  There are motions to make all hosts in an enterprise act
as their own firewall, but it may be a while before this is widely trusted
and accepted.)  Even on HTTP, TLS isn't particularly firewall friendly as it
doesn't allow inspection (hence abuse of port 443).

So my point is, perimeter defence and end-to-end encryption/authentication
are both important security issues.  We need to avoid developing one
facility at the expense of the other.

BTW - I've taken the liberty of re-ordering Brian's list into (rough)
categories:-

Perimeter defence type things:
-----------------------
2. Firewall
3. DoS attack mitigation
5. Service provider infrastructure hiding
7. Legal Intercept (pjc - maybe a thing on its own e.g. regulatory.)

QoS type things:
-----------------
4. SLA enforcement/measurement/facilitation
7. Packet marking and remarking
9. Bandwidth management/policing

Addressing IP deployment issues type things:
-----------------------------
1. NAT traversal (and actual NAT functions)

'Regular' SIP proxy type things:
--------------------------------
6. Routing services (pjc - I assume this is SIP routing)
10. Call admission control
11. CDR creation and other billing functions
12. Protocol "repair"

Misc!:
---------
8. Protocol interwork (pjc - really a GW function?)

Of these categories, the first two are the ones I feel are not addressed by
other SIP pieces.  With regard to NAT, there are other ways to do NAT
traversal.  However, if you are required to have a DMZ proxy then having it
do NAT traversal as well may be conceptually easier than other solutions.

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware
http://www.tech-know-ware.com
For LMX XML to C++ binding see http://www.xml2cpp.com
=============================================

----- Original Message ----- 
From: "Brian Rosen" <br@brianrosen.net>
To: "'Ram Dantu'" <RDANTU@egw.unt.edu>; <jdrosen@dynamicsoft.com>;
<sipping@ietf.org>
Sent: Saturday, October 16, 2004 6:54 PM
Subject: RE: [Sipping] What problems are SBCs addressing?


> The big one is that IETF specifications will REQUIRE TLS security for
> emergency calls (1-1-2/9-1-1/...) because location is carried in the
> signaling.  When I checked last, there were no SBCs which would maintain a
> sips connection.  That may have changed, but it's an issue.
>
> There are a number of other issues with respect to emergency calls that
will
> require changes in SBCs, but with respect to security its maintaining TLS.
>
> Brian
>
> > -----Original Message-----
> > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf
> > Of Ram Dantu
> > Sent: Friday, October 15, 2004 6:00 PM
> > To: jdrosen@dynamicsoft.com; sipping@ietf.org
> > Subject: Re: [Sipping] What problems are SBCs addressing?
> >
> >
> > We are having a workshop on this topic (VoIP Security).
> > In particular, we would like to work on the issues what
> > SBCs are not addressing. Let me know if you need
> > further information
> >
> > http://www.globecom2004.org/images/W05_CFP.pdf
> >
> > Ram Dantu
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Mon Oct 18 09:14:27 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 JAA14512
	for <sipping-web-archive@ietf.org>; Mon, 18 Oct 2004 09:14:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJXXI-0008Ha-2f
	for sipping-web-archive@ietf.org; Mon, 18 Oct 2004 09:26:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJXGc-0006Jm-LD; Mon, 18 Oct 2004 09:09:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJX8B-0005Ga-8B
	for sipping@megatron.ietf.org; Mon, 18 Oct 2004 09:00:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13335
	for <sipping@ietf.org>; Mon, 18 Oct 2004 09:00:53 -0400 (EDT)
Message-Id: <200410181300.JAA13335@ietf.org>
Received: from winwebhosting.com ([67.15.20.8] helo=dx24.winwebhosting.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJXK0-000807-Ri
	for sipping@ietf.org; Mon, 18 Oct 2004 09:13:19 -0400
Received: from acs-24-154-127-195.zoominternet.net ([24.154.127.195]
	helo=BROSENLT) by dx24.winwebhosting.com with esmtpa (Exim 4.43)
	id 1CJX7t-0001N1-KE; Mon, 18 Oct 2004 08:00:37 -0500
From: "Brian Rosen" <br@brianrosen.net>
To: "'Pete Cordell'" <pete@tech-know-ware.com>, <jdrosen@dynamicsoft.com>,
        <sipping@ietf.org>
Subject: RE: [Sipping] What problems are SBCs addressing?
Date: Mon, 18 Oct 2004 09:00:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcS079jCOVsdUswPRba/R3P2BiPwlAAINu2w
In-Reply-To: <002a01c4b4ef$d7f83d50$c700a8c0@RW>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-PopBeforeSMTPSenders: br@brianrosen.net,brosen
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx24.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: 7bit
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: 7bit

Pete

TLS is not end to end, it is hop by hop.  An SBC could implement
sips and be able to inspect, but most don't.  That's not a standards
problem; if they were 3261 compliant, they would implement TLS.
Few do. S/MIME is end to end.  SBCs clearly break that.  There is
tension between end users that want security and network operators
that want to protect the network against theft of service, etc.
It should be possible to find a standards-based way to do that,
and I'm hopeful that the discussion Jonathan started will.

The discussion about packet marking/remarking was an example of 
something other than perimeter defense which is not currently
addressed by standards.  If there was, SBCs would not need
to rewrite SDP to force media to go through it.

The categories may be helpful, but there are many ways to
cut the pie.  Call Admission control is a QoS thing, for
example.   Routing is a perimeter defense; all customer proxies
route all calls to the network to the SBC.  It does the
route beyond.  If the SBC wasn't there, the customer would
have to do it.  Et cetera. 

Brian


> -----Original Message-----
> From: Pete Cordell [mailto:pete@tech-know-ware.com]
> Sent: Monday, October 18, 2004 4:53 AM
> To: Brian Rosen; jdrosen@dynamicsoft.com; sipping@ietf.org
> Subject: Re: [Sipping] What problems are SBCs addressing?
> 
> The apparent incompatibility between proxy based perimeter defence and
> things like TLS (e.g. end-to-end encryption/authentication) is something I
> want to emphasis.  (Most firewall functions are currently located at the
> network perimeter.  There are motions to make all hosts in an enterprise
> act
> as their own firewall, but it may be a while before this is widely trusted
> and accepted.)  Even on HTTP, TLS isn't particularly firewall friendly as
> it
> doesn't allow inspection (hence abuse of port 443).
> 
> So my point is, perimeter defence and end-to-end encryption/authentication
> are both important security issues.  We need to avoid developing one
> facility at the expense of the other.
> 
> BTW - I've taken the liberty of re-ordering Brian's list into (rough)
> categories:-
> 
> Perimeter defence type things:
> -----------------------
> 2. Firewall
> 3. DoS attack mitigation
> 5. Service provider infrastructure hiding
> 7. Legal Intercept (pjc - maybe a thing on its own e.g. regulatory.)
> 
> QoS type things:
> -----------------
> 4. SLA enforcement/measurement/facilitation
> 7. Packet marking and remarking
> 9. Bandwidth management/policing
> 
> Addressing IP deployment issues type things:
> -----------------------------
> 1. NAT traversal (and actual NAT functions)
> 
> 'Regular' SIP proxy type things:
> --------------------------------
> 6. Routing services (pjc - I assume this is SIP routing)
> 10. Call admission control
> 11. CDR creation and other billing functions
> 12. Protocol "repair"
> 
> Misc!:
> ---------
> 8. Protocol interwork (pjc - really a GW function?)
> 
> Of these categories, the first two are the ones I feel are not addressed
> by
> other SIP pieces.  With regard to NAT, there are other ways to do NAT
> traversal.  However, if you are required to have a DMZ proxy then having
> it
> do NAT traversal as well may be conceptually easier than other solutions.
> 
> Pete.
> --
> =============================================
> Pete Cordell
> Tech-Know-Ware
> http://www.tech-know-ware.com
> For LMX XML to C++ binding see http://www.xml2cpp.com
> =============================================
> 
> ----- Original Message -----
> From: "Brian Rosen" <br@brianrosen.net>
> To: "'Ram Dantu'" <RDANTU@egw.unt.edu>; <jdrosen@dynamicsoft.com>;
> <sipping@ietf.org>
> Sent: Saturday, October 16, 2004 6:54 PM
> Subject: RE: [Sipping] What problems are SBCs addressing?
> 
> 
> > The big one is that IETF specifications will REQUIRE TLS security for
> > emergency calls (1-1-2/9-1-1/...) because location is carried in the
> > signaling.  When I checked last, there were no SBCs which would maintain
> a
> > sips connection.  That may have changed, but it's an issue.
> >
> > There are a number of other issues with respect to emergency calls that
> will
> > require changes in SBCs, but with respect to security its maintaining
> TLS.
> >
> > Brian
> >
> > > -----Original Message-----
> > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf
> > > Of Ram Dantu
> > > Sent: Friday, October 15, 2004 6:00 PM
> > > To: jdrosen@dynamicsoft.com; sipping@ietf.org
> > > Subject: Re: [Sipping] What problems are SBCs addressing?
> > >
> > >
> > > We are having a workshop on this topic (VoIP Security).
> > > In particular, we would like to work on the issues what
> > > SBCs are not addressing. Let me know if you need
> > > further information
> > >
> > > http://www.globecom2004.org/images/W05_CFP.pdf
> > >
> > > Ram Dantu
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sip@ietf.org for new developments of core SIP
> > >
> >
> >
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> 




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


From sipping-bounces@ietf.org  Mon Oct 18 13:44: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 NAA05501
	for <sipping-web-archive@ietf.org>; Mon, 18 Oct 2004 13:44:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJbkf-0005OS-VW
	for sipping-web-archive@ietf.org; Mon, 18 Oct 2004 13:56:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJb27-00017E-Rh; Mon, 18 Oct 2004 13:10:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJaj0-0006EB-4d
	for sipping@megatron.ietf.org; Mon, 18 Oct 2004 12:51:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23690
	for <sipping@ietf.org>; Mon, 18 Oct 2004 10:58:28 -0400 (EDT)
Received: from cmailg3.svr.pol.co.uk ([195.92.195.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJZ9j-00025D-AE
	for sipping@ietf.org; Mon, 18 Oct 2004 11:10:55 -0400
Received: from user-5323.lns1-c7.dsl.pol.co.uk ([84.65.148.203] helo=RW)
	by cmailg3.svr.pol.co.uk with smtp (Exim 4.14)
	id 1CJYxJ-0005Fd-Im; Mon, 18 Oct 2004 15:57:49 +0100
Message-ID: <001001c4b522$d733aca0$c700a8c0@RW>
From: "Pete Cordell" <pete@tech-know-ware.com>
To: "Brian Rosen" <br@brianrosen.net>, <sipping@ietf.org>
References: <E1CJX7x-0007cZ-00@pluto.webfusion.co.uk>
Subject: Re: [Sipping] What problems are SBCs addressing?
Date: Mon, 18 Oct 2004 15:52:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
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: f2984bf50fb52a9e56055f779793d783
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: "Brian Rosen" <br@brianrosen.net>


> TLS is not end to end, it is hop by hop.  An SBC could implement
> sips and be able to inspect, but most don't.  That's not a standards
> problem; if they were 3261 compliant, they would implement TLS.
> Few do. S/MIME is end to end.  SBCs clearly break that.  There is
> tension between end users that want security and network operators
> that want to protect the network against theft of service, etc.
> It should be possible to find a standards-based way to do that,
> and I'm hopeful that the discussion Jonathan started will.

Ah, yes.  It's the end to end issues and the possible conflicts that I was
hoping to raise.

I assume by the term 'network operators' you mean carriers like AT+T, MCI
etc.  There may also be tensions between end users such as a cubicle
occupier who wants authenticated calls (or end-to-end encryption) in an
enterprise and the network administrator of the enterprise who doesn't want
to leave holes for malicious access (viruses, trojans, buffer overflows
etc).

> The discussion about packet marking/remarking was an example of
> something other than perimeter defense which is not currently
> addressed by standards.  If there was, SBCs would not need
> to rewrite SDP to force media to go through it.

Agreed, I lumped this under QoS.  (I'm assuming that by packet
marking/remarking this is with a view to prioritising traffic etc.)

> The categories may be helpful, but there are many ways to
> cut the pie.  Call Admission control is a QoS thing, for
> example.   Routing is a perimeter defense; all customer proxies
> route all calls to the network to the SBC.  It does the
> route beyond.  If the SBC wasn't there, the customer would
> have to do it.  Et cetera.

Agreed, there are many ways to cut the pie.  Re: the specific examples you
raise, I suppose I see the result of a call admission exercise as something
that may then kick off a QoS activity.  Having decided that QoS is needed it
then becomes an exercise in providing it.  I saw routing as a way of finding
where a person is at a particular time as 'routing as a service', whereas
routing to make data go through a control point as a means to an end that
was more to do with packet marking etc.

Maybe its best just to stay vague about the categories!

> Brian

Pete

> > -----Original Message-----
> > From: Pete Cordell [mailto:pete@tech-know-ware.com]
> > Sent: Monday, October 18, 2004 4:53 AM
> > To: Brian Rosen; jdrosen@dynamicsoft.com; sipping@ietf.org
> > Subject: Re: [Sipping] What problems are SBCs addressing?
> >
> > The apparent incompatibility between proxy based perimeter defence and
> > things like TLS (e.g. end-to-end encryption/authentication) is something
I
> > want to emphasis.  (Most firewall functions are currently located at the
> > network perimeter.  There are motions to make all hosts in an enterprise
> > act
> > as their own firewall, but it may be a while before this is widely
trusted
> > and accepted.)  Even on HTTP, TLS isn't particularly firewall friendly
as
> > it
> > doesn't allow inspection (hence abuse of port 443).
> >
> > So my point is, perimeter defence and end-to-end
encryption/authentication
> > are both important security issues.  We need to avoid developing one
> > facility at the expense of the other.
> >
> > BTW - I've taken the liberty of re-ordering Brian's list into (rough)
> > categories:-
> >
> > Perimeter defence type things:
> > -----------------------
> > 2. Firewall
> > 3. DoS attack mitigation
> > 5. Service provider infrastructure hiding
> > 7. Legal Intercept (pjc - maybe a thing on its own e.g. regulatory.)
> >
> > QoS type things:
> > -----------------
> > 4. SLA enforcement/measurement/facilitation
> > 7. Packet marking and remarking
> > 9. Bandwidth management/policing
> >
> > Addressing IP deployment issues type things:
> > -----------------------------
> > 1. NAT traversal (and actual NAT functions)
> >
> > 'Regular' SIP proxy type things:
> > --------------------------------
> > 6. Routing services (pjc - I assume this is SIP routing)
> > 10. Call admission control
> > 11. CDR creation and other billing functions
> > 12. Protocol "repair"
> >
> > Misc!:
> > ---------
> > 8. Protocol interwork (pjc - really a GW function?)
> >
> > Of these categories, the first two are the ones I feel are not addressed
> > by
> > other SIP pieces.  With regard to NAT, there are other ways to do NAT
> > traversal.  However, if you are required to have a DMZ proxy then having
> > it
> > do NAT traversal as well may be conceptually easier than other
solutions.
> >
> > Pete.
> > --
> > =============================================
> > Pete Cordell
> > Tech-Know-Ware
> > http://www.tech-know-ware.com
> > For LMX XML to C++ binding see http://www.xml2cpp.com
> > =============================================
> >
> > ----- Original Message -----
> > From: "Brian Rosen" <br@brianrosen.net>
> > To: "'Ram Dantu'" <RDANTU@egw.unt.edu>; <jdrosen@dynamicsoft.com>;
> > <sipping@ietf.org>
> > Sent: Saturday, October 16, 2004 6:54 PM
> > Subject: RE: [Sipping] What problems are SBCs addressing?
> >
> >
> > > The big one is that IETF specifications will REQUIRE TLS security for
> > > emergency calls (1-1-2/9-1-1/...) because location is carried in the
> > > signaling.  When I checked last, there were no SBCs which would
maintain
> > a
> > > sips connection.  That may have changed, but it's an issue.
> > >
> > > There are a number of other issues with respect to emergency calls
that
> > will
> > > require changes in SBCs, but with respect to security its maintaining
> > TLS.
> > >
> > > Brian
> > >
> > > > -----Original Message-----
> > > > From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> > Behalf
> > > > Of Ram Dantu
> > > > Sent: Friday, October 15, 2004 6:00 PM
> > > > To: jdrosen@dynamicsoft.com; sipping@ietf.org
> > > > Subject: Re: [Sipping] What problems are SBCs addressing?
> > > >
> > > >
> > > > We are having a workshop on this topic (VoIP Security).
> > > > In particular, we would like to work on the issues what
> > > > SBCs are not addressing. Let me know if you need
> > > > further information
> > > >
> > > > http://www.globecom2004.org/images/W05_CFP.pdf
> > > >
> > > > Ram Dantu
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the 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 Oct 19 01:19: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 BAA03526
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 01:19:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJmbn-0003eB-3j
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 01:32:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJm5d-0001AV-DV; Tue, 19 Oct 2004 00:59:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJlmj-0006Lp-Qj
	for sipping@megatron.ietf.org; Tue, 19 Oct 2004 00:39:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29963
	for <sipping@ietf.org>; Tue, 19 Oct 2004 00:39:37 -0400 (EDT)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJlyl-0002mw-2P
	for sipping@ietf.org; Tue, 19 Oct 2004 00:52:13 -0400
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	i9J4dbfM010787
	for <sipping@ietf.org>; Tue, 19 Oct 2004 06:39:37 +0200 (MEST)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	Tue, 19 Oct 2004 06:39:36 +0200
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id 4KCBSJ6X; Tue, 19 Oct 2004 06:39:36 +0200
Received: from ericsson.com (E-D56E4F79CD634.lmf.ericsson.se [131.160.37.124])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id D89D018AA9; Tue, 19 Oct 2004 07:39:35 +0300 (EEST)
Message-ID: <41749A87.1060606@ericsson.com>
Date: Tue, 19 Oct 2004 07:39:35 +0300
X-Sybari-Trust: d4ba9246 8cefd49f 593dc5fb 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Oct 2004 04:39:36.0698 (UTC)
	FILETIME=[A341F5A0:01C4B595]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: tachimoto.shinya@lab.ntt.co.jp, Rohan Mahy <rohan@ekabal.com>,
        Kumiko Ono <Ono.Kumiko@lab.ntt.co.jp>,
        Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] WGLC: e2m security requirements
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

Folks,

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

http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-reqs-04.txt

This WGLC will finish on November 20th. Please, send you comments to the 
authors and to the list.

Thanks,

Gonzalo


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


From sipping-bounces@ietf.org  Tue Oct 19 01:42: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 BAA05224
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 01:42:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CJmxq-00047j-5Q
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 01:55:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJmhE-0007y0-1T; Tue, 19 Oct 2004 01:38:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJmNT-0004LC-LB
	for sipping@megatron.ietf.org; Tue, 19 Oct 2004 01:17:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03462
	for <sipping@ietf.org>; Tue, 19 Oct 2004 01:17:37 -0400 (EDT)
Received: from filter1.kt.co.kr ([147.6.42.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJmZV-0003bk-VC
	for sipping@ietf.org; Tue, 19 Oct 2004 01:30:11 -0400
Received: from external ([147.6.9.113]) by filter1 (1.0) id i9J5GmE00B26;
	Tue, 19 Oct 2004 14:16:48 +0900
X-SMF-UNIQ33B8657C0E4123ECDBACEB8E52847943: i9J5GmE00B26
Message-ID: <00be01c4b59a$eaba85a0$71090693@ROMEO>
From: =?utf-8?B?7Zmp7KeE6rK9?= <jkhwang@kt.co.kr>
To: <sipping@ietf.org>
Subject: Re: [SIPPING] automatic answer
Date: Tue, 19 Oct 2004 14:17:23 +0900
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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="===============1511419219=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6

This is a multi-part message in MIME format.

--===============1511419219==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00BB_01C4B5E6.5A86B660"

This is a multi-part message in MIME format.

------=_NextPart_000_00BB_01C4B5E6.5A86B660
Content-Type: text/plain;
 charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBGb2xrcywNCg0KDQpJIGhhdmUgbm90IGZvdW5kIG91dCB0aGUgcmVsYXRlZCBJLUQgb3Ig
UkZDIHJlZ2FyZGluZyAiYXV0b21hdGljIGFuc3dlciBmZWF0dXJlIiBmb3IgU0lQIHBob25lLg0K
DQpUbyBpbXBsZW1lbnQgaW4gdGhlIFNJUCBwaG9uZSwgaXMgaXQgcmVhc29uYWJsZSB0byB1c2Ug
Q2FsbC1JbmZvIGZpZWxkID8NCg0KDQpBbnkgcmVwb25zZSB3b3VsZCBiZSBhcHByZWNpYXRlZC4N
Cg0KDQpKaW5reXVuZyBId2FuZw0KS1QNCg0KICAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0t
IA0KICBGcm9tOiDtmansp4Tqsr0gDQogIFRvOiBzaXBwaW5nQGlldGYub3JnIA0KICBTZW50OiBT
YXR1cmRheSwgT2N0b2JlciAwOSwgMjAwNCAxMjowMSBQTQ0KICBTdWJqZWN0OiBhdXRvbWF0aWMg
YW5zd2VyDQoNCg0KICBIaSwgDQoNCiAgSXMgdGhlcmUgYW55IEktRCByZWdhcmRpbmcgcGFyYW1z
IGZvciBTSVAgcGhvbmUgdG8gYW5zd2VyIGF1dG9tYXRpY2FsbHkgPyAoZm9yIGFuc3dlcmluZyBt
YWNoaW5lIGZ1bmN0aW9uYWxpdHkpDQoNCiAgSSB3b3VsZCBsaWtlIHRvIGtub3cgd2hlbiB0aGUg
Y2FsbCBhcnJpdmVzIGEgcGhvbmUsIGJ5IHdoaWNoIHBhcmFtL2hlYWRlciB2YWx1ZSB0aGUgcGhv
bmUgYW5zd2VycyB3aXRob3V0IHJpbmdpbmcuDQoNCg0KDQogIEFueSByZXBvbnNlIHdvdWxkIGJl
IGFwcHJlY2lhdGVkLg0KDQoNCiAgSmlua3l1bmcgSHdhbmcNCiAgS1Q=

------=_NextPart_000_00BB_01C4B5E6.5A86B660
Content-Type: text/html;
 charset="utf-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT48L1RJVExFPg0KPE1FVEEgaHR0cC1lcXVpdj1D
b250ZW50LVR5cGUgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIGNv
bnRlbnQ9Ik1TSFRNTCA2LjAwLjI4MDAuMTQ1OCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9T
VFlMRT4NCjwvSEVBRD4NCjxCT0RZIHRleHQ9IzAwMDAwMCBiZ0NvbG9yPSNmZmZmZmY+DQo8RElW
PjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPkRlYXIgRm9sa3MsPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6
ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAw
MDA4MCBzaXplPTI+SSBoYXZlIG5vdCBmb3VuZCBvdXQgdGhlIHJlbGF0ZWQgSS1EIG9yIA0KUkZD
IHJlZ2FyZGluZyAiYXV0b21hdGljIGFuc3dlciBmZWF0dXJlIiBmb3IgU0lQIHBob25lLjwvRk9O
VD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNp
emU9Mj5UbyBpbXBsZW1lbnQgaW4gdGhlIFNJUCBwaG9uZSwgaXMgaXQgDQpyZWFzb25hYmxlIHRv
IHVzZSBDYWxsLUluZm8gZmllbGQgPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3qtbTr
prwgY29sb3I9IzAwMDA4MCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBm
YWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPkFueSByZXBvbnNlIHdvdWxk
IGJlIA0KYXBwcmVjaWF0ZWQuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBj
b2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9
6rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZP
TlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+Smlua3l1bmcgSHdhbmc8L0ZPTlQ+
PC9ESVY+DQo8RElWPjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPktUPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48
L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8QkxPQ0tRVU9URSBkaXI9bHRyIA0Kc3R5bGU9IlBBRERJTkct
UklHSFQ6IDBweDsgUEFERElORy1MRUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7IEJPUkRFUi1M
RUZUOiAjMDAwMDgwIDJweCBzb2xpZDsgTUFSR0lOLVJJR0hUOiAwcHgiPg0KICA8RElWIHN0eWxl
PSJGT05UOiAxMHB0IOq1tOumvCI+LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSA8L0RJVj4N
CiAgPERJViANCiAgc3R5bGU9IkJBQ0tHUk9VTkQ6ICNlNGU0ZTQ7IEZPTlQ6IDEwcHQg6rW066a8
OyBmb250LWNvbG9yOiBibGFjayI+PEI+RnJvbTo8L0I+IDxBIA0KICB0aXRsZT1qa2h3YW5nQGt0
LmNvLmtyIGhyZWY9Im1haWx0bzpqa2h3YW5nQGt0LmNvLmtyIj7tmansp4Tqsr08L0E+IDwvRElW
Pg0KICA8RElWIHN0eWxlPSJGT05UOiAxMHB0IOq1tOumvCI+PEI+VG86PC9CPiA8QSB0aXRsZT1z
aXBwaW5nQGlldGYub3JnIA0KICBocmVmPSJtYWlsdG86c2lwcGluZ0BpZXRmLm9yZyI+c2lwcGlu
Z0BpZXRmLm9yZzwvQT4gPC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDEwcHQg6rW066a8Ij48
Qj5TZW50OjwvQj4gU2F0dXJkYXksIE9jdG9iZXIgMDksIDIwMDQgMTI6MDEgDQogIFBNPC9ESVY+
DQogIDxESVYgc3R5bGU9IkZPTlQ6IDEwcHQg6rW066a8Ij48Qj5TdWJqZWN0OjwvQj4gYXV0b21h
dGljIGFuc3dlcjwvRElWPg0KICA8RElWPjxCUj48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPeq1
tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj5IaSwgPC9GT05UPjwvRElWPg0KICA8RElWPjxGT05U
IGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCiAg
PERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj5JcyB0aGVyZSBhbnkg
SS1EIHJlZ2FyZGluZyBwYXJhbXMgZm9yIA0KICBTSVAgcGhvbmUgdG8gYW5zd2VyIGF1dG9tYXRp
Y2FsbHkgPyAoZm9yIGFuc3dlcmluZyBtYWNoaW5lIA0KICBmdW5jdGlvbmFsaXR5KTwvRk9OVD48
L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBz
aXplPTI+SSB3b3VsZCBsaWtlIHRvIGtub3cgd2hlbiB0aGUgY2FsbCANCiAgYXJyaXZlcyBhIHBo
b25lLCBieSB3aGljaCBwYXJhbS9oZWFkZXIgdmFsdWUgdGhlIHBob25lIGFuc3dlcnMgd2l0aG91
dCANCiAgcmluZ2luZy48L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29s
b3I9IzAwMDA4MCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9
6rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCiAgPERJVj48
Rk9OVCBmYWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQogIDxESVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+QW55IHJlcG9u
c2Ugd291bGQgYmUgDQogIGFwcHJlY2lhdGVkLjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBm
YWNlPeq1tOumvCBjb2xvcj0jMDAwMDgwIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQogIDxE
SVY+PEZPTlQgZmFjZT3qtbTrprwgY29sb3I9IzAwMDA4MCBzaXplPTI+PC9GT05UPiZuYnNwOzwv
RElWPg0KICA8RElWPjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMwMDAwODAgc2l6ZT0yPkppbmt5
dW5nIEh3YW5nPC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U96rW066a8IGNvbG9yPSMw
MDAwODAgDQpzaXplPTI+S1Q8L0ZPTlQ+PC9ESVY+PC9CTE9DS1FVT1RFPjwvQk9EWT48L0hUTUw+
DQo=

------=_NextPart_000_00BB_01C4B5E6.5A86B660--



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




From sipping-bounces@ietf.org  Tue Oct 19 18:24: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 SAA22654
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 18:24:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK2b1-0004vI-0b
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 18:36:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsmw-00078p-MN; Tue, 19 Oct 2004 08:08:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsV3-0003zy-Ss; Tue, 19 Oct 2004 07:49:57 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14611;
	Tue, 19 Oct 2004 07:49:56 -0400 (EDT)
Message-Id: <200410191149.HAA14611@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:49:56 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-kpml-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: 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-05.txt
	Pages		: 54
	Date		: 2004-10-18
	
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-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-kpml-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-kpml-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-10-18173235.I-D@ietf.org>

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 19 18:27:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22902
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 18:27:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK2ej-000500-3z
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 18:40:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsmz-00079X-EL; Tue, 19 Oct 2004 08:08:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsVA-000419-Tv; Tue, 19 Oct 2004 07:50:04 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14623;
	Tue, 19 Oct 2004 07:50:03 -0400 (EDT)
Message-Id: <200410191150.HAA14623@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:50:03 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-list-conferencing-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.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-01.txt
	Pages		: 9
	Date		: 2004-10-18
	
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-01.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-01.txt".

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


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

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

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

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

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

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 19 18:50:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25212
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 18:50:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK30b-0005he-Sp
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 19:03:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsn2-0007AE-Qw; Tue, 19 Oct 2004 08:08:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsVF-00041K-4x; Tue, 19 Oct 2004 07:50:09 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14630;
	Tue, 19 Oct 2004 07:50:07 -0400 (EDT)
Message-Id: <200410191150.HAA14630@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:50:07 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-list-message-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.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--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-01.txt
	Pages		: 18
	Date		: 2004-10-18
	
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 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-01.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-01.txt".

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


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

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

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

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

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

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 19 19: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 TAA26791
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 19:01:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK3Bj-00067E-Ii
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 19:14:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsn5-0007B0-Hz; Tue, 19 Oct 2004 08:08:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsVJ-00041X-K1; Tue, 19 Oct 2004 07:50:13 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14638;
	Tue, 19 Oct 2004 07:50:12 -0400 (EDT)
Message-Id: <200410191150.HAA14638@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:50:12 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-multiple-refer-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.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		: Refering to Multiple Resources in the Session 
			  Initiation Protocol (SIP)
	Author(s)	: G. Camarillo, et al.
	Filename	: draft-ietf-sipping-multiple-refer-01.txt
	Pages		: 12
	Date		: 2004-10-18
	
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 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-01.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-01.txt".

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


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

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

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

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

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

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 19 19:13: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 TAA28602
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 19:13:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK3MU-0006a5-B1
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 19:25:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsn8-0007BZ-8G; Tue, 19 Oct 2004 08:08:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsVO-00041r-7G; Tue, 19 Oct 2004 07:50:18 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14645;
	Tue, 19 Oct 2004 07:50:16 -0400 (EDT)
Message-Id: <200410191150.HAA14645@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:50:16 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-services-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.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		: 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-01.txt
	Pages		: 11
	Date		: 2004-10-18
	
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-01.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-01.txt".

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


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

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

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

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

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

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

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 19 19:21:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00118
	for <sipping-web-archive@ietf.org>; Tue, 19 Oct 2004 19:21:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CK3Uz-00071Z-5G
	for sipping-web-archive@ietf.org; Tue, 19 Oct 2004 19:34:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsnA-0007C4-U9; Tue, 19 Oct 2004 08:08:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CJsVS-000428-7i; Tue, 19 Oct 2004 07:50:22 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14652;
	Tue, 19 Oct 2004 07:50:20 -0400 (EDT)
Message-Id: <200410191150.HAA14652@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 19 Oct 2004 07:50:20 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-uri-list-subscribe-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.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		: Subscriptions to Request-Contained Resource Lists in 
			  the Session Initiation Protocol (SIP)
	Author(s)	: G. Camarillo, et al.
	Filename	: draft-ietf-sipping-uri-list-subscribe-01.txt
	Pages		: 9
	Date		: 2004-10-18
	
This document specifies a way to create subscription to a list of
   resources in SIP.  This is achieved by including the list of
   resources in the body of a SUBSCRIBE.  Instead of having a subscriber
   send a SUBSCRIBE for each resource individually, the subscriber
   defines the resource list, subscribes to it, and gets notifications
   about changes in the resources' state using a single SUBSCRIBE
   dialog.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-uri-list-subscribe-01.txt

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

Content-Type: text/plain
Content-ID: <2004-10-18173306.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  Wed Oct 20 22:27:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12973
	for <sipping-web-archive@ietf.org>; Wed, 20 Oct 2004 22:27:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKSsS-0002To-Uu
	for sipping-web-archive@ietf.org; Wed, 20 Oct 2004 22:40:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKITu-0008Rn-WE; Wed, 20 Oct 2004 11:34:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKHns-0002IM-G9; Wed, 20 Oct 2004 10:51:04 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11645;
	Wed, 20 Oct 2004 10:51:01 -0400 (EDT)
Message-Id: <200410201451.KAA11645@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, 20 Oct 2004 10:51:01 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D
	ACTION:draft-ietf-sipping-conferencing-framework-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Framework for Conferencing with the Session Initiation Protocol
	Author(s)	: J. Rosenberg
	Filename	: draft-ietf-sipping-conferencing-framework-03.txt
	Pages		: 36
	Date		: 2004-10-19
	
The Session Initiation Protocol (SIP) supports the initiation,
modification, and termination of media sessions between user agents.
These sessions are managed by SIP dialogs, which represent a SIP
relationship between a pair of user agents. Because dialogs are
between pairs of user agents, SIP's usage for two-party
communications (such as a phone call), is obvious. Communications
sessions with multiple participants, generally known as conferencing,
are more complicated. This document defines a framework for how such
conferencing can occur. This framework describes the overall
architecture, terminology, and protocol components needed for multi-
party conferencing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-framework-03.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-conferencing-framework-03.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-conferencing-framework-03.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-10-20105503.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-conferencing-framework-03.txt

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

Content-Type: text/plain
Content-ID: <2004-10-20105503.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  Wed Oct 20 22:33: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 WAA13899
	for <sipping-web-archive@ietf.org>; Wed, 20 Oct 2004 22:33:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKSy3-0002lC-Hn
	for sipping-web-archive@ietf.org; Wed, 20 Oct 2004 22:46:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKITz-0008WJ-OJ; Wed, 20 Oct 2004 11:34:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKHoH-0002LZ-HU; Wed, 20 Oct 2004 10:51:30 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11660;
	Wed, 20 Oct 2004 10:51:27 -0400 (EDT)
Message-Id: <200410201451.KAA11660@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, 20 Oct 2004 10:51:26 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-consent-framework-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Framework for Consent-Based Communications in the 
			  Session Initiation Protocol (SIP)
	Author(s)	: J. Rosenberg, et al.
	Filename	: draft-ietf-sipping-consent-framework-00.txt
	Pages		: 16
	Date		: 2004-10-19
	
The Session Initiation Protocol (SIP) supports communications across
   many media types, including real-time audio, video, text, instant
   messaging, and presence.  In its current form, it allows session
   invitations, instant messages, and other requests to be delivered
   from one party to another without requiring explicit consent of the
   recipient.  Without such consent, it is possible for SIP to be used
   for malicious purposes, including spam and denial-of-service attacks.
   This document identifies a framework for consent-based communications
   in SIP.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-consent-framework-00.txt

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

Content-Type: text/plain
Content-ID: <2004-10-20105510.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  Wed Oct 20 22:39: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 WAA14614
	for <sipping-web-archive@ietf.org>; Wed, 20 Oct 2004 22:39:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKT3Y-0002zw-9L
	for sipping-web-archive@ietf.org; Wed, 20 Oct 2004 22:52:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKIU2-00005b-R2; Wed, 20 Oct 2004 11:34:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKHoQ-0002N2-Fu; Wed, 20 Oct 2004 10:51:38 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11667;
	Wed, 20 Oct 2004 10:51:35 -0400 (EDT)
Message-Id: <200410201451.KAA11667@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, 20 Oct 2004 10:51:35 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-certs-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.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		: Certificate Management Service for SIP
	Author(s)	: C. Jennings, J. Peterson
	Filename	: draft-ietf-sipping-certs-00.txt
	Pages		: 18
	Date		: 2004-10-19
	
This draft defines a Credential Service that uses a SIP subscribe/
   notify mechanism to discover other users' certificates and
   credentials and be notified about changes to these certificates.
   Other user agents that want to contact that AOR can retrieve these
   certificates from the server.  The result is that widespread
   deployment of S/MIME in SIP is possible, because no extra expense or
   effort is required of the end user.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-certs-00.txt

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

Content-Type: text/plain
Content-ID: <2004-10-20105519.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  Wed Oct 20 22:46: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 WAA15703
	for <sipping-web-archive@ietf.org>; Wed, 20 Oct 2004 22:46:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKTAr-0003Jo-PG
	for sipping-web-archive@ietf.org; Wed, 20 Oct 2004 22:59:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKIU5-00005y-Nv; Wed, 20 Oct 2004 11:34:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKHow-0002RG-2e; Wed, 20 Oct 2004 10:52:10 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11699;
	Wed, 20 Oct 2004 10:52:07 -0400 (EDT)
Message-Id: <200410201452.KAA11699@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, 20 Oct 2004 10:52:07 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-consent-reqs-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Requirements for Consent-Based Communications in the 
			  Session Initiation Protocol (SIP)
	Author(s)	: J. Rosenberg, et al.
	Filename	: draft-ietf-sipping-consent-reqs-00.txt
	Pages		: 9
	Date		: 2004-10-19
	
The Session Initiation Protocol (SIP) supports communications across
   many media types, including real-time audio, video, text, instant
   messaging, and presence.  In its current form, it allows session
   invitations, instant messages, and other requests to be delivered
   from one party to another without requiring explicit consent of the
   recipient.  Without such consent, it is possible for SIP to be used
   for malicious purposes, including spam and denial-of-service attacks.
   This document identifies a set of requirements for extensions to SIP
   that add consent-based communications.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-consent-reqs-00.txt

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

Content-Type: text/plain
Content-ID: <2004-10-20105529.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 Oct 21 08:32: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 IAA15748
	for <sipping-web-archive@ietf.org>; Thu, 21 Oct 2004 08:32:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKcJZ-000863-OX
	for sipping-web-archive@ietf.org; Thu, 21 Oct 2004 08:45:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKb7d-0000uw-05; Thu, 21 Oct 2004 07:28:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKSsj-0007sW-O9
	for sipping@megatron.ietf.org; Wed, 20 Oct 2004 22:40:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15058
	for <sipping@ietf.org>; Wed, 20 Oct 2004 22:40:47 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKT5G-00035n-JR
	for sipping@ietf.org; Wed, 20 Oct 2004 22:53:47 -0400
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com
	[63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i9L2ecdj012466
	for <sipping@ietf.org>; Wed, 20 Oct 2004 22:40:39 -0400 (EDT)
Message-ID: <41772189.3010304@dynamicsoft.com>
Date: Wed, 20 Oct 2004 22:40:09 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping@ietf.org
References: <200410201451.KAA11645@ietf.org>
In-Reply-To: <200410201451.KAA11645@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: I-D
	ACTION:draft-ietf-sipping-conferencing-framework-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Content-Transfer-Encoding: 7bit

This draft is the result of efforts to remove nearly all of the non-sip 
aspects of conferencing from the framework, and move those to the newly 
published xcon framework document:

http://www.ietf.org/internet-drafts/draft-barnes-xcon-framework-00.txt

As a result of this, any open issues have evaporated and moved into the 
xcon area.

Thanks,
Jonathan R.

Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.
> 
> 	Title		: A Framework for Conferencing with the Session Initiation Protocol
> 	Author(s)	: J. Rosenberg
> 	Filename	: draft-ietf-sipping-conferencing-framework-03.txt
> 	Pages		: 36
> 	Date		: 2004-10-19
> 	
> The Session Initiation Protocol (SIP) supports the initiation,
> modification, and termination of media sessions between user agents.
> These sessions are managed by SIP dialogs, which represent a SIP
> relationship between a pair of user agents. Because dialogs are
> between pairs of user agents, SIP's usage for two-party
> communications (such as a phone call), is obvious. Communications
> sessions with multiple participants, generally known as conferencing,
> are more complicated. This document defines a framework for how such
> conferencing can occur. This framework describes the overall
> architecture, terminology, and protocol components needed for multi-
> party conferencing.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-conferencing-framework-03.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-conferencing-framework-03.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-conferencing-framework-03.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.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@dynamicsoft.com                        FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From sipping-bounces@ietf.org  Thu Oct 21 08:58:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21645
	for <sipping-web-archive@ietf.org>; Thu, 21 Oct 2004 08:58:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKcjC-00015t-Be
	for sipping-web-archive@ietf.org; Thu, 21 Oct 2004 09:11:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKbOH-0004x5-PL; Thu, 21 Oct 2004 07:45:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKZzb-0006Cw-Vm
	for sipping@megatron.ietf.org; Thu, 21 Oct 2004 06:16:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25877
	for <sipping@ietf.org>; Thu, 21 Oct 2004 06:16:16 -0400 (EDT)
Received: from eastmail3.ntt-east.co.jp ([202.229.5.46]
	helo=evx3.enoc.east.ntt.co.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKaC5-0002Yd-Db
	for sipping@ietf.org; Thu, 21 Oct 2004 06:29:20 -0400
Received: from emix1.enoc.east.ntt.co.jp 
	by evx3.enoc.east.ntt.co.jp with ESMTP id i9LAFcp00042;
	Thu, 21 Oct 2004 19:15:38 +0900 (JST)
Received: from cip4.noc.east.ntt.co.jp 
	by emix1.enoc.east.ntt.co.jp with ESMTP id i9LAFcj13929;
	Thu, 21 Oct 2004 19:15:38 +0900 (JST)
Received: from [10.8.52.30] ([10.8.52.30])
	by cip4.noc.east.ntt.co.jp (MOS 3.4.6-GR) with ESMTP id AVT00032;
	Thu, 21 Oct 2004 19:15:38 +0900 (JST)
Date: Thu, 21 Oct 2004 19:15:41 +0900
From: "Jun KOSHIKO(Office)" <j.koshiko@rdc.east.ntt.co.jp>
To: sipping@ietf.org
Message-Id: <20041021191240.A5ED.J.KOSHIKO@rdc.east.ntt.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.11.02 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Subject: [Sipping] New draft on Reason-Header extension
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

Folks,

I would like to bring the attention of the group to a new internet
draft on Reason-Header extension to indicate locations.
The draft can be found at
http://www13.plala.or.jp/jtomo/internet-drafts/draft-koshiko-sipping-reason-indicating-locations-00.txt

The draft will be submitted after Nov 7.
I'll appreciate any comments and thoughts.

Regards,
Jun KOSHIKO

---------------------------------------------------------
Jun KOSHIKO
Research and Development Center
NTT-east Corporation

Telephone  +81 3 5359 5104
Facsimile  +81 3 5359 4768
E-mail: j.koshiko@rdc.east.ntt.co.jp
19-2 Nishi-shinjuku 3-chome Shinjuku-ku Tokyo 163-8019 Japan
---------------------------------------------------------


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 21 12:38: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 MAA20827
	for <sipping-web-archive@ietf.org>; Thu, 21 Oct 2004 12:38:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKgAX-0007g5-Ci
	for sipping-web-archive@ietf.org; Thu, 21 Oct 2004 12:52:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKfkx-0000C5-20; Thu, 21 Oct 2004 12:25:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKfV5-0006bY-67
	for sipping@megatron.ietf.org; Thu, 21 Oct 2004 12:09:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17450
	for <sipping@ietf.org>; Thu, 21 Oct 2004 12:09:11 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKfhi-0006wy-AZ
	for sipping@ietf.org; Thu, 21 Oct 2004 12:22:18 -0400
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id i9LG8fv22244
	for <sipping@ietf.org>; Thu, 21 Oct 2004 12:08:41 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <V22JL4KF>; Thu, 21 Oct 2004 12:08:41 -0400
Message-ID: <7A3E36B3528ED04A880178D337F30C9A0150A3C5@zrc2hxm1.corp.nortel.com>
From: "Amy Pendleton" <aspen@nortelnetworks.com>
To: SIPPING WG list <sipping@ietf.org>
Subject: FW: [SIPPING] draft-johnston-sipping-rtcp-summary-04.txt
Date: Thu, 21 Oct 2004 12:08:32 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
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="===============0328987104=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8

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.

--===============0328987104==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4B788.36C45119"

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_01C4B788.36C45119
Content-Type: text/plain

An updated version of this draft is now available.  Many of the comments
received have hopefully been addressed by this new version.

> Title		: A Performance Report Event Package For SIP
> Author(s)   : A. Johnston, H. Sinnreich, A. Clark, A. Pendleton
> Filename    : draft-johnston-sipping-rtcp-summary-04.txt
> Pages       : 24
> Date        : 2004-10-14
> 
> This document discusses the motivation and requirements for the
> delivery of performance reports and other summary reports from VoIP
> applications in endpoints to non-participants in the session.  A
> publication mechanism using a new SIP events package is proposed as a
> solution.  An event package "perfrpt" and an application/perfrtp MIME
> type is defined in this document along with some example call flows.
> 
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-summary-04.t
xt
<http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-summary-04.
txt> 





------_=_NextPart_001_01C4B788.36C45119
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>FW: [SIPPING] draft-johnston-sipping-rtcp-summary-04.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Courier New">An updated version of this draft =
is now available.&nbsp; Many of the comments received have hopefully =
been addressed by this new version.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Title&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : A Performance Report Event =
Package For SIP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Author(s)&nbsp;&nbsp; : A. =
Johnston, H. Sinnreich, A. Clark, A. Pendleton</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Filename&nbsp;&nbsp;&nbsp; : =
draft-johnston-sipping-rtcp-summary-04.txt</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New">Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 24</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier =
New">Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2004-10-14</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">This document discusses the =
motivation and requirements for the</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">delivery of performance reports =
and other summary reports from VoIP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">applications in endpoints to =
non-participants in the session.&nbsp; A</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">publication mechanism using a =
new SIP events package is proposed as a</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">solution.&nbsp; An event =
package &quot;perfrpt&quot; and an application/perfrtp MIME</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">type is defined in this =
document along with some example call flows.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">A URL for this Internet-Draft =
is:</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS"></FONT> <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-=
summary-04.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.ietf.org/internet-drafts/draft-johnston-sipping-rtcp-sum=
mary-04.txt</FONT></U></A>
</P>
<BR>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4B788.36C45119--


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



From sipping-bounces@ietf.org  Thu Oct 21 20:32: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 UAA12872
	for <sipping-web-archive@ietf.org>; Thu, 21 Oct 2004 20:32:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CKnYO-0006MN-MX
	for sipping-web-archive@ietf.org; Thu, 21 Oct 2004 20:45:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKl88-0006nO-19; Thu, 21 Oct 2004 18:09:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKj8A-0003SK-7u; Thu, 21 Oct 2004 16:01:50 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14272;
	Thu, 21 Oct 2004 16:01:48 -0400 (EDT)
Message-Id: <200410212001.QAA14272@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, 21 Oct 2004 16:01:47 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-toip-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Framework of requirements for real-time text conversation using SIP.
	Author(s)	: A. Van Wijk
	Filename	: draft-ietf-sipping-toip-00.txt
	Pages		: 37
	Date		: 2004-10-20
	
This document provides the framework of requirements for text 
conversation with real time character-by-character interactive 
flow over the IP network using the Session Initiation Protocol. 
The requirements for general real-time text-over-IP telephony, 
point-to point and conference calls, transcoding, relay services, 
user mobility, interworking between text-over-IP telephony and 
existing text-telephony, and some special features including 
instant messaging have been described.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-toip-00.txt

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

Content-Type: text/plain
Content-ID: <2004-10-21154809.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 Oct 22 14:16:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26223
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 14:16:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL4AB-0003bA-58
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 14:29:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL3tf-0002Ci-DK; Fri, 22 Oct 2004 14:12:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL3nT-0000OM-Uw
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 14:05:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25425
	for <sipping@ietf.org>; Fri, 22 Oct 2004 14:05:48 -0400 (EDT)
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL40I-0003Pi-QU
	for sipping@ietf.org; Fri, 22 Oct 2004 14:19:07 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (sccrmhc13) with SMTP
	id <20041022180517016000m3q9e>; Fri, 22 Oct 2004 18:05:17 +0000
Message-ID: <41794BD6.5B81062B@pingtel.com>
Date: Fri, 22 Oct 2004 14:05:10 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] instance-ID for SIP UA
References: <E5880434292FCB448F00BDAEE44A60D009662C@EXC01C.cselt.it>
	<41503B43.4030602@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: 7bit
Cc: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit

Yes the main point is that the instance-ID is unique.  Just like the
call-id, the format is not important, uniqueness is.  I agree with
Pauls suggested approaches for generating instance-Ids.  It is also
desirable that the instance-id be persistant for the lifetime of the
user agent.  However as Paul points out some applications require
short user agent lifetimes.

I would add one other recommendation.  As instance-Ids are likely
to be used by adminstrators (e.g. to associate users, devices and profiles,
etc.). Instance-IDs that are easily recognised and replicated by
human beings will make the administrator's job easier.  The ability
to do things like use a bar code scanner on a hardphone to obtain its
MAC address or instance-Id makes life a little easier.  Implementors
of soft UAs will probably want to consider providing means of obtaining
the instance-id before and/or after install so that it can be provided 
out of band to the adminstrator.


Paul Kyzivat wrote:
> 
> Simonetti Gabrielle wrote:
> > In the "Framework for SIP User Agent Profile Delivery", the subscription URI for the "device" profile is based upon the identity of  the device, for the Profile Delivery Server to identify which "device" profile is associated with a specific instance of a User Agent.
> >
> > Let us consider the case of software UA running on multi-user computers where the MAC address is shared and cannot be used as unique identifier. The Framework suggests that in this case a URN be used as the user portion of the device URI, with a reference to the GRUU draft. Section 6 says:
> > "A GRUU is associated [...] with the combination of an AOR and instance ID. [...] The AOR identifies a resource, such as a user or service within a domain, and the instance ID identifies a specific UA instance servicing requests for that resource."
> >
> > My questions relate to the Instance-ID: to my understanding, in the case of the Profile Delivery Framework, the instance-ID itself may be used in the URI to retrieve the "device" profile, if it identifies a specific UA instance with a SIP URI.
> >
> >    First issue - What is the format of the instance-ID?
> > We would like a standardized instance-ID for all UA. Jennings draft suggests the format "RANID-" followed by a 16 digit representation of a random 64 bit number. Couldn't this number be associated with the local domain to obtain a unique URI identifying the UA instance to be used for the subscription to the "device" profile?
> 
> In the GRUU spec we tried not to be too specific about this - it is only
> important that there be a mechanism for comparing instance IDs and that
> each be unique. For this purpose it is sufficient that the id be a URN.
> 
> However, we did have in mind a particular form of URN as especially
> suitable: the UUID URN as defined in draft-mealling-uuid-urn-03. But we
> didn't want to reference it normatively because it would impose a
> dependency on the order in which they become RFCs.
> 
> >    Second issue - Who creates the instance-ID?
> > Should the UA create the instance-ID itself, by generating a random number and having its uniqueness checked by a local server? Or should the instance-ID be provided directly by a local server to the UA at registration to avoid unecessary messages running on the network (since in the case the instance-ID created by the UA is not unique, the server would have to provide the UA with a new one anyway)?
> 
> I don't think there is any single answer to this. The following are my
> personal opinions:
> 
> - a hardware device that contains only one instance (e.g. a phone)
>    should probably create the id itself from its mac address.
>    For this purpose it would be sufficient to use a timestamp of zero.
> 
> - for a software device on a multi-purpose system, where multiple
>    instances might exist, a new instance id should be created each
>    time a new instance is created.
>    . if each instance is created via some sort of installation
>      process, and has persistent state, then the id should be
>      created as part of the installation process and saved with
>      the state. (The installer that creates the instance could
>      run on the same machine or a different one.)
>    . if instances are created dynamically and have no persistent
>      state (e.g. via a "login") then the id needs to be created
>      each time an instance is created.
> 
> There are other cases, and other possible answers. There is no need for
> a uniform process as long as the result is a unique URN in each case.
> 
> >    Third issue - How should the UA obtain the instance-ID?
> 
> See above.
> 
> > It would be appropriate to use SIP to deliver the instance-ID to a UA, eg with the REGISTER method. Are there any other methods that should be considered to deliver the instance-ID?
> 
> I don't see how you can use SIP to deliver the id, since you would need
> to uniquely identify the recipient first. This is a chicken and egg problem.
> 
> >    Fourth issue - Storing the instance-ID
> > What if the UA "forgets" its instance-ID? Does it need to be delivered the same instance-ID as it had before, since the Profile Delivery Server keeps a correspondance between the device profile and a specific instance-ID? How should this problem be solved?
> 
> It depends on how it was created in the first place. If it was created
> from a mac address that is burned into the device, then it won't be
> forgotten unless the mac interface is replaced. If so, the device
> becomes a new device after that.
> 
> For soft devices that persistently store their id, you can use whatever
> mechanism you like to back it up and recover it. And if you can't do
> that you have to create a new one and start over.
> 
> Note that draft-mealling-uuid-urn-03 also has a "name based" way to
> generate a UUID. If you use that mechanism, and have some way to
> remember the name, then you can reconstruct the UUID from it.
> 
>         Paul
> 
> > Regards,
> >
> > Gabrielle Simonetti
> > Telecom Italia
> >
> >
> >
> >
> >
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> >
> > ====================================================================
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the persons
> > above and may contain confidential information. If you have received
> > the message in error, be informed that any use of the content hereof
> > is prohibited. Please return it immediately to the sender and delete
> > the message. Should you have any questions, please send an e_mail to
> > MailAdmin@tilab.com. Thank you
> > ====================================================================
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Fri Oct 22 14:37: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 OAA27819
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 14:37:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL4VL-00040N-76
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 14:51:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL4EZ-0008Mo-Fk; Fri, 22 Oct 2004 14:33:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL4A2-0006k8-Ky
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 14:29:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27009
	for <sipping@ietf.org>; Fri, 22 Oct 2004 14:29:07 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL4Mr-0003ow-S3
	for sipping@ietf.org; Fri, 22 Oct 2004 14:42:26 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (rwcrmhc12) with SMTP
	id <20041022182835014004ncb5e>; Fri, 22 Oct 2004 18:28:35 +0000
Message-ID: <4179514E.D928929E@pingtel.com>
Date: Fri, 22 Oct 2004 14:28:30 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping] instance-ID for SIP UA
References: <E5880434292FCB448F00BDAEE44A60D009663B@EXC01C.cselt.it>
	<41517EFC.3050303@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Cc: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit



Paul Kyzivat wrote:
> 
> Simonetti Gabrielle wrote:
> >
> >>>   First issue - What is the format of the instance-ID?
> >>>We would like a standardized instance-ID for all UA.
> >>
> >>Jennings draft suggests the format "RANID-" followed by a 16
> >>digit representation of a random 64 bit number. Couldn't this
> >>number be associated with the local domain to obtain a unique
> >>URI identifying the UA instance to be used for the
> >>subscription to the "device" profile?
> >>
> >>In the GRUU spec we tried not to be too specific about this -
> >>it is only
> >>important that there be a mechanism for comparing instance
> >>IDs and that
> >>each be unique. For this purpose it is sufficient that the id
> >>be a URN.
> >>
> >>However, we did have in mind a particular form of URN as especially
> >>suitable: the UUID URN as defined in
> >>draft-mealling-uuid-urn-03. But we
> >>didn't want to reference it normatively because it would impose a
> >>dependency on the order in which they become RFCs.
> >
> > The one thing that tickled me about using the GRUU to retrieve the device profile is that it involves an AOR. Yet the "device" profile is only concerned with the device itself and there is no user involved in the process at this point. So should the URN alone be used as the request URI and in the From/To Header fields? Or should it be escaped and associated to the local domain?
> 
> I don't think anyone is suggesting that you use the gruu to retrieve the
> device profile.
> 

Yes the GRUU should not be used as the subscription URI for configuration.  
The instance-id is escaped and used as the user-id portion when forming the 
URI for subscription as described in sections 3.13.1 and 4.1 of 
draft-ietf-sipping-config-framework-04.txt  Please let me know how
I can clarify these sections if they have caused your confusion
above on applying the instance-id.

> What is being suggested is that the gruu mechanism now uses an instance
> ID to identify the specific UA that is requesting the gruu, and that
> that same instance ID could be used to retrieve the "device" profile.
> 
> I believe the identity and uniqueness properties required by the two
> applications are the same, so the same id seems appropriate.
> 
>         Paul
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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


From sipping-bounces@ietf.org  Fri Oct 22 15:13: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 PAA00824
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 15:13:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL540-0004dD-82
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 15:27:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL4ow-0001z1-Cz; Fri, 22 Oct 2004 15:11:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL4nK-00010c-OU
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 15:09:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00286
	for <sipping@ietf.org>; Fri, 22 Oct 2004 15:09:43 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL50A-0004Ya-4P
	for sipping@ietf.org; Fri, 22 Oct 2004 15:23:02 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (rwcrmhc12) with SMTP
	id <20041022190911014004rae9e>; Fri, 22 Oct 2004 19:09:11 +0000
Message-ID: <41795AD2.57693EAB@pingtel.com>
Date: Fri, 22 Oct 2004 15:09:06 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: Re: [Sipping] Comments on config framework draft- URIs and
	eventpackage parameters
References: <E5880434292FCB448F00BDAEE44A60D009665A@EXC01C.cselt.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit


Simonetti Gabrielle wrote:

> 
> > Section 4.6
> > ------------
> >
> > - This sentence:
> >    "When the "profile-name" is application, but the "app-id" parameter
> > is absent, this specifies that the user wishes to SUBSCRIBE to all
> > documents for all application usages associated with the user in the
> > request-uri."
> >
> > contradicts with this one:
> >
> > "If the "profile-name" is "application", the "app-id" MUST be present as well."
> >
> > The latter says its a MUST, but the former said the "app-id"
> > missing is feature.
> 
> Actually, it is not specified in the framework which of the Event Header parameters are obligatory/optional/unnecessary in a subscription. For example, I would imagine that for the "device" profile subscription, the parameter "vendor" is obligatory, while the parameters "model" and  "version" are optional (the parameter "vendor" alone in a subscription would correspond to the profile relative to all devices from one same vendor). On the opposite, for the "application" profile subscription, the "app-id" parameter could be obligatory while "vendor", "model" and "version" are unnecessary.

Wow.  Thanks, I will fix that.  It was intended that vendor, model and version
were manditory for all the profiles.  Though it may not be necessary, it is
potentially useful to the profile delivery server to know these parameters
should it desire to customize the profile based upon the specific implementation.
In the perfect world they will all be have the same.  However we are in a
real world and I think that it is important to give the profile delivery server
the ability to customize the profiles.  If we do not make these mandatory,
implementors will not put them and the profile delivery server will be
running blind.

app-id is supposed to be optional for application profiles to specify a 
single application profile as opposed to all application profiles.  It
is ignored for non-application profile types.

similarly document is optional for all profile types to specify a 
specific document or element.



> 
> Regards,
> Gabrielle
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> ====================================================================
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 22 15:39: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 PAA03162
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 15:39:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL5TH-00054j-NH
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 15:53:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL5AV-0002oQ-Nw; Fri, 22 Oct 2004 15:33:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL55S-0007Vc-JD
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 15:28:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02494
	for <sipping@ietf.org>; Fri, 22 Oct 2004 15:28:26 -0400 (EDT)
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL5II-0004rW-5C
	for sipping@ietf.org; Fri, 22 Oct 2004 15:41:46 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (sccrmhc13) with SMTP
	id <20041022192753016000kj6le>; Fri, 22 Oct 2004 19:27:53 +0000
Message-ID: <41795F36.85ABD001@pingtel.com>
Date: Fri, 22 Oct 2004 15:27:50 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: Re: [Sipping] Comments on config framework draft- URIs and
	eventpackage parameters
References: <E5880434292FCB448F00BDAEE44A60D009665A@EXC01C.cselt.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit



Simonetti Gabrielle wrote:
> 
> > Section 3.13.1
> > --------------
> >
> > - What if instance does not matter? Example all Nokia phone
> > 6600 model require the same profile, instance does not
> > matter. Vendor and model is the only thing needed to download
> > a profile. There is no need for the service provider to have
> > separate profiles for every device, especially will they are
> > identical.
> 
> I agree that the instance-id might not matter in the case of the "device" profile. In fact using the instance-id creates unnecessary subscription targets, as these can be grouped by "model", for example, as you say.
> 1/What do you suggest for the format of the subscription URI then, leaving out the instance-id?
> 2/The question has already been raised whether "vendor", "model" and "version" are sufficient to identify the precise profile to be delivered, e.g. in the case where a particular UA model has different components, each with its own version number. A possible solution would be to define a new parameter "component" for the Event Header to identify the component for which the subscription is made.

The instance-id does matter in the device profile when you consider the
boot strapping of a new user agent.  Out of the box a new UA only knows 
its instance-id (or how to generate one).   It also knows how to use its
instance-id to form the URI to subscribe for the device profile.  The
device profile needs to contain the default user AOR so that the UA
can subsequently figure out what user profile to subscribe to.  Hense,
minimally all device profiles may differ by the value of the default
user AOR.

This is not the only deployment strategey, but it is certainly one
we want to support.  Other deployment strategies are also supported:

1) preprovisioned UAs which know their default user's AOR.

2) UA's which prompt the user for their AOR

Regardless, I think that we still want to make the instance-id
manditory as the user-id part of the device subscription URI.
The fact that the profile delivery server may deliver the exact
same profile to all devices of the same vendor, model and version
is an implementation choice.  Without the vendor, model, version
and instance-id the profile delivery server does not have a choice
to be smart or dumb.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 22 17:00: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 RAA15308
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 17:00:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL6jF-0000M4-Oy
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 17:13:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL5jl-0008Hl-6G; Fri, 22 Oct 2004 16:10:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL5gY-00067V-NC
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 16:06:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05794
	for <sipping@ietf.org>; Fri, 22 Oct 2004 16:06:46 -0400 (EDT)
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL5tN-0005kT-Oy
	for sipping@ietf.org; Fri, 22 Oct 2004 16:20:07 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (rwcrmhc13) with SMTP
	id <2004102220061401500mvrrpe>; Fri, 22 Oct 2004 20:06:14 +0000
Message-ID: <41796831.B9EB4FD2@pingtel.com>
Date: Fri, 22 Oct 2004 16:06:09 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Goix Walter <Walter.Goix@TILAB.COM>
Subject: Re: [Sipping] Comments on config framework draft- URIs
	andeventpackage parameters
References: <91C9464F6AFC0647A2D8069E25DBF4962FFB54@EXC01B.cselt.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit


Goix Walter wrote:
> 
> Inline
> 
> > > Section 3.13.1
> > > --------------
> > >
> > > - What if instance does not matter? Example all Nokia phone
> > > 6600 model require the same profile, instance does not
> > > matter. Vendor and model is the only thing needed to download
> > > a profile. There is no need for the service provider to have
> > > separate profiles for every device, especially will they are
> > > identical.
> >
> > I agree that the instance-id might not matter in the case of
> > the "device" profile. In fact using the instance-id creates
> > unnecessary subscription targets, as these can be grouped by
> > "model", for example, as you say.
> > 1/What do you suggest for the format of the subscription URI
> > then, leaving out the instance-id? 2/The question has already
> > been raised whether "vendor", "model" and "version" are
> > sufficient to identify the precise profile to be delivered,
> > e.g. in the case where a particular UA model has different
> > components, each with its own version number. A possible
> > solution would be to define a new parameter "component" for
> > the Event Header to identify the component for which the
> > subscription is made.
> 
> What about a URL pointing to a CC/PP XML profile to identify the device?
> Most of the times, such URLs already embed all "vendor", "model" and
> "version" information only looking at the HTTP address and without
> reading the actual XML content. Processing the content may provide
> further information for a device profile delivery server to identify the
> target of the subscription and apply its own rules to identify when that
> particular watcher/device should be notified.
> This would allow to remove (or put as optional) the fixed and limited
> set of parameters of the Event: header, and may also be reused in other
> subscriptions (local, user, app).
> 

I think that I would like to avoid introducing another set of
syntax from which to parse vendor, model and version.  I think
providing them as parameters is simpler.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 22 17:58:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26814
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 17:58:43 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL7dl-00047X-Ay
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 18:12:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL6gb-0007Kx-6z; Fri, 22 Oct 2004 17:10:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL5mW-0001rX-SB; Fri, 22 Oct 2004 16:13:00 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06577;
	Fri, 22 Oct 2004 16:12:56 -0400 (EDT)
Message-Id: <200410222012.QAA06577@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, 22 Oct 2004 16:12:56 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-cc-conferencing-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: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Session Initiation Protocol Call Control - Conferencing for User Agents
	Author(s)	: A. Johnston, O. Levin
	Filename	: draft-ietf-sipping-cc-conferencing-05.txt
	Pages		: 39
	Date		: 2004-10-22
	
This specification defines conferencing call control features for the
   Session Initiation Protocol (SIP).  This document builds on the
   Conferencing Requirements and Framework documents to define how a
   tightly coupled SIP conference works.  The approach is explored from
   different user agent (UA) types perspective: conference-unaware,
   conference-aware and focus UAs.  The use of URIs in conferencing,
   OPTIONS for capabilities discovery, and call control using REFER are
   covered in detail with example call flow diagrams.  The usage of the
   isfocus feature tag is defined.  A SIP option tag for
   conference-aware UAs is defined.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-cc-conferencing-05.txt

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

Content-Type: text/plain
Content-ID: <2004-10-22162054.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 Oct 22 18:00:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27274
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 18:00:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL7fZ-0004GW-T4
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 18:13:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL6gh-0007Pp-7f; Fri, 22 Oct 2004 17:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL5mv-00024J-Rg; Fri, 22 Oct 2004 16:13:25 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06677;
	Fri, 22 Oct 2004 16:13:21 -0400 (EDT)
Message-Id: <200410222013.QAA06677@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, 22 Oct 2004 16:13:21 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-cc-transfer-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
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		: Session Initiation Protocol Call Control - Transfer
	Author(s)	: R. Sparks, et al.
	Filename	: draft-ietf-sipping-cc-transfer-03.txt
	Pages		: 54
	Date		: 2004-10-22
	
This document describes providing Call Transfer capabilities in the
   Session Initiation Protocol (SIP).  SIP extensions such as REFER and
   Replaces are used to provide a number of transfer services including
   blind transfer, consultative transfer, and attended transfer.  This
   work is part of the SIP multiparty call control framework.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-transfer-03.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-cc-transfer-03.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-10-22162108.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-cc-transfer-03.txt

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

Content-Type: text/plain
Content-ID: <2004-10-22162108.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 Oct 22 18:14: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 SAA01225
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 18:14:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL7tH-0005Ny-02
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 18:28:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL6kw-0000j6-BF; Fri, 22 Oct 2004 17:15:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL61X-0003pt-VR
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 16:28:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08885
	for <sipping@ietf.org>; Fri, 22 Oct 2004 16:28:27 -0400 (EDT)
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL6EJ-0006ZB-Dy
	for sipping@ietf.org; Fri, 22 Oct 2004 16:41:47 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (rwcrmhc11) with SMTP
	id <20041022202748013009doqme>; Fri, 22 Oct 2004 20:27:48 +0000
Message-ID: <41796D40.FCE372DB@pingtel.com>
Date: Fri, 22 Oct 2004 16:27:44 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Goix Walter <Walter.Goix@TILAB.COM>
Subject: Re: [Sipping] Comments on config framework draft- URIs
	andeventpackage parameters
References: <91C9464F6AFC0647A2D8069E25DBF4962FFB54@EXC01B.cselt.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit


Goix Walter wrote:

> > > Section 3.13.3
> > > --------------
> > >
> > > - about placing an "anonymous" user name. Why isn't
> > > sip:example.com enough (no user part)? If user part is
> > > present, it MUST be ignored.
> >
> > The instance-id might be useful here in the user part of the
> > "local" profile URI, in the case where the default local
> > parameters delivered by the modem depend on the device.
> 
> I agree. If we think at local domains as "home" and "visited"-types of
> domains, a "home" domain server may recognize a specific instance of a
> device as belonging to its own domain and configure it differently from
> another device in "roaming".

I think the capabilities provided or allowed by the local network
are more closely associated with the user than the device.  That is 
purpose of the optional network-user event parameter. The user's
identity is provided in the form of their AOR so that the network
has the option of providing capabilties specific to the user.

See also:
http://www.ietf.org/mail-archive/web/sipping/current/msg06982.html

> 
> Laurent-Walter Goix
> Telecom Italia - TILAB
> Service and Platform Innovation - Service Control Platforms
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> ====================================================================
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 22 19:01: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 TAA09859
	for <sipping-web-archive@ietf.org>; Fri, 22 Oct 2004 19:01:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CL8c8-00080n-QL
	for sipping-web-archive@ietf.org; Fri, 22 Oct 2004 19:14:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL7qO-0007R1-JP; Fri, 22 Oct 2004 18:25:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7L2-0008MT-5w
	for sipping@megatron.ietf.org; Fri, 22 Oct 2004 17:52:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25963
	for <sipping@ietf.org>; Fri, 22 Oct 2004 17:52:39 -0400 (EDT)
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL7Xr-0003nB-LV
	for sipping@ietf.org; Fri, 22 Oct 2004 18:06:00 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (sccrmhc12) with SMTP
	id <2004102221520801200ftmo6e>; Fri, 22 Oct 2004 21:52:08 +0000
Message-ID: <41798101.7CC4628A@pingtel.com>
Date: Fri, 22 Oct 2004 17:52:01 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <50B1CBA96870A34799A506B2313F26670252D359@ntht201e>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: [Sipping] Re: Config framework - issue with parameters send in
	Event header
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: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Thanks for the comments.  I would like to hear opinions from
folks on the list on whether they think this is a current
requirement or not.

Thanks,
Dan

"Elwell, John" wrote:
> 
> Dan,
> 
> In reviewing the draft-ietf-sipping-config-framework-04, I noticed that
> several parameters had been defined for the Event header giving information
> about the device, i.e., "vendor", "model" and "version". I am concerned that
> these may not be sufficient in all cases for the profile delivery server to
> determine the precise profile to be delivered. Moreover, the profile
> delivery server may use these parameters to compile an inventory of devices
> for admin purposes, and more detailed information might be needed for this
> purpose, even if it does not influence the choice of profile to be
> delivered. Examples of extended information that might be considered useful
> for the profile delivery server are:
> 
> - where a particular UA model has different components, each with its own
> version number (e.g., hardware version and software version);
> - where a particular UA model has some optional extras, these may need to be
> listed together with their respective version numbers.
> 

I did not see any comments on this on the list.  Are there any opinions
out there?  I see no technical reasons against adding a components
parameter.  Components values can be a vendor scoped token. If there
is more than one component that the user agent wants to specify it
could add more than one "component" parameter each have a value of
a token.

My main reservation is the case for simplicity.  It is very easy to
add parameters in the future if we really need them.  Please speak
up if you think there is a case for defining this now.

> Has any consideration been given to providing an extensible mechanism for
> delivering UA information in a SUBSCRIBE request to a profile delivery
> server?
> 

Doesn't the Event header parameters construct provide this?  Do we need
something more specific to profile delivery?

> John Elwell (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  Sat Oct 23 05:22: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 FAA10917
	for <sipping-web-archive@ietf.org>; Sat, 23 Oct 2004 05:22:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLIJb-0001Oi-6O
	for sipping-web-archive@ietf.org; Sat, 23 Oct 2004 05:35:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLHwq-0001RA-DA; Sat, 23 Oct 2004 05:12:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLHvn-0000db-D7
	for sipping@megatron.ietf.org; Sat, 23 Oct 2004 05:11:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10316
	for <sipping@ietf.org>; Sat, 23 Oct 2004 05:11:20 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLI8n-0001F5-A0
	for sipping@ietf.org; Sat, 23 Oct 2004 05:24:49 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (rwcrmhc12) with SMTP
	id <20041023091051014004jj2me>; Sat, 23 Oct 2004 09:10:51 +0000
Message-ID: <417A2017.7C25A17C@pingtel.com>
Date: Sat, 23 Oct 2004 05:10:47 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Hisham Khartabil <hisham.khartabil@nokia.com>, sipping@ietf.org
Subject: RE: [Sipping] Comments on config framework draft
Content-Type: text/plain; charset=iso-8859-1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2d133cc328f58695161c98bb4f4dc213
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA10316
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: 79bb66f827e54e9d5c5c7f1f9d645608
Content-Transfer-Encoding: quoted-printable

Hisham:
Thank you for the good comments and edits.  I have worked most of these
into the draft.  Some of these were already spun off on different threads.
I have pulled a few issues out and will spin a thread for them.  There ar=
e
a few comments and questions for clarification below.

Thank you very much.

Cheers,
Dan


Hisham Khartabil wrote:
> If you want to discuss a particular issue, please start a new email thr=
ead.
>=20
> Section 2.3
> ------------
>=20
> - "If the content is provided indirectly the
>    UA SHOULD retrieve the profile from the specified URI upon receipt o=
f
>    the change notification."
>=20
> The SHOULD is way too strong here. I don't have to retrieve whatever is=
 behind the link. A MAY will suffice here.

Changed

>=20
> - "A very high level data model is implied here with the separation of
>    these four profile types.  Each profile type requires a separate
>    subscription to retrieve the profile."
>=20
> I would say that each profile type *instance* needs a separate subscrip=
tion unless multiple app-id, document, etc. If I'm wrong, then there is s=
omething wrong with the description of profile types and instances.

added
>=20
> Section 3.2
> -----------
>=20
> - "This package defines the following new parameters for the event
>    header: "profile-name", "vendor", "model", "version", "effective-by"=
,
>    "document", "app-id".  The effective-by parameter is for use in
>    NOTIFY requests only.  The others are for use in the SUBSCRIBE
>    request, but may be used in NOTIFY requests as well."
>=20
> What should a server so if effected-by parameter appears in a SUBSCRIBE=
. I say ignore.
> What should a client do if other parameters appear in a NOTIFY. I say i=
gnore.

I agree and have added text.
>=20
> - "The "network-user" parameter is used when subscribing for local
>    network profiles.  If the value of the profile-name parameter is not
>    "local", the "network-user" parameter has no defined meaning.  If th=
e
>    user has special privileges beyond that of an anonymous user in the
>    local network, the "network-user" parameter identifies the user to
>    the local network.  The value of this parameter is the user's addres=
s
>    of record.  The SUBSCRIBE server may authenticate the subscriber to
>    verify this AOR."
>=20
> I don't believe this is needed. Authentication should be out of scope o=
f this document. Also, the identity (AOR) of the user should be derived a=
fter authentication locally, no need for the network-user param.

There was a thread on this and I think that Volker explained the need.

>=20
> - "The "effective-by" parameter in the Event header of the NOTIFY
>    specifies the maximum number of seconds before the user agent MUST
>    make the new profile effective.  A value of 0 (zero) indicates that
>    the user agent MUST make the profiles effective immediately (despite
>    possible service interruptions).  This gives the profile delivery
>    server the power to control when the profile is effective.  This may
>    be important to resolve an emergency problem or disable a user agent
>    immediately."
>=20
> Now can a server enforce this. If a server really wants a user to chang=
e the profile, there is no mechanism to enforce the new profile.

The server cannot enforce this.  Thanks to John Elwell'c comments, I
have made this non-normative here and made this normative in
section 3.8 Subscriber processing of NOTIFY requests

>=20
> - "Event: sip-profile;profile-name=3D
>       "http://example.com/services/user-profiles/users/freds.xml";;
>                vendor=3Dpremier;model=3Dtrs8000;version=3D5.5"
>=20
> Something is wrong with the above example. Why is the profile name an x=
cap URI?

Yes the example did not get updated with the changes in the last draft.
The example should look like:

Event: sip-profile;profile-name=3D"user";document=3D
   "http://example.com/services/user-profiles/users/freds.xml";
            vendor=3Dpremier;model=3Dtrs8000;version=3D5.5



> Section 3.7
> ------------
>=20
> - "A user agent can provide hotelling by collecting a user=CBs AOR and
>    credentials needed to SUBSCRIBE and retrieve the user's profiles.
>    hotelling functionality is achieved by subscribing to the user's AOR
>    and specifying the "user" profile type.  This same mechanism can als=
o
>    be used to secure a user agent, requiring a user to login to enable
>    functionality beyond the default user=CBs restricted functionality."
>=20
> Again, the user's AOR should not be explicitly required by the server. =
After authentication, the server should be able to deduce the user's AoR =
from some DB.

Sorry, I am not following this.  The AOR is needed by the user agent so
that it can set the URI for the SUBSCRIBE for the user profile.  This is
in the case where the user agent either does not have a default user or
someone other than the default user wishes to have their user profile
effective on the user agent.

>=20
> Section 3.8
> ------------
>=20
> - Need more text in this section talking about app-id, event header etc.

I will add some more.

>=20
> Section 3.13.1
> --------------
>=20
> - What if instance does not matter? Example all Nokia phone 6600 model =
require the same profile, instance does not matter. Vendor and model is t=
he only thing needed to download a profile. There is no need for the serv=
ice provider to have separate profiles for every device, especially will =
they are identical.

There is a thread on this.  I think the user agent cannot make the decisi=
on
as to whether an instance id is needed.  I think that it should always in=
clude
one.  The profiles will not be identical in the bootstrapping case.  Each
device profile will minimally differ by the default user properties.


>=20
> Section 3.13.3
> --------------
>=20
> - about placing an "anonymous" user name. Why isn't sip:example.com eno=
ugh (no user part)? If user part is present, it MUST be ignored.

Doesn't what you suggest require a change to the way location services
provided through proxies and redirect servers work.  A special user name
seems like a lower impact, easier to implement change.

>=20
> Section 4.1.2
> -------------
>=20
> - I don't think this section should have normative text (SHOULD and MUS=
T)

Ok, I will change it to recommended, but implementation choice.  I worry
a little that if each implementation uses a slightly different order
or suvset of the discovery steps, you will end up with different
results with user agents from different vendors.

>=20
> - "Once a user agent has successfully discovered, enrolled, received a
>    NOTIFY response with profile data or URI(s), the user agent SHOULD
>    cache the device profile SUBCRIBE URI to avoid having to rediscover
>    the profile delivery server again in the future."
>=20
> Why a SHOULD? the device profile SUBSCRIBE URI might be provided in the=
 local profile, so SHOULD is only in certain circumstances that the URI w=
as not in the local profile.

If my UA discovered it's profile when I plugged in the first time in the
office and later I went to the airport, I would not want to trust the
local network to over ride the device profile.  I am ok with the local
network providing constraints and policy, but not with it setting
configuration of my UA device profile.  Every time the URI changes
there should probably be a confirmation of trust/identity of the
profile delivery server.  The confirmation may require user=20
prompting which is bother some in the least if it is every time
my UA changes local network domains.

>=20
> Section 4.1.3
> --------------
>=20
> - User's AoR can also be on the SIM card, for mobile devices with SIM c=
ards.

I will add this and a note on it being pre-provisioned as well.


> Section 4.3
> ------------
>=20
> - "Optionally the differential changes may be obtained by
>    including the content-type defined in [I-D.ietf-simple-xcap-package]
>    in the Accept header of the SUBSCRIBE request"
>=20
> Which one? there are more than 1 MIME types defined in that draft.

I will fix this.

>=20
> Section 4.6
> ------------
>=20
> - "This provides a convenient way for a single subscription to be used
>    to obtain all application data.  The XCAP root is determined by a
>    local mapping."
>=20
> How? What does a NOTIFY body look like? This question also applies to t=
he example later in the section:

I am not sure what the question is here.  The local mapping is an impleme=
ntation
and configuration issue for the XCAP server.  The NOTIFY data format is
out of scope for this draft.

>=20
> "  SUBSCRIBE sip:user-aor at example.com SIP/2.0
>    Event: sip-profile;profile-name=3Dapplication
>=20
>=20
>    The server would map the request URI to an XUI (user-aor, for
>    example) and the xcap root based on local policy.  If there are two
>    AUIDs, "resource-lists" [I-D.ietf-simple-xcap-list-usage] and
>    "rls-services" [I-D.ietf-simple-xcap-list-usage], this would result
>    in a subscription to all documents"
>=20
>=20
> - This sentence:
>    "When the
>    "profile-name" is application, but the "app-id" parameter is absent,
>    this specifies that the user wishes to SUBSCRIBE to all documents fo=
r
>    all application usages associated with the user in the request-uri."
>=20
> contradicts with this one:
>=20
> "If the "profile-name"
>    is "application", the "app-id" MUST be present as well."
>=20
> The latter says its a MUST, but the former said the "app-id" missing is=
 feature.
>=20

I will fix this.  I think that the MUST was meant to be if=20
profile-name is application AND "document" is specified THEN
app-id MUST be specified, but I think even that statement is
incorrect.  I have to think this through a bit.

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> NITs
> =3D=3D=3D=3D

Fixed. =20

>=20
> Section 2.3
> ------------
>=20
> - s/ event packet/ event package
> - s/ This make this/ This makes this
> - s/ It is he author's/ It is the author's
>=20
> Section 3.5
> ------------
>=20
> - FTP reference missing
>=20
> Section 3.7
> ------------
>=20
> - 2x s/ user=CBs/ user's
>=20
> Section 3.12
> -------------
>=20
> - SIP messages are not valid. For example, Via header is missing=20
>=20
> Section 3.13.1
> ---------------
>=20
> - s/ loose/ lose
>=20
> Section 3.13.3
> --------------
>=20
> - s/ the use part/ the user part
>=20
> Section 4.1
> ------------
>=20
> - s/ discover/ discovery
>=20
> Section 4.1
> ------------
>=20
> - a/ SUBCRIBE/ SUBSCRIBE
>=20
> Section 4.2
> -----------
>=20
> - s/ discovery/ discover
>=20
> Section 4.6
> ------------
>=20
> - quotes are missing around the word "application". 3rd line, 3rd parag=
raph.
> - "the server would the "device" profile ..." ???


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 23 05:36: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 FAA11752
	for <sipping-web-archive@ietf.org>; Sat, 23 Oct 2004 05:36:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLIX4-0001f1-As
	for sipping-web-archive@ietf.org; Sat, 23 Oct 2004 05:49:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLIIB-0002RF-K8; Sat, 23 Oct 2004 05:34:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLIGS-0001Us-Rl
	for sipping@megatron.ietf.org; Sat, 23 Oct 2004 05:32:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11543
	for <sipping@ietf.org>; Sat, 23 Oct 2004 05:32:42 -0400 (EDT)
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLITR-0001a9-6e
	for sipping@ietf.org; Sat, 23 Oct 2004 05:46:11 -0400
Received: from pingtel.com (c-128-233-147-24.ne.biz.attbb.net[24.147.233.128])
	by comcast.net (sccrmhc12) with SMTP
	id <2004102309321101200fsggpe>; Sat, 23 Oct 2004 09:32:11 +0000
Message-ID: <417A2518.13BA9FA7@pingtel.com>
Date: Sat, 23 Oct 2004 05:32:08 -0400
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp.  http://www.pingtel.com
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Hisham Khartabil <hisham.khartabil@nokia.com>, sipping@ietf.org
Subject: RE: [Sipping] Comments on config framework draft - security issues
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
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: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Hisham Khartabil wrote:

> 
> Section 3.6
> -----------
> 
> - "If content indirection is used for delivering the
>    profiles, the notifier does not need to authenticate the subscription
>    as the profile content is not transported in the SUBSCRIBE or NOTIFY
>    transaction messages."
> 
> So what? the body of the NOTIFY still contains valuable information. I think it is a bad idea to suggest that authentication is not needed. I would say authentication is always needed.

What is there that authentication is going to protect?  Dialog information
and the profile URI are not protected by authentication. These require
TLS and S/MIME

> 
> - "If the user or device is not known to the profile delivery server,
>    the implementer MAY accept the subscription or reject it.  It is
>    recommended that the implementer accept the subscription."
> 
> I think this is a very bad recommendation. This a a potential DoS attack on the server. The server should reject any subscriptions from unknown users or devices (opposite to the current recommendation)

There are a few important use cases that require the subscriptions 
from unknown user agents to be accepted.

1) A new user agent is plugged into an enterprise environment.  The
subscription server accepts the subscription and provides a default
device profile that gives the device the ability to call the help
desk (UA administrator) and emergency services.

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

> 
> - "If the profile delivery server does not accept the subscription from
>    an unknown user or device, the administer or user must manually
>    provoke the user agent to reSUBSCRIBE."
> 
> So what? a UA can automatically and regularly retry the subscription if it wants.

You do not want a bunch of new UAs in an enterprise polling with a 
SUBSCRIBE every minute to check if the profile delivery server now
has a profile.  That is a bigger DoS problem than accepting the
subscription.

> 
> 
> Section 4.2
> ------------
> 
> - "However the profile server SHOULD
>    accept (with 2xx response) SUBSCRIBE requests from any user agent as
>    explained in Section 3.5."
> 
> I repeat my concerns here. This is a potential DoS attack.
>


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 24 18:51:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08071
	for <sipping-web-archive@ietf.org>; Sun, 24 Oct 2004 18:51:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLrQ3-00077t-SB
	for sipping-web-archive@ietf.org; Sun, 24 Oct 2004 19:05:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLr9d-0000Cm-E4; Sun, 24 Oct 2004 18:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLr8V-000070-0b
	for sipping@megatron.ietf.org; Sun, 24 Oct 2004 18:46:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07745
	for <sipping@ietf.org>; Sun, 24 Oct 2004 18:46:48 -0400 (EDT)
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 1CLrLo-00071t-C2
	for sipping@ietf.org; Sun, 24 Oct 2004 19:00:37 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2004 15:57:16 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9OMkDYJ029128;
	Sun, 24 Oct 2004 15:46:15 -0700 (PDT)
Received: from [10.0.1.3] (sjc-vpn4-1494.cisco.com [10.21.85.213])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATK15198;
	Sun, 24 Oct 2004 15:46:15 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Sun, 24 Oct 2004 12:44:26 -0700
Subject: Re: [Sipping] instance-ID for SIP UA
From: Cullen Jennings <fluffy@cisco.com>
To: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>,
        sipping <sipping@ietf.org>
Message-ID: <BDA1542A.16B0B%fluffy@cisco.com>
In-Reply-To: <E5880434292FCB448F00BDAEE44A60D009662C@EXC01C.cselt.it>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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.7 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

On 9/21/04 5:49 AM, "Simonetti Gabrielle" <Gabrielle.Simonetti@TILAB.COM>
wrote:

>    First issue - What is the format of the instance-ID?
> We would like a standardized instance-ID for all UA. Jennings draft suggests
> the format "RANID-" followed by a 16 digit representation of a random 64 bit
> number. Couldn't this number be associated with the local domain to obtain a
> unique URI identifying the UA instance to be used for the subscription to the
> "device" profile?
>  

I have done a 180 degree turn on my opinion on this. I have become a fan of
UUID. It mixes the best of MAC and RANDID. It works for softphones and
hardphones (whatever those are :-) I don't really believe UUID works better
than RANID but I have become convinced that there are a large group of
people that disagree with me and that we can all agree on UUID.

The UA should create the ID.

The UA should store the ID.

Though we could specify a ton of things and say use any of them, I see no
reason why any of the alternatives are better than UUID (other than for some
esoteric IETF process reasons) so I would be happier to see just one thing
implemented.




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 24 18:52: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 SAA08189
	for <sipping-web-archive@ietf.org>; Sun, 24 Oct 2004 18:52:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLrRZ-0007AI-6O
	for sipping-web-archive@ietf.org; Sun, 24 Oct 2004 19:06:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLr9e-0000Cs-62; Sun, 24 Oct 2004 18:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLr8V-000071-6B
	for sipping@megatron.ietf.org; Sun, 24 Oct 2004 18:46:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07748
	for <sipping@ietf.org>; Sun, 24 Oct 2004 18:46:48 -0400 (EDT)
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 1CLrLp-000724-L0
	for sipping@ietf.org; Sun, 24 Oct 2004 19:00:37 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2004 15:57:18 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9OMkDYL029128;
	Sun, 24 Oct 2004 15:46:17 -0700 (PDT)
Received: from [10.0.1.3] (sjc-vpn4-1494.cisco.com [10.21.85.213])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id ATK15199;
	Sun, 24 Oct 2004 15:46:15 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Sun, 24 Oct 2004 12:53:57 -0700
From: Cullen Jennings <fluffy@cisco.com>
To: John Elwell <john.elwell@siemens.com>, Jason Fischl <jason@purplecomm.com>
Message-ID: <BDA15665.16B0D%fluffy@cisco.com>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670252D280@ntht201e>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: sipping <sipping@ietf.org>
Subject: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit


Good points - inline ...


On 7/15/04 3:01 AM, "Elwell, John" <john.elwell@siemens.com> wrote:

> Cullen, 
> 
> 1. I see nothing to indicate what happens if the called user is busy, switched
> off, etc. at the time the request with receipt arrives. This might be a
> particular problem for the case where the UAS is a PSTN gateway, since it
> probably won't check on the availability of the destination user before
> sending the 402, so if the party is not available or busy it will probably
> still be not available or busy when the request with receipt arrives.
>

yes - this is a somewhat fundamental limitation of the whole system. It
somewhat assumes that if you pay, you will at least go to voicemail. Even if
the proxy found out if the UA was online, there is no  way to know if the
user will answer, or if they do answer, will they instantly hangup.

> Trying later would help in some circumstances, but the draft suggests a window
> of only 30s between payment and accepting the request. Also the caller may not
> be interested later.
> 
> 2. It talks about a proxy in the same domain as the UAS performing UAS
> behaviour, but what about a proxy in the same domain as the UAC performing UAC
> behaviour? For example, a proxy in an enterprise may wish to  make payments on
> behalf of its users.
> 

Yes - I would like to make this work. I think is the next rev, perhaps, I
will move the transfer of the receipt to a header to make this possible.
Originally I was concerned about the consent aspects of this but as I looked
at how the OSP Token worked and a few other things, I suspect we can make
this work fine such that the outbound proxy for the UAC can make the payment
on the UAC's behalf.

> John Elwell (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  Sun Oct 24 20:03: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 UAA11802
	for <sipping-web-archive@ietf.org>; Sun, 24 Oct 2004 20:03:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CLsYW-0008Fu-8p
	for sipping-web-archive@ietf.org; Sun, 24 Oct 2004 20:17:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CLsJq-0004hx-13; Sun, 24 Oct 2004 20:02:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLsJT-0004fl-Es
	for sipping@megatron.ietf.org; Sun, 24 Oct 2004 20:02:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11699
	for <sipping@ietf.org>; Sun, 24 Oct 2004 20:02:14 -0400 (EDT)
Received: from web53408.mail.yahoo.com ([206.190.37.55])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLsWo-0008EB-C3
	for sipping@ietf.org; Sun, 24 Oct 2004 20:16:02 -0400
Message-ID: <20041025000144.21144.qmail@web53408.mail.yahoo.com>
Received: from [24.147.233.128] by web53408.mail.yahoo.com via HTTP;
	Sun, 24 Oct 2004 17:01:44 PDT
X-RocketYMMF: dgpetrie
Date: Sun, 24 Oct 2004 17:01:44 -0700 (PDT)
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Subject: Re: [Sipping] instance-ID for SIP UA
To: Cullen Jennings <fluffy@cisco.com>,
        Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>,
        sipping <sipping@ietf.org>
In-Reply-To: <BDA1542A.16B0B%fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dpetrie@pingtel.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955

Perhaps I am missing a requirement or a discussion
thread on the list.  Can someone point to the reason
this is anything other than an implementation
decision?

Why is this a standards issue?  It seems to me the
only requirement is that it be unique.  Who cares 
how we get there?

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

> On 9/21/04 5:49 AM, "Simonetti Gabrielle"
> <Gabrielle.Simonetti@TILAB.COM>
> wrote:
> 
> >    First issue - What is the format of the
> instance-ID?
> > We would like a standardized instance-ID for all
> UA. Jennings draft suggests
> > the format "RANID-" followed by a 16 digit
> representation of a random 64 bit
> > number. Couldn't this number be associated with
> the local domain to obtain a
> > unique URI identifying the UA instance to be used
> for the subscription to the
> > "device" profile?
> >  
> 
> I have done a 180 degree turn on my opinion on this.
> I have become a fan of
> UUID. It mixes the best of MAC and RANDID. It works
> for softphones and
> hardphones (whatever those are :-) I don't really
> believe UUID works better
> than RANID but I have become convinced that there
> are a large group of
> people that disagree with me and that we can all
> agree on UUID.
> 
> The UA should create the ID.
> 
> The UA should store the ID.
> 
> Though we could specify a ton of things and say use
> any of them, I see no
> reason why any of the alternatives are better than
> UUID (other than for some
> esoteric IETF process reasons) so I would be happier
> to see just one thing
> implemented.
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 25 06:53:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12427
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 06:53:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM2gi-0003S8-CP
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 07:06:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM2S4-0001D0-VD; Mon, 25 Oct 2004 06:51:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM2MT-0000nI-2G
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 06:46:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11944
	for <sipping@ietf.org>; Mon, 25 Oct 2004 06:45:58 -0400 (EDT)
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM2Zu-0003Hq-1z
	for sipping@ietf.org; Mon, 25 Oct 2004 06:59:54 -0400
Received: from dynamicsoft.com ([63.113.46.28])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i9PAjodj004123
	for <sipping@ietf.org>; Mon, 25 Oct 2004 06:45:50 -0400 (EDT)
Message-ID: <417CD93B.1000005@dynamicsoft.com>
Date: Mon, 25 Oct 2004 06:45:15 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Subject: [Sipping] updated sip-spam I-D
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Folks,

I've just submitted an update to the sip-spam draft. Until it appears in 
the archives, you can pick up a copy at:

http://www.jdrosen.net/papers/draft-rosenberg-sipping-spam-01.txt

Here are the diffs:

* added Jon Peterson as co-author

* added text on reputation services as a means for preventing spam

* added text on using address obfuscation in websites as a technique. 
Included
a discussion on enum as a target for spammers

* added text on limited use addresses and the way in which presence and
buddy list systems can help with them

* add recommendation for a transition mechanism to strong identity

* added a discussion on session vs. page mode and the implications on
spam prevention

* made it clear that white lists are superior to black lists, due to the
ease of changing addresses. Refocused the white list discussion on IM 
systems
as the prototypical example.


Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@dynamicsoft.com                        FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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


From sipping-bounces@ietf.org  Mon Oct 25 07:17: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 HAA14643
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 07:17:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM34F-0003yg-Rl
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 07:31:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM2p9-00039E-RK; Mon, 25 Oct 2004 07:15:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM2ma-0002p4-S8
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 07:13:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14133
	for <sipping@ietf.org>; Mon, 25 Oct 2004 07:12:57 -0400 (EDT)
Received: from cluster-b.mailcontrol.com ([217.68.146.190]
	helo=rly05b.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM301-0003rM-Sf
	for sipping@ietf.org; Mon, 25 Oct 2004 07:26:54 -0400
Received: from GBNEWP0758M.eu.ubiquity.net (news.ubiquity.net [194.202.146.92])
	by rly05b.srv.mailcontrol.com (MailControl) with ESMTP id
	i9PBCRnk023484
	for <sipping@ietf.org>; Mon, 25 Oct 2004 12:12:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 25 Oct 2004 12:12:16 +0100
Message-ID: <45730E094814E44488F789C1CDED27AE03118545@gbnewp0758m.eu.ubiquity.net>
Thread-Topic: Updated NAT scenarios draft
Thread-Index: AcS6g3xXWcYMKj9/QmGG4EY8d83mpQ==
From: "Chris Boulton" <cboulton@ubiquity.net>
To: <sipping@ietf.org>
X-Scanned-By: MailControl A-05-00-00 (www.mailcontrol.com)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Subject: [Sipping] Updated NAT scenarios 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>
Content-Type: multipart/mixed; boundary="===============0679519802=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48

This is a multi-part message in MIME format...

--===============0679519802==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4BA83.7C551C60"

This is a multi-part message in MIME format...

------_=_NextPart_001_01C4BA83.7C551C60
Content-Type: text/plain;
	charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

All,

            I've just submitted a new version of the NAT scenarios
draft.  Until it appears in the archives, it can be found at:

=20

http://www.ubiquitysoftware.com/ietf/draft-ietf-sipping-nat-scenarios-01
.txt

=20

=20

This document has a new start and so is still in its very early stages.
I have submitted to let you folks take a look and comment on the
direction - the detail will be consolidated in the next version which
will be polished.  Please could you take a look and comment on the new
direction + suggest any future call scenarios that you would like to see
included (that are not currently listed in the index).

=20

Best Regards,

=20

Chris.

=20



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.

------_=_NextPart_001_01C4BA83.7C551C60
Content-Type: text/html;
	charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* 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
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>All,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; I&#8217;ve
just submitted a new version of the NAT scenarios draft.&nbsp; Until it app=
ears
in the archives, it can be found at:</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><a
href=3D"http://www.ubiquitysoftware.com/ietf/draft-ietf-sipping-nat-scenari=
os-01.txt">http://www.ubiquitysoftware.com/ietf/draft-ietf-sipping-nat-scen=
arios-01.txt</a></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>This document has a new start and so is still in its very
early stages.&nbsp; I have submitted to let you folks take a look and comme=
nt
on the direction &#8211; the detail will be consolidated in the next version
which will be polished.&nbsp; Please could you take a look and comment on t=
he
new direction + suggest any future call scenarios that you would like to see
included (that are not currently listed in the index).</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Best Regards,</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Chris.</span></font></p>

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

</div>

</body>

</html>
<br><br>
<FONT style=3D"BACKGROUND-COLOR: #ffffff">
<DIV>
<DIV><FONT face=3DVerdana color=3D#808080 size=3D1>This email and any attac=
hed files are confidential and copyright protected.&nbsp; If you are not th=
e addressee, any dissemination, distribution or copying of this communicati=
on is strictly prohibited.&nbsp; Unless otherwise expressly agreed in writi=
ng, nothing stated in this communication shall be legally binding.</FONT></=
DIV></DIV></FONT>

------_=_NextPart_001_01C4BA83.7C551C60--


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



From sipping-bounces@ietf.org  Mon Oct 25 07:52: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 HAA17826
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 07:52:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM3ci-0004re-SE
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 08:06:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM3NR-0006Db-Hl; Mon, 25 Oct 2004 07:51:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM3MD-0006Ac-Ol
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 07:49:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17738
	for <sipping@ietf.org>; Mon, 25 Oct 2004 07:49:48 -0400 (EDT)
Received: from cms1.etri.re.kr ([129.254.16.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM3Ze-0004oU-KG
	for sipping@ietf.org; Mon, 25 Oct 2004 08:03:43 -0400
Received: from eunahT6124 (eunah.etri.re.kr [129.254.112.200]) by
	cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail
	Service Version 5.5.2657.72)
	id VRH2D2X3; Mon, 25 Oct 2004 20:49:35 +0900
Message-ID: <014f01c4ba88$a807d260$c870fe81@eunahT6124>
From: "Eunsook Kim" <eunah@etri.re.kr>
To: <sipping@ietf.org>
Date: Mon, 25 Oct 2004 20:49:16 +0900
Organization: ETRI
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [Sipping] Fw: Conf-Floor-Package Comments
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Eunsook Kim <eunah@etri.re.kr>
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="===============1699615482=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86

--===============1699615482==
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJFdW5zb29rIEtpbSIgPGV1bmFo
QGV0cmkucmUua3I+DQpUbzogIlNoYXJvbiBGcmlkbWFuIiA8U2hhcm9uLkZyaWRtYW5AZm9sbG93
YXAuY29tPg0KU2VudDogTW9uZGF5LCBPY3RvYmVyIDI1LCAyMDA0IDc6NDQgUE0NClN1YmplY3Q6
IFJlOiBDb25mLUZsb29yLVBhY2thZ2UgQ29tbWVudHMNCg0KDQo+IFRoYW5rcyBmb3IgeW91ciBj
b21tZW50LiBNeSBhbnN3ZXJzIGFyZSBpbi1saW5lLg0KPiBUaGUgcmV2aXNlZCB2ZXJzaW9uIHJl
ZmxlY3RpbmcgeW91ciBjb21tZW50IGNhbiBiZSBmb3VuZCBhdA0KPiBodHRwOi8vcGVjLmV0cmku
cmUua3IvfmV1bmFoL2lldGYvZHJhZnQtZWtpbS1zaXBwaW5nLWNvbmYtZmxvb3ItcGFja2FnZS0w
MS50eHQgLA0KPiB3aGljaCBpcyBub3QgcmVnaXN0ZXJlZCB0byB0aGUgSUVURiBzaXRlLiBJJ2xs
IHJlZ2lzdGVyIGl0IGxhdGVyIGFmdGVyIGdldHRpbmcgbW9yZSBjb21tZW50cywgDQo+IGFuZCBy
ZXZpc2luZyBhZnRlciB0aGUgbWVldGluZy4gDQo+IA0KPiBUaGUgaW5pdGlhbCB2ZXJzaW9uIGlz
IGZvdW5kIGF0IA0KPiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1l
a2ltLXNpcHBpbmctY29uZi1mbG9vci1wYWNrYWdlLTAwLnR4dA0KPiANCj4gSSdsbCBhbHNvIGFw
cHJlY2lhdGUgYW55IGNvbW1lbnRzIGFuZCB0aG91Z2h0cyBmcm9tIG90aGVyIGZvbGtzIHdobyBh
cmUgaW50ZXJlc3RlZCBpbiANCj4gY29uZmVyZW5jZSB3b3JrLiANCj4gVGhlIGRyYWZ0IGRlZmlu
ZXMgYSBTSVAgZXZlbnQgcGFja2FnZSB0byBvYnRhaW4gaW5mb3JtYXRpb24gYWJvdXQNCj4gdGhl
IHN0YXR1cyBvZiB0aGUgZmxvb3JzIGluIGEgY29uZmVyZW5jZS4gDQo+IEFzIHlvdSBrbm93LCBY
Q09OLVdHIGlzIHdvcmtpbmcgZm9yIGEgZmxvb3ItY29udHJvbCBwcm90b2NvbCwgQkZDUCwgYW5k
IA0KPiBmbG9vciBzdGF0dXMgaW5mb3JtYXRpb24gY2FuIGJlIG9idGFpbmVkIHVzaW5nIEJGQ1Au
IEhvd2V2ZXIsDQo+IHRoZXJlIG1heSBiZSBzb21lIFNJUCB1c2VycyB3aG8gZG9lc24ndCBoYXZl
IHN1Y2ggcHJvdG9jb2wsIGJ1dCBzdGlsbCB3YW50IHRvDQo+IHJlY2VpdmUgZmxvb3Igc3RhdHVz
IGluZm9ybWF0aW9uLiAoRm9yIGV4YW1wbGUsIGluIGFuIGF1ZGlvIGNvbmZlcmVuY2UsIHdoZXJl
DQo+IHNvbWUgcGFuZWxzIHRhbGsgYW5kIG1hbnkgYXVkaWVuY2UgbGlzdGVuIHRvIHRoZSB0YWxr
cywgdGhlIGF1ZGllbmNlIG1heSBub3QgDQo+IG5lZWQgd2hvbGUgZmxvb3IgY29udHJvbCBmdW5j
dGlvbnMsIGJ1dCBtYXkgd2FudCB0byBrbm93IHdoaWNoIHBhbmVsIGlzIGN1cnJlbnRseSB0YWxr
aW5nKQ0KPiBJIHdvdWxkIGxpa2UgdG8ga25vdyB5b3VyIG9waW5pb24gb24gdGhpcyBhcHByb2Fj
aC4NCj4gDQo+IA0KPiA+SSBoYXZlIGZvdW5kIGZldyBtaW5vciBpbmNvbnNpc3RlbmNpZXMgYmV0
d2VlbiB0aGUgc2NoZW1hLCBzYW1wbGUgYW5kDQo+ID5leHBsYW5hdGlvbiAtIHRoYXQgbWF5IG5l
ZWQgc29tZSBjbGFyaWZpY2F0aW9uOg0KPiA+DQo+ID4qIFNlY3Rpb24gNSAtIFJvb3QgaXMgZmxv
b3JzLWluZm8gcmF0aGVyIHRoYW4gZmxvb3INCj4gPiogU2VjdGlvbiA1LjEgbWVudGlvbiByZXNv
dXJjZSBmb3IgZmxvb3ItaW5mbywgd2hlcmUgc2NoZW1hIGluDQo+ID41LjIgYW5kIHNhbXBsZSBp
biA1LjMgc2hvdyByZXNvdXJjZXMgDQo+IA0KPiBUaGFua3MsIEkgY29ycmVjdCB0aGUgdHlwb3MN
Cj4gDQo+ID4qIFNlY3Rpb24gNS4xIDxjaGFpcnM+IGNvbnRhaW4gemVybyBvciBtb3JlIDxjaGFp
cj4gc28gdGhlcmUgaXMNCj4gPm5vIGluaGVyZW50IG5lZWQgZm9yIHplcm8gb3IgbW9yZSA8Y2hh
aXJzPiAodW5sZXNzIHNvbWUgYXR0cmlidXRlcyBhcmUNCj4gPmludHJvZHVjZWQgb3IgdGhlIGRp
ZmZlcmVuY2UgYmV0d2VlbiA8Y2hhaXI+IHJlc2lkaW5nIHVuZGVyIGRpZmZlcmVudA0KPiA+PGNo
YWlycz4gYXJlIGV4cGxhaW5lZCkNCj4gDQo+IEkgdGhpbmsgdGhhdCB0aGVyZSBtYXkgZXhpc3Qg
b25lIG9yIG1vcmUgZmxvb3IgY2hhaXIgZm9yIG1ha2luZyBmbG9vciBkZWNpc2lvbi4NCj4gU28s
IEkgZGVmaW5lIDxjaGFpcnM+IHdoaWNoIGNhbiBoYXZlIG11bHRpcGxlIDxjaGFpcj4gZWxlbWVu
dHMuDQo+IEJ1dCwgPGNoYWlycz4gaXMgYW4gb3B0aW9uYWwgaW5mb3JtYXRpb24sIHNvIHplcm8g
b3IgbW9yZSA8Y2hhaXJzPiB3aWxsIGJlIGFwcGVhci4NCj4gDQo+ID4qIDUuMS4zIHRyYW5zYWN0
aW9uIGF0dHJpYnV0ZSB0byB0aGUgPHN0YXRlPiBlbGVtZW50IGlzIG5vdA0KPiA+cHJlc2VudCBp
biBzY2hlbWEgb3Igc2FtcGxlIC0gaXQgc2VlbXMgdGhlIHRyYW5zYWN0aW9uLWlkIGJlbG9uZ3Mg
dG8NCj4gPnRoZSA8Zmxvb3Itc3RhdGU+IGNoaWxkIG9mIHRoZSA8c3RhdGU+IGVsZW1lbnQuIFRo
ZSB0cmFuc2FjdGlvbi1pZA0KPiA+bm90aW9uIChlLmcuIGEgZmxvb3IgcmVsYXRlZCB0cmFuc2Fj
dGlvbikgYW5kIHRoZSBhZ2dyZWdhdGlvbiBvZg0KPiA+bXVsdGlwbGUgc3VjaCB0cmFuc2FjdGlv
bnMgLyBhY3Rpb25zIGlzIG5vdCBleHBsYWluZWQsIGFuZCBtYXkgYmUgYW4NCj4gPmltcG9ydGFu
dCBkZXNpZ24gZGVjaXNpb24NCj4gDQo+IFRoZSBzY2hlbWEgYW5kIGV4YW1wbGUgc2hvdyA8c3Rh
dGU+IHdoaWNoIGhhcyA8Zmxvb3JzdGF0ZT4gZWxlbWVudC4NCj4gPGZsb29yc3RhdGU+IGhhcyB0
aGUgInRyYW5zYWN0aW9uLWlkIiBhdHRyaWJ1dGUsIGFuZCBvdGhlciBzdWItZWxlbWVudC4NCj4g
VGhlIGNvbnRleHQgd2FzIG5vdCBjbGVhciwgc28gSSBjaGFuZ2VkLg0KPiANCj4gPiogNS4xLjMg
M3JkIHBhcmFncmFwaCBwcm9iYWJseSBzcGVha3Mgb24gPGZsb29yLWFjdGlvbj4sIGEgY2hpbGQN
Cj4gPm9mIDxmbG9vci1zdGF0ZT4NCj4gDQo+IGNvcnJlY3QuIEkgY2hhbmdlZC4NCj4gDQo+ID4q
IDUuMS4zIDxleHBpcmF0aW9uPiBleHBsYW5hdGlvbiBpcyBub3QgY2xlYXIgdG8gbWUNCj4gSXQg
ZXhwbGFpbnMgd2hlbiB0aGUgZmxvb3IgYWN0aW9uIGlzIGV4cGlyZWQsIHNvIHRoYXQgaXQgb25s
eSB1c2VmdWwgZm9yICJncmFudGVkIiBhY3Rpb24uDQo+ICANCj4gDQo+ID5CVFcsIGFsdGhvdWdo
IGl0IGlzIGFuIGludGVybmV0IGRyYWZ0IHRoYXQgbXVzdCBleHBpcmUsIEkgYmVsaWV2ZSBpdA0K
PiA+c2hvdWxkIGhhdmUgaXRzIDZNIChlLmcuIGV4cGlyZSBpbiBBcHJpbCAyMDA1KQ0KPiANCj4g
WWVzLCBJdCB3YXMgdHlwby4gVGhhbmtzLiANCj4gDQo+ID5EbyB5b3UgdGhpbmsgc29tZSBwZXJm
b3JtYW5jZSBndWlkZWxpbmVzIG9yIHVzYWdlIG1pZ2h0IGJlIGhlbHBmdWwsDQo+ID5ldmVuIHRv
dWdoIGl0IGlzIGV4cGxhaW5lZCB0aGF0IGl0IGRvZXMgbm90IHJlcGxhY2Ugb3RoZXIgZmxvb3IN
Cj4gPm1hbmFnZW1lbnQgcHJvdG9jb2xzIChpLmUuIHNvbWUgYXJndWUgdGhhdCB1c2luZyBTSVAg
RVAgcmF0aGVyIHRoYW4NCj4gPmluc2lkZSB0aGUgUlQgbWVkaWEgYXJiaXRyYXRpb24gaXMgc2xv
d2VyIGFuZCBtYXkgcmVzdWx0IGluIHVzZXINCj4gPmV4cGVyaWVuY2UgZmF1bHRzKS4gIA0KPiAN
Cj4gQXMgeW91IHVuZGVyc3RhbmQsIHRoaXMgZHJhZnQgaXMgbm90IGZvciByZXBsYWNpbmcgb3Ro
ZXIgZmxvb3IgY29udHJvbCBwcm90b2NvbC4NCj4gVGhpcyBkb2N1bWVudCBjdXJyZW50bHkgZGVm
aW5lcyB0byBvYnRhaW4gZmxvb3Igc3RhdHVzIGluZm9ybWF0aW9uLA0KPiBub3QgdG8gbWFrZSBv
cGVyYXRpb25zIG9mIGZsb29yIGNvbnRyb2wuDQo+IFNvLCB0aGUgcGVyZm9ybWFuY2UgZ3VpZGVs
aW5lcyBjYW4gYmUgbWFrZSB3aGVuIGl0IGNhbiBiZSB3b3JrIA0KPiBhcyBhbiBhbHRlcm5hdGl2
ZSB3YXkgZm9yIGZsb29yIGNvbnRyb2wgcHJvdG9jb2xzLg0KPiBXZWxsLCBsZXQncyBkaXNjdXNz
IG1vcmUgYWJvdXQgaXQgYXQgV2FzaGluZ3RvbiBEQyBtZWV0aW5nLCANCj4gZ2F0aGVyaW5nIG1v
cmUgb3BpbmlvbiBvbiB0aGlzIG1hdHRlci4NCj4gDQo+IFRoYW5rcyBhZ2FpbiBmb3IgYWxsIHlv
dXIgY29tbWVudHMuDQo+IA0KPiBldW5haA0KPiANCj4gIA0KPiANCj4gIA0KPiANCj4gIA0KPiAN
Cj4g



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


From sipping-bounces@ietf.org  Mon Oct 25 08:29: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 IAA20651
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 08:29:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM4CW-0005Y0-P0
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 08:43:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM3xw-0008TO-V5; Mon, 25 Oct 2004 08:28:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM3uM-0008GH-Uo
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 08:25:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20367
	for <sipping@ietf.org>; Mon, 25 Oct 2004 08:25:05 -0400 (EDT)
Received: from cs.columbia.edu ([128.59.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM47m-0005T0-SP
	for sipping@ietf.org; Mon, 25 Oct 2004 08:39:01 -0400
Received: from razor.cs.columbia.edu
	(IDENT:ZVb5Si9w94XNFpJ+UNlprCYEtxqsR6E5@razor.cs.columbia.edu
	[128.59.16.8])
	by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9PCOwA4020493
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <sipping@ietf.org>; Mon, 25 Oct 2004 08:24:59 -0400 (EDT)
Received: from [127.0.0.1] (IDENT:cF9F4OP72sBjhoccyw1cldJuEL31IGt3@localhost
	[127.0.0.1])
	by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9PCOwXH005642
	for <sipping@ietf.org>; Mon, 25 Oct 2004 08:24:58 -0400
Message-ID: <417CF099.6050907@cs.columbia.edu>
Date: Mon, 25 Oct 2004 08:24:57 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 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.1.0,
	Antispam-Data: 2004.10.24.0
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: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Updates to emergency services drafts
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

http://www.cs.columbia.edu/sip/draft/emergency-req/draft-schulzrinne-sipping-emergency-req-01.html
http://www.cs.columbia.edu/sip/draft/emergency-arch/draft-schulzrinne-sipping-emergency-arch-02.html

These integrate comments received.

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  Mon Oct 25 09:09: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 JAA23616
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 09:09:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM4pC-0006MH-C4
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 09:23:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM4ae-0003JH-Cq; Mon, 25 Oct 2004 09:08:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM4ZW-00036T-5v
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 09:07:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23492
	for <sipping@ietf.org>; Mon, 25 Oct 2004 09:07:36 -0400 (EDT)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM4my-0006IA-4m
	for sipping@ietf.org; Mon, 25 Oct 2004 09:21:32 -0400
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
	(PMDF V6.0-24 #40642) id <0I65002015OOZP@siemenscomms.co.uk> for
	sipping@ietf.org; Mon, 25 Oct 2004 14:05:12 +0100 (BST)
Received: from ntht206e.siemenscomms.co.uk ([137.223.247.52])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0I650024J5ONL4@siemenscomms.co.uk>; Mon,
	25 Oct 2004 14:05:11 +0100 (BST)
Received: by ntht206e.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <VL7D6BKX>; Mon, 25 Oct 2004 14:07:00 +0100
Content-return: allowed
Date: Mon, 25 Oct 2004 14:06:58 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: "'Daniel G. Petrie'" <dpetrie@pingtel.com>
Message-id: <50B1CBA96870A34799A506B2313F26670252D4CC@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: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7BIT
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: [Sipping] RE: Config framework - issue with parameters send in
	Event header
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: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7BIT

Dan,

In-line [JRE]

John (john.elwell@siemens.com) 

-----Original Message-----
From: Daniel G. Petrie [mailto:dpetrie@pingtel.com] 
Sent: 22 October 2004 22:52
To: Elwell, John
Cc: 'sipping@ietf.org'
Subject: Re: Config framework - issue with parameters send in Event header

Thanks for the comments.  I would like to hear opinions from
folks on the list on whether they think this is a current
requirement or not.

Thanks,
Dan

"Elwell, John" wrote:
> 
> Dan,
> 
> In reviewing the draft-ietf-sipping-config-framework-04, I noticed that
> several parameters had been defined for the Event header giving
information
> about the device, i.e., "vendor", "model" and "version". I am concerned
that
> these may not be sufficient in all cases for the profile delivery server
to
> determine the precise profile to be delivered. Moreover, the profile
> delivery server may use these parameters to compile an inventory of
devices
> for admin purposes, and more detailed information might be needed for this
> purpose, even if it does not influence the choice of profile to be
> delivered. Examples of extended information that might be considered
useful
> for the profile delivery server are:
> 
> - where a particular UA model has different components, each with its own
> version number (e.g., hardware version and software version);
> - where a particular UA model has some optional extras, these may need to
be
> listed together with their respective version numbers.
> 

I did not see any comments on this on the list.  Are there any opinions
out there?  I see no technical reasons against adding a components
parameter.  Components values can be a vendor scoped token. If there
is more than one component that the user agent wants to specify it
could add more than one "component" parameter each have a value of
a token.

My main reservation is the case for simplicity.  It is very easy to
add parameters in the future if we really need them.  Please speak
up if you think there is a case for defining this now.

> Has any consideration been given to providing an extensible mechanism for
> delivering UA information in a SUBSCRIBE request to a profile delivery
> server?
> 

Doesn't the Event header parameters construct provide this?  Do we need
something more specific to profile delivery?
[JRE] I guess I am confused about the mechanism for adding new Event header
parameters. Looking at RFC3265, there does not appear to be any IANA
registry for Event header parameters. Perhaps this is intentional - perhaps
parameters are intended to be interpreted within the context of the
particular event package concerned.
Looking at the config framework, I don't see anything there to register the
new parameters (vendor, model, etc.) - sorry I failed to pick that up during
my review. However, even if the config framework were to register these
parameters with IANA, it might require an update to the config framework in
future to add new parameters unless, in creating the registry, it allowed
other means to add new parameters. What I had in mind was the ability for a
particular vendor to add further parameters according to his needs. These
might be meaningful to a server from the same vendor or would be silently
discarded if not recognised. So if there is not sufficient interest in the
community for the "component" parameter, at least a particular vendor could
define something similar.

> John Elwell (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 Oct 25 09:43: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 JAA25886
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 09:43:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM5M6-0006yt-VQ
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 09:57:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM52m-0006Jt-Hm; Mon, 25 Oct 2004 09:37:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM51x-0006FS-Pl
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 09:37:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25488
	for <sipping@ietf.org>; Mon, 25 Oct 2004 09:36:59 -0400 (EDT)
Message-Id: <200410251336.JAA25488@ietf.org>
Received: from smtp002.bizmail.yahoo.com ([216.136.172.126])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CM5FP-0006rh-QR
	for sipping@ietf.org; Mon, 25 Oct 2004 09:50:56 -0400
Received: from unknown (HELO a1b30cjcb7gf94) (david@kayote.com@62.56.252.250
	with login)
	by smtp002.bizmail.yahoo.com with SMTP; 25 Oct 2004 13:36:57 -0000
From: "David" <david@kayote.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] updated sip-spam I-D
Date: Mon, 25 Oct 2004 15:43:17 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <417CD93B.1000005@dynamicsoft.com>
Thread-Index: AcS6mJVj3HrWk5aZTQCkAkH+3ZnUgg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable

Hi Jonathan.

It would appear to me that the consent models are being derived from =
both
email and IM and as such have a yes/no criteria for acceptance or =
rejection
of messages. Person X can either contact me or not.=20

Why not explore a more web like model where pages are classified into =
zones
vis-=E0-vis security. In this implementation, a user defines the =
security
policy of his browser (e.g. accepting cookies etc,) and can then browse
unhindered in "secure"
zones while being prompted in suspicious ones.

In applying this to voice, let's introduce levels of trust (similar to =
the
reputation score you mention) using some sort of tag (perhaps attached =
to
the Asserted ID). The callee would then be able to custom define his
preferences in the end device based on these levels - each end user is
empowered to set his own policy regarding spam or other security related
issues. The level can be set high for calls with certificate asserted =
IDs,
lower for calls coming from trusted zones, lower still for untrusted
callers, and lowest for spam or other security violations. Security =
level
screening can be implemented either at some downstream proxy or at the =
UA.

As an example, in the case of voice spam a user can decide that any call
with security level 1 (not verified) should be automatically blocked, =
calls
with level 2 (bad reputation or few praises) should be automatically =
sent to
voice mail, calls with level 3 (so so reputation or positive reputation)
could be sent a Turing test and calls with level 4 could be =
automatically
accepted (white list). The value of making this decision in the end =
device
is that the user could then take advantage of phone features such as for
example, different rings for the varying levels of security.

David Schwartz=20

> -----Original Message-----
> From: sipping-bounces@ietf.org=20
> [mailto:sipping-bounces@ietf.org] On Behalf Of Jonathan Rosenberg
> Sent: Monday, October 25, 2004 12:45 PM
> To: sipping
> Subject: [Sipping] updated sip-spam I-D
>=20
> Folks,
>=20
> I've just submitted an update to the sip-spam draft. Until it=20
> appears in the archives, you can pick up a copy at:
>=20
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-spam-01.txt
>=20
> Here are the diffs:
>=20
> * added Jon Peterson as co-author
>=20
> * added text on reputation services as a means for preventing spam
>=20
> * added text on using address obfuscation in websites as a technique.=20
> Included
> a discussion on enum as a target for spammers
>=20
> * added text on limited use addresses and the way in which=20
> presence and buddy list systems can help with them
>=20
> * add recommendation for a transition mechanism to strong identity
>=20
> * added a discussion on session vs. page mode and the=20
> implications on spam prevention
>=20
> * made it clear that white lists are superior to black lists,=20
> due to the ease of changing addresses. Refocused the white=20
> list discussion on IM systems as the prototypical example.
>=20
>=20
> Thanks,
> Jonathan R.
> --=20
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Director, Service Provider VoIP Architecture   Parsippany, NJ=20
> 07054-2711
> Cisco Systems
> jdrosen@dynamicsoft.com                        FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.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
>=20
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.775 / Virus Database: 522 - Release Date: 10/8/2004
> =20
>=20

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 10/8/2004
=20


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


From sipping-bounces@ietf.org  Mon Oct 25 12:05: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 MAA09296
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 12:05:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM7ZT-0001fj-Jz
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 12:19:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM78u-00068i-EW; Mon, 25 Oct 2004 11:52:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM6yZ-0004RR-Vt
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 11:41:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05539
	for <sipping@ietf.org>; Mon, 25 Oct 2004 11:41:36 -0400 (EDT)
Received: from mail1.telekom.de ([62.225.183.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM7C2-0000cB-B2
	for sipping@ietf.org; Mon, 25 Oct 2004 11:55:34 -0400
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP;
	Mon, 25 Oct 2004 17:40:53 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <VS2HTF5G>; Mon, 25 Oct 2004 17:40:53 +0200
Message-Id: <76C27E1CE3FFC847B4D51C645D6F42AA15FDD3@E9JDF.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: sipping@ietf.org
Subject: AW: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
Date: Mon, 25 Oct 2004 17:40:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: fluffy@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.2 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab


>On 7/15/04 3:01 AM, "Elwell, John" <john.elwell@siemens.com> wrote:

>> Cullen, 
>> 
>> 1. I see nothing to indicate what happens if the called user is busy, 
>> switched
>> off, etc. at the time the request with receipt arrives. This might be a
>> particular problem for the case where the UAS is a PSTN gateway, since it
>> probably won't check on the availability of the destination user before
>> sending the 402, so if the party is not available or busy it will 
>> probably still be not available or busy when the request with receipt 
>> arrives.

> yes - this is a somewhat fundamental limitation of the whole system. It
> somewhat assumes that if you pay, you will at least go to voicemail. Even 
> if the proxy found out if the UA was online, there is no  way to know if 
> the user will answer, or if they do answer, will they instantly hangup.

By the end of the month, the merchant presents his receipts to the Payment 
Service Provider and gets the money. The merchant (= the PSTN gateway 
provider) could choose to discard receipts for calls to unavailable 
destinations. 

When I wrote
http://www.potaroo.net/ietf/idref/draft-beck-sipping-svc-charging-req/
(http://www.ietf.org/proceedings/03mar/slides/sipping-8.pdf)
two years ago, I had such a scheme in mind. Re-INVITEs carrying receipts of
small sums could limit the damage for the caller if the called party cheats. 
 
As there is a financial incentive for malicious users, security is even more
critical than for other protocols. Installing malicious programs on a 
victim's PC that call expensive numbers is worse than just installing
DDoS bots (but perhaps clueless users will finally secure their system if they have to pay). On the other hand, will users accept a system where they
have to type in a password every time they make a call? Can 
http://www.ietf.org/internet-drafts/draft-tschofenig-sip-saml-00.txt
help?

Besides Spam prevention, draft-jennings-sipping-pay allows new useful
services. 


Wolfgang

--
T-Systems
IP Platform Services
Am Kavalleriesand 3
64295 Darmstadt
Germany




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 25 12:09: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 MAA09798
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 12:09:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CM7dI-0001oN-IE
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 12:23:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CM7OO-0001KZ-QZ; Mon, 25 Oct 2004 12:08:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CM79j-0006Jl-MZ
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 11:53:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07037
	for <sipping@ietf.org>; Mon, 25 Oct 2004 11:53:08 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM7NC-00011U-Si
	for sipping@ietf.org; Mon, 25 Oct 2004 12:07:07 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-5.cisco.com with ESMTP; 25 Oct 2004 08:53:22 -0700
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9PFqXYJ010732;
	Mon, 25 Oct 2004 08:52:34 -0700 (PDT)
Received: from [10.32.245.154] (stealth-10-32-245-154.cisco.com
	[10.32.245.154])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id i9PFsIVr014802;
	Mon, 25 Oct 2004 08:54:18 -0700
In-Reply-To: <41795AD2.57693EAB@pingtel.com>
References: <E5880434292FCB448F00BDAEE44A60D009665A@EXC01C.cselt.it>
	<41795AD2.57693EAB@pingtel.com>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <E2605062-269D-11D9-A86C-000A95C73842@cisco.com>
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] Comments on config framework draft- URIs and
	eventpackage parameters
Date: Mon, 25 Oct 2004 11:52:33 -0400
To: "Daniel G. Petrie" <dpetrie@pingtel.com>
X-Pgp-Agent: GPGMail 1.0.2
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1098719659.799118"; x:"432200"; a:"rsa-sha1"; b:"nofws:2680";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"oZVWQ2HkD/w7NwyUItudEFPia6hmbD/O2i7Ys4J9lY+BTdLz5TBWMnEijFkxa"
	"3lnyCh8LSufCRoS9+aau6J7CUICtQZSOhNuVG81PY4ej1h6ac3HJoWWW58BPT"
	"nJlWg/V88QD5u2ostcwVJZnpLS6gfnUSZky4emyZY2a8As6mI=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] Comments on config framework draft- URIs and
	ev" "entpackage parameters"; c:"Date: Mon, 25 Oct 2004 11:52:33 -0400"
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: c0bedb65cce30976f0bf60a0a39edea4
Cc: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1813606341=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30


--===============1813606341==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-6-153269167"


--Apple-Mail-6-153269167
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit


On Oct 22, 2004, at 3:09 PM, Daniel G. Petrie wrote:
[snip]

>> Actually, it is not specified in the framework which of the Event 
>> Header parameters are obligatory/optional/unnecessary in a 
>> subscription. For example, I would imagine that for the "device" 
>> profile subscription, the parameter "vendor" is obligatory, while the 
>> parameters "model" and  "version" are optional (the parameter 
>> "vendor" alone in a subscription would correspond to the profile 
>> relative to all devices from one same vendor). On the opposite, for 
>> the "application" profile subscription, the "app-id" parameter could 
>> be obligatory while "vendor", "model" and "version" are unnecessary.
>
> Wow.  Thanks, I will fix that.  It was intended that vendor, model and 
> version
> were manditory for all the profiles.  Though it may not be necessary, 
> it is
> potentially useful to the profile delivery server to know these 
> parameters
> should it desire to customize the profile based upon the specific 
> implementation.
> In the perfect world they will all be have the same.  However we are 
> in a
> real world and I think that it is important to give the profile 
> delivery server
> the ability to customize the profiles.  If we do not make these 
> mandatory,
> implementors will not put them and the profile delivery server will be
> running blind.
>
On the contrary, experience has shown that people use the presence of 
such information to "customize" their way to non-interoperability. I 
have no objection to including the implementation information because 
it helps both customization and debugging, but I suggest two things:
a) That these fields NOT be mandatory. I would be ok with SHOULD 
strength, as long as there is some kind of escape clause to cover 
ensuring anonymity of implementation where desired so that bad 
customizations can be avoided.
b) That the presence of these fields MUST not alter the operation of 
any configuration protocol machinery - it may only be used to customize 
the delivered data.

Dave.

--Apple-Mail-6-153269167
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFBfSFBjWaEtlTdKuYRAjm2AKDX5XmFiZB3EXtbIiv/pyfyZPjgXQCgxDYg
27S64Z/6eGq8UxeAc4TMCqQ=
=svd+
-----END PGP SIGNATURE-----

--Apple-Mail-6-153269167--



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




From sipping-bounces@ietf.org  Mon Oct 25 19:07: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 TAA10136
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 19:07:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CME9L-0001aB-CX
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 19:21:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMBUc-0004lf-Mv; Mon, 25 Oct 2004 16:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMB77-0007WP-Uj; Mon, 25 Oct 2004 16:06:45 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29888;
	Mon, 25 Oct 2004 16:06:43 -0400 (EDT)
Message-Id: <200410252006.QAA29888@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 25 Oct 2004 16:06:43 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D
	ACTION:draft-ietf-sipping-app-interaction-framework-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: A Framework for Application Interaction in the Session Initiation Protocol (SIP)
	Author(s)	: J. Rosenberg
	Filename	: draft-ietf-sipping-app-interaction-framework-03.txt
	Pages		: 39
	Date		: 2004-10-25
	
This document describes a framework for the interaction between users
   and Session Initiation Protocol (SIP) based applications.  By
   interacting with applications, users can guide the way in which they
   operate.  The focus of this framework is stimulus signaling, which
   allows a user agent to interact with an application without knowledge
   of the semantics of that application.  Stimulus signaling can occur
   to a user interface running locally with the client, or to a remote
   user interface, through media streams.  Stimulus signaling
   encompasses a wide range of mechanisms, ranging from clicking on
   hyperlinks, to pressing buttons, to traditional Dual Tone Multi
   Frequency (DTMF) input.  In all cases, stimulus signaling is
   supported through the use of markup languages, which play a key role
   in this framework.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-app-interaction-framework-03.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-app-interaction-framework-03.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-app-interaction-framework-03.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-10-25162220.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-app-interaction-framework-03.txt

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

Content-Type: text/plain
Content-ID: <2004-10-25162220.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  Mon Oct 25 19:10: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 TAA11036
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 19:10:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMECx-0001ra-9E
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 19:24:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMBUj-00053B-Uo; Mon, 25 Oct 2004 16:31:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMB7Y-0007ju-H4; Mon, 25 Oct 2004 16:07:12 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00092;
	Mon, 25 Oct 2004 16:07:09 -0400 (EDT)
Message-Id: <200410252007.QAA00092@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 25 Oct 2004 16:07:09 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-callerprefs-usecases-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Guidelines for Usage of the Session Initiation 
			  Protocol (SIP) Caller Preferences Extension
	Author(s)	: J. Rosenberg, P. Kyzivat
	Filename	: draft-ietf-sipping-callerprefs-usecases-03.txt
	Pages		: 43
	Date		: 2004-10-25
	
This document contains guidelines for usage of the Caller Preferences
Extension to the Session Initiation Protocol (SIP). It motivates the
benefits of caller preferences with specific example applications,
provides use cases to show proper operation, provides guidance on the
applicability of the registered feature tags, and describes a
straightforward implementation of the matching algorithm.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-callerprefs-usecases-03.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-callerprefs-usecases-03.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-callerprefs-usecases-03.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-10-25162226.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-callerprefs-usecases-03.txt

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

Content-Type: text/plain
Content-ID: <2004-10-25162226.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  Mon Oct 25 20:02: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 UAA21127
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 20:02:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMF0g-00050w-9Q
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 20:16:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMEVS-0003Ek-89; Mon, 25 Oct 2004 19:44:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMDZD-0000dw-AF
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 18:43:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04700
	for <sipping@ietf.org>; Mon, 25 Oct 2004 18:43:51 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMDmk-0008FR-Dx
	for sipping@ietf.org; Mon, 25 Oct 2004 18:57:54 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 25 Oct 2004 19:03:38 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9PMf4Ss016525; 
	Mon, 25 Oct 2004 18:41:04 -0400 (EDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMN91277; Mon, 25 Oct 2004 18:41:03 -0400 (EDT)
Message-ID: <417D80FF.7040404@cisco.com>
Date: Mon, 25 Oct 2004 18:41:03 -0400
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: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sipping] RE: Config framework - issue with parameters send in
	Event header
References: <50B1CBA96870A34799A506B2313F26670252D4CC@ntht201e>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: 7bit
Cc: "'Daniel G. Petrie'" <dpetrie@pingtel.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: 7bit

Did anyone consider providing these parameters as a body in the 
SUBSCRIBE? (Something like a "filter" in a warped sort of way.)

	Paul

Elwell, John wrote:
> Dan,
> 
> In-line [JRE]
> 
> John (john.elwell@siemens.com) 
> 
> -----Original Message-----
> From: Daniel G. Petrie [mailto:dpetrie@pingtel.com] 
> Sent: 22 October 2004 22:52
> To: Elwell, John
> Cc: 'sipping@ietf.org'
> Subject: Re: Config framework - issue with parameters send in Event header
> 
> Thanks for the comments.  I would like to hear opinions from
> folks on the list on whether they think this is a current
> requirement or not.
> 
> Thanks,
> Dan
> 
> "Elwell, John" wrote:
> 
>>Dan,
>>
>>In reviewing the draft-ietf-sipping-config-framework-04, I noticed that
>>several parameters had been defined for the Event header giving
> 
> information
> 
>>about the device, i.e., "vendor", "model" and "version". I am concerned
> 
> that
> 
>>these may not be sufficient in all cases for the profile delivery server
> 
> to
> 
>>determine the precise profile to be delivered. Moreover, the profile
>>delivery server may use these parameters to compile an inventory of
> 
> devices
> 
>>for admin purposes, and more detailed information might be needed for this
>>purpose, even if it does not influence the choice of profile to be
>>delivered. Examples of extended information that might be considered
> 
> useful
> 
>>for the profile delivery server are:
>>
>>- where a particular UA model has different components, each with its own
>>version number (e.g., hardware version and software version);
>>- where a particular UA model has some optional extras, these may need to
> 
> be
> 
>>listed together with their respective version numbers.
>>
> 
> 
> I did not see any comments on this on the list.  Are there any opinions
> out there?  I see no technical reasons against adding a components
> parameter.  Components values can be a vendor scoped token. If there
> is more than one component that the user agent wants to specify it
> could add more than one "component" parameter each have a value of
> a token.
> 
> My main reservation is the case for simplicity.  It is very easy to
> add parameters in the future if we really need them.  Please speak
> up if you think there is a case for defining this now.
> 
> 
>>Has any consideration been given to providing an extensible mechanism for
>>delivering UA information in a SUBSCRIBE request to a profile delivery
>>server?
>>
> 
> 
> Doesn't the Event header parameters construct provide this?  Do we need
> something more specific to profile delivery?
> [JRE] I guess I am confused about the mechanism for adding new Event header
> parameters. Looking at RFC3265, there does not appear to be any IANA
> registry for Event header parameters. Perhaps this is intentional - perhaps
> parameters are intended to be interpreted within the context of the
> particular event package concerned.
> Looking at the config framework, I don't see anything there to register the
> new parameters (vendor, model, etc.) - sorry I failed to pick that up during
> my review. However, even if the config framework were to register these
> parameters with IANA, it might require an update to the config framework in
> future to add new parameters unless, in creating the registry, it allowed
> other means to add new parameters. What I had in mind was the ability for a
> particular vendor to add further parameters according to his needs. These
> might be meaningful to a server from the same vendor or would be silently
> discarded if not recognised. So if there is not sufficient interest in the
> community for the "component" parameter, at least a particular vendor could
> define something similar.
> 
> 
>>John Elwell (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
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 25 20:05: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 UAA21716
	for <sipping-web-archive@ietf.org>; Mon, 25 Oct 2004 20:05:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMF3u-00057T-EN
	for sipping-web-archive@ietf.org; Mon, 25 Oct 2004 20:19:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMEWr-0004f8-OD; Mon, 25 Oct 2004 19:45:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMDmS-0007Eq-CT
	for sipping@megatron.ietf.org; Mon, 25 Oct 2004 18:57:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07602
	for <sipping@ietf.org>; Mon, 25 Oct 2004 18:57:32 -0400 (EDT)
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 1CMDzz-0000lK-Dp
	for sipping@ietf.org; Mon, 25 Oct 2004 19:11:35 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 25 Oct 2004 16:08:19 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9PMv86s013552;
	Mon, 25 Oct 2004 15:57:09 -0700 (PDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMN92192; Mon, 25 Oct 2004 18:57:07 -0400 (EDT)
Message-ID: <417D84C3.5070509@cisco.com>
Date: Mon, 25 Oct 2004 18:57:07 -0400
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: dpetrie@pingtel.com
Subject: Re: [Sipping] instance-ID for SIP UA
References: <20041025000144.21144.qmail@web53408.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>,
        Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.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: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: 7bit



Daniel G. Petrie wrote:
> Perhaps I am missing a requirement or a discussion
> thread on the list.  Can someone point to the reason
> this is anything other than an implementation
> decision?
> 
> Why is this a standards issue?  It seems to me the
> only requirement is that it be unique.  Who cares 
> how we get there?

At one level I agree that it doesn't really matter as long as it is 
unique. To guarantee uniqueness, you must say *something* about the 
format. About the minimum you can say is that it is a URI, or a URN.

There is a pragmatic issue of how you compare these things to determine 
if they indeed are unique. Each URI/URN scheme has its own comparison 
rules. So in principle you can't compare two of them if you don't 
understand the format.

I doubt this is a practical problem. Byte-for-byte comparison when you 
don't know any better will probably produce decent results.

	Paul

> 
> --- Cullen Jennings <fluffy@cisco.com> wrote:
> 
> 
>>On 9/21/04 5:49 AM, "Simonetti Gabrielle"
>><Gabrielle.Simonetti@TILAB.COM>
>>wrote:
>>
>>
>>>   First issue - What is the format of the
>>
>>instance-ID?
>>
>>>We would like a standardized instance-ID for all
>>
>>UA. Jennings draft suggests
>>
>>>the format "RANID-" followed by a 16 digit
>>
>>representation of a random 64 bit
>>
>>>number. Couldn't this number be associated with
>>
>>the local domain to obtain a
>>
>>>unique URI identifying the UA instance to be used
>>
>>for the subscription to the
>>
>>>"device" profile?
>>> 
>>
>>I have done a 180 degree turn on my opinion on this.
>>I have become a fan of
>>UUID. It mixes the best of MAC and RANDID. It works
>>for softphones and
>>hardphones (whatever those are :-) I don't really
>>believe UUID works better
>>than RANID but I have become convinced that there
>>are a large group of
>>people that disagree with me and that we can all
>>agree on UUID.
>>
>>The UA should create the ID.
>>
>>The UA should store the ID.
>>
>>Though we could specify a ton of things and say use
>>any of them, I see no
>>reason why any of the alternatives are better than
>>UUID (other than for some
>>esoteric IETF process reasons) so I would be happier
>>to see just one thing
>>implemented.
>>
>>
>>
>>
>>_______________________________________________
>>Sipping mailing list 
>>https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the 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 Oct 26 03:15: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 DAA04704
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 03:15:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMLmL-00048V-Ky
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 03:30:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMLWn-0001fE-Bl; Tue, 26 Oct 2004 03:13:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMLVv-0001Jq-BG
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 03:13:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04545
	for <sipping@ietf.org>; Tue, 26 Oct 2004 03:13:00 -0400 (EDT)
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMLjW-00044z-0k
	for sipping@ietf.org; Tue, 26 Oct 2004 03:27:06 -0400
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
	(PMDF V6.0-24 #40642) id <0I6600H01JXS92@siemenscomms.co.uk> for
	sipping@ietf.org; Tue, 26 Oct 2004 08:10:41 +0100 (BST)
Received: from ntht206e.siemenscomms.co.uk ([137.223.247.52])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0I6600G25JXRVA@siemenscomms.co.uk>; Tue,
	26 Oct 2004 08:10:39 +0100 (BST)
Received: by ntht206e.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <VL7D61FY>; Tue, 26 Oct 2004 08:12:27 +0100
Content-return: allowed
Date: Tue, 26 Oct 2004 08:12:27 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] RE: Config framework - issue with parameters send i	n
	Event header
To: Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <50B1CBA96870A34799A506B2313F26670252D4D5@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: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: 7BIT
Cc: "'Daniel G. Petrie'" <dpetrie@pingtel.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Content-Transfer-Encoding: 7BIT

Paul,

I guess that is what I had in the back of my mind - why header parameters
and why not an XML body.

John


-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of Paul Kyzivat
Sent: 25 October 2004 23:41
To: Elwell, John
Cc: 'Daniel G. Petrie'; 'sipping@ietf.org'
Subject: Re: [Sipping] RE: Config framework - issue with parameters send in
Event header

Did anyone consider providing these parameters as a body in the 
SUBSCRIBE? (Something like a "filter" in a warped sort of way.)

	Paul

Elwell, John wrote:
> Dan,
> 
> In-line [JRE]
> 
> John (john.elwell@siemens.com) 
> 
> -----Original Message-----
> From: Daniel G. Petrie [mailto:dpetrie@pingtel.com] 
> Sent: 22 October 2004 22:52
> To: Elwell, John
> Cc: 'sipping@ietf.org'
> Subject: Re: Config framework - issue with parameters send in Event header
> 
> Thanks for the comments.  I would like to hear opinions from
> folks on the list on whether they think this is a current
> requirement or not.
> 
> Thanks,
> Dan
> 
> "Elwell, John" wrote:
> 
>>Dan,
>>
>>In reviewing the draft-ietf-sipping-config-framework-04, I noticed that
>>several parameters had been defined for the Event header giving
> 
> information
> 
>>about the device, i.e., "vendor", "model" and "version". I am concerned
> 
> that
> 
>>these may not be sufficient in all cases for the profile delivery server
> 
> to
> 
>>determine the precise profile to be delivered. Moreover, the profile
>>delivery server may use these parameters to compile an inventory of
> 
> devices
> 
>>for admin purposes, and more detailed information might be needed for this
>>purpose, even if it does not influence the choice of profile to be
>>delivered. Examples of extended information that might be considered
> 
> useful
> 
>>for the profile delivery server are:
>>
>>- where a particular UA model has different components, each with its own
>>version number (e.g., hardware version and software version);
>>- where a particular UA model has some optional extras, these may need to
> 
> be
> 
>>listed together with their respective version numbers.
>>
> 
> 
> I did not see any comments on this on the list.  Are there any opinions
> out there?  I see no technical reasons against adding a components
> parameter.  Components values can be a vendor scoped token. If there
> is more than one component that the user agent wants to specify it
> could add more than one "component" parameter each have a value of
> a token.
> 
> My main reservation is the case for simplicity.  It is very easy to
> add parameters in the future if we really need them.  Please speak
> up if you think there is a case for defining this now.
> 
> 
>>Has any consideration been given to providing an extensible mechanism for
>>delivering UA information in a SUBSCRIBE request to a profile delivery
>>server?
>>
> 
> 
> Doesn't the Event header parameters construct provide this?  Do we need
> something more specific to profile delivery?
> [JRE] I guess I am confused about the mechanism for adding new Event
header
> parameters. Looking at RFC3265, there does not appear to be any IANA
> registry for Event header parameters. Perhaps this is intentional -
perhaps
> parameters are intended to be interpreted within the context of the
> particular event package concerned.
> Looking at the config framework, I don't see anything there to register
the
> new parameters (vendor, model, etc.) - sorry I failed to pick that up
during
> my review. However, even if the config framework were to register these
> parameters with IANA, it might require an update to the config framework
in
> future to add new parameters unless, in creating the registry, it allowed
> other means to add new parameters. What I had in mind was the ability for
a
> particular vendor to add further parameters according to his needs. These
> might be meaningful to a server from the same vendor or would be silently
> discarded if not recognised. So if there is not sufficient interest in the
> community for the "component" parameter, at least a particular vendor
could
> define something similar.
> 
> 
>>John Elwell (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
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the 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 Oct 26 06: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 GAA19087
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 06:17:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMObe-0007p3-B1
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 06:31:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMONE-00021V-Cj; Tue, 26 Oct 2004 06:16:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMOHZ-00085D-AG
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 06:10:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18609
	for <sipping@ietf.org>; Tue, 26 Oct 2004 06:10:23 -0400 (EDT)
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMOVB-0007fL-G5
	for sipping@ietf.org; Tue, 26 Oct 2004 06:24:31 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAKM9000534; Tue, 26 Oct 2004 19:10:20 +0900 (JST)
Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAJjH000654; Tue, 26 Oct 2004 19:10:19 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAJSN000646; Tue, 26 Oct 2004 19:10:19 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAIuM018276; Tue, 26 Oct 2004 19:10:18 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAIg1018272; Tue, 26 Oct 2004 19:10:18 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAImh026604; Tue, 26 Oct 2004 19:10:18 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAH9a007629; Tue, 26 Oct 2004 19:10:17 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (img0.m.ecl.ntt.co.jp [129.60.5.145])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAHAL007624; Tue, 26 Oct 2004 19:10:17 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id TAA29063;
	Tue, 26 Oct 2004 19:10:16 +0900 (JST)
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
To: sipping@ietf.org
Date: Tue, 26 Oct 2004 19:09:49 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.52 (WinNT,501)
Message-Id: <4DC4BB43EDC35Aono.kumiko@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Subject: [Sipping] e2m security open issue: label for the target body
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit

Hi,

I've submitted an update draft of the e2m security mechanism (http://www.
ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-03.txt). 
There are two major open issues on the mechanism of end-to-middle 
security. I would like to hear your opinions on these. 

Open issue#1: How to label the target body.

In order for a proxy server to easily determine whether to process MIME 
bodies and which one, UA needs a way to label the body targeted at a 
particular proxy server(s). 

After receiving many comments at the last IETF meeting about this, I 
gave it some thought and came up with some conclusion, so I want to 
share with you my preference in accomplishing the labeling and the 
reason behind my preference.

Options for labeling:
A-1. a new SIP header, i.e.: "Proxy-Required-Body".
A-2. a new parameter in a SIP header, i.e.: "content-id" param in "Route" 
header.
B-1. a new MIME header, i.e.: "Content-Target".
B-2. a new parameter in a MIME header, i.e.: "required-entity" param in 
"Content-Disposition".

When a message has a target body destined for a proxy server, MIME 
header options (B) shows a greater performance than SIP header options 
(A) in searching the target body. This is because options A require the 
inspection of the SIP header and "Content-ID" MIME header, while options 
B only require the inspection of the MIME header.

When a message has no target body destined for a proxy server, it is 
easier for SIP header options (A) to determine that fact, as it only 
needs to look at the SIP header. 

However, if integrity protection of the label is required, inner headers 
need to be created using sipfrag attached with a signature. And the 
validation of the signature would reduce the advantage of the ease in 
determining the needs to search the body. If the security level of the 
label is considered to be the same as that of routing headers, use of 
TLS would satisfy the integrity requirements which will allow the SIP 
header options (A) to retain their advantage.

Since few of messages in all the traffic through a proxy server will 
likely utilize e2m security, the ease in determining the needs to search 
the body overweighs the performance in searching the target body. 
Therefore, I changed the proposed option, from MIME header options to 
SIP headers. Since a new parameter in Route header has more impact on a 
proxy server, I believe Option A-1, with a new SIP header the best 
choice.

Your feedback is very welcome.

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


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


From sipping-bounces@ietf.org  Tue Oct 26 06:20: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 GAA19572
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 06:20:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMOfB-0007xh-AX
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 06:34:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMONF-00022H-Jj; Tue, 26 Oct 2004 06:16:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMOHv-0008Hz-J9
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 06:10:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18635
	for <sipping@ietf.org>; Tue, 26 Oct 2004 06:10:45 -0400 (EDT)
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMOVZ-0007fp-3G
	for sipping@ietf.org; Tue, 26 Oct 2004 06:24:53 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAiqD000651; Tue, 26 Oct 2004 19:10:44 +0900 (JST)
Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAiYv000859; Tue, 26 Oct 2004 19:10:44 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAhQN000853; Tue, 26 Oct 2004 19:10:43 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAhFC018466; Tue, 26 Oct 2004 19:10:43 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAhdY018462; Tue, 26 Oct 2004 19:10:43 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAgAL026644; Tue, 26 Oct 2004 19:10:42 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAgn1007741; Tue, 26 Oct 2004 19:10:42 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (img0.m.ecl.ntt.co.jp [129.60.5.145])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9QAAgP5007738; Tue, 26 Oct 2004 19:10:42 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id TAA29083;
	Tue, 26 Oct 2004 19:10:41 +0900 (JST)
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
To: sipping@ietf.org
Date: Tue, 26 Oct 2004 19:10:14 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.52 (WinNT,501)
Message-Id: <4FC4BB43FC59F9ono.kumiko@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Subject: [Sipping] e2m security open issue: notification with error codes
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Hi,

Here is the second issue on mechanism of e2m security.

Open Issue#2: How does a proxy server notify the needs of end-to-middle 
security to the UAC by using error codes?

After discussion with some of the WG member, and giving some thought on 
how UAC might realize the need of e2m security utilization, I realized 
that proxy should have a way to notify the UAC about e2m security 
utilization in addition to using UAC driven method, such as session 
policy package. 

There are two cases where a proxy server needs a UAC to utilize
end-to-middle security in its communication.
1) When the proxy server needs to view an encrypted data sent by UAC. We 
can say this case to be somewhat of a security downgrading and it 
requires end-to-middle confidentiality.
2) When the proxy server needs to validate the data integrity of the 
message. We can say this to be somewhat of a security upgrading, and it 
requires end-to-middle integrity.
In both cases, the information for notification (error codes) to UAC 
should include the case (reason) and target content type. 

Looking at pre-existing error codes, "493 Undecipherable" can be 
utilized for the first case as it means that peer requires the 
capability to decrypt. However, there are no error codes that indicate 
its requirement to carry out an integrity validation. 
I think we need a new error code, such as "495 Signature required" for 
clarification. Also as stated above, I think that the target content 
type should be described in Warning header.

Your feedback is very welcome.

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


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


From sipping-bounces@ietf.org  Tue Oct 26 07:25:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25286
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 07:25:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMPg8-0000ns-Pt
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 07:39:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMPQc-0007jM-3t; Tue, 26 Oct 2004 07:23:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMPOn-00079X-Ec
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 07:21:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24966
	for <sipping@ietf.org>; Tue, 26 Oct 2004 07:21:56 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMPcR-0000jO-3S
	for sipping@ietf.org; Tue, 26 Oct 2004 07:36:03 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i9QBLqP6015886;
	Tue, 26 Oct 2004 13:21:52 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i9QBLqBO012034;
	Tue, 26 Oct 2004 13:21:52 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <4BVR6260>; Tue, 26 Oct 2004 13:21:52 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F051C86AE@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org
Subject: RE: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
Date: Tue, 26 Oct 2004 13:21:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: fluffy@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.2 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

hi wolfgang, 

thanks for pointing to saml-sip. in fact i have added a few lines to the
updated draft on the compensation issue (section 6.4 of
http://www.tschofenig.priv.at/drafts/draft-tschofenig-sip-saml-01.txt) . 
i agree with you that there is some potential for new services beyond just
spam prevention. 

ciao
hannes

> -----Original Message-----
> From: Beck01, Wolfgang [mailto:BeckW@t-systems.com]
> Sent: Montag, 25. Oktober 2004 17:41
> To: sipping@ietf.org
> Cc: fluffy@cisco.com
> Subject: AW: [Sipping] Re: Questions on draft-jennings-sipping-pay-00
> 
> 
> >On 7/15/04 3:01 AM, "Elwell, John" <john.elwell@siemens.com> wrote:
> 
> >> Cullen,
> >> 
> >> 1. I see nothing to indicate what happens if the called
> user is busy,
> >> switched off, etc. at the time the request with receipt
> arrives. This
> >> might be a particular problem for the case where the UAS is a PSTN 
> >> gateway, since it probably won't check on the availability of the 
> >> destination user before sending the 402, so if the party is not 
> >> available or busy it will probably still be not available or busy 
> >> when the request with receipt arrives.
> 
> > yes - this is a somewhat fundamental limitation of the
> whole system. 
> > It somewhat assumes that if you pay, you will at least go to 
> > voicemail. Even if the proxy found out if the UA was
> online, there is
> > no  way to know if the user will answer, or if they do
> answer, will they instantly hangup.
> 
> By the end of the month, the merchant presents his receipts to the 
> Payment Service Provider and gets the money. The merchant (= the PSTN 
> gateway
> provider) could choose to discard receipts for calls to unavailable 
> destinations.
> 
> When I wrote
> http://www.potaroo.net/ietf/idref/draft-beck-sipping-svc-charging-req/
> (http://www.ietf.org/proceedings/03mar/slides/sipping-8.pdf)
> two years ago, I had such a scheme in mind. Re-INVITEs carrying 
> receipts of small sums could limit the damage for the caller if the 
> called party cheats.

>  
> As there is a financial incentive for malicious users, security is 
> even more critical than for other protocols.
> Installing malicious programs on a victim's PC that call expensive 
> numbers is worse than just installing DDoS bots (but perhaps clueless 
> users will finally secure their system if they have to pay). On the 
> other hand, will users accept a system where they have to type in a 
> password every time they make a call? Can 
> http://www.ietf.org/internet-drafts/draft-tschofenig-sip-saml-00.txt
> help?
> 
> Besides Spam prevention, draft-jennings-sipping-pay allows new useful 
> services.


ciao
hannes

> 
> 
> Wolfgang
> 
> --
> T-Systems
> IP Platform Services
> Am Kavalleriesand 3
> 64295 Darmstadt
> Germany
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 26 13:25: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 NAA26154
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 13:25:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMVIN-000065-1n
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 13:39:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMUuA-0004jy-7E; Tue, 26 Oct 2004 13:14:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMUj3-0000zX-8b
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 13:03:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23219
	for <sipping@ietf.org>; Tue, 26 Oct 2004 13:03:10 -0400 (EDT)
Received: from smtp1.clb.oleane.net ([213.56.31.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMUwk-0007cj-Co
	for sipping@ietf.org; Tue, 26 Oct 2004 13:17:23 -0400
Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be
	forged)) by smtp1.clb.oleane.net with ESMTP id i9QH2cee008773
	for <sipping@ietf.org>; Tue, 26 Oct 2004 19:02:38 +0200
Message-Id: <200410261702.i9QH2cee008773@smtp1.clb.oleane.net>
From: "peter" <peter.lewis@upperside.fr>
To: <sipping@ietf.org>
Date: Tue, 26 Oct 2004 19:02:34 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcS7fZaBZNSdZGs4SU+hfmT+lQ1BTg==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Subject: [Sipping] WiFi Voice Conference
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="===============0449939577=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0

This is a multi-part message in MIME format.

--===============0449939577==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0081_01C4BB8E.5A8D5B20"

This is a multi-part message in MIME format.

------=_NextPart_000_0081_01C4BB8E.5A8D5B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

- What are the market drivers for VoWLAN? 
- How will VoWLAN systems prioritize and deliver data packets? 
- What are the planning and engineering issues? 
- What about security and privacy? 

At the WiFi Voice Conference to be held in Paris on 10 to 13 May, 2005.
distinguished experts 

and key players in the field will address these questions with detailed and
technical explanations. 

A call for papers is online at:

 <http://www.upperside.fr/wifi05/wifivoice2005intro.htm>
http://www.upperside.fr/wifi05/wifivoice2005intro.htm

 

 


------=_NextPart_000_0081_01C4BB8E.5A8D5B20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns: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=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>- What are the market drivers for VoWLAN? <br>
- How will VoWLAN systems prioritize and deliver data packets? <br>
- What are the planning and engineering issues?&nbsp;<br>
- What about security and privacy?&nbsp;<br>
<br>
At the WiFi Voice Conference to be held in <st1:place =
w:st=3D"on"><st1:City
 w:st=3D"on">Paris</st1:City></st1:place> on <strong><b><font =
face=3DArial><span
style=3D'font-family:Arial'>10 to 13 May, =
2005.</span></font></b></strong>
distinguished experts <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'>and key players in the field will address these
questions with detailed and technical explanations. <br>
<br>
<span class=3Dtextebold>A call for papers </span><span class=3Dtexte>is =
online at:</span><o:p></o:p></span></font></p>

<p class=3DMsoNormal><span class=3Dtexte><font size=3D1 =
face=3DArial><span
style=3D'font-size:9.0pt;font-family:Arial'><a
href=3D"http://www.upperside.fr/wifi05/wifivoice2005intro.htm"
title=3D"http://www.upperside.fr/wifi05/wifivoice2005intro.htm"><font
color=3Dblack><span lang=3DEN-GB =
style=3D'color:windowtext'>http://www.upperside.fr/wifi05/wifivoice2005in=
tro.htm</span></font></a><o:p></o:p></span></font></span></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_0081_01C4BB8E.5A8D5B20--



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




From sipping-bounces@ietf.org  Tue Oct 26 14:44:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02371
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 14:44:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMWWr-0001wy-Fr
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 14:58:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMWFo-0001yv-Ic; Tue, 26 Oct 2004 14:41:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMWDJ-0001WM-QO
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 14:38:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02049
	for <sipping@ietf.org>; Tue, 26 Oct 2004 14:38:32 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMWR1-0001rM-Fi
	for sipping@ietf.org; Tue, 26 Oct 2004 14:52:44 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I670038EFCMD1@dns2.cselt.it> for sipping@ietf.org; Tue,
	26 Oct 2004 20:29:10 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Oct 2004 20:35:02 +0200
Date: Tue, 26 Oct 2004 20:38:00 +0200
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] instance-ID for SIP UA / Device URI
To: "Daniel G. Petrie" <dpetrie@pingtel.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EBC2@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] instance-ID for SIP UA / Device URI
thread-index: AcS7iutHXe8ri60EQ2C4YaByMrTAkQ==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2004 18:35:02.0937 (UTC)
	FILETIME=[81B74890:01C4BB8A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: quoted-printable

Dan,

The sentence that caused my confusion about the GRUU is the following =
(in section 3.13.1 of the configuration framework draft):
  "The approach to defining a user agent instance ID in for GRUU =
[I-D.ietf-sip-gruu] should be considered."
It sounds like the GRUU draft defines a format for the instance ID, =
which is not the case. If you want to leave the reference to the GRUU =
draft, I think this sentence should be changed to explain what is really =
suggested, i.e. that the same instance ID as the one used for GRUU could =
be used to retrieve the device profile.=20
In addition, when recommending to use a URN as the format for the =
instance ID, why not include a non-normative reference to =
draft-mealling-uuid-urn-03 as an example?

Now regarding the hostname of the Device URI, the draft says:=20
  "The host and port portion of the URI are set to that of the domain or =
address of the profile delivery server which manages that user agent."
Does that mean that the default domain corresponds to the domain of the =
device's constructor?

Thanks,
Gabrielle

> -----Original Message-----
> From: Daniel G. Petrie [mailto:dpetrie@pingtel.com]
> Sent: venerd=EC 22 ottobre 2004 20.29
> To: Paul Kyzivat
> Cc: Simonetti Gabrielle; sipping@ietf.org
> Subject: Re: [Sipping] instance-ID for SIP UA

>=20
> Yes the GRUU should not be used as the subscription URI for=20
> configuration. =20
> The instance-id is escaped and used as the user-id portion=20
> when forming the=20
> URI for subscription as described in sections 3.13.1 and 4.1 of=20
> draft-ietf-sipping-config-framework-04.txt  Please let me know how
> I can clarify these sections if they have caused your confusion
> above on applying the instance-id.
>=20
> > What is being suggested is that the gruu mechanism now uses=20
> an instance
> > ID to identify the specific UA that is requesting the gruu, and that
> > that same instance ID could be used to retrieve the=20
> "device" profile.
> >=20
> > I believe the identity and uniqueness properties required by the two
> > applications are the same, so the same id seems appropriate.
> >=20
> >         Paul
> >=20



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

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

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


From sipping-bounces@ietf.org  Tue Oct 26 14:47: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 OAA02553
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 14:47:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMWZp-00022Q-Rc
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 15:01:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMWFr-0001zB-UE; Tue, 26 Oct 2004 14:41:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMWDP-0001Wd-Aa
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 14:38:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02053
	for <sipping@ietf.org>; Tue, 26 Oct 2004 14:38:37 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMWR7-0001rP-3E
	for sipping@ietf.org; Tue, 26 Oct 2004 14:52:49 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I670033IFCSS5@dns2.cselt.it> for sipping@ietf.org; Tue,
	26 Oct 2004 20:29:16 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Oct 2004 20:35:09 +0200
Date: Tue, 26 Oct 2004 20:38:07 +0200
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] Comments on config framework draft- URIs and event
	package parameters
To: "Daniel G. Petrie" <dpetrie@pingtel.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EBC3@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] Comments on config framework draft- URIs and event
	package parameters
thread-index: AcS7iu9QEoP/4BXpTxucGDS0SWzXqw==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2004 18:35:09.0281 (UTC)
	FILETIME=[857F4D10:01C4BB8A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable

Dan,
inline.

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

Let's consider the case where the device profiles are delivered by a =
server within the constructor (that manages the UA versions): the =
constructor might not be aware of the identity of the users using the =
devices. On the contrary, the service provider is the one holding the =
user profiles, and could thus keep an association between instance IDs =
and default AORs. In addition, in some cases, the access provider =
coincides with the service provider... Have you considered including the =
default AOR in the local profile together with the other SIP parameters =
rather than in the device profile?=20


> This is not the only deployment strategey, but it is certainly one
> we want to support.  Other deployment strategies are also supported:
>=20
> 1) preprovisioned UAs which know their default user's AOR.
>=20
> 2) UA's which prompt the user for their AOR
>=20
> Regardless, I think that we still want to make the instance-id
> manditory as the user-id part of the device subscription URI.
> The fact that the profile delivery server may deliver the exact
> same profile to all devices of the same vendor, model and version
> is an implementation choice.  Without the vendor, model, version
> and instance-id the profile delivery server does not have a choice
> to be smart or dumb.
>=20

ok.

Gabrielle




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

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

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


From sipping-bounces@ietf.org  Tue Oct 26 14:50: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 OAA02744
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 14:50:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMWcF-00026d-Sx
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 15:04:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMWFt-0001zH-3F; Tue, 26 Oct 2004 14:41:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMWDb-0001Xq-Jk
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 14:38:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02065
	for <sipping@ietf.org>; Tue, 26 Oct 2004 14:38:49 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMWRJ-0001rV-70
	for sipping@ietf.org; Tue, 26 Oct 2004 14:53:01 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I670033UFD4S5@dns2.cselt.it> for sipping@ietf.org; Tue,
	26 Oct 2004 20:29:28 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 26 Oct 2004 20:35:21 +0200
Date: Tue, 26 Oct 2004 20:38:18 +0200
From: Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>
Subject: RE: [Sipping] Config framework - issue with parameters send in Event
	header
To: Paul Kyzivat <pkyzivat@cisco.com>,
        "Elwell, John" <john.elwell@siemens.com>
Message-id: <E5880434292FCB448F00BDAEE44A60D025EBC4@EXC01C.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: RE: [Sipping] Config framework - issue with parameters send in
	Event header
thread-index: AcS7ivZfS9ML5RE2TLW68v2rUCczdQ==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2004 18:35:21.0312 (UTC)
	FILETIME=[8CAB1600:01C4BB8A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Content-Transfer-Encoding: quoted-printable
Cc: "Daniel G. Petrie" <dpetrie@pingtel.com>, sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable

Providing the parameters in the body of the SUBSCRIBE is a good idea but =
would increase the load on the network, as well as require the =
definition of a new data schema for the SUBSCRIBE body. Why not use the =
User-Agent Header defined in RFC3261 to transport the information about =
the UA originating the request? It can contain several components =
together with their version number (e.g. the Nokia traditional =
User-Agent string used for HTTP: Nokia6600/ 1.0 (4.03.24) SymbianOS/ 6.1 =
Series60/ 2.0 Profile/ MIDP- 2.0 Configuration/ CLDC- 1.0). In this =
case, the order in which the information is set in the header is not =
specified, however the constructor would know how the UA forms the =
header and thus understand the subscribe request for the device profile. =
This header would have to be mandatory in the profile delivery requests.
Gabrielle


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



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

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

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


From sipping-bounces@ietf.org  Tue Oct 26 19:51: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 TAA02509
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 19:51:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMbJn-0003qQ-FW
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 20:05:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMZ1z-0005um-3j; Tue, 26 Oct 2004 17:39:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMYSS-0000Zx-Ey; Tue, 26 Oct 2004 17:02:20 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20945;
	Tue, 26 Oct 2004 17:02:17 -0400 (EDT)
Message-Id: <200410262102.RAA20945@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 26 Oct 2004 17:02:17 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-location-requirements-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: 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		: Requirements for Session Initiation Protocol Location Conveyance
	Author(s)	: J. Polk, B. Rosen
	Filename	: draft-ietf-sipping-location-requirements-02.txt
	Pages		: 47
	Date		: 2004-10-26
	
This document presents the framework and requirements for usage of 
   the Session Initiation Protocol (SIP) to convey user location 
   information from one Session Initiation Protocol (SIP) entity to 
   another SIP entity.  We consider cases where location information is
   conveyed from end to end, as well as cases where message routing by 
   intermediaries is influenced by the location of the session 
   initiator.  We offer a set of solutions to the requirements, based 
   on the scenario(s) being addressed.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-location-requirements-02.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 26 19:52:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02896
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 19:52:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMbLI-0003y8-0C
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 20:07:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMZ2C-0006Hi-Be; Tue, 26 Oct 2004 17:39:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMYTy-0001EL-OH; Tue, 26 Oct 2004 17:03:54 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21391;
	Tue, 26 Oct 2004 17:03:52 -0400 (EDT)
Message-Id: <200410262103.RAA21391@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 26 Oct 2004 17:03:52 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-session-indep-policy-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.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Session-Independent Session Initiation Protocol (SIP) 
			  Policies - Mechanism and Policy Schema
	Author(s)	: V. Hilt, et al.
	Filename	: draft-ietf-sipping-session-indep-policy-01.txt
	Pages		: 24
	Date		: 2004-10-26
	
This draft specifies an XML schema for profile data for SIP
   session-policies.  It defines a delivery mechanism for SIP
   session-policies that are independent of a specific SIP session.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-session-indep-policy-01.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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





From sipping-bounces@ietf.org  Tue Oct 26 20:51:27 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 UAA16300
	for <sipping-web-archive@ietf.org>; Tue, 26 Oct 2004 20:51:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMcFy-0008E0-CO
	for sipping-web-archive@ietf.org; Tue, 26 Oct 2004 21:05:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMbzy-0001qh-QU; Tue, 26 Oct 2004 20:49:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMbrw-0005eA-69
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 20:40:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15121
	for <sipping@ietf.org>; Tue, 26 Oct 2004 20:40:50 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMc5g-0007ot-V2
	for sipping@ietf.org; Tue, 26 Oct 2004 20:55:05 -0400
Received: from zrtpd0j9.us.nortel.com (zrtpd0j9.us.nortel.com [47.140.203.27])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id i9R0e8Q05396; Tue, 26 Oct 2004 20:40:08 -0400 (EDT)
Received: by zrtpd0j9.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <VNLC8X9R>; Tue, 26 Oct 2004 20:40:07 -0400
Message-ID: <1ECE0EB50388174790F9694F77522CCFDF33C7@zrc2hxm0.corp.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Chris Boulton'" <cboulton@ubiquity.net>,
        "'sipping@ietf.org'"
	<sipping@ietf.org>,
        "'jdrosen@dynamicsoft.com'" <jdrosen@dynamicsoft.com>
Subject: RE: [Sipping] Updated NAT scenarios draft
Date: Tue, 26 Oct 2004 20:39:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
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="===============2101625578=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606

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.

--===============2101625578==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4BBBD.7CA2C66C"

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_01C4BBBD.7CA2C66C
Content-Type: text/plain

Hi Chris,

I believe that instead of specifically endorsing TURN as THE media relay 
mechanism, we talk about media relays more generically. We can mention TURN
as an 
example, of a type of media relay as long as we mention the other type
(i.e., a 
B2BUA/SBC approach).

Specifically, I propose rewording section 3.2.3 as follows:



3.2.3  Media Relays

   As mentioned in the previous section, the STUN protocol does not work
   for UDP traversal through a Symmetric style NAT.  Media Relays 
   provide the solution for UDP traversal of symmetric NAT.  

   Media Relays provides an external address and guarantee traffic will 
   reach the associated internal address.

   Two types of media relays exist:

	(1) Media Relays where there is a B2BUA redirecting the 
	    media to Media Relay. 

	    These Media Relays do not require support of any 
	    additional protocol on the SIP UA. A Session
	    Border Controller is an example of such a Media Relay. 

	(2) Media Relays where an explicit protocol is defined between
	    the media endpoint and the Media Relay. 

	    These Media Relays do not require a B2BUA. TURN is an example 
	    of such a protocol. TURN is extremely similar to STUN in both 
	    syntax and operation. The full details of the TURN specification

	    are defined in [10].  

   Media Relays will almost always provide media traffic to a
   SIP entity but it is RECOMMENDED that this method only be used as a
   last resort and not as a general mechanism for NAT traversal.  This
   is because using Media Relays have a high performance costs when 
   relaying media traffic.


-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of Chris Boulton
Sent: Monday, October 25, 2004 04:12
To: sipping@ietf.org
Subject: [Sipping] Updated NAT scenarios draft


All,
            I've just submitted a new version of the NAT scenarios draft.
Until it appears in the archives, it can be found at:

http://www.ubiquitysoftware.com/ietf/draft-ietf-sipping-nat-scenarios-01.txt


This document has a new start and so is still in its very early stages.  I
have submitted to let you folks take a look and comment on the direction -
the detail will be consolidated in the next version which will be polished.
Please could you take a look and comment on the new direction + suggest any
future call scenarios that you would like to see included (that are not
currently listed in the index).

Best Regards,

Chris.




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
agreed in writing, nothing stated in this communication shall be legally
binding.

------_=_NextPart_001_01C4BBBD.7CA2C66C
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [Sipping] Updated NAT scenarios draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Chris,</FONT>
</P>

<P><FONT SIZE=3D2>I believe that instead of specifically endorsing TURN =
as THE media relay </FONT>
<BR><FONT SIZE=3D2>mechanism, we talk about media relays more =
generically. We can mention TURN as an </FONT>
<BR><FONT SIZE=3D2>example, of a type of media relay as long as we =
mention the other type (i.e., a </FONT>
<BR><FONT SIZE=3D2>B2BUA/SBC approach).</FONT>
</P>

<P><FONT SIZE=3D2>Specifically, I propose rewording section 3.2.3 as =
follows:</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>3.2.3&nbsp; Media Relays</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; As mentioned in the previous section, =
the STUN protocol does not work</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; for UDP traversal through a Symmetric =
style NAT.&nbsp; Media Relays </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; provide the solution for UDP traversal =
of symmetric NAT.&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Media Relays provides an external =
address and guarantee traffic will </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; reach the associated internal =
address.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Two types of media relays exist:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>(1) Media =
Relays where there is a B2BUA redirecting the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; media to Media Relay. </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; These Media Relays do not require support =
of any </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; additional protocol on the SIP UA. A =
Session</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; Border Controller is an example of such a =
Media Relay. </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>(2) Media =
Relays where an explicit protocol is defined between</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; the media endpoint and the Media Relay. =
</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; These Media Relays do not require a B2BUA. =
TURN is an example </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; of such a protocol. TURN is extremely =
similar to STUN in both </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; syntax and operation. The full details of =
the TURN specification </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; are defined in [10].&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Media Relays will almost always provide =
media traffic to a</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; SIP entity but it is RECOMMENDED that =
this method only be used as a</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; last resort and not as a general =
mechanism for NAT traversal.&nbsp; This</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; is because using Media Relays have a =
high performance costs when </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; relaying media traffic.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: sipping-bounces@ietf.org [<A =
HREF=3D"mailto:sipping-bounces@ietf.org">mailto:sipping-bounces@ietf.org=
</A>] On Behalf Of Chris Boulton</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, October 25, 2004 04:12</FONT>
<BR><FONT SIZE=3D2>To: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Sipping] Updated NAT scenarios =
draft</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>All,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; I've just submitted a new version of the NAT scenarios draft.&nbsp; =
Until it appears in the archives, it can be found at:</FONT></P>

<P><FONT SIZE=3D2><A =
HREF=3D"http://www.ubiquitysoftware.com/ietf/draft-ietf-sipping-nat-scen=
arios-01.txt" =
TARGET=3D"_blank">http://www.ubiquitysoftware.com/ietf/draft-ietf-sippin=
g-nat-scenarios-01.txt</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>This document has a new start and so is still in its =
very early stages.&nbsp; I have submitted to let you folks take a look =
and comment on the direction - the detail will be consolidated in the =
next version which will be polished.&nbsp; Please could you take a look =
and comment on the new direction + suggest any future call scenarios =
that you would like to see included (that are not currently listed in =
the index).</FONT></P>

<P><FONT SIZE=3D2>Best Regards,</FONT>
</P>

<P><FONT SIZE=3D2>Chris.</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>This email and any attached files are confidential =
and copyright protected.&nbsp; If you are not the addressee, any =
dissemination, distribution or copying of this communication is =
strictly prohibited.&nbsp; Unless otherwise expressly agreed in =
writing, nothing stated in this communication shall be legally =
binding.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4BBBD.7CA2C66C--


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



From sipping-bounces@ietf.org  Wed Oct 27 11:03: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 LAA11902
	for <sipping-web-archive@ietf.org>; Wed, 27 Oct 2004 11:03:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMpYr-0007MY-Hd
	for sipping-web-archive@ietf.org; Wed, 27 Oct 2004 11:18:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMpG2-0003vT-Qs; Wed, 27 Oct 2004 10:58:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMpDa-0003Q6-Nn
	for sipping@megatron.ietf.org; Wed, 27 Oct 2004 10:56:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11228
	for <sipping@ietf.org>; Wed, 27 Oct 2004 10:56:04 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMpRT-0007AV-Cx
	for sipping@ietf.org; Wed, 27 Oct 2004 11:10:27 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 27 Oct 2004 10:55:31 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9REtSWT001457
	for <sipping@ietf.org>; Wed, 27 Oct 2004 10:55:28 -0400 (EDT)
Received: from cisco.com ([161.44.79.201]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id AMP16173; Wed, 27 Oct 2004 10:55:27 -0400 (EDT)
Message-ID: <417FB6DE.5020508@cisco.com>
Date: Wed, 27 Oct 2004 10:55:26 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
References: <200410252007.QAA00092@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: draft-ietf-sipping-callerprefs-usecases-03.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: 7bit

A new version of draft-ietf-sipping-callerprefs-usecases is now 
available on the server. There are no dramatic changes here - just 
cleaning it up for completion. The following changes have been made in 
this version:

- changes made to how the "message" feature param is referenced.
   (To "+sip.message) This is due to an oversight discovered in
   RFC 3840.

- use of "sip.extensions" was corrected (to "+sip.extensions")

- The "UA Routing" case has been removed. It was never a great
   example, and now GRUU provides a much better alternative.

- references updated

- a new section has been added, providing some implementation guidance
   on how the matching algorithm could be implemented.

- extra explanation provided about use of require and explicit tags.

- an alternative solution provided for the "Prefer Voicemail" case.

- q-value changed in "Mobile Phone Only" case to make the cae
   more sensible.

- Some text has ben added to the "Usage of the Feature Tags"
   section, replacing an OPEN ISSUE.

- some editorial notes removed.

- The TODO section has been removed. (I believe everything in
   it has been done.)

I think this is about ready for WGLC.

	Paul

Internet-Drafts@ietf.org wrote:
> 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		: Guidelines for Usage of the Session Initiation 
> 			  Protocol (SIP) Caller Preferences Extension
> 	Author(s)	: J. Rosenberg, P. Kyzivat
> 	Filename	: draft-ietf-sipping-callerprefs-usecases-03.txt
> 	Pages		: 43
> 	Date		: 2004-10-25
> 	
> This document contains guidelines for usage of the Caller Preferences
> Extension to the Session Initiation Protocol (SIP). It motivates the
> benefits of caller preferences with specific example applications,
> provides use cases to show proper operation, provides guidance on the
> applicability of the registered feature tags, and describes a
> straightforward implementation of the matching algorithm.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-callerprefs-usecases-03.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-callerprefs-usecases-03.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-callerprefs-usecases-03.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.
> 
> -------------------------------------------------------------------------
> 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.
> 
> 
> -------------------------------------------------------------------------
> 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: i9PNCZTM024964
> 
> 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
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 27 11:36: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 LAA16121
	for <sipping-web-archive@ietf.org>; Wed, 27 Oct 2004 11:36:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMq4Q-0008TP-TB
	for sipping-web-archive@ietf.org; Wed, 27 Oct 2004 11:50:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMpnI-000775-21; Wed, 27 Oct 2004 11:33:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMpWp-0002xz-2v
	for sipping@megatron.ietf.org; Wed, 27 Oct 2004 11:15:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13548
	for <sipping@ietf.org>; Wed, 27 Oct 2004 11:15:56 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMpkh-0007jg-Jk
	for sipping@ietf.org; Wed, 27 Oct 2004 11:30:20 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 27 Oct 2004 08:24:32 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9RFFN6s010695;
	Wed, 27 Oct 2004 08:15:23 -0700 (PDT)
Received: from [10.32.245.154] (stealth-10-32-245-154.cisco.com
	[10.32.245.154])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id i9RFGu65031392;
	Wed, 27 Oct 2004 08:16:57 -0700
In-Reply-To: <4DC4BB43EDC35Aono.kumiko@lab.ntt.co.jp>
References: <4DC4BB43EDC35Aono.kumiko@lab.ntt.co.jp>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <0213A6EA-282B-11D9-BDDE-000A95C73842@cisco.com>
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] e2m security open issue: label for the target body
Date: Wed, 27 Oct 2004 11:15:16 -0400
To: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
X-Pgp-Agent: GPGMail 1.0.2
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1098890220.451825"; x:"432200"; a:"rsa-sha1"; b:"nofws:5876";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"mvJS00V3X6jwpS/Wqg6XM5tMZC9BuHdmdKhGk8GfAqfzzuIGqXct1/SGQo6P8"
	"iaFufF4UWFYwzwRrcNbghmt1osjFfOoZ0cP41N2D6ixp/ofpBLDKwrjtAViGZ"
	"qnsmE7pSdjjYYNxDqLtry3ttjfjl+I2OtN6ARURSEqciDFl1w=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] e2m security open issue: label for the target
	b" "ody"; c:"Date: Wed, 27 Oct 2004 11:15:16 -0400"
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: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2136016592=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5


--===============2136016592==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-2-323832665"


--Apple-Mail-2-323832665
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for a cogent analysis and the time to investigate the options. I 
find your conclusion to use SIP rather than MIME headers persuasive and 
agree with it.

In addition to the reasons cited I would add two:
1) Modifying MIME seems less attractive because we are not solving a 
MIME problem here - it's a SIP problem. The MIME guys would have ??? 
over their heads as to why MIME would need this functionality.

2) The integrity issues cited about using unprotected SIP headers to 
indicate which bodies to process don't strike me as a problem in 
practice. There are two cases: (a)changing/removing the SIP header so 
that a proxy that should process a MIME body doesn't, and 
(b)adding/changing a SIP header so that proxy that shouldn't process 
the header does.

In case (a) no security is violated since the only reason the proxy 
should look at the body is because the UA *wants* it to - if the body 
isn't processed the UA might not get some service it otherwise would 
get, and/or  the request might fail because of that. This represents a 
DoS attack, but such an attack could be trivially mounted by just 
scribbling on the MIME body itself. In case (b) nothing bad happens 
functionally, but as you point out the proxy/proxies are coerced into 
doing extra work for no reason. Since there are probably about 100 
other ways to make proxies do extra work this one seems no more 
troublesome.

There is a minor issue of detectability of the attack, but I'm not 
convinced that is worth worrying about to the extent of the bother and 
overhead of using SIPFRAG.

Between option A-1 and A-2 I find A-2 (add content-ids to route header) 
more elegant. Hovever, we've had discussions in the past about whether 
extending the Route header for other things might cause 
backward-compatibility issues and avoided it on that basis. It might be 
good to poll the implementers to look at their route header handling 
code to gauge the practical impact.

Thanks and regards, Dave.


On Oct 26, 2004, at 6:09 AM, Kumiko Ono wrote:

> Hi,
>
> I've submitted an update draft of the e2m security mechanism 
> (http://www.
> ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-03.txt).
> There are two major open issues on the mechanism of end-to-middle
> security. I would like to hear your opinions on these.
>
> Open issue#1: How to label the target body.
>
> In order for a proxy server to easily determine whether to process MIME
> bodies and which one, UA needs a way to label the body targeted at a
> particular proxy server(s).
>
> After receiving many comments at the last IETF meeting about this, I
> gave it some thought and came up with some conclusion, so I want to
> share with you my preference in accomplishing the labeling and the
> reason behind my preference.
>
> Options for labeling:
> A-1. a new SIP header, i.e.: "Proxy-Required-Body".
> A-2. a new parameter in a SIP header, i.e.: "content-id" param in 
> "Route"
> header.
> B-1. a new MIME header, i.e.: "Content-Target".
> B-2. a new parameter in a MIME header, i.e.: "required-entity" param in
> "Content-Disposition".
>
> When a message has a target body destined for a proxy server, MIME
> header options (B) shows a greater performance than SIP header options
> (A) in searching the target body. This is because options A require the
> inspection of the SIP header and "Content-ID" MIME header, while 
> options
> B only require the inspection of the MIME header.
>
> When a message has no target body destined for a proxy server, it is
> easier for SIP header options (A) to determine that fact, as it only
> needs to look at the SIP header.
>
> However, if integrity protection of the label is required, inner 
> headers
> need to be created using sipfrag attached with a signature. And the
> validation of the signature would reduce the advantage of the ease in
> determining the needs to search the body. If the security level of the
> label is considered to be the same as that of routing headers, use of
> TLS would satisfy the integrity requirements which will allow the SIP
> header options (A) to retain their advantage.
>
> Since few of messages in all the traffic through a proxy server will
> likely utilize e2m security, the ease in determining the needs to 
> search
> the body overweighs the performance in searching the target body.
> Therefore, I changed the proposed option, from MIME header options to
> SIP headers. Since a new parameter in Route header has more impact on a
> proxy server, I believe Option A-1, with a new SIP header the best
> choice.
>
> Your feedback is very welcome.
>
> Thanks in advance,
> Kumiko
> --
> Kumiko Ono
> NTT Network Service Systems Labs.
> Tel +81 422 59 4508/Fax +81 422 60 4012
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com

--Apple-Mail-2-323832665
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFBf7uFjWaEtlTdKuYRAq29AJ4msN2DXOSiEPc3veUtMXfjkeVxOQCfc/ve
7S0q0IRs8oFX+P3lpLjIYAM=
=8WGr
-----END PGP SIGNATURE-----

--Apple-Mail-2-323832665--



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




From sipping-bounces@ietf.org  Wed Oct 27 11:43: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 LAA16718
	for <sipping-web-archive@ietf.org>; Wed, 27 Oct 2004 11:43:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMqBJ-0000A8-Gu
	for sipping-web-archive@ietf.org; Wed, 27 Oct 2004 11:57:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMpnK-00078W-6v; Wed, 27 Oct 2004 11:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMpYY-0003Pm-1V
	for sipping@megatron.ietf.org; Wed, 27 Oct 2004 11:17:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13771
	for <sipping@ietf.org>; Wed, 27 Oct 2004 11:17:43 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMpmQ-0007ni-1b
	for sipping@ietf.org; Wed, 27 Oct 2004 11:32:07 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 27 Oct 2004 08:26:18 -0700
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 i9RFGxYJ016498;
	Wed, 27 Oct 2004 08:16:59 -0700 (PDT)
Received: from [10.32.245.154] (stealth-10-32-245-154.cisco.com
	[10.32.245.154])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id i9RFIheG031399;
	Wed, 27 Oct 2004 08:18:46 -0700
In-Reply-To: <4FC4BB43FC59F9ono.kumiko@lab.ntt.co.jp>
References: <4FC4BB43FC59F9ono.kumiko@lab.ntt.co.jp>
Mime-Version: 1.0 (Apple Message framework v619)
Message-Id: <41C93B42-282B-11D9-BDDE-000A95C73842@cisco.com>
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] e2m security open issue: notification with error codes
Date: Wed, 27 Oct 2004 11:17:03 -0400
To: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
X-Pgp-Agent: GPGMail 1.0.2
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1098890327.157843"; x:"432200"; a:"rsa-sha1"; b:"nofws:2933";
	e:"Iw==";
	n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"bD9/l2BKIUzoWs9Wlz8qasO+JuY6nNFiqbbFSOJuQdGijR7Fb2DakSmpfQbTl"
	"wQgoycLayBZl1asGbJCL6triS+QE4s3trV8cIOEd6DD3+9TJxq0bfw0fV1k5X"
	"20GFK611wl3VUVJPiQ3MAmCO6XINzrUfsXddMXtGJv61otzY8=";
	c:"From: David R Oran <oran@cisco.com>";
	c:"Subject: Re: [Sipping] e2m security open issue: notification with
	erro" "r codes"; c:"Date: Wed, 27 Oct 2004 11:17:03 -0400"
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: b7b9551d71acde901886cc48bfc088a6
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1917140923=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5


--===============1917140923==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-3-323939437"


--Apple-Mail-3-323939437
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

Again, good description and analysis. I agree with your conclusion.
Dave.

On Oct 26, 2004, at 6:10 AM, Kumiko Ono wrote:

> Hi,
>
> Here is the second issue on mechanism of e2m security.
>
> Open Issue#2: How does a proxy server notify the needs of end-to-middle
> security to the UAC by using error codes?
>
> After discussion with some of the WG member, and giving some thought on
> how UAC might realize the need of e2m security utilization, I realized
> that proxy should have a way to notify the UAC about e2m security
> utilization in addition to using UAC driven method, such as session
> policy package.
>
> There are two cases where a proxy server needs a UAC to utilize
> end-to-middle security in its communication.
> 1) When the proxy server needs to view an encrypted data sent by UAC. 
> We
> can say this case to be somewhat of a security downgrading and it
> requires end-to-middle confidentiality.
> 2) When the proxy server needs to validate the data integrity of the
> message. We can say this to be somewhat of a security upgrading, and it
> requires end-to-middle integrity.
> In both cases, the information for notification (error codes) to UAC
> should include the case (reason) and target content type.
>
> Looking at pre-existing error codes, "493 Undecipherable" can be
> utilized for the first case as it means that peer requires the
> capability to decrypt. However, there are no error codes that indicate
> its requirement to carry out an integrity validation.
> I think we need a new error code, such as "495 Signature required" for
> clarification. Also as stated above, I think that the target content
> type should be described in Warning header.
>
> Your feedback is very welcome.
>
> Thanks in advance,
> Kumiko
> --
> Kumiko Ono
> NTT Network Service Systems Labs.
> Tel +81 422 59 4508/Fax +81 422 60 4012
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com

--Apple-Mail-3-323939437
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFBf7vvjWaEtlTdKuYRAoLhAJ46mMK2Z46KUazAy9/kQYh5RFlMHACgg4qQ
jRM12fjjqBUemIUTOXZqdLs=
=+dJa
-----END PGP SIGNATURE-----

--Apple-Mail-3-323939437--



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




From sipping-bounces@ietf.org  Thu Oct 28 08:44: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 IAA08077
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 08:44:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CN9rX-0008Rg-A9
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 08:58:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CN9cL-0003On-9z; Thu, 28 Oct 2004 08:43:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CN9bP-0003Eq-Io
	for sipping@megatron.ietf.org; Thu, 28 Oct 2004 08:42:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07965
	for <sipping@ietf.org>; Thu, 28 Oct 2004 08:42:03 -0400 (EDT)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN9pI-0008Pu-2E
	for sipping@ietf.org; Thu, 28 Oct 2004 08:56:36 -0400
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	i9SCfoR2032330
	for <sipping@ietf.org>; Thu, 28 Oct 2004 14:41:50 +0200
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 28 Oct 2004 14:41:49 +0200
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id VSV6VKQ2; Thu, 28 Oct 2004 14:41:49 +0200
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.59])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 1C51E18AAA; Thu, 28 Oct 2004 15:41:49 +0300 (EEST)
Message-ID: <4180E90C.1010408@ericsson.com>
Date: Thu, 28 Oct 2004 15:41:48 +0300
X-Sybari-Trust: bb06e86b bfd556f1 a08104cf 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Agenda requests for DC
References: <4164EAE8.1090105@ericsson.com>
In-Reply-To: <4164EAE8.1090105@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Oct 2004 12:41:49.0948 (UTC)
	FILETIME=[7E894BC0:01C4BCEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Folks,

our agenda needs to be ready by November 1st. If you have not sent us 
your agenda request yet, do so NOW!

These are the agenda requests received so far:
http://www.softarmor.com/sipping/meets/ietf61/requests.html

If you did send us your agenda request, but you cannot find it in the 
web page above, you should seriously consider sending it again ;o)

Regards,

Gonzalo


Gonzalo Camarillo wrote:

> Folks,
> 
> we will be gathering agenda requests for the SIPPING meeting in 
> Washington DC under the following link:
> 
> http://www.softarmor.com/sipping/meets/ietf61/requests.html
> 
> As usual, if you use the template provided at the end of this email to
> submit your agenda request, it will make this task easier. Agenda
> requests are submitted in an email addressed to the chairs.
> 
> Regarding the requests we will be accepting and rejecting, we intend to 
> use a large part of the meeting to discuss issues related to WG items, 
> as we did in the last meeting. We will only discuss individual 
> contributions that have received considerable attention since the last 
> meeting.
> 
> 
>     <tr>
>       <td><a href="mailto:Gonzalo.Camarillo@ericsson.com">
> Gonzalo Camarillo</a></td>
>       <td>Exploders</td>
>       <td><center>5</center></td>
>       <td>
> <a
> href="http://www.ietf.org/internet-drafts/draft-camarillo-sipping-exploders-02.txt"> 
> 
> draft-camarillo-sipping-exploders-02.txt</a></td>
>     </tr>
> 
> 
> Thanks,
> 
> Gonzalo
> SIPPING co-chair
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 28 08:55: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 IAA09069
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 08:55:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNA2U-0000Hc-Jk
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 09:10:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CN9k8-000517-Oo; Thu, 28 Oct 2004 08:51:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CN9jj-0004pk-H8
	for sipping@megatron.ietf.org; Thu, 28 Oct 2004 08:50:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08518
	for <sipping@ietf.org>; Thu, 28 Oct 2004 08:50:38 -0400 (EDT)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN9xa-00008A-1U
	for sipping@ietf.org; Thu, 28 Oct 2004 09:05:12 -0400
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
	i9SCoNWR017663
	for <sipping@ietf.org>; Thu, 28 Oct 2004 14:50:23 +0200 (MEST)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 28 Oct 2004 14:50:23 +0200
Received: from mail.lmf.ericsson.se (dossier.lmf.ericsson.se [131.160.11.13])
	by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id VJSLZ44J; Thu, 28 Oct 2004 14:50:23 +0200
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.37.59])
	by mail.lmf.ericsson.se (Postfix) with ESMTP
	id 1A56E18AA9; Thu, 28 Oct 2004 15:50:23 +0300 (EEST)
Message-ID: <4180EB0E.7060406@ericsson.com>
Date: Thu, 28 Oct 2004 15:50:22 +0300
X-Sybari-Trust: b93b20dd bfd556f1 a08104cf 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Oct 2004 12:50:23.0775 (UTC)
	FILETIME=[B0CD12F0:01C4BCEC]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>, Eric Burger <eburger@brooktrout.com>,
        mdolly@att.com, Dean Willis <dean.willis@softarmor.com>
Subject: [Sipping] WGLC: KPML
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: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

Folks,

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

http://www.ietf.org/internet-drafts/draft-ietf-sipping-kpml-06.txt

This WGLC will finish on November 20th. Please, send you comments to the 
authors and to the list.

Thanks,

Gonzalo



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


From sipping-bounces@ietf.org  Thu Oct 28 10:23:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16542
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 10:23:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNBPm-0002JB-Rh
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 10:38:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNB5y-0000xi-BD; Thu, 28 Oct 2004 10:17:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNB2V-0008Gl-3k
	for sipping@megatron.ietf.org; Thu, 28 Oct 2004 10:14:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15711
	for <sipping@ietf.org>; Thu, 28 Oct 2004 10:14:06 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNBGZ-00029A-HT
	for sipping@ietf.org; Thu, 28 Oct 2004 10:28:41 -0400
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9SEDpl24357; Thu, 28 Oct 2004 17:13:52 +0300 (EET DST)
X-Scanned: Thu, 28 Oct 2004 17:13:31 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i9SEDVpl020961;
	Thu, 28 Oct 2004 17:13:31 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00Q7gyAQ; Thu, 28 Oct 2004 17:13:29 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9SEDPS19421; Thu, 28 Oct 2004 17:13:25 +0300 (EET DST)
Received: from esebe017.NOE.Nokia.com ([172.21.138.56]) by
	esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 28 Oct 2004 17:12:43 +0300
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by
	esebe017.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 28 Oct 2004 17:12:43 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Comments on config framework draft
Date: Thu, 28 Oct 2004 17:12:43 +0300
Message-ID: <5816828233DEFA41807A6CFDFDF2343C3A8BD8@esebe056.ntc.nokia.com>
Thread-Topic: [Sipping] Comments on config framework draft
Thread-Index: AcS44EYjCncMvalSRS+f6ZYhEGcnuAEFhu9A
To: <dpetrie@pingtel.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 28 Oct 2004 14:12:43.0962 (UTC)
	FILETIME=[3161C9A0:01C4BCF8]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable



> -----Original Message-----
> From: ext Daniel G. Petrie [mailto:dpetrie@pingtel.com]
> Sent: 23.October.2004 12:11
> To: Khartabil Hisham (Nokia-TP-MSW/Helsinki); sipping@ietf.org
> Subject: RE: [Sipping] Comments on config framework draft
>=20
>=20
> > Section 3.7
> > ------------
> >=20
> > - "A user agent can provide hotelling by collecting a user=CBs AOR =
and
> >    credentials needed to SUBSCRIBE and retrieve the user's profiles.
> >    hotelling functionality is achieved by subscribing to=20
> the user's AOR
> >    and specifying the "user" profile type.  This same=20
> mechanism can also
> >    be used to secure a user agent, requiring a user to=20
> login to enable
> >    functionality beyond the default user=CBs restricted=20
> functionality."
> >=20
> > Again, the user's AOR should not be explicitly required by=20
> the server. After authentication, the server should be able=20
> to deduce the user's AoR from some DB.
>=20
> Sorry, I am not following this.  The AOR is needed by the=20
> user agent so
> that it can set the URI for the SUBSCRIBE for the user=20
> profile.  This is
> in the case where the user agent either does not have a=20
> default user or
> someone other than the default user wishes to have their user profile
> effective on the user agent.

I misunderstood this one. I thought the user has to supply its AOR to =
the server using some parameter in the event header. Just ignore.

>=20
> >=20
>=20
>=20
> >=20
> > Section 3.13.3
> > --------------
> >=20
> > - about placing an "anonymous" user name. Why isn't=20
> sip:example.com enough (no user part)? If user part is=20
> present, it MUST be ignored.
>=20
> Doesn't what you suggest require a change to the way location services
> provided through proxies and redirect servers work.  A=20
> special user name
> seems like a lower impact, easier to implement change.

Not really. A server should understand the context in which the =
subscription is being made and need to rely on username for anything. =
You are subscribing to the server afterall and the request-uri carries =
the resource you are subscribing to.

/Hisham

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 28 15:04: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 PAA17767
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 15:04:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNFnY-0004vo-71
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 15:19:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNCmg-0005oi-Nn; Thu, 28 Oct 2004 12:05:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNBvy-0000yF-VT; Thu, 28 Oct 2004 11:11:27 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23452;
	Thu, 28 Oct 2004 11:11:25 -0400 (EDT)
Message-Id: <200410281511.LAA23452@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, 28 Oct 2004 11:11:25 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-kpml-06.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 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-06.txt
	Pages		: 54
	Date		: 2004-10-27
	
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-06.txt

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


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

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


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

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

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

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

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

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

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

Content-Type: text/plain
Content-ID: <2004-10-28110329.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 Oct 28 15:04: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 PAA17880
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 15:04:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNFny-0004xL-67
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 15:19:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNCmh-0005rT-Mi; Thu, 28 Oct 2004 12:05:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNBwD-00017d-V6; Thu, 28 Oct 2004 11:11:41 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23481;
	Thu, 28 Oct 2004 11:11:40 -0400 (EDT)
Message-Id: <200410281511.LAA23481@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, 28 Oct 2004 11:11:40 -0400
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-nat-scenarios-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.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		: Best Current Practices for NAT Traversal for SIP
	Author(s)	: C. Boulton, J. Rosenberg
	Filename	: draft-ietf-sipping-nat-scenarios-01.txt
	Pages		: 25
	Date		: 2004-10-27
	
Traversal of the Session Initiation Protocol (SIP) and the sessions
   it establishes through Network Address Translators (NAT) is a complex
   problem.  Currently there are many deployment scenarios and traversal
   mechanisms for media traffic.  This document aims to provide concrete
   recommendations and a unified method for NAT traversal as well as
   documenting corresponding call flows.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-nat-scenarios-01.txt

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

Content-Type: text/plain
Content-ID: <2004-10-28110335.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 Oct 28 19:19: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 TAA08363
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 19:19:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNJm6-0002mZ-M7
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 19:33:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNGYJ-0006rc-H8; Thu, 28 Oct 2004 16:07:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNEo2-0003KD-DN
	for sipping@megatron.ietf.org; Thu, 28 Oct 2004 14:15:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06939
	for <sipping@ietf.org>; Thu, 28 Oct 2004 14:15:25 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNF28-0001Ll-JM
	for sipping@ietf.org; Thu, 28 Oct 2004 14:30:01 -0400
Received: from [63.110.3.195] ([63.110.3.195]) (authenticated bits=0)
	by nylon.softarmor.com (8.12.11/8.12.11) with ESMTP id i9SIFbdO001550
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Oct 2004 13:15:38 -0500
Message-ID: <41813716.1050109@softarmor.com>
Date: Thu, 28 Oct 2004 13:14:46 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?UTF-8?B?7Zmp7KeE6rK9?= <jkhwang@kt.co.kr>
Subject: Re: [Sipping] automatic answer
References: <41062F5D.9040101@eresmas.net>
	<019501c4adac$572a8100$71090693@ROMEO>
In-Reply-To: <019501c4adac$572a8100$71090693@ROMEO>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by nylon.softarmor.com id
	i9SIFbdO001550
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable

=ED=99=A9=EC=A7=84=EA=B2=BD (Jinkyung Hwang) wrote:

> Hi,
> =20
> Is there any I-D regarding params for SIP phone to answer=20
> automatically ? (for answering machine functionality)
> =20
> I would like to know when the call arrives a phone, by which=20
> param/header value the phone answers without ringing.
> =20
> =20

This generally isn't something that is signaled to the answering=20
machine, it's just something the answering machine does because it KNOWS=20
it's an answering machine.

Remember, SIP isn't about network control of edge devices. Rather, it is=20
about how a bunch of edge devices can find and engage each other in an=20
appropriate  and useful manner.

The routing infrastructure and the calling party generally don't know=20
that a specific device is an answering machine. They know that it's a=20
possible endpoint, and they MAY know something about previous routing=20
attempts or decisions made elsewhere in the network. Consequently,=20
having them insert some sort of special parameter to make the device=20
"act like an answering machine" is probably inappropriate.

For example, I sometimes use an Asterisk box to provide voice-mail=20
services for my SIP phone. No special paramters or singaling are sent=20
from my proxy to the Asterisk box to invoke it. Instead, it REGISTERs to=20
my AOR just like all my other SIP endpoints. But rather than answering=20
immediately on receiving a 200 OK, it is configured to wait ten seconds.=20
Consequently, if I answer at one of my SIP phones in a timely fashion,=20
the Asterisk VM is never connected, but if I don't answer, it picks up=20
the call.


That being said, they are two places that useful information might be=20
conveyed.

If the asnwering machine is being reached as a result of a call=20
forwarding action performed by a proxy (perhaps as a result of a CPL=20
script), then the URI for the answering machine can be constructed and=20
configured into the forwarding proxy to convey meaningful information,=20
which MIGHT include device-specific parameters. This approach is=20
dicsussed in Cullen Jenning's draft,  draft-jennings-sip-voicemail-uri-03.

Another possibility would be for the call-forwarding action to be=20
presented in the request delivered to the answering machine in the=20
format specified by the history-info document that I announced a=20
working-group last call on earlier today. While this may be useful for=20
certain PSTN-interaction cases, I personally find it an unattractive=20
approach for implementing general-purpose voice mail solutions of the=20
kind I described above.

--
Dean



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
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 Oct 28 22:23:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23503
	for <sipping-web-archive@ietf.org>; Thu, 28 Oct 2004 22:23:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNMed-0008R8-48
	for sipping-web-archive@ietf.org; Thu, 28 Oct 2004 22:38:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNK28-0006z2-Dh; Thu, 28 Oct 2004 19:50:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNIGS-0002ac-9g
	for sipping@megatron.ietf.org; Thu, 28 Oct 2004 17:57:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22130
	for <sipping@ietf.org>; Thu, 28 Oct 2004 17:56:55 -0400 (EDT)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNIUY-0006cE-IS
	for sipping@ietf.org; Thu, 28 Oct 2004 18:11:35 -0400
Received: from [10.10.108.16] ([65.119.52.228]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id i9SLuk3w062349
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO);
	Thu, 28 Oct 2004 16:56:47 -0500 (CDT) (envelope-from ben@nostrum.com)
In-Reply-To: <416F538A.1050508@dynamicsoft.com>
References: <416F538A.1050508@dynamicsoft.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3FA3EB92-292C-11D9-BD18-000D93B0AE1A@nostrum.com>
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
Subject: Re: [Sipping] What problems are SBCs addressing?
Date: Thu, 28 Oct 2004 16:56:40 -0500
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
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: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit

Apologies if this one has already been mentioned, but if I am reading 
it correctly,  the "session" privacy mode in rfc3323 seems to imply 
something that looks a lot like an SBC.

On Oct 14, 2004, at 11:35 PM, Jonathan Rosenberg wrote:

> Folks,
>
> As many of you know, there are a large number of products on the 
> market these days under the general moniker "Session Border 
> Controller"; generally these are B2BUas that play some kind of policy 
> enforcement and control function, typically at trust boundaries.
>
> Our specifications don't define how B2BUas should operate, and they 
> say nothing at all about an SBC (although they do address many 
> problems that relate to inter-domain operations and trust boundaries). 
> However, the preponderence of these devices in the market and in VoIP 
> networks seems to indicate that there are real problems that providers 
> believe they have, which they feel these products are solving for 
> them.
>
> This begs the important question - what are those problems, and are 
> those problems for which the IETF has produced specifications to 
> address? If not, is there a need to do so? If yes, are these products 
> using those specifications, and if not, why have those solutions not 
> seen implementation and/or deployment?
>
> Put in another way, sipping is all about requirements and problems, 
> and it is clear that there are one or more problems here somewhere. Do 
> we understand those requirements, and do we need to produce 
> specifications to address them?
>
> This is a fairly meaty topic, one for which I expect to see lots of 
> emails in reply to this note suggesting answers ;) Furthermore, we are 
> planning an informal get together at IETF 61 to continue the dialog, 
> focusing squarely on understanding requirements and specification 
> gaps. Details TBA shortly. Whether one likes the solutions that are 
> out there or not, the first step in doing anything is to understand 
> the requirements. I really want to do that.
>
> I think it's important to have this discussion now, while there is 
> still time to address these issues with standards-based solutions. To 
> paraphrase Spencer Dawkins' recent note - I don't want to have a BoF 
> session three years hence called "son-of-behave", where we discuss 
> what an SBC should do, wishing that we had written specifications 
> three years earlier and thus avoided the interop mess that had 
> resulted. Given the recent concerns about GRUU and SIP identity 
> operation through SBC, this is even more telling.
>
> Inputs from people who work for vendors of such devices, your input is 
> most welcome..
>
> Thanks,
> Jonathan R.
>
> -- 
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 29 03:12: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 DAA00969
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 03:12:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNR9u-00076L-RX
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 03:26:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNQdC-0001RX-8U; Fri, 29 Oct 2004 02:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CJq60-00072T-Aa
	for sipping@megatron.ietf.org; Tue, 19 Oct 2004 05:15:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03950
	for <sipping@ietf.org>; Tue, 19 Oct 2004 05:15:49 -0400 (EDT)
Received: from natnoddy.rzone.de ([81.169.145.166])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJqI5-0008Ao-Pf
	for sipping@ietf.org; Tue, 19 Oct 2004 05:28:26 -0400
Received: from snom.de (pD951647E.dip.t-dialin.net [217.81.100.126])
	by post.webmailer.de (8.13.1/8.13.1) with ESMTP id i9J9FXYb027951;
	Tue, 19 Oct 2004 11:15:37 +0200 (MEST)
Subject: RE: [SIPPING] automatic answer
MIME-Version: 1.0
Content-class: urn:content-classes:message
Date: Tue, 19 Oct 2004 11:18:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <B52FDDEC7CBE9D40B36FE900C9AD78B4125A11@merenge.intern.snom.de>
Thread-Topic: [SIPPING] automatic answer
thread-index: AcS1oylB7X4O+oBkRvmR+gHx52GwLQAF5lTA
From: "Christian Stredicke" <Christian.Stredicke@snom.de>
To: =?ks_c_5601-1987?B?yLLB+LDm?= <jkhwang@kt.co.kr>, <sipping@ietf.org>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
X-Mailman-Approved-At: Fri, 29 Oct 2004 02:52:58 -0400
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="===============1004895050=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 1.5 (+)
X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b

This is a multi-part message in MIME format.

--===============1004895050==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4B5BC.9E643364"
Content-class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4B5BC.9E643364
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

As far as I know there is a vendors that sends such headers:
INVITE sip:abc SIP/2.0
From: <sip:a@domain>
To: <sip:b@domain>
Call-Info: <sip:b@domain>;answer-after=3D0

We challenge that request because of the security implications.

CS


________________________________

	From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On =
Behalf Of ???
	Sent: Tuesday, October 19, 2004 2:16 PM
	To: sipping@ietf.org
	Subject: Re: [SIPPING] automatic answer
=09
=09
	Dear Folks,
	=20
	=20
	I have not found out the related I-D or RFC regarding "automatic answer =
feature" for SIP phone.
	=20
	To implement in the SIP phone, is it reasonable to use Call-Info field =
?
	=20
	=20
	Any reponse would be appreciated.
	=20
	=20
	Jinkyung Hwang
	KT
	=20

		----- Original Message -----=20
		From: =C8=B2=C1=F8=B0=E6 <mailto:jkhwang@kt.co.kr> =20
		To: sipping@ietf.org=20
		Sent: Saturday, October 09, 2004 12:01 PM
		Subject: automatic answer

		Hi,=20
		=20
		Is there any I-D regarding params for SIP phone to answer =
automatically ? (for answering machine functionality)
		=20
		I would like to know when the call arrives a phone, by which =
param/header value the phone answers without ringing.
		=20
		=20
		=20
		Any reponse would be appreciated.
		=20
		=20
		Jinkyung Hwang
		KT


------_=_NextPart_001_01C4B5BC.9E643364
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><FONT face=3DVerdana color=3D#0000ff =
size=3D2><SPAN=20
class=3D639200509-19102004>As far as I know there is a vendors that =
sends such=20
headers:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT><SPAN class=3D639200509-19102004>
<P><FONT face=3DVerdana color=3D#0000ff size=3D2>INVITE sip:abc =
SIP/2.0<BR>From:=20
&lt;sip:a@domain&gt;<BR>To: &lt;sip:b@domain&gt;<BR>Call-Info:=20
&lt;sip:b@domain&gt;;answer-after=3D0</FONT></P>
<P><FONT face=3DVerdana><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D639200509-19102004>We </SPAN>challenge&nbsp;<SPAN=20
class=3D639200509-19102004>that request because of the </SPAN>security=20
implications<SPAN=20
class=3D639200509-19102004>.</SPAN></FONT></FONT></FONT></P></SPAN></FONT=
></DIV>
<DIV dir=3Dltr align=3Dleft><FONT><SPAN =
class=3D639200509-19102004></SPAN></FONT><FONT=20
face=3DVerdana><FONT color=3D#0000ff><FONT size=3D2>C<SPAN=20
class=3D639200509-19102004>S</SPAN></FONT></FONT></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> sipping-bounces@ietf.org=20
  [mailto:sipping-bounces@ietf.org] <B>On Behalf Of =
</B>???<BR><B>Sent:</B>=20
  Tuesday, October 19, 2004 2:16 PM<BR><B>To:</B>=20
  sipping@ietf.org<BR><B>Subject:</B> Re: [SIPPING] automatic=20
  answer<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Dear =
Folks,</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>I have not =
found out the related I-D=20
  or RFC regarding "automatic answer feature" for SIP =
phone.</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>To implement =
in the SIP phone, is it=20
  reasonable to use Call-Info field ?</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Any reponse =
would be=20
  appreciated.</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Jinkyung =
Hwang</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2>KT</FONT></DIV>
  <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt =B1=BC=B8=B2">----- Original Message ----- =
</DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt =B1=BC=B8=B2; font-color: =
black"><B>From:</B>=20
    <A title=3Djkhwang@kt.co.kr =
href=3D"mailto:jkhwang@kt.co.kr">=C8=B2=C1=F8=B0=E6</A> </DIV>
    <DIV style=3D"FONT: 10pt =B1=BC=B8=B2"><B>To:</B> <A =
title=3Dsipping@ietf.org=20
    href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 10pt =B1=BC=B8=B2"><B>Sent:</B> Saturday, =
October 09, 2004 12:01=20
    PM</DIV>
    <DIV style=3D"FONT: 10pt =B1=BC=B8=B2"><B>Subject:</B> automatic =
answer</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Hi, =
</FONT></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Is there any =
I-D regarding params=20
    for SIP phone to answer automatically ? (for answering machine=20
    functionality)</FONT></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>I would like =
to know when the call=20
    arrives a phone, by which param/header value the phone answers =
without=20
    ringing.</FONT></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Any reponse =
would be=20
    appreciated.</FONT></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080 size=3D2>Jinkyung =
Hwang</FONT></DIV>
    <DIV><FONT face=3D=B1=BC=B8=B2 color=3D#000080=20
size=3D2>KT</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4B5BC.9E643364--


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



From sipping-bounces@ietf.org  Fri Oct 29 03:12:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01049
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 03:12:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNRAM-00077Y-Jc
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 03:27:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNQdE-0001T4-7l; Fri, 29 Oct 2004 02:53:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CLsFO-0004Wd-32
	for sipping@megatron.ietf.org; Sun, 24 Oct 2004 19:58:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11525
	for <sipping@ietf.org>; Sun, 24 Oct 2004 19:58:00 -0400 (EDT)
Received: from web53409.mail.yahoo.com ([206.190.37.56])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLsSi-0008A6-7V
	for sipping@ietf.org; Sun, 24 Oct 2004 20:11:49 -0400
Message-ID: <20041024235730.27063.qmail@web53409.mail.yahoo.com>
Received: from [24.147.233.128] by web53409.mail.yahoo.com via HTTP;
	Sun, 24 Oct 2004 16:57:30 PDT
Date: Sun, 24 Oct 2004 16:57:30 -0700 (PDT)
From: Dan Petrie <dgpetrie@yahoo.com>
Subject: Re: [Sipping] instance-ID for SIP UA
To: Cullen Jennings <fluffy@cisco.com>,
        Simonetti Gabrielle <Gabrielle.Simonetti@TILAB.COM>,
        sipping <sipping@ietf.org>
In-Reply-To: <BDA1542A.16B0B%fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
X-Mailman-Approved-At: Fri, 29 Oct 2004 02:52:58 -0400
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: 92df29fa99cf13e554b84c8374345c17

Perhaps I am missing a requirement or a discussion
thread on the list.  Can someone point to the reason
this is anything other than an implementation
decision?

Why is this a standards issue?  It seems to me the
only requirement is that it be unique.  Who cares 
how we get there?


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

> On 9/21/04 5:49 AM, "Simonetti Gabrielle"
> <Gabrielle.Simonetti@TILAB.COM>
> wrote:
> 
> >    First issue - What is the format of the
> instance-ID?
> > We would like a standardized instance-ID for all
> UA. Jennings draft suggests
> > the format "RANID-" followed by a 16 digit
> representation of a random 64 bit
> > number. Couldn't this number be associated with
> the local domain to obtain a
> > unique URI identifying the UA instance to be used
> for the subscription to the
> > "device" profile?
> >  
> 
> I have done a 180 degree turn on my opinion on this.
> I have become a fan of
> UUID. It mixes the best of MAC and RANDID. It works
> for softphones and
> hardphones (whatever those are :-) I don't really
> believe UUID works better
> than RANID but I have become convinced that there
> are a large group of
> people that disagree with me and that we can all
> agree on UUID.
> 
> The UA should create the ID.
> 
> The UA should store the ID.
> 
> Though we could specify a ton of things and say use
> any of them, I see no
> reason why any of the alternatives are better than
> UUID (other than for some
> esoteric IETF process reasons) so I would be happier
> to see just one thing
> implemented.
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 Oct 29 03:13: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 DAA01174
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 03:13:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNRB6-0007AD-Eg
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 03:28:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNQdF-0001TB-EC; Fri, 29 Oct 2004 02:53:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMdn0-000845-82
	for sipping@megatron.ietf.org; Tue, 26 Oct 2004 22:43:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23051
	for <sipping@ietf.org>; Tue, 26 Oct 2004 22:43:51 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMe0b-0001ng-6I
	for sipping@ietf.org; Tue, 26 Oct 2004 22:58:08 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I6800FRR27XAF@mailout2.samsung.com> for sipping@ietf.org; Wed,
	27 Oct 2004 11:43:10 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I68002J5241IB@mailout2.samsung.com> for
	sipping@ietf.org; Wed, 27 Oct 2004 11:40:50 +0900 (KST)
Received: from foremost ([165.213.227.126])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I6800MGX241M0@mmp1.samsung.com> for sipping@ietf.org;
	Wed, 27 Oct 2004 11:40:49 +0900 (KST)
Date: Wed, 27 Oct 2004 11:39:28 +0900
From: sunil vatnal <sunil.vatnal@samsung.com>
In-reply-to: <OF843BA883.AC6FD7A8-ON65256F39.0022E460-65256F39.0025134E@hssworld.com>
To: anagarajan@hssworld.com, sipping@ietf.org,
        sip-implementors@cs.columbia.edu, jdrosen@dynamicsoft.com,
        schulzrinne@cs.columbia.edu, Gonzalo.Camarillo@ericsson.com,
        alan.johnston@wcom.com, jon.peterson@neustar.com,
        rsparks@dynamicsoft.com, mjh@icir.org, schooler@research.att.com
Message-id: <000001c4bbce$2eaf8b50$7ee3d5a5@foremost>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7BIT
X-Mailman-Approved-At: Fri, 29 Oct 2004 02:52:58 -0400
Subject: [Sipping] RE: [Sip-implementors] Doubt regarding comparison of
 From-Tag, To-tag and Via-branch
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: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7BIT

Hi Anil,
It's defined in the RFC that tokens are always case-insensitive. Only
the tokens expressed in quoted strings are case-sensitive. You can
implement case-insensitive comparison in this case.
- sunil vatnal

-----Original Message-----
From: sip-implementors-bounces@cs.columbia.edu
[mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of
anagarajan@hssworld.com
Sent: Tuesday, October 26, 2004 3:47 PM
To: sipping@ietf.org; sip-implementors@cs.columbia.edu;
jdrosen@dynamicsoft.com; schulzrinne@cs.columbia.edu;
Gonzalo.Camarillo@ericsson.com; alan.johnston@wcom.com;
jon.peterson@neustar.com; rsparks@dynamicsoft.com; mjh@icir.org;
schooler@research.att.com
Subject: [Sip-implementors] Doubt regarding comparison of
From-Tag,To-tag and Via-branch





Hi All,
            I have a doubt regarding comparison of From-Tag,To-tag and
Via-branch for matching the transaction.
While comparing the tags and branch parameters, whether the comparison
should be case-sensitive or case-insensitive.
In section 7.3.1 of RFC3261:-
   "When comparing header fields, field names are always case-
   insensitive.  Unless otherwise stated in the definition of a
   particular header field, field values, parameter names, and parameter
   values are case-insensitive.  Tokens are always case-insensitive."

As per the grammar of From-tag and To-tag:-
tag-param   =  "tag" EQUAL token
and grammar of branch parameter of Via header is:-
via-branch        =  "branch" EQUAL token

In the definition of From,To and Via headers, there is no definition
that
the values should be case-sensitive.
Does that mean that we should do case-insensitive comparison?
Please confirm on this.

Regards
Anil N

Hughes Software Systems (HSS)-  B'lore India
Office Number: +91-80-51067074

***********************  HSS-Private   ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems
Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it
is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering,
or
disclosing the contents of this message. HSS accepts no responsibility
for
loss or damage arising from the use of the information transmitted by
this
email including damage from virus."

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 29 04:48: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 EAA08700
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 04:48:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNSfE-000156-2t
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 05:03:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNSE3-0004d8-JY; Fri, 29 Oct 2004 04:35:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNRrO-0000NZ-4T
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 04:11:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06082
	for <sipping@ietf.org>; Fri, 29 Oct 2004 04:11:44 -0400 (EDT)
From: David.Rio@alcatel.fr
Received: from smail.alcatel.fr ([64.208.49.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNS5c-0000KY-QA
	for sipping@ietf.org; Fri, 29 Oct 2004 04:26:29 -0400
Received: from frmail28.netfr.alcatel.fr (frmail28.netfr.alcatel.fr
	[155.132.251.28])
	by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id i9T8BbrN031049
	for <sipping@ietf.org>; Fri, 29 Oct 2004 10:11:37 +0200
Received: from [159.217.209.70] ([159.217.209.70])
	by frmail28.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
	with ESMTP id 2004102910113523:1490 ;
	Fri, 29 Oct 2004 10:11:35 +0200 
Message-ID: <4181FB36.3000002@alcatel.fr>
Date: Fri, 29 Oct 2004 10:11:34 +0200
Organization: Alcatel CIT
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping@ietf.org
X-MIMETrack: Itemize by SMTP Server on FRMAIL28/FR/ALCATEL(Release 5.0.9a
	|January 7, 2002) at 10/29/2004 10:11:35,
	Serialize by Router on FRMAIL28/FR/ALCATEL(Release 5.0.9a |January 7,
	2002) at 10/29/2004 10:11:36,
	Serialize complete at 10/29/2004 10:11:36
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Subject: [Sipping] Porting IN/INAP IVR applications to IMS networks
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="===============1528711091=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 2.3 (++)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221

This is a multi-part message in MIME format.
--===============1528711091==
Content-Type: multipart/alternative;
	boundary="------------050306020400070109080306"

This is a multi-part message in MIME format.
--------------050306020400070109080306
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello dear sipping members,

Within TDM technology, most of the Telco operators have developped 
services for their IN networks using the INAP protocol.
This protocol defines some operations to address an IVR peripheral in 
the network (named SRP in #7 networks, MRF
in IMS, Media Server in IT). Those operations are PA, PCUI, ...

        INAP                    #7+INAP
SCP <-------------> Switch <--------------> SRP

Those operators are at present looking for solutions to easily adapt 
those applications to IMS/NGN/IT networks.
The architectures are quite similar (equivalent building blocks) .... 
but the protocols not.

        SIP                        SIP
AS <------------> Softswitch <--------------> MRF/Media Server

The IMS defines that the MRF is splitted into two parts : MRF-C and MRF-P.

   SIP               SIP or H.248
<---------> MRF-C <----------------> MRP-P

The protocol between MRF-C and MRF-P is still discussed.

Nevertheless, the existing SIP protocol is not enough to port the 
existing INAP applications.
We do not have the equivalent of the INAP IVR commands.

A solutions is to embed a media protocol within SIP message as body 
attachment.
Some solutions have been proposed as draft to this workgroup : Netann, 
MOML, MSML.
Some other alternatives exist such as VoiceXML.

But all those protocols address new applications, not the existing.
Either they do not offer enough parameters (MSML) to replace INAP commands
with an equivalent command, either they have a different architecture 
and philosophy
that suppose a huge work to adapt those existing applications (MOML).

Considering this problem, we have developped at Alcatel an XML-based 
protocol, that
makes the porting of those applications from INAP to SIP+XML very easy : 
the same
commands exist, with the same names, the same parameters, the same 
behaviour.
(AMSML : Application / Media-Server Markup Language).
The protocol is very simple, not so powerfull as MOML in its current 
release but makes
the porting very easily ; just replace INAP commands with their AMSML 
equivalent.
New commands can be easily added.
We have already used it to port some applications with success. The time 
necessary
to port an existing application is drastically reduced.

We are wondering if there would be any interest in proposing this 
protocol to this workgroup
in order to share experiences and potentially define a common standard ?

Are there other people working on this subject ?

Best regards

David RIO

-- 
David Rio
Alcatel


--------------050306020400070109080306
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello dear sipping members,<br>
<br>
Within TDM technology, most of the Telco operators have developped
services for their IN networks using the INAP protocol.<br>
This protocol defines some operations to address an IVR peripheral in
the network (named SRP in #7 networks, MRF<br>
in IMS, Media Server in IT). Those operations are PA, PCUI, ...<br>
<br>
<font face="Courier New, Courier, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
INAP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; #7+INAP<br>
SCP &lt;-------------&gt; Switch &lt;--------------&gt; SRP<br>
</font><br>
Those operators are at present looking for solutions to easily adapt
those applications to IMS/NGN/IT networks.<br>
The architectures are quite similar (equivalent building blocks) ....
but the protocols not.<br>
<br>
<font face="Courier New, Courier, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SIP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SIP</font><br>
<font face="Courier New, Courier, monospace">AS &lt;------------&gt;
Softswitch &lt;--------------&gt; MRF/Media Server<br>
</font><br>
The IMS defines that the MRF is splitted into two parts : MRF-C and
MRF-P.<br>
<br>
<font face="Courier New, Courier, monospace">&nbsp;&nbsp; SIP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SIP
or H.248</font><br>
<font face="Courier New, Courier, monospace">&lt;---------&gt; MRF-C
&lt;----------------&gt; MRP-P<br>
</font><br>
The protocol between MRF-C and MRF-P is still discussed.<br>
<br>
Nevertheless, the existing SIP protocol is not enough to port the
existing INAP applications.<br>
We do not have the equivalent of the INAP IVR commands.<br>
<br>
A solutions is to embed a media protocol within SIP message as body
attachment.<br>
Some solutions have been proposed as draft to this workgroup : Netann,
MOML, MSML.<br>
Some other alternatives exist such as VoiceXML.<br>
<br>
But all those protocols address new applications, not the existing.<br>
Either they do not offer enough parameters (MSML) to replace INAP
commands<br>
with an equivalent command, either they have a different architecture
and philosophy<br>
that suppose a huge work to adapt those existing applications (MOML).<br>
<br>
Considering this problem, we have developped at Alcatel an XML-based
protocol, that<br>
makes the porting of those applications from INAP to SIP+XML very easy
: the same<br>
commands exist, with the same names, the same parameters, the same
behaviour.<br>
(AMSML : Application / Media-Server Markup Language).<br>
The protocol is very simple, not so powerfull as MOML in its current
release but makes <br>
the porting very easily ; just replace INAP commands with their AMSML
equivalent. <br>
New commands can be easily added.<br>
We have already used it to port some applications with success. The
time necessary<br>
to port an existing application is drastically reduced.<br>
<br>
We are wondering if there would be any interest in proposing this
protocol to this workgroup<br>
in order to share experiences and potentially define a common standard ?<br>
<br>
Are there other people working on this subject ?<br>
<br>
Best regards<br>
<br>
David RIO<br>
<pre class="moz-signature" cols="72">-- 
David Rio
Alcatel</pre>
</body>
</html>

--------------050306020400070109080306--


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



From sipping-bounces@ietf.org  Fri Oct 29 06:36:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15433
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 06:36:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNUM0-0003Ad-LN
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 06:51:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNTib-0006wr-Rf; Fri, 29 Oct 2004 06:10:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNTQP-0004BM-LM
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 05:52:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12944
	for <sipping@ietf.org>; Fri, 29 Oct 2004 05:51:59 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNTef-0002Iz-FJ
	for sipping@ietf.org; Fri, 29 Oct 2004 06:06:45 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9T9pdl26968; Fri, 29 Oct 2004 12:51:39 +0300 (EET DST)
X-Scanned: Fri, 29 Oct 2004 12:51:18 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i9T9pINA023983;
	Fri, 29 Oct 2004 12:51:18 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 00ZEVgLI; Fri, 29 Oct 2004 12:50:23 EEST
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9T9oNS15462; Fri, 29 Oct 2004 12:50:23 +0300 (EET DST)
Received: from esebe016.NOE.Nokia.com ([172.21.138.55]) by
	esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 29 Oct 2004 12:50:23 +0300
Received: from esebe056.NOE.Nokia.com ([172.21.143.51]) by
	esebe016.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 29 Oct 2004 12:50:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Re: Config framework - issue with parameters send
	inEvent header
Date: Fri, 29 Oct 2004 12:50:22 +0300
Message-ID: <5816828233DEFA41807A6CFDFDF2343C3A8BE5@esebe056.ntc.nokia.com>
Thread-Topic: [Sipping] Re: Config framework - issue with parameters send
	inEvent header
Thread-Index: AcS4i99Xb2+XAsyPSamh4h6x7REvTAFEL78A
To: <dpetrie@pingtel.com>, <john.elwell@siemens.com>
X-OriginalArrivalTime: 29 Oct 2004 09:50:22.0917 (UTC)
	FILETIME=[B566AF50:01C4BD9C]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable

I think this is stretching the scope of this draft a little. We can do =
without them for now.

/Hisham

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
> Behalf Of ext Daniel G. Petrie
> Sent: 23.October.2004 00:52
> To: Elwell, John
> Cc: 'sipping@ietf.org'
> Subject: [Sipping] Re: Config framework - issue with parameters send
> inEvent header
>=20
>=20
> Thanks for the comments.  I would like to hear opinions from
> folks on the list on whether they think this is a current
> requirement or not.
>=20
> Thanks,
> Dan
>=20
> "Elwell, John" wrote:
> >=20
> > Dan,
> >=20
> > In reviewing the draft-ietf-sipping-config-framework-04, I=20
> noticed that
> > several parameters had been defined for the Event header=20
> giving information
> > about the device, i.e., "vendor", "model" and "version". I=20
> am concerned that
> > these may not be sufficient in all cases for the profile=20
> delivery server to
> > determine the precise profile to be delivered. Moreover, the profile
> > delivery server may use these parameters to compile an=20
> inventory of devices
> > for admin purposes, and more detailed information might be=20
> needed for this
> > purpose, even if it does not influence the choice of profile to be
> > delivered. Examples of extended information that might be=20
> considered useful
> > for the profile delivery server are:
> >=20
> > - where a particular UA model has different components,=20
> each with its own
> > version number (e.g., hardware version and software version);
> > - where a particular UA model has some optional extras,=20
> these may need to be
> > listed together with their respective version numbers.
> >=20
>=20
> I did not see any comments on this on the list.  Are there=20
> any opinions
> out there?  I see no technical reasons against adding a components
> parameter.  Components values can be a vendor scoped token. If there
> is more than one component that the user agent wants to specify it
> could add more than one "component" parameter each have a value of
> a token.
>=20
> My main reservation is the case for simplicity.  It is very easy to
> add parameters in the future if we really need them.  Please speak
> up if you think there is a case for defining this now.
>=20
> > Has any consideration been given to providing an extensible=20
> mechanism for
> > delivering UA information in a SUBSCRIBE request to a=20
> profile delivery
> > server?
> >=20
>=20
> Doesn't the Event header parameters construct provide this? =20
> Do we need
> something more specific to profile delivery?
>=20
> > John Elwell (john.elwell@siemens.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
>=20

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


From sipping-bounces@ietf.org  Fri Oct 29 08:54:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25818
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 08:54:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNWUw-0006Ex-4F
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 09:08:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNW3j-000143-MV; Fri, 29 Oct 2004 08:40:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNVqY-00080A-UW
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 08:27:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23858
	for <sipping@ietf.org>; Fri, 29 Oct 2004 08:27:09 -0400 (EDT)
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNW4f-0005gl-8n
	for sipping@ietf.org; Fri, 29 Oct 2004 08:41:56 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQtQ1002468; Fri, 29 Oct 2004 21:26:55 +0900 (JST)
Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQtYu008773; Fri, 29 Oct 2004 21:26:55 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQste008769; Fri, 29 Oct 2004 21:26:54 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQsjm015462; Fri, 29 Oct 2004 21:26:54 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100])
	by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQsSb015456; Fri, 29 Oct 2004 21:26:54 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp
	[129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQsF2014305; Fri, 29 Oct 2004 21:26:54 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQrcS013519; Fri, 29 Oct 2004 21:26:53 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (img0.m.ecl.ntt.co.jp [129.60.5.145])
	by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id
	i9TCQrxc013516; Fri, 29 Oct 2004 21:26:53 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id VAA27167;
	Fri, 29 Oct 2004 21:26:53 +0900 (JST)
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
To: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] e2m security open issue: label for the target body
Date: Fri, 29 Oct 2004 21:26:50 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.65 (WinNT,501)
In-Reply-To: <0213A6EA-282B-11D9-BDDE-000A95C73842@cisco.com>
References: <0213A6EA-282B-11D9-BDDE-000A95C73842@cisco.com>
Message-Id: <5DC4BDB290A239ono.kumiko@lab.ntt.co.jp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
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: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: 7bit

Thanks for your useful comments.
See inline.

At 00:15 2004/10/28, David R Oran wrote:
>Thanks for a cogent analysis and the time to investigate the options. I 
>find your conclusion to use SIP rather than MIME headers persuasive and 
>agree with it.
>
>In addition to the reasons cited I would add two:
>1) Modifying MIME seems less attractive because we are not solving a 
>MIME problem here - it's a SIP problem. The MIME guys would have ??? 
>over their heads as to why MIME would need this functionality.

I agree. Since all parts of multipart MIME usually target the same 
entities, it is not necessary to indicate the targeted entity of each 
part of MIME in general.

>2) The integrity issues cited about using unprotected SIP headers to 
>indicate which bodies to process don't strike me as a problem in 
>practice. There are two cases: (a)changing/removing the SIP header so 
>that a proxy that should process a MIME body doesn't, and 
>(b)adding/changing a SIP header so that proxy that shouldn't process 
>the header does.
>
>In case (a) no security is violated since the only reason the proxy 
>should look at the body is because the UA *wants* it to - if the body 
>isn't processed the UA might not get some service it otherwise would 
>get, and/or  the request might fail because of that. This represents a 
>DoS attack, but such an attack could be trivially mounted by just 
>scribbling on the MIME body itself. In case (b) nothing bad happens 
>functionally, but as you point out the proxy/proxies are coerced into 
>doing extra work for no reason. Since there are probably about 100 
>other ways to make proxies do extra work this one seems no more 
>troublesome.
>
>There is a minor issue of detectability of the attack, but I'm not 
>convinced that is worth worrying about to the extent of the bother and 
>overhead of using SIPFRAG.

I was worrying about case(a). My concern was how the UA knows if the 
body is processed properly. However, I find that it is a issue about 
acknowlegement of the UA's request rather than an issue of security. 

>Between option A-1 and A-2 I find A-2 (add content-ids to route header) 
>more elegant. Hovever, we've had discussions in the past about whether 
>extending the Route header for other things might cause 
>backward-compatibility issues and avoided it on that basis. It might be 
>good to poll the implementers to look at their route header handling 
>code to gauge the practical impact.

>Thanks and regards, Dave.

I agree that it's good idea to poll the implementers about the practical 
impact. Actually, I have encountered the problem at the SIPit event. Our 
client/proxy couldn't process the Route header that had unknown 
parameters.:-)

Thank you so much,
Kumiko

>On Oct 26, 2004, at 6:09 AM, Kumiko Ono wrote:
>
>> Hi,
>>
>> I've submitted an update draft of the e2m security mechanism 
>> (http://www.
>> ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-03.txt).
>> There are two major open issues on the mechanism of end-to-middle
>> security. I would like to hear your opinions on these.
>>
>> Open issue#1: How to label the target body.
>>
>> In order for a proxy server to easily determine whether to process MIME
>> bodies and which one, UA needs a way to label the body targeted at a
>> particular proxy server(s).
>>
>> After receiving many comments at the last IETF meeting about this, I
>> gave it some thought and came up with some conclusion, so I want to
>> share with you my preference in accomplishing the labeling and the
>> reason behind my preference.
>>
>> Options for labeling:
>> A-1. a new SIP header, i.e.: "Proxy-Required-Body".
>> A-2. a new parameter in a SIP header, i.e.: "content-id" param in 
>> "Route"
>> header.
>> B-1. a new MIME header, i.e.: "Content-Target".
>> B-2. a new parameter in a MIME header, i.e.: "required-entity" param in
>> "Content-Disposition".
>>
>> When a message has a target body destined for a proxy server, MIME
>> header options (B) shows a greater performance than SIP header options
>> (A) in searching the target body. This is because options A require the
>> inspection of the SIP header and "Content-ID" MIME header, while 
>> options
>> B only require the inspection of the MIME header.
>>
>> When a message has no target body destined for a proxy server, it is
>> easier for SIP header options (A) to determine that fact, as it only
>> needs to look at the SIP header.
>>
>> However, if integrity protection of the label is required, inner 
>> headers
>> need to be created using sipfrag attached with a signature. And the
>> validation of the signature would reduce the advantage of the ease in
>> determining the needs to search the body. If the security level of the
>> label is considered to be the same as that of routing headers, use of
>> TLS would satisfy the integrity requirements which will allow the SIP
>> header options (A) to retain their advantage.
>>
>> Since few of messages in all the traffic through a proxy server will
>> likely utilize e2m security, the ease in determining the needs to 
>> search
>> the body overweighs the performance in searching the target body.
>> Therefore, I changed the proposed option, from MIME header options to
>> SIP headers. Since a new parameter in Route header has more impact on a
>> proxy server, I believe Option A-1, with a new SIP header the best
>> choice.
>>
>> Your feedback is very welcome.
>>
>> Thanks in advance,
>> Kumiko
>> --
>> Kumiko Ono
>> NTT Network Service Systems Labs.
>> Tel +81 422 59 4508/Fax +81 422 60 4012
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
>David R. Oran
>Cisco Fellow
>Cisco Systems
>7 Ladyslipper Lane
>Acton, MA 01720 USA
>Tel: +1 978 264 2048
>Email: oran@cisco.com

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


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


From sipping-bounces@ietf.org  Fri Oct 29 10:41: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 KAA05648
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 10:41:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNYAW-0000No-5W
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 10:55:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNXeq-0000zv-1i; Fri, 29 Oct 2004 10:23:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXW1-0002vs-4v
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 10:14:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02854
	for <sipping@ietf.org>; Fri, 29 Oct 2004 10:14:03 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXkI-00089w-93
	for sipping@ietf.org; Fri, 29 Oct 2004 10:28:51 -0400
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id i9TEDQQ22787; Fri, 29 Oct 2004 10:13:26 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <V4Y5X6NP>; Fri, 29 Oct 2004 10:13:26 -0400
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB022C445F@zrc2hxm1.corp.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: "'eburger@brooktrout.com'" <eburger@brooktrout.com>
Date: Fri, 29 Oct 2004 10:13:14 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: [Sipping] Comments on draft-burger-sipping-netann-10
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="===============1640036897=="
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433

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.

--===============1640036897==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4BDC1.6DABD8CB"

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_01C4BDC1.6DABD8CB
Content-Type: text/plain

Hi Eric,

I was just doing a quick review of the updated netann draft and had a couple
minor comments.

1.  It appears that one change was removing the underscores, sip and hyphen
from the user parts.  However, it looks like there's one part that was
overlooked in section 6 on page 16. The third paragraph still reads:
" Clearly, with the use of underbars, sip, and a hyphen, this conflict is
much smaller than the potential for a conflict like "Postmaster". "
So, I would think that paragraph needs to be removed.  If you do that,
though, you kindof lose the flow of that Postmaster example in paragraph 2
and the 4th paragraph stating:
"The key point is, one cannot confuse the namespace at a Media Server with
the namespace for an organization."
Perhaps, changing that statement to the following would be okay (combining
that with paragraph 3 and thus leading into the example in the next
paragraph):
"However, a key point is that one cannot confuse the namespace at a Media
Server with the namespace for an organization, as highlighted by the example
in the following paragraph."

2.  Some nits on the references:
- the references to kpml [11] and conferencing framework [14] are outdated.
- why is RFC2543 [19] listed?  I don't see a reference within the doc.

Regards,
Mary H. Barnes
mary.barnes@nortelnetworks.com


------_=_NextPart_001_01C4BDC1.6DABD8CB
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-burger-sipping-netann-10</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Eric,</FONT>
</P>

<P><FONT SIZE=3D2>I was just doing a quick review of the updated netann =
draft and had a couple minor comments.</FONT>
</P>

<P><FONT SIZE=3D2>1.&nbsp; It appears that one change was removing the =
underscores, sip and hyphen from the user parts.&nbsp; However, it =
looks like there's one part that was overlooked in section 6 on page =
16. The third paragraph still reads:</FONT></P>

<P><FONT SIZE=3D2>&quot; Clearly, with the use of underbars, sip, and a =
hyphen, this conflict is much smaller than the potential for a conflict =
like &quot;Postmaster&quot;. &quot;</FONT></P>

<P><FONT SIZE=3D2>So, I would think that paragraph needs to be =
removed.&nbsp; If you do that, though, you kindof lose the flow of that =
Postmaster example in paragraph 2 and the 4th paragraph =
stating:</FONT></P>

<P><FONT SIZE=3D2>&quot;The key point is, one cannot confuse the =
namespace at a Media Server with the namespace for an =
organization.&quot;</FONT>
<BR><FONT SIZE=3D2>Perhaps, changing that statement to the following =
would be okay (combining that with paragraph 3 and thus leading into =
the example in the next paragraph):</FONT></P>

<P><FONT SIZE=3D2>&quot;However, a key point is that one cannot confuse =
the namespace at a Media Server with the namespace for an organization, =
as highlighted by the example in the following =
paragraph.&quot;</FONT></P>

<P><FONT SIZE=3D2>2.&nbsp; Some nits on the references:</FONT>
<BR><FONT SIZE=3D2>- the references to kpml [11] and conferencing =
framework [14] are outdated.</FONT>
<BR><FONT SIZE=3D2>- why is RFC2543 [19] listed?&nbsp; I don't see a =
reference within the doc.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Mary H. Barnes</FONT>
<BR><FONT SIZE=3D2>mary.barnes@nortelnetworks.com</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4BDC1.6DABD8CB--


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



From sipping-bounces@ietf.org  Fri Oct 29 21:56: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 VAA03776
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 21:56:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNiho-0007r7-1Q
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 22:11:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNiPp-0004BM-1H; Fri, 29 Oct 2004 21:52:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNiIt-0001dL-7J
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 21:45:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03295
	for <sipping@ietf.org>; Fri, 29 Oct 2004 21:45:13 -0400 (EDT)
Received: from salvelinus.brooktrout.com ([204.176.205.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNiXH-0007hP-LV
	for sipping@ietf.org; Fri, 29 Oct 2004 22:00:08 -0400
Received: from nhmail2.needham.brooktrout.com (nhmail2.eng.brooktrout.com
	[204.176.205.242])
	by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id
	i9U1e3G3020503; Fri, 29 Oct 2004 21:40:09 -0400 (EDT)
Received: by nhmail2.eng.brooktrout.com with Internet Mail Service
	(5.5.2653.19) id <PQMPPG45>; Fri, 29 Oct 2004 21:37:14 -0400
Message-ID: <EDD694D47377D7119C8400D0B77FD331C10C13@nhmail2.eng.brooktrout.com>
From: Eric Burger <eburger@brooktrout.com>
To: Mary Barnes <mary.barnes@nortelnetworks.com>
Date: Fri, 29 Oct 2004 21:36:52 -0400
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: 769a46790fb42fbb0b0cc700c82f7081
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: [Sipping] RE: Comments on draft-burger-sipping-netann-10
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Good to see someone is looking at it!

Since netann has not changed substantially in two years, and just about all
of the media server vendors are supporting it as is in -10 (not -09, see
__sip- below), is this going to go anywhere in the IETF?  Given it is now
industry practice, is it a BCP?  It certainly is a CP...

On the comments:
Good catch on the __sip- mistake.  BTW, since absolutely none of the 5+
media server vendors had plans to implement __sip-, and since it was a red
herring in the first place, I took it out.  I'll reword that section.

I'll update the references.  The RFC2543 reference smells like an xml2rfc
opportunity...

-----Original Message-----
From: Mary Barnes [mailto:mary.barnes@nortelnetworks.com]
Sent: Friday, October 29, 2004 10:13 AM
To: 'eburger@brooktrout.com'
Cc: 'sipping@ietf.org'
Subject: Comments on draft-burger-sipping-netann-10


Hi Eric, 
I was just doing a quick review of the updated netann draft and had a couple
minor comments. 
1.  It appears that one change was removing the underscores, sip and hyphen
from the user parts.  However, it looks like there's one part that was
overlooked in section 6 on page 16. The third paragraph still reads:
" Clearly, with the use of underbars, sip, and a hyphen, this conflict is
much smaller than the potential for a conflict like "Postmaster". "
So, I would think that paragraph needs to be removed.  If you do that,
though, you kindof lose the flow of that Postmaster example in paragraph 2
and the 4th paragraph stating:
"The key point is, one cannot confuse the namespace at a Media Server with
the namespace for an organization." 
Perhaps, changing that statement to the following would be okay (combining
that with paragraph 3 and thus leading into the example in the next
paragraph):
"However, a key point is that one cannot confuse the namespace at a Media
Server with the namespace for an organization, as highlighted by the example
in the following paragraph."
2.  Some nits on the references: 
- the references to kpml [11] and conferencing framework [14] are outdated. 
- why is RFC2543 [19] listed?  I don't see a reference within the doc. 
Regards, 
Mary H. Barnes 
mary.barnes@nortelnetworks.com 

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


From sipping-bounces@ietf.org  Fri Oct 29 22:44: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 WAA06062
	for <sipping-web-archive@ietf.org>; Fri, 29 Oct 2004 22:44:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNjSg-00006H-No
	for sipping-web-archive@ietf.org; Fri, 29 Oct 2004 22:59:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNj3r-0004nm-8p; Fri, 29 Oct 2004 22:33:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNiww-0001oX-7F
	for sipping@megatron.ietf.org; Fri, 29 Oct 2004 22:26:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05363
	for <sipping@ietf.org>; Fri, 29 Oct 2004 22:26:36 -0400 (EDT)
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNjBK-0008Il-7F
	for sipping@ietf.org; Fri, 29 Oct 2004 22:41:31 -0400
Received: from bertculpepper@netscape.net
	by imo-d01.mx.aol.com (mail_out_v37_r3.8.) id l.b.ed4ecb0 (16238);
	Fri, 29 Oct 2004 22:26:01 -0400 (EDT)
Received: from [192.168.0.3] (48.144.8.67.cfl.rr.com [67.8.144.48]) by
	air-in03.mx.aol.com (v102.9) with ESMTP id
	MAILININ32-3f6e4182fbb7c1; Fri, 29 Oct 2004 22:26:01 -0400
Message-ID: <4182FC37.6080205@netscape.net>
Date: Fri, 29 Oct 2004 22:28:07 -0400
From: Bert Culpepper <bertculpepper@netscape.net>
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
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Subject: Re: [Sipping] WGLC: KPML
References: <4180EB0E.7060406@ericsson.com>
In-Reply-To: <4180EB0E.7060406@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 67.8.144.48
X-Mailer: Unknown (No Version)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: mdolly@att.com, Eric Burger <eburger@brooktrout.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: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

I sent comments to the authors on the -05 revision but due to the WGLC I
repeat a few here in case the WG may have an opinion.

- The document has the following statement in the abstract.

   "The event package uses SUBSCRIBE messages and allows for XML
   documents that define and describe filter specifications for capturing
   key presses (DTMF Tones) entered at a presentation-free User Interface
   SIP User Agent (UA)."

Two things here, one is that this statement implies that the event
package is limited to use with presentation-free UAs.  The second is the
phrase "(DTMF Tones)", this package is an alternative to the use of DTMF
tones being used to represent key presses.  I would just remove "(DTMF
Tones)" and "presentation-free User Interface" from the paragraph.

- The same comments apply to the first paragraph of the Introduction.
Again, it should not be implied that the scope of the event package is
limited to DTMF reporting but is applicable to any scenario where a user
presses a keypad (hard or soft).  I do feel that it should be pointed
out that the event package is useful for both presentation-free User
Interfaces and those with a display of some sort, and that it can
replace the use of DTMF to represent user input.

The rest of my comments are editorial.

- I've always understood Reference numbers should start a 1 and 
increment from there, and should reflect their order of appearance in 
the document.

- s/inferace/interface/ in the 3rd paragraph of section 2.

- s/provde/provide/ in the 9th paragraph of section 2.

- "an" is repeated in the paragraph preceding Figure 6.

- s/Subcriptions/Subscriptions/ in section 3.8's title.

- s/supressionand/supression and/ in the last paragraph of section 4.3.

- The note at the end of section 4.3 should be removed.  I'm not aware
of a use case for this at this point and the hope is to finish this work 
quickly AFAIK, so the note should be removed.

Best Regards,
Bert


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


From sipping-bounces@ietf.org  Sat Oct 30 08:06:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18210
	for <sipping-web-archive@ietf.org>; Sat, 30 Oct 2004 08:06:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNsEA-0000je-PZ
	for sipping-web-archive@ietf.org; Sat, 30 Oct 2004 08:21:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNrnE-0005za-C7; Sat, 30 Oct 2004 07:53:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNrf5-0002ZI-7z
	for sipping@megatron.ietf.org; Sat, 30 Oct 2004 07:44:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17076
	for <sipping@ietf.org>; Sat, 30 Oct 2004 07:44:45 -0400 (EDT)
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNrtY-0000FC-NV
	for sipping@ietf.org; Sat, 30 Oct 2004 07:59:45 -0400
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	i9UBh8xD008763
	for <sipping@ietf.org>; Sat, 30 Oct 2004 06:44:08 -0500
Received: from OCCLUST04EVS1.ugd.att.com (135.38.164.12) by
	attrh5i.attrh.att.com (7.1.006)
	id 41729863002A5B60; Sat, 30 Oct 2004 07:44:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] RE: Comments on draft-burger-sipping-netann-10
Date: Sat, 30 Oct 2004 06:44:07 -0500
Message-ID: <28F05913385EAC43AF019413F674A0170A412800@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: [Sipping] RE: Comments on draft-burger-sipping-netann-10
Thread-Index: AcS+I65hTCNwWCZOS8yDZu6n6w/BQQAUc3Eg
From: "Dolly, Martin C, ALABS" <mdolly@att.com>
To: <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable
Cc: Mary Barnes <mary.barnes@nortelnetworks.com>,
        Eric Burger <eburger@brooktrout.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: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable

If the Bloody Red Sox can win the World Series, netann can move forward
for approval....

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
Behalf Of Eric Burger
Sent: Friday, October 29, 2004 9:37 PM
To: Mary Barnes
Cc: 'sipping@ietf.org'
Subject: [Sipping] RE: Comments on draft-burger-sipping-netann-10


Good to see someone is looking at it!

Since netann has not changed substantially in two years, and just about
all
of the media server vendors are supporting it as is in -10 (not -09, see
__sip- below), is this going to go anywhere in the IETF?  Given it is
now
industry practice, is it a BCP?  It certainly is a CP...

On the comments:
Good catch on the __sip- mistake.  BTW, since absolutely none of the 5+
media server vendors had plans to implement __sip-, and since it was a
red
herring in the first place, I took it out.  I'll reword that section.

I'll update the references.  The RFC2543 reference smells like an
xml2rfc
opportunity...

-----Original Message-----
From: Mary Barnes [mailto:mary.barnes@nortelnetworks.com]
Sent: Friday, October 29, 2004 10:13 AM
To: 'eburger@brooktrout.com'
Cc: 'sipping@ietf.org'
Subject: Comments on draft-burger-sipping-netann-10


Hi Eric,=20
I was just doing a quick review of the updated netann draft and had a
couple
minor comments.=20
1.  It appears that one change was removing the underscores, sip and
hyphen
from the user parts.  However, it looks like there's one part that was
overlooked in section 6 on page 16. The third paragraph still reads:
" Clearly, with the use of underbars, sip, and a hyphen, this conflict
is
much smaller than the potential for a conflict like "Postmaster". "
So, I would think that paragraph needs to be removed.  If you do that,
though, you kindof lose the flow of that Postmaster example in paragraph
2
and the 4th paragraph stating:
"The key point is, one cannot confuse the namespace at a Media Server
with
the namespace for an organization."=20
Perhaps, changing that statement to the following would be okay
(combining
that with paragraph 3 and thus leading into the example in the next
paragraph):
"However, a key point is that one cannot confuse the namespace at a
Media
Server with the namespace for an organization, as highlighted by the
example
in the following paragraph."
2.  Some nits on the references:=20
- the references to kpml [11] and conferencing framework [14] are
outdated.=20
- why is RFC2543 [19] listed?  I don't see a reference within the doc.=20
Regards,=20
Mary H. Barnes=20
mary.barnes@nortelnetworks.com=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  Sat Oct 30 14:45: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 OAA10302
	for <sipping-web-archive@ietf.org>; Sat, 30 Oct 2004 14:45:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNySi-0007Tk-7b
	for sipping-web-archive@ietf.org; Sat, 30 Oct 2004 15:00:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNy1A-0002WF-8s; Sat, 30 Oct 2004 14:32:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNxy3-0000Nx-Bj; Sat, 30 Oct 2004 14:28:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09367;
	Sat, 30 Oct 2004 14:28:45 -0400 (EDT)
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CNyCY-0007C4-DT; Sat, 30 Oct 2004 14:43:49 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm34183e566; Sun, 31 Oct 2004 02:30:09 +0800
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jmd417f6221; Wed, 27 Oct 2004 07:56:58 +0800
Received: from megatron.ietf.org([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm0417ee6b8; Wed, 27 Oct 2004 07:56:58 +0800
Received: from megatron.ietf.org([132.151.6.71]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id AISP action; Wed, 27 Oct 2004 07:56:58 +0800
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMZ24-0005xn-Pk; Tue, 26 Oct 2004 17:39:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMYSS-0000Zx-Ey; Tue, 26 Oct 2004 17:02:20 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20945;
	Tue, 26 Oct 2004 17:02:17 -0400 (EDT)
Message-Id: <200410262102.RAA20945@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 26 Oct 2004 17:02:17 -0400
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-location-requirements-02.txt
X-BeenThere: sipping@ietf.org
Reply-To: internet-drafts@ietf.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.4 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8

--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 Session Initiation Protocol Location Conveyance
	Author(s)	: J. Polk, B. Rosen
	Filename	: draft-ietf-sipping-location-requirements-02.txt
	Pages		: 47
	Date		: 2004-10-26
	
This document presents the framework and requirements for usage of 
   the Session Initiation Protocol (SIP) to convey user location 
   information from one Session Initiation Protocol (SIP) entity to 
   another SIP entity.  We consider cases where location information is
   conveyed from end to end, as well as cases where message routing by 
   intermediaries is influenced by the location of the session 
   initiator.  We offer a set of solutions to the requirements, based 
   on the scenario(s) being addressed.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-location-requirements-02.txt

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

Content-Type: text/plain
Content-ID: <2004-10-26161200.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
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--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 Oct 30 15:07: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 PAA12133
	for <sipping-web-archive@ietf.org>; Sat, 30 Oct 2004 15:07:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CNyoM-0007yI-M9
	for sipping-web-archive@ietf.org; Sat, 30 Oct 2004 15:22:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNyL5-0007iX-AR; Sat, 30 Oct 2004 14:52:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNyAj-0004fv-Ja; Sat, 30 Oct 2004 14:41:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10056;
	Sat, 30 Oct 2004 14:41:51 -0400 (EDT)
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CNyPG-0007Ow-Ni; Sat, 30 Oct 2004 14:56:55 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jmc041845021; Sun, 31 Oct 2004 02:43:21 +0800
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm13417efa20; Wed, 27 Oct 2004 08:03:53 +0800
Received: from megatron.ietf.org([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm0417ee631; Wed, 27 Oct 2004 07:58:52 +0800
Received: from megatron.ietf.org([132.151.6.71]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id AISP action; Wed, 27 Oct 2004 07:58:52 +0800
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMZ2I-0006Jl-7n; Tue, 26 Oct 2004 17:39:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMYTy-0001EL-OH; Tue, 26 Oct 2004 17:03:54 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21391;
	Tue, 26 Oct 2004 17:03:52 -0400 (EDT)
Message-Id: <200410262103.RAA21391@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 26 Oct 2004 17:03:52 -0400
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-session-indep-policy-01.txt
X-BeenThere: sipping@ietf.org
Reply-To: internet-drafts@ietf.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.4 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: Session-Independent Session Initiation Protocol (SIP) 
			  Policies - Mechanism and Policy Schema
	Author(s)	: V. Hilt, et al.
	Filename	: draft-ietf-sipping-session-indep-policy-01.txt
	Pages		: 24
	Date		: 2004-10-26
	
This draft specifies an XML schema for profile data for SIP
   session-policies.  It defines a delivery mechanism for SIP
   session-policies that are independent of a specific SIP session.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-session-indep-policy-01.txt

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

Content-Type: text/plain
Content-ID: <2004-10-26161206.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
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--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  Sun Oct 31 02:35: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 CAA04529
	for <sipping-web-archive@ietf.org>; Sun, 31 Oct 2004 02:35:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COAU4-0002re-DY
	for sipping-web-archive@ietf.org; Sun, 31 Oct 2004 02:50:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COA5h-0005hS-AU; Sun, 31 Oct 2004 02: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 1COA1A-0003T4-B5
	for sipping@megatron.ietf.org; Sun, 31 Oct 2004 02:20:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03497
	for <sipping@ietf.org>; Sun, 31 Oct 2004 02:20:46 -0500 (EST)
Message-Id: <200410310720.CAA03497@ietf.org>
Received: from smtp006.bizmail.sc5.yahoo.com ([66.163.175.83])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COAFn-0002em-WD
	for sipping@ietf.org; Sun, 31 Oct 2004 02:35:56 -0500
Received: from unknown (HELO a1b30cjcb7gf94) (david@kayote.com@62.56.252.250
	with login)
	by smtp006.bizmail.sc5.yahoo.com with SMTP; 31 Oct 2004 07:20:41 -0000
From: "David" <david@kayote.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>
Subject: RE: [Sipping] automatic answer
Date: Sun, 5 Dec 2004 09:27:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <41813716.1050109@softarmor.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTam9Zej//eKBbgScuShFkkTN5Hbg==
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: quoted-printable
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: quoted-printable

Hi Dean.

While I totally agree that the network should not control the edges,
however, I would contend that there is a difference between controlling =
and
informing. I do not see the harm in a network providing extra services =
to
the edges in the form of additional information regarding the request =
about
to be made. Whether in the case of voice mail or spam, I think that if =
the
network has some info that it wishes to share it should do so and allow =
the
edge to decide what to do with this information. Thus, in this =
particular
case the network does not have to KNOW that the edge is an answering
machine, rather it could say "By the way, if you are an answering =
machine
...".=20

David Schwartz=20

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

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004
=20


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application 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 Oct 31 09:36:27 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 JAA00819
	for <sipping-web-archive@ietf.org>; Sun, 31 Oct 2004 09:36:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COH3U-0005sU-Dt
	for sipping-web-archive@ietf.org; Sun, 31 Oct 2004 09:51:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COGcA-0003eY-H9; Sun, 31 Oct 2004 09:23:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COGX3-0002wa-Ua
	for sipping@megatron.ietf.org; Sun, 31 Oct 2004 09:18:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29333
	for <sipping@ietf.org>; Sun, 31 Oct 2004 09:18:08 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COGla-0005Wn-J1
	for sipping@ietf.org; Sun, 31 Oct 2004 09:33:22 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	i9VEHvfM007382
	for <sipping@ietf.org>; Sun, 31 Oct 2004 15:17:57 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 31 Oct 2004 15:17:56 +0100
Received: from ericsson.com (EFO9N000L5C7100 [153.88.40.89]) by
	esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id VJSMQ5S5; Sun, 31 Oct 2004 15:17:56 +0100
Message-ID: <4184F413.7080105@ericsson.com>
Date: Sun, 31 Oct 2004 16:17:55 +0200
X-Sybari-Trust: a552c36b bfd556f1 fb3935f1 00000139
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2004 14:17:56.0669 (UTC)
	FILETIME=[6B0256D0:01C4BF54]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>,
        Jonathan Rosemberg <jdrosen@dynamicsoft.com>,
        Dean Willis <dwillis@dynamicsoft.com>,
        Alan Johnston <alan.johnston@mci.com>, roni.even@polycom.co.il,
        Orit Levin <oritl@microsoft.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: [Sipping] WGLC: Conferencing documents
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Folks,

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

draft-ietf-sipping-conferencing-requirements-01.txt
draft-ietf-sipping-conferencing-framework-03.txt
draft-ietf-sipping-conference-package-06.txt
draft-ietf-sipping-cc-conferencing-05.txt

This WGLC will finish on November 20th. Please, send your comments to 
the authors and to the list.

Thanks,

Gonzalo


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


From sipping-bounces@ietf.org  Sun Oct 31 17:13:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08722
	for <sipping-web-archive@ietf.org>; Sun, 31 Oct 2004 17:13:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COOBQ-0006Zu-Ml
	for sipping-web-archive@ietf.org; Sun, 31 Oct 2004 17:28:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CONsB-00039d-6C; Sun, 31 Oct 2004 17:08:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CONnW-0002be-Mq
	for sipping@megatron.ietf.org; Sun, 31 Oct 2004 17:03:38 -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 RAA08161
	for <sipping@ietf.org>; Sun, 31 Oct 2004 17:03:36 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COO2F-0006OU-Sv
	for sipping@ietf.org; Sun, 31 Oct 2004 17:18:55 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 31 Oct 2004 14:12:59 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9VM33cp028462
	for <sipping@ietf.org>; Sun, 31 Oct 2004 14:03:03 -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 OAA11752 for
	<sipping@ietf.org>; Sun, 31 Oct 2004 14:03:02 -0800 (PST)
Message-Id: <4.3.2.7.2.20041031155710.03978d60@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 31 Oct 2004 16:03:04 -0500
To: sipping@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Sipping] Update to Location conveyance ID 
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: 82c9bddb247d9ba4471160a9a865a5f3

I've updated the Location Conveyance ID at:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-location-requirements-02.txt

Here are the main changes from the previous version:

    - added requirements for 2 new 4XX error responses (Bad Location
      Information) and (Retry Location Body)

    - added "Bad Location Information" as section 8.6

    - added "Retry Location Body " as section 9.3

    - added support for session mode to cover packet sizes larger than
      the single packet limit of 1300 bytes in the message body

    - added requirement for a SIP entity to SUBSCRIBE to another for
      location information

    - added SUBSCRIBE and NOTIFY as section 8.5

    - added requirement to have user turn off any tracking created by
      subscription

    - removed doubt about which method to use for updating location
      after a INVITE is sent (update)

    - cleaned up which method is to be used if there is no dialog
      existing (message)

    - removed use of reINVITE to convey location

    - clarified that UAs include <provided-by> element of PIDF-LO when
      placing an emergency call (to inform ERC who supplied Location
      information)

    - updated list of open issues

    - added to IANA Considerations section for the two new 4XX level
      error responses requested in the last meeting

I've requested time at the meeting already - and would appreciate comments 
to this list

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


